Andy Green has worked on a set of patches adding many features to OMAP4 such as HDMI audio/video, FM receiver, etc. Before I merge that into the Linaro kernel tree I need some assurance that this won't break existing OMAP3 support, especially video. The branch is available in the linux-linaro-2.6.38 Git repository on git.linaro.org, in the "testing" branch.
So please if you have an OMAP3 board and can perform some testing that would be appreciated.
Nicolas
Nicolas, Andy:
I noticed this commit:
This introduces a defconfig version of Sebastien Jan's reference config for Panda.
To use the defconfig, you need to use the following scheme to expand it back to being a full config
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig >>.config make ARCH=arm oldnoconfig
From Seb Jan about the original reference config -->
Note on OMAP3 based boards: Deactivate OMAP3 based boards since their support has not been integrated (some boards would not build). Keep OMAP3 and ARCH_3430 because OMAP4 support is not yet properly supported by configuration and dependencies (ex: v4l2, DSI)
Does that mean that with this tree we cannot have a single omap[34] kernel?
Thanks, John
On Wed, Apr 20, 2011 at 11:58 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
Andy Green has worked on a set of patches adding many features to OMAP4 such as HDMI audio/video, FM receiver, etc. Before I merge that into the Linaro kernel tree I need some assurance that this won't break existing OMAP3 support, especially video. The branch is available in the linux-linaro-2.6.38 Git repository on git.linaro.org, in the "testing" branch.
So please if you have an OMAP3 board and can perform some testing that would be appreciated.
Nicolas
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Wed, Apr 20, 2011 at 5:20 PM, John Rigby john.rigby@linaro.org wrote:
Nicolas, Andy:
I noticed this commit:
This introduces a defconfig version of Sebastien Jan's reference config for Panda.
To use the defconfig, you need to use the following scheme to expand it back to being a full config
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig >>.config make ARCH=arm oldnoconfig
From Seb Jan about the original reference config -->
Note on OMAP3 based boards: Deactivate OMAP3 based boards since their support has not been integrated (some boards would not build).
Which omap3 boards aren't building? your 2.6.38 is pretty close to 2.6.39 right?
Keep OMAP3 and ARCH_3430 because OMAP4 support is not yet properly supported by configuration and dependencies (ex: v4l2, DSI)
Does that mean that with this tree we cannot have a single omap[34] kernel?
Thanks, John
On Wed, Apr 20, 2011 at 11:58 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
Andy Green has worked on a set of patches adding many features to OMAP4 such as HDMI audio/video, FM receiver, etc. Before I merge that into the Linaro kernel tree I need some assurance that this won't break existing OMAP3 support, especially video. The branch is available in the linux-linaro-2.6.38 Git repository on git.linaro.org, in the "testing" branch.
So please if you have an OMAP3 board and can perform some testing that would be appreciated.
Nicolas
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 04/20/2011 11:20 PM, Somebody in the thread at some point said:
Hi -
I noticed this commit:
This introduces a defconfig version of Sebastien Jan's reference config for Panda.
To use the defconfig, you need to use the following scheme to expand it back to being a full config
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfig
From Seb Jan about the original reference config -->
Note on OMAP3 based boards: Deactivate OMAP3 based boards since their support has not been integrated (some boards would not build). Keep OMAP3 and ARCH_3430 because OMAP4 support is not yet properly supported by configuration and dependencies (ex: v4l2, DSI)
Does that mean that with this tree we cannot have a single omap[34] kernel?
No you can build the combined kernel OK now. In this commit -->
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git%3Ba=patch%3B...
I enabled overo, pandora, beagle, zoom, igep0020 in the defconfig and it built OK. I updated Seb's defconfig commit to use this new differential defconfig stuff recommended by npitre (and document how to unpack it since it wasn't obvious) but thought I had better leave his original status in the commit log until it's confirmed it actually works or not on OMAP3 not just builds now.
I have a Beagle XM, but l-m-c breaks here writing to a real SD card and the alternative method (3G image) takes several hours from the ubuntu vm I am running it from. I plan to meddle with that some more today.
-Andy
On Thu, Apr 21, 2011 at 2:29 AM, Andy Green andy@warmcat.com wrote:
On 04/20/2011 11:20 PM, Somebody in the thread at some point said:
Hi -
I noticed this commit:
This introduces a defconfig version of Sebastien Jan's reference config for Panda.
To use the defconfig, you need to use the following scheme to expand it back to being a full config
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfig
From Seb Jan about the original reference config -->
Note on OMAP3 based boards: Deactivate OMAP3 based boards since their support has not been integrated (some boards would not build). Keep OMAP3 and ARCH_3430 because OMAP4 support is not yet properly supported by configuration and dependencies (ex: v4l2, DSI)
Does that mean that with this tree we cannot have a single omap[34] kernel?
No you can build the combined kernel OK now. In this commit -->
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git%3Ba=patch%3B...
I enabled overo, pandora, beagle, zoom, igep0020 in the defconfig and it built OK. I updated Seb's defconfig commit to use this new differential defconfig stuff recommended by npitre (and document how to unpack it since it wasn't obvious) but thought I had better leave his original status in the commit log until it's confirmed it actually works or not on OMAP3 not just builds now.
I have a Beagle XM, but l-m-c breaks here writing to a real SD card and the alternative method (3G image) takes several hours from the ubuntu vm I am running it from. I plan to meddle with that some more today.
What is l-m-c? What is the 3G image method?
-Andy
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On 04/21/2011 05:07 PM, Somebody in the thread at some point said:
Hi -
I have a Beagle XM, but l-m-c breaks here writing to a real SD card and the alternative method (3G image) takes several hours from the ubuntu vm I am running it from. I plan to meddle with that some more today.
What is l-m-c? What is the 3G image method?
linaro-media-create. It's used to bind linaro hardware packs to a rootfs tarball. The alternative method is to have it create a big image file to disk, in this case a 3GByte image file, and dd that on to the SD Card.
-Andy
On 04/21/2011 10:20 AM, Andy Green wrote:
On 04/21/2011 05:07 PM, Somebody in the thread at some point said:
Hi -
I have a Beagle XM, but l-m-c breaks here writing to a real SD card and the alternative method (3G image) takes several hours from the ubuntu vm I am running it from. I plan to meddle with that some more today.
What is l-m-c? What is the 3G image method?
linaro-media-create. It's used to bind linaro hardware packs to a rootfs tarball. The alternative method is to have it create a big image file to disk, in this case a 3GByte image file, and dd that on to the SD Card.
Hi Jason,
If you'd like more information about l-m-c, there is a brief "how to" at:
https://wiki.linaro.org/Resources/HowTo/L-M-C
--Matt
-Andy
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 21 April 2011 19:36, Matt Waddel matt.waddel@canonical.com wrote:
On 04/21/2011 10:20 AM, Andy Green wrote:
linaro-media-create. It's used to bind linaro hardware packs to a rootfs tarball. The alternative method is to have it create a big image file to disk, in this case a 3GByte image file, and dd that on to the SD Card.
If you'd like more information about l-m-c, there is a brief "how to" at:
Certainly very brief.. While it works for testing hwpacks and rootfs's already created, the next obvious steps "howto to try my own kernel" or "how to add my own package to rootfs" are kinda missing.
Riku
On 04/22/2011 07:41 AM, Riku Voipio wrote:
On 21 April 2011 19:36, Matt Waddel matt.waddel@canonical.com wrote:
On 04/21/2011 10:20 AM, Andy Green wrote:
linaro-media-create. It's used to bind linaro hardware packs to a rootfs tarball. The alternative method is to have it create a big image file to disk, in this case a 3GByte image file, and dd that on to the SD Card.
If you'd like more information about l-m-c, there is a brief "how to" at:
Certainly very brief.. While it works for testing hwpacks and rootfs's already created, the next obvious steps "howto to try my own kernel" or "how to add my own package to rootfs" are kinda missing.
Hi Riku,
Correct, that page is brief. Allow me put in a plug for the whole HowTo site here:
https://wiki.linaro.org/Resources/HowTo
There are pages with more detail on adding hardware/packages to l-m-c. A couple that might be useful are:
https://wiki.linaro.org/Resources/HowTo/AddingNewHardwareSupport https://wiki.linaro.org/Platform/DevPlatform/ComponentReleasesWithBzr
If there is a specific HowTo that you feel is missing, let me know and we would be happy add it.
--Matt
Riku
On Thu, 21 Apr 2011, Andy Green wrote:
On 04/20/2011 11:20 PM, Somebody in the thread at some point said:
Hi -
I noticed this commit:
This introduces a defconfig version of Sebastien Jan's reference config for Panda.
To use the defconfig, you need to use the following scheme to expand it back to being a full config
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfig
[...]
No you can build the combined kernel OK now. In this commit -->
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git%3Ba=patch%3B...
I enabled overo, pandora, beagle, zoom, igep0020 in the defconfig and it built OK. I updated Seb's defconfig commit to use this new differential defconfig stuff recommended by npitre (and document how to unpack it since it wasn't obvious) but thought I had better leave his original status in the commit log until it's confirmed it actually works or not on OMAP3 not just builds now.
Still... what's wrong with simply doing:
make omap4_defconfig
and be done with it?
Nicolas
On 04/21/2011 07:08 PM, Somebody in the thread at some point said:
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfig
make omap4_defconfig
Wow that is a lot simpler... if you know it.
When trying to figure this out I googled the original patch that added the savedefconfig and it doesn't mention this Makefile magic; I guess it was added later.
In the meanwhile, I guess I learned something about conifg merging by hand.
-Andy
On Thu, 21 Apr 2011, Andy Green wrote:
On 04/21/2011 07:08 PM, Somebody in the thread at some point said:
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfig
make omap4_defconfig
Wow that is a lot simpler... if you know it.
When trying to figure this out I googled the original patch that added the savedefconfig and it doesn't mention this Makefile magic; I guess it was added later.
In fact, this has been there almost forever. The rule is in scripts/kconfig/Makefile on line 354.
There are a lot of nice Make targets available. Just try "make help".
Nicolas
On 04/21/2011 07:47 PM, Somebody in the thread at some point said:
On Thu, 21 Apr 2011, Andy Green wrote:
On 04/21/2011 07:08 PM, Somebody in the thread at some point said:
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfigmake omap4_defconfig
Wow that is a lot simpler... if you know it.
When trying to figure this out I googled the original patch that added the savedefconfig and it doesn't mention this Makefile magic; I guess it was added later.
In fact, this has been there almost forever. The rule is in scripts/kconfig/Makefile on line 354.
Still, the fact is before you can just copy a whole config from arch/arm/configs to be .config and vice-versa which has been my usage pattern. Now with these optimized defconfigs, that doesn't work; it doesn't hurt to document how to use the new way (even better with your make target method). It's possible I'm the only guy who missed the day at school where they talked about arbitrary defconfig targets in Makefile but I doubt it.
There are a lot of nice Make targets available. Just try "make help".
For some years I used O= in my build scripts because when building multiple targets from the same tree continuously it can be a nice timesaver. Likewise I use sparse and so on from there. I agree there are lots of nice Make targets in there.
-Andy
On Fri, 22 Apr 2011, Andy Green wrote:
On 04/21/2011 07:47 PM, Somebody in the thread at some point said:
On Thu, 21 Apr 2011, Andy Green wrote:
On 04/21/2011 07:08 PM, Somebody in the thread at some point said:
make ARCH=arm defconfig cat arch/arm/configs/omap4_defconfig>>.config make ARCH=arm oldnoconfigmake omap4_defconfig
Wow that is a lot simpler... if you know it.
When trying to figure this out I googled the original patch that added the savedefconfig and it doesn't mention this Makefile magic; I guess it was added later.
In fact, this has been there almost forever. The rule is in scripts/kconfig/Makefile on line 354.
Still, the fact is before you can just copy a whole config from arch/arm/configs to be .config and vice-versa which has been my usage pattern. Now with these optimized defconfigs, that doesn't work; it doesn't hurt to document how to use the new way (even better with your make target method).
Sure. And you can still copy arch/arm/configs/foo_defconfig to .config and it should work (maybe a "make oldconfig" needed not to be prompted for all missing options). But "make foo_defconfig" is shorter.
It's possible I'm the only guy who missed the day at school where they talked about arbitrary defconfig targets in Makefile but I doubt it.
Well, most people are not aware of those goodies, so don't feel ashamed. I'm sure you weren't alone at the beach that day. ;-)
Nicolas
On 04/22/2011 02:50 PM, Somebody in the thread at some point said:
Hi -
Still, the fact is before you can just copy a whole config from arch/arm/configs to be .config and vice-versa which has been my usage pattern. Now with these optimized defconfigs, that doesn't work; it doesn't hurt to document how to use the new way (even better with your make target method).
Sure. And you can still copy arch/arm/configs/foo_defconfig to .config and it should work (maybe a "make oldconfig" needed not to be prompted
My build scripts among other things do a silentoldconfig every time before the main build, that is not enough anyway to use it directly. Otherwise I wouldn't've noticed there was any issue.
for all missing options). But "make foo_defconfig" is shorter.
It's possible I'm the only guy who missed the day at school where they talked about arbitrary defconfig targets in Makefile but I doubt it.
Well, most people are not aware of those goodies, so don't feel ashamed. I'm sure you weren't alone at the beach that day. ;-)
Sure, I appreciate your telling me and everyone else on the lists that it existed.
-Andy
Is the plan to include the "testing" branch for this cycle?
On Wed, Apr 20, 2011 at 11:58 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
Andy Green has worked on a set of patches adding many features to OMAP4 such as HDMI audio/video, FM receiver, etc. Before I merge that into the Linaro kernel tree I need some assurance that this won't break existing OMAP3 support, especially video. The branch is available in the linux-linaro-2.6.38 Git repository on git.linaro.org, in the "testing" branch.
So please if you have an OMAP3 board and can perform some testing that would be appreciated.
Nicolas
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Wed, 27 Apr 2011, John Rigby wrote:
Is the plan to include the "testing" branch for this cycle?
I'd like to have confirmation that it doesn't break OMAP3 first. The OMAP4 support in that branch comes from sources that have expressed in the past that OMAP3 could be broken as a result.
Nicolas
Thanks to Ricardo I have created a packaged version of a merge of the master and testing branches.
http://git.linaro.org/gitweb?p=people/jcrigby/linux-linaro-packaged-next-wip...
the bare kernel plus some fixes are in the "panda_no_packaging" the "master" branch has normal packaging added.
It currently has no video on omap3.
John
On Wed, Apr 27, 2011 at 8:42 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
On Wed, 27 Apr 2011, John Rigby wrote:
Is the plan to include the "testing" branch for this cycle?
I'd like to have confirmation that it doesn't break OMAP3 first. The OMAP4 support in that branch comes from sources that have expressed in the past that OMAP3 could be broken as a result.
Nicolas
linaro-kernel@lists.linaro.org
-
Andy Green -
Jason Kridner -
John Rigby -
Matt Waddel -
Nicolas Pitre -
Riku Voipio -
Robert Nelson