hi all,
HiKey will support Ubuntu, Debian and Fedora systerm and so on for estuary.
visit:http://open-estuary.com/
You try Estuary for HiKey and if you meet testing problem, we will improve it. First, here is what you did:
mkdir ~/work/open-estuary cd ~/work/open-estuary repo init -u https://github.com/open-estuary/estuary.git repo sync cd estuary ./build.sh -p HiKey -d Ubuntu
Thank you xinwei
It sounds great!
On 20 November 2015 at 14:37, Xinwei Kong kong.kongxinwei@hisilicon.com wrote:
hi all,
HiKey will support Ubuntu, Debian and Fedora systerm and so on for estuary.
visit:http://open-estuary.com/
You try Estuary for HiKey and if you meet testing problem, we will improve it. First, here is what you did:
mkdir ~/work/open-estuary cd ~/work/open-estuary repo init -u https://github.com/open-estuary/estuary.git repo sync cd estuary ./build.sh -p HiKey -d Ubuntu
Thank you xinwei
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
On 11/20/2015 06:37 AM, Xinwei Kong wrote:
hi all,
HiKey will support Ubuntu, Debian and Fedora systerm and so on for estuary.
visit:http://open-estuary.com/
I've looked at that page and am confused as to _what_ actually this open estuary is? The architecture diagram implies it is a whole Linux distribution. I've read the goals and I'm still none the wiser. It even forks the Linux kernel, boot loaders, etc. Why?
Cheers
Thomas
hi Thomas
On 2015/11/20 17:48, Thomas B. Rücker wrote:
On 11/20/2015 06:37 AM, Xinwei Kong wrote:
hi all,
HiKey will support Ubuntu, Debian and Fedora systerm and so on for estuary.
visit:http://open-estuary.com/
I've looked at that page and am confused as to _what_ actually this open estuary is? The architecture diagram implies it is a whole Linux distribution. I've read the goals and I'm still none the wiser. It even forks the Linux kernel, boot loaders, etc. Why?
Estuary is a complete open source solution for ARM based systems for ICT domain. It can provide you a quick launch pad to start with ARM Server Solution!
Thank you xinwei
Cheers
Thomas
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
On 20 November 2015 at 06:37, Xinwei Kong kong.kongxinwei@hisilicon.com wrote:
hi all,
HiKey will support Ubuntu, Debian and Fedora systerm and so on for estuary.
visit:http://open-estuary.com/
Hi, We really need all the 96boards to be fully supported in the upstream Linux kernel, not vendor trees. I appreciate that it takes a lot of effort to get code upstream, but the benefit is that *all* the interested distros (i.e. the ones we may not be working with directly) can then more easily support the boards once they are in the kernel. Also, the stability and performance of the board can improve due to wider peer review of the code and the effective lifetime of the board can be increased as potentially breaking code changes can be spotted in tree.
I have been unable to do any meaningful work with my Hikey board because I haven't been able to work with a mainline kernel on it. Hopefully this will soon improve.
Cheers, -- Steve
On 23 November 2015 at 21:14, Steve Capper steve.capper@linaro.org wrote:
On 20 November 2015 at 06:37, Xinwei Kong kong.kongxinwei@hisilicon.com wrote:
hi all,
HiKey will support Ubuntu, Debian and Fedora systerm and so on for
estuary.
visit:http://open-estuary.com/
Hi, We really need all the 96boards to be fully supported in the upstream Linux kernel, not vendor trees. I appreciate that it takes a lot of effort to get code upstream,
We are on it. You should see more in v4.4, v4.5. for HiKey/Hi6220 SoC.
but the benefit is that *all* the interested distros (i.e. the ones we may not be working with directly) can then more easily support the boards once they are in the kernel. Also, the stability and performance of the board can improve due to wider peer review of the code and the effective lifetime of the board can be increased as potentially breaking code changes can be spotted in tree.
I have been unable to do any meaningful work with my Hikey board because I haven't been able to work with a mainline kernel on it. Hopefully this will soon improve.
We have a hikey mainline branch now. It based on v4.3, plus several topics which are not accepted yet.
https://github.com/96boards/linux/tree/hikey-mainline-rebase
This is a rebase tree, with tracking mainline as its target.
And yes, you reminded me that I should send emails to this list when I got new features in hikey-mainline-rebase.
-Guodong Tech Lead, Linaro HiSilicon Landing Team
Cheers,
Steve _______________________________________________ Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
Hi,
On Tue, 2015-11-24 at 00:03 +0800, Guodong Xu wrote:
On 23 November 2015 at 21:14, Steve Capper steve.capper@linaro.org wrote:
I have been unable to do any meaningful work with my Hikey board because I haven't been able to work with a mainline kernel on it. Hopefully this will soon improve.
We have a hikey mainline branch now. It based on v4.3, plus several topics which are not accepted yet.
https://github.com/96boards/linux/tree/hikey-mainline-rebase
This is a rebase tree, with tracking mainline as its target.
When developers talk of mainline or upstream, they generally mean the latest unstable, not what was the unstable a month ago.
This hikey-mainline-rebase is worthless to me and anyone else trying to develop kernel code because we are working against 4.4.
-Geoff
On 02/12/15 20:27, Geoff Levand wrote:
Hi,
On Tue, 2015-11-24 at 00:03 +0800, Guodong Xu wrote:
On 23 November 2015 at 21:14, Steve Capper steve.capper@linaro.org wrote:
I have been unable to do any meaningful work with my Hikey board because I haven't been able to work with a mainline kernel on it. Hopefully this will soon improve.
We have a hikey mainline branch now. It based on v4.3, plus several topics which are not accepted yet.
https://github.com/96boards/linux/tree/hikey-mainline-rebase
This is a rebase tree, with tracking mainline as its target.
When developers talk of mainline or upstream, they generally mean the latest unstable, not what was the unstable a month ago.
This hikey-mainline-rebase is worthless to me and anyone else trying to develop kernel code because we are working against 4.4.
It would be potentially useful if the the rebase branch were updated as soon as possible after X.YY-rc1 is released.
Tracking X.YY-rc2 through X.YY-rc7 is helpful but much less critical since it should be fairly easy for other developers to rebase between members of the X.YY family when they need to.
Working on top of rebase kernels is clearly still second best to working on the mainline but, nevertheless, when the hardware has compelling advantages it is much more comfortable if the focus of the rebase tree is -rc1.
Daniel.
On Fri, Dec 4, 2015 at 4:47 PM, Daniel Thompson daniel.thompson@linaro.org wrote:
On 02/12/15 20:27, Geoff Levand wrote:
Hi,
On Tue, 2015-11-24 at 00:03 +0800, Guodong Xu wrote:
On 23 November 2015 at 21:14, Steve Capper steve.capper@linaro.org wrote:
I have been unable to do any meaningful work with my Hikey board because I haven't been able to work with a mainline kernel on it. Hopefully this will soon improve.
We have a hikey mainline branch now. It based on v4.3, plus several topics which are not accepted yet.
https://github.com/96boards/linux/tree/hikey-mainline-rebase
This is a rebase tree, with tracking mainline as its target.
When developers talk of mainline or upstream, they generally mean the latest unstable, not what was the unstable a month ago.
This hikey-mainline-rebase is worthless to me and anyone else trying to develop kernel code because we are working against 4.4.
It would be potentially useful if the the rebase branch were updated as soon as possible after X.YY-rc1 is released.
Tracking X.YY-rc2 through X.YY-rc7 is helpful but much less critical since it should be fairly easy for other developers to rebase between members of the X.YY family when they need to.
Working on top of rebase kernels is clearly still second best to working on the mainline but, nevertheless, when the hardware has compelling advantages it is much more comfortable if the focus of the rebase tree is -rc1.
Agreed. IMO, -rc1 and -rc2 bring in the big changes. So updating quickly up to -rc2 is helpful. There is also the hope the the stack of patches being rebased is getting reduced as we go.
On Tue, Nov 24, 2015 at 12:03:55AM +0800, Guodong Xu wrote:
On 23 November 2015 at 21:14, Steve Capper steve.capper@linaro.org wrote:
We really need all the 96boards to be fully supported in the upstream Linux kernel, not vendor trees. I appreciate that it takes a lot of effort to get code upstream,
We are on it. You should see more in v4.4, v4.5. for HiKey/Hi6220 SoC.
Could you point at the specific changes here please? I've just looked at the DT for v4.4 and for -next and I'm not seeing any changes enabling new hardware support in either so presumably I'm missing something.
-
Amit Kucheria -
Daniel Thompson -
Geoff Levand -
Guodong Xu -
Mark Brown -
Steve Capper -
Thomas B. Rücker -
Xinliang Liu -
Xinwei Kong