Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On Fri, Jan 27, 2012 at 12:47 PM, Alexander Sack wrote: > On Wed, Jan 25, 2012 at 9:33 PM, Zygmunt Krynicki > wrote: >> HI. >> >> I'm building a LAVA service for running fast models. Quite soon (*) >> we'll be ready to open an alpha access. Right now you will need to >> bring your own root filesystem and kernel image to use it. With that >> in mind I wanted to start a discussion about the state of A15 support >> in Linaro kernel(s). I need to understand two things: >> >> 1) Are we ready to do automatic builds for A15 kernels? > > We can do builds on ci.linaro.org - as soon as we have a branch/tag of > a public git tree and a defconfig we would be ready to go. Might > require a few minor tweaks if the LAVA job for A15 needs different > input parameters, so if that's the case let Deepti and Danilo know > about the details. It definitely will. There will be a different job specification for simulation targets. I'll send an update when this part becomes ready ZK ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On Wed, Jan 25, 2012 at 9:33 PM, Zygmunt Krynicki wrote: > HI. > > I'm building a LAVA service for running fast models. Quite soon (*) > we'll be ready to open an alpha access. Right now you will need to > bring your own root filesystem and kernel image to use it. With that > in mind I wanted to start a discussion about the state of A15 support > in Linaro kernel(s). I need to understand two things: > > 1) Are we ready to do automatic builds for A15 kernels? We can do builds on ci.linaro.org - as soon as we have a branch/tag of a public git tree and a defconfig we would be ready to go. Might require a few minor tweaks if the LAVA job for A15 needs different input parameters, so if that's the case let Deepti and Danilo know about the details. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On 27 Jan 2012, at 10:33, Pawel Moll wrote: > On Thu, 2012-01-26 at 19:20 +0100, Zygmunt Krynicki wrote: >> It also requires a license from arm for each machine >> that runs it (it binds to mac address) > > This could be mitigated by setting up a Flex licence server for machines > in the farm, with floating licences instead of noded-locked ones. After > all that's what we have internally at ARM - we wouldn't cope with > generating licenses for every single machine here ;-) I have some floating licences, and am intending to put flex on the server farm once I've re-installed and got OpenStack running. Dave ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On 27 January 2012 10:30, Pawel Moll wrote: > I'm planning to modify the boot.S to be able to create an AXF file from > separate kernel and DTB (will happen next week, if anyone wants to try > it let me know and I'll notify you when it's ready) I would suggest you start out with the patches I did to let the model load the kernel and initrd via semihosting: https://lists.cs.columbia.edu/pipermail/android-virt/2012-January/000570.html extending those to also support --dtb would be much more useful and flexible than the make-an-AXF-file approach. -- PMM ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On Thu, 2012-01-26 at 21:19 +0100, Zygmunt Krynicki wrote: > >>> With Pawel Moll's VExpress device tree support patches on top of > >>> mainline, we can produce a single kernel config and a set of device > >>> trees which allow booting on all the A15-based model variants. > > About device trees, does the simulator need an explicitly provided > device tree (in a way we currently provide the kernel image and > ramdisk) or is the dt table built into the image? Currently the simplest way of booting a DT kernel on a model is to use the CONFIG_ARM_APPENDED_DTB=y and CONFIG_ARM_ATAG_DTB_COMPAT=y and simply feed the model with concatenated zImage+DTB. Tested last night. One hint: do _not_ use earlyprintk on models - current version of DEBUG_LL in my DT4VE patches can fail in such case. I'm planning to modify the boot.S to be able to create an AXF file from separate kernel and DTB (will happen next week, if anyone wants to try it let me know and I'll notify you when it's ready), but the long term (hopefully next FM release, mid-this-year) plan is to teach the model environment about Linux and DT so no wrapper would be necessary at all. Cheers! Paweł ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On 26 January 2012 20:19, Zygmunt Krynicki wrote: > About device trees, does the simulator need an explicitly provided > device tree (in a way we currently provide the kernel image and > ramdisk) or is the dt table built into the image? The simulator doesn't care whether you're using device tree or not, it is merely emulating a CPU. The boot-wrapper code currently does not support passing a device tree blob in, so you'll need to use the kernel config option to support appending the device tree to the uImage, or alternatively not use a device tree at all. The bootwrapper could probably be enhanced to be device-tree aware; I was talking to Dave about this the other day. -- PMM ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Linaro-validation] Linaro kernel tree for A15 for daily builds
On Thu, Jan 26, 2012 at 8:52 PM, Ryan Harkin wrote: > On 26 January 2012 19:34, Scott Bambrough wrote: >> On 12-01-26 01:24 PM, Dave Martin wrote: >>> >>> On Wed, Jan 25, 2012 at 09:33:35PM +0100, Zygmunt Krynicki wrote: HI. I'm building a LAVA service for running fast models. Quite soon (*) we'll be ready to open an alpha access. Right now you will need to bring your own root filesystem and kernel image to use it. With that in mind I wanted to start a discussion about the state of A15 support in Linaro kernel(s). I need to understand two things: 1) Are we ready to do automatic builds for A15 kernels? 2) If so, which configs and trees should we consider >>> >>> >>> The basic A15 CPU support is upstream, but no board support. >>> >>> The board support emulation on the model is for obscure reasons not >>> exactly the same as a real VExpress, but it's pretty close. >>> >>> With Pawel Moll's VExpress device tree support patches on top of >>> mainline, we can produce a single kernel config and a set of device >>> trees which allow booting on all the A15-based model variants. About device trees, does the simulator need an explicitly provided device tree (in a way we currently provide the kernel image and ramdisk) or is the dt table built into the image? >>> >>> I'll be pushing a tree onto git.linaro.org soon with that stuff. >> >> >> Why don't you push the changes to the ARM LT and let them manage pushing the >> tree out. Then we can maintain it and take the burden off of you. I suspect >> you will be rather busy. > > Indeed, my tree is already hosting your (dmart's) AMBA Device > Discovery fixes and Pawel's Device Tree additions, so placing your A15 > model stuff on top is not a problem for me. > > Here's our current working tree: > http://git.linaro.org/gitweb?p=landing-teams/working/arm/kernel.git;a=summary > > This is already booting real A15 Versatile Express hardware, so we're > part the way there already. > > R. > > ___ > linaro-validation mailing list > linaro-validat...@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-validation ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
