Re: [OE-core] [PATCH 0/4] kernel-yocto: consolidated pull request
On Fri, May 31, 2013 at 3:07 AM, Richard Purdie wrote: > On Fri, 2013-05-31 at 15:14 +0900, Saul Wold wrote: >> On 05/31/2013 12:28 PM, Bruce Ashfield wrote: >> > Richard/Saul, >> > >> > While I continue to battle with gcc 4.8, I've got a collection of other >> > fixes >> > that don't need to wait. Here's part of those pending changes. >> > >> > - Remove the yocto 3.2 kernel, early in the Yocto 1.5 cycle as promised >> >> Did I miss a request to remove the .bbappend from meta-yocto-bsp? There >> seems to be a 3.2 bbappend still. > > In the interests of getting roughly caught up with patches, I've added a > patch to delete this as well... Argh. yes. That's sitting on my oe-core branch and I managed to not send it out. Thanks for fixing it up. Bruce > > Cheers, > > Richard > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] adding kernel headers to sysroot
On 13-06-02 10:30 AM, Koen Martens wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bruce, On Thu, May 16, 2013 at 11:41:20AM -0400, Bruce Ashfield wrote: On 13-05-16 11:25 AM, Koen Martens wrote: I have added a kernel header file to the linux kernel for my project, that exposes a public API for new kernel functionality I have implemented. This header file is needed to compile certain user-space programs. I have been trying to get this include file in the sysroot used to compile the user- space programs (as well as in the SDK i build for the project). - point your application at the STAGING_KERNEL_DIR and include the header from there. You are already coupled to the kernel, since you need this header, so it isn't as evil as it seems. This will also get you SDK support. - Install the header file to another location in the sysroot and include it from there. You can do this via an append to the kernel install. Assuming you don't collide with existing headers, you could use this to install into a standard location as well, but things start to get a bit more risk. You can also arrange I went with the latter option, but i'm still curious as to what part of oe magic installs the standard kernel headers? That's the linux-libc-headers package. It uses the matching linux release tarball and installs them to the /usr/include/linux directory structure. And good choice on the latter option. I've been working with this more myself lately, and if you attempt to install over top of the libc-headers location, you'll end up with package ordering issues if you use the SDK, and in general, not be triggering the right rebuilds when things change. Bruce How often does the header file change ? If it really is static there's another option, and that is to capture the header in the applications themselves and simply use it that way. iptables, and other user application have done this in the past, and will do it again in the future. Yep, i'm aware of the way ipfilter does it, from personal experience with the insanity that causes :) Thanks! Koen - -- https://ohm2013.org/- outdoor hacker conference, August 2013, NL http://www.sonologic.nl/- hosting and DBA http://koenmartens.nl/ - curriculum vitae https://www.revspace.nl/- hackerspace in Den Haag, NL http://signal.hackerspaces.org/ - hackerspace radio -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGrVw8ACgkQktDgRrkFPpa0rQCfWUXPWJEUKKn5Ngc8MOdSzlt+ clcAoIoGA7jIiVBvZXQz2MpiXHD6/6Tj =zYrm -END PGP SIGNATURE- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Linux kernel build dependency of 'bc'
On Thu, Jun 6, 2013 at 11:11 AM, Otavio Salvador wrote: > Hello Bruce, > > I got a build failure in my auto builder; it has a very lean system install > and it spot something it is new for me. It seems the kernel now depends on > 'bc' util. > > I tried to find a 'bc-native' and couldn't find so I'd like to know if it > is a known issue and if someone is already working in a 'bc-native' recipe > to proper fix the issue. Following up on this thread late (I was on a plane all day), this hasn't popped up on my builders, but then again, all of mine have bc, so I wouldn't have noticed for some time. If nothing has been entered bugzilla for this, we should do that now, just to avoid more than one person going ahead and adding bc-native! Bruce > > Regards, > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://projetos.ossystems.com.br > Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] cramfs: import recipe from meta-oe
On Tue, Jun 11, 2013 at 11:41 AM, Andrea Adami wrote:
> On Tue, Jun 11, 2013 at 4:22 PM, Saul Wold wrote:
>> On 06/11/2013 07:14 AM, Andrea Adami wrote:
>>>
>>> ping
>>>
>>> Maybe you want cramfs in recipes-devtools and not in recipes-support?
>>> Feedback, please
>>>
>> Apologies, we will not accept this recipe being moved into oe-core, there is
>> not a strong case to move it to oe-core, cramfs is a image
>> type that is not heavily used, and the recipe is available in meta-oe.
>>
> Saul,
>
> See... the 'not heavily used' is always relative: there are still
> many devices out in the wild with cramfs 'firmwares'.
>
> You're missing my first point: I/we aim to have as less layer
> interdependency as possible (oe-core + BSP) so having to add meta-oe
> is just an unneeded burden for most cases.
I have a similar use case with BSPs and deployment methods. I missed
the start of the thread, but thought the idea of moving this into oe-core
along side the other image types was a good idea. I personally don't see
a big issue or burden with moving it into the base since to me, that's where
image types and formats belong.
Cheers,
Bruce
> Oh, and it would be one recipe less in that meta-oe pot.
>
> Thx for your review
>
> Cheers
> Andrea
>
>> Sau!
>>
>>> Andrea
>>>
>>> On Tue, Jun 4, 2013 at 1:51 PM, Andrea Adami
>>> wrote:
Note there would be also the possibility to use the mkfs.cramfs
provided by util-linux implementing changes in image_types.bbclass and
util-linux itself.
Seems a bit overkill to me but still an option...
Andrea
On Tue, Jun 4, 2013 at 1:39 PM, Andrea Adami
wrote:
>
> ping
>
> Recipe is rather stable (tarball of v.1.1 dated 2002) and cramfs can
> be handy for read-only images on legacy devices.
>
> All the needed infrastructure is already present in
> image_types.bbclass so I'd say this recipe has been mistakenly
> forgotten when splitting out oe-core
>
>
> Andrea
>
> On Sun, May 26, 2013 at 1:23 AM, Andrea Adami
> wrote:
>>
>> * though listed in IMAGE_FSTYPES the helper is missing so
>> * make oe-core autosufficient importing the recipe.
>> * Fix PN -> BPN to avoid fetch errors with cramfs-native
>>
>> Signed-off-by: Andrea Adami
>> ---
>> meta/recipes-support/cramfs/cramfs_1.1.bb | 29
>> +
>> 1 file changed, 29 insertions(+)
>> create mode 100644 meta/recipes-support/cramfs/cramfs_1.1.bb
>>
>> diff --git a/meta/recipes-support/cramfs/cramfs_1.1.bb
>> b/meta/recipes-support/cramfs/cramfs_1.1.bb
>> new file mode 100644
>> index 000..0bca0e1
>> --- /dev/null
>> +++ b/meta/recipes-support/cramfs/cramfs_1.1.bb
>> @@ -0,0 +1,29 @@
>> +DESCRIPTION = "Builds cramfs filesystems for embedded systems"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM =
>> "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
>> +DEPENDS = "zlib"
>> +
>> +PE = "1"
>> +
>> +SRC_URI =
>> "http://sourceforge.net/projects/cramfs/files/cramfs/1.1/${BPN}-${PV}.tar.gz";
>> +
>> +SRC_URI[md5sum] = "d3912b9f7bf745fbfea68f6a9b9de30f"
>> +SRC_URI[sha256sum] =
>> "133caca2c4e7c64106555154ee0ff693f5cf5beb9421ce2eb86baee997d22368"
>> +
>> +EXTRA_OEMAKE = "\
>> +'CC=${CC}' \
>> +'CFLAGS=${CFLAGS}' \
>> +'LDFLAGS=${LDFLAGS}' \
>> +"
>> +
>> +do_compile_prepend() {
>> +ln -sf GNUmakefile Makefile
>> +}
>> +
>> +do_install() {
>> +install -d ${D}${bindir}
>> +install mkcramfs ${D}${bindir}
>> +install cramfsck ${D}${bindir}
>> +}
>> +
>> +BBCLASSEXTEND = "native"
>> --
>> 1.8.1.5
>>
>>> ___
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>>
>>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Fix for kernel 3.8/gcc-4.8 segfault on qemuarm
On 13-06-17 11:30 PM, Khem Raj wrote: Hi Bruce and All Finally after a long innings I have diagnosed the mystery behind the below segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't show when compiled with gcc 4.7 Unable to handle kernel paging request at virtual address pgd = c0004000 [] *pgd=07ffe831, *pte=, *ppte= Internal error: Oops: 17 [#1] PREEMPT ARM Modules linked in: CPU: 0Not tainted (3.8.0-yocto-standard+ #32) PC is at kmem_cache_alloc+0x38/0x154 LR is at subsys_system_register+0x34/0xd8 pc : []lr : []psr: a153 sp : c7835ef0 ip : c7904590 fp : r10: c0688dc4 r9 : c06db900 r8 : c0327244 r7 : r6 : 80d0 r5 : c7801380 r4 : r3 : r2 : 0078 r1 : 80d0 r0 : c7801380 Flags: NzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment kernel Control: 00093177 Table: 4000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc78341b8) Stack: (0xc7835ef0 to 0xc7836000) 5ee0: c06a5564 c06b8b8c c7834028 5f00: c0680218 c0327244 c7835f28 c06a5564 0006 c7834028 c06db900 c0688dd4 5f20: c7835f28 c00089a0 c0657f44 0006 c086e561 0006 c06a5534 5f40: c06a5564 0006 c06db900 c0680218 c069fd68 008e c069fd5c c0680924 5f60: 0006 0006 c0680218 5f80: c04f5e68 c04f5e70 5fa0: c04f5e68 c000deb0 5fc0: 5fe0: 0013 [] (kmem_cache_alloc+0x38/0x154) from [] (subsys_system_register+0x34/0xd8) [] (subsys_system_register+0x34/0xd8) from [] (init_clocksource_sysfs+0x10/0x54) [] (init_clocksource_sysfs+0x10/0x54) from [] (do_one_initcall+0x10c/0x17c) [] (do_one_initcall+0x10c/0x17c) from [] (kernel_init_freeable+0x164/0x224) [] (kernel_init_freeable+0x164/0x224) from [] (kernel_init+0x8/0x150) [] (kernel_init+0x8/0x150) from [] (ret_from_fork+0x14/0x24) Code: e5934000 e354 0a1a e5953014 (e7941003) ---[ end trace f4d187650e17fc5c ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b Please apply the patch below to linux-yocto-3.8 http://sakrah.dontexist.org/files/patches/0001-ARM-7668-1-fix-memset-related-crashes-caused-by-rece.patch This is a back port from 3.9 therefore safe. The problem is not limited to linux-yocto it also impacts upstream 3.8 stable but 3.8 stable is end of life so why bother. If linux-yocto upgrades to 3.9 or 3.10 and drops 3.8 in 1.5 then we are ok too. That's interesting. I got the same crash on linux-yocto-dev, so I kept debugging here. Did linux-yocto-dev boot out of the box for you with gcc 4.8 ? Bruce Let me know how it goes Thanks -Khem ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Fix for kernel 3.8/gcc-4.8 segfault on qemuarm
On 13-06-17 11:30 PM, Khem Raj wrote:
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behind the below
segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't show
when compiled with gcc 4.7
There also seems to be a follow up patch:
commit 418df63adac56841ef6b0f1fcf435bc64d4ed177
Author: Nicolas Pitre
Date: Tue Mar 12 13:00:42 2013 +0100
ARM: 7670/1: fix the memset fix
Commit 455bd4c430b0 ("ARM: 7668/1: fix memset-related crashes caused by
recent GCC (4.7.2) optimizations") attempted to fix a compliance issue
with the memset return value. However the memset itself became broken
by that patch for misaligned pointers.
This fixes the above by branching over the entry code from the
misaligned fixup code to avoid reloading the original pointer.
Also, because the function entry alignment is wrong in the Thumb mode
compilation, that fixup code is moved to the end.
While at it, the entry instructions are slightly reworked to help dual
issue pipelines.
Signed-off-by: Nicolas Pitre
Tested-by: Alexander Holler
Signed-off-by: Russell King
:100644 100644 d912e73... 94b0650... M arch/arm/lib/memset.S
I've staged it as well, and will do a boot test in the morning once
my build has completed. Time to call it a night here.
Bruce
Unable to handle kernel paging request at virtual address
pgd = c0004000
[] *pgd=07ffe831, *pte=, *ppte=
Internal error: Oops: 17 [#1] PREEMPT ARM
Modules linked in:
CPU: 0Not tainted (3.8.0-yocto-standard+ #32)
PC is at kmem_cache_alloc+0x38/0x154
LR is at subsys_system_register+0x34/0xd8
pc : []lr : []psr: a153
sp : c7835ef0 ip : c7904590 fp :
r10: c0688dc4 r9 : c06db900 r8 : c0327244
r7 : r6 : 80d0 r5 : c7801380 r4 :
r3 : r2 : 0078 r1 : 80d0 r0 : c7801380
Flags: NzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment kernel
Control: 00093177 Table: 4000 DAC: 0017
Process swapper (pid: 1, stack limit = 0xc78341b8)
Stack: (0xc7835ef0 to 0xc7836000)
5ee0: c06a5564 c06b8b8c c7834028
5f00: c0680218 c0327244 c7835f28 c06a5564 0006 c7834028 c06db900 c0688dd4
5f20: c7835f28 c00089a0 c0657f44 0006 c086e561 0006 c06a5534
5f40: c06a5564 0006 c06db900 c0680218 c069fd68 008e c069fd5c c0680924
5f60: 0006 0006 c0680218
5f80: c04f5e68 c04f5e70
5fa0: c04f5e68 c000deb0
5fc0:
5fe0: 0013
[] (kmem_cache_alloc+0x38/0x154) from []
(subsys_system_register+0x34/0xd8)
[] (subsys_system_register+0x34/0xd8) from []
(init_clocksource_sysfs+0x10/0x54)
[] (init_clocksource_sysfs+0x10/0x54) from []
(do_one_initcall+0x10c/0x17c)
[] (do_one_initcall+0x10c/0x17c) from []
(kernel_init_freeable+0x164/0x224)
[] (kernel_init_freeable+0x164/0x224) from []
(kernel_init+0x8/0x150)
[] (kernel_init+0x8/0x150) from [] (ret_from_fork+0x14/0x24)
Code: e5934000 e354 0a1a e5953014 (e7941003)
---[ end trace f4d187650e17fc5c ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b
Please apply the patch below to linux-yocto-3.8
http://sakrah.dontexist.org/files/patches/0001-ARM-7668-1-fix-memset-related-crashes-caused-by-rece.patch
This is a back port from 3.9 therefore safe. The problem is not limited to
linux-yocto it also impacts upstream 3.8 stable
but 3.8 stable is end of life so why bother. If linux-yocto upgrades to 3.9 or
3.10 and drops 3.8 in 1.5 then we are ok too.
Let me know how it goes
Thanks
-Khem
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Fix for kernel 3.8/gcc-4.8 segfault on qemuarm
On 13-06-18 12:41 AM, Khem Raj wrote:
On Jun 17, 2013, at 9:37 PM, Bruce Ashfield
wrote:
On 13-06-17 11:30 PM, Khem Raj wrote:
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behind the below
segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't show
when compiled with gcc 4.7
There also seems to be a follow up patch:
commit 418df63adac56841ef6b0f1fcf435bc64d4ed177
Author: Nicolas Pitre
Date: Tue Mar 12 13:00:42 2013 +0100
ARM: 7670/1: fix the memset fix
Commit 455bd4c430b0 ("ARM: 7668/1: fix memset-related crashes caused by
recent GCC (4.7.2) optimizations") attempted to fix a compliance issue
with the memset return value. However the memset itself became broken
by that patch for misaligned pointers.
This fixes the above by branching over the entry code from the
misaligned fixup code to avoid reloading the original pointer.
Also, because the function entry alignment is wrong in the Thumb mode
compilation, that fixup code is moved to the end.
While at it, the entry instructions are slightly reworked to help dual
issue pipelines.
Signed-off-by: Nicolas Pitre
Tested-by: Alexander Holler
Signed-off-by: Russell King
:100644 100644 d912e73... 94b0650... M arch/arm/lib/memset.S
I've staged it as well, and will do a boot test in the morning once
my build has completed. Time to call it a night here.
I did not need anything other than the first patch to get over the segfault.
but yes it completes the fix
so having both is better
So very strange. I got one segfault, and then this:
Linux version 3.8.13-yocto-standard (bruce@yow-bashfiel-d2) (gcc version
4.8.1 (GCC) ) #2 PREEMPT Tue Jun 18 00:36:55 EDT 2013
qemuarm login: root
root@qemuarm:~# uname -a
Linux qemuarm 3.8.13-yocto-standard #2 PREEMPT Tue Jun 18 00:36:55 EDT
2013 armv5tejl GNU/Linux
Which means I may have just been unlucky on my testing with 3.10, or
something
else is going on.
Regardless, this is progress and I'll do some stress testing here and
get a pull request out to RP in the next day or so.
Bruce
Bruce
Unable to handle kernel paging request at virtual address
pgd = c0004000
[] *pgd=07ffe831, *pte=, *ppte=
Internal error: Oops: 17 [#1] PREEMPT ARM
Modules linked in:
CPU: 0Not tainted (3.8.0-yocto-standard+ #32)
PC is at kmem_cache_alloc+0x38/0x154
LR is at subsys_system_register+0x34/0xd8
pc : []lr : []psr: a153
sp : c7835ef0 ip : c7904590 fp :
r10: c0688dc4 r9 : c06db900 r8 : c0327244
r7 : r6 : 80d0 r5 : c7801380 r4 :
r3 : r2 : 0078 r1 : 80d0 r0 : c7801380
Flags: NzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment kernel
Control: 00093177 Table: 4000 DAC: 0017
Process swapper (pid: 1, stack limit = 0xc78341b8)
Stack: (0xc7835ef0 to 0xc7836000)
5ee0: c06a5564 c06b8b8c c7834028
5f00: c0680218 c0327244 c7835f28 c06a5564 0006 c7834028 c06db900 c0688dd4
5f20: c7835f28 c00089a0 c0657f44 0006 c086e561 0006 c06a5534
5f40: c06a5564 0006 c06db900 c0680218 c069fd68 008e c069fd5c c0680924
5f60: 0006 0006 c0680218
5f80: c04f5e68 c04f5e70
5fa0: c04f5e68 c000deb0
5fc0:
5fe0: 0013
[] (kmem_cache_alloc+0x38/0x154) from []
(subsys_system_register+0x34/0xd8)
[] (subsys_system_register+0x34/0xd8) from []
(init_clocksource_sysfs+0x10/0x54)
[] (init_clocksource_sysfs+0x10/0x54) from []
(do_one_initcall+0x10c/0x17c)
[] (do_one_initcall+0x10c/0x17c) from []
(kernel_init_freeable+0x164/0x224)
[] (kernel_init_freeable+0x164/0x224) from []
(kernel_init+0x8/0x150)
[] (kernel_init+0x8/0x150) from [] (ret_from_fork+0x14/0x24)
Code: e5934000 e354 0a1a e5953014 (e7941003)
---[ end trace f4d187650e17fc5c ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b
Please apply the patch below to linux-yocto-3.8
http://sakrah.dontexist.org/files/patches/0001-ARM-7668-1-fix-memset-related-crashes-caused-by-rece.patch
This is a back port from 3.9 therefore safe. The problem is not limited to
linux-yocto it also impacts upstream 3.8 stable
but 3.8 stable is end of life so why bother. If linux-yocto upgrades to 3.9 or
3.10 and drops 3.8 in 1.5 then we are ok too.
Let me know how it goes
Thanks
-Khem
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Fix for kernel 3.8/gcc-4.8 segfault on qemuarm
On Tue, Jun 18, 2013 at 1:25 AM, Khem Raj wrote:
>
> On Jun 17, 2013, at 9:58 PM, Bruce Ashfield
> wrote:
>
>> On 13-06-18 12:41 AM, Khem Raj wrote:
>>>
>>> On Jun 17, 2013, at 9:37 PM, Bruce Ashfield
>>> wrote:
>>>
>>>> On 13-06-17 11:30 PM, Khem Raj wrote:
>>>>> Hi Bruce and All
>>>>>
>>>>> Finally after a long innings I have diagnosed the mystery behind the
>>>>> below segfault that we see on kernel 3.8 which compiled with gcc 4.8 but
>>>>> don't show when compiled with gcc 4.7
>>>>>
>>>>>
>>>>
>>>> There also seems to be a follow up patch:
>>>>
>>>> commit 418df63adac56841ef6b0f1fcf435bc64d4ed177
>>>> Author: Nicolas Pitre
>>>> Date: Tue Mar 12 13:00:42 2013 +0100
>>>>
>>>>ARM: 7670/1: fix the memset fix
>>>>
>>>>Commit 455bd4c430b0 ("ARM: 7668/1: fix memset-related crashes caused by
>>>>recent GCC (4.7.2) optimizations") attempted to fix a compliance issue
>>>>with the memset return value. However the memset itself became broken
>>>>by that patch for misaligned pointers.
>>>>
>>>>This fixes the above by branching over the entry code from the
>>>>misaligned fixup code to avoid reloading the original pointer.
>>>>
>>>>Also, because the function entry alignment is wrong in the Thumb mode
>>>>compilation, that fixup code is moved to the end.
>>>>
>>>>While at it, the entry instructions are slightly reworked to help dual
>>>>issue pipelines.
>>>>
>>>>Signed-off-by: Nicolas Pitre
>>>>Tested-by: Alexander Holler
>>>>Signed-off-by: Russell King
>>>>
>>>> :100644 100644 d912e73... 94b0650... M arch/arm/lib/memset.S
>>>>
>>>>
>>>>
>>>> I've staged it as well, and will do a boot test in the morning once
>>>> my build has completed. Time to call it a night here.
>>>
>>> I did not need anything other than the first patch to get over the
>>> segfault. but yes it completes the fix
>>> so having both is better
>>
>> So very strange. I got one segfault, and then this:
>>
>> Linux version 3.8.13-yocto-standard (bruce@yow-bashfiel-d2) (gcc version
>> 4.8.1 (GCC) ) #2 PREEMPT Tue Jun 18 00:36:55 EDT 2013
>>
>>
>>
>> qemuarm login: root
>> root@qemuarm:~# uname -a
>> Linux qemuarm 3.8.13-yocto-standard #2 PREEMPT Tue Jun 18 00:36:55 EDT 2013
>> armv5tejl GNU/Linux
>>
>>
>>
>> Which means I may have just been unlucky on my testing with 3.10, or
>> something
>> else is going on.
>
> Well I have been booting latest linus's (3.10-rc6) master compiled with gcc
> 4.8 just one patch from linux-yocto see below
>
Very odd. I would have just done the bisection myself, but my starting known
point "good" point .. was a fail. So I've instead been looking at assembly dumps
of memory management routines.
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/commit/?h=standard/arm-versatile-926ejs&id=351d133943b50a9dfeee07661d44254722a19f04
>
> I wonder why this patch hasn't made upstream yet.
It was sent upstream, and rmk wanted to go to ARM ltd to rework the patch after
getting some boards specs. Looks like the process is still ongoing.
Cheers,
Bruce
>
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto/3.8: fix gcc 4.8 ARM boot issues
Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards
when gcc 4.8 is used.
Without the following mainline backports:
f200475 ARM: 7670/1: fix the memset fix
8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2)
optimizations
The following trap will be seen on boot:
[] (kmem_cache_alloc_trace+0x54/0x210) from []
(con_insert_unipair+0xcc/0x11c)
[] (con_insert_unipair+0xcc/0x11c) from []
(con_set_default_unimap+0xfc/0x198)
[] (con_set_default_unimap+0xfc/0x198) from []
(console_map_init+0x44/0x58)
[] (console_map_init+0x44/0x58) from []
(vty_init+0x16c/0x1b0)
[] (vty_init+0x16c/0x1b0) from [] (tty_init+0x108/0x148)
[] (tty_init+0x108/0x148) from []
(chr_dev_init+0xb4/0xd8)
[] (chr_dev_init+0xb4/0xd8) from []
(do_one_initcall+0x11c/0x18c)
[] (do_one_initcall+0x11c/0x18c) from []
(kernel_init_freeable+0x16c/0x254)
[] (kernel_init_freeable+0x16c/0x254) from []
(kernel_init+0x18/0x160)
[] (kernel_init+0x18/0x160) from []
(ret_from_fork+0x14/0x20)
Code: e593a000 e35a 0a20 e5943014 (e79a1003)
---[ end trace e6c62de166779f86 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b
Moderate stress and board testing shows the fix to hold, and it is good for
broader testing.
[YOCTO #4549]
Signed-off-by: Khem Raj
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |4 ++--
meta/recipes-kernel/linux/linux-yocto_3.8.bb | 14 +++---
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
index c156be7..a3001ac 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
@@ -8,9 +8,9 @@ LINUX_KERNEL_TYPE = "preempt-rt"
KMETA = "meta"
-SRCREV_machine ?= "e0ac9992f1bf4830de49df884a3d2f273d02637b"
-SRCREV_machine_qemuppc ?= "ea4de76a916dd3620e74e565ff42fafb5bb40843"
-SRCREV_meta ?= "edd6461602f6c2fc27bc72997e4437f422a9dccd"
+SRCREV_machine ?= "4fb187301ca153d496b2a96293dffde34d3b1a56"
+SRCREV_machine_qemuppc ?= "547c4ea570933ab7ece9f10d2c46875b460cd337"
+SRCREV_meta ?= "c0851dfb8535635e1e31d4a5146d3f021e30506c"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
index 2073ee3..d9cc82a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
@@ -12,8 +12,8 @@ LINUX_VERSION ?= "3.8.13"
KMETA = "meta"
-SRCREV_machine ?= "1f973c0fc8eea9a8f9758f47cf689ba89dbe9a25"
-SRCREV_meta ?= "edd6461602f6c2fc27bc72997e4437f422a9dccd"
+SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
+SRCREV_meta ?= "c0851dfb8535635e1e31d4a5146d3f021e30506c"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
index 1517f40..0c21f7b 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
@@ -3,13 +3,13 @@ require recipes-kernel/linux/linux-yocto.inc
KBRANCH_DEFAULT = "standard/base"
KBRANCH = "${KBRANCH_DEFAULT}"
-SRCREV_machine_qemuarm ?= "e267fe88798892416828d89bde7f778380b87a90"
-SRCREV_machine_qemumips ?= "813bae2e17db9310f220935e87d168c8e52fafaf"
-SRCREV_machine_qemuppc ?= "f90923775f9bcec3ce23246e8fb59d8f9551e566"
-SRCREV_machine_qemux86 ?= "1f973c0fc8eea9a8f9758f47cf689ba89dbe9a25"
-SRCREV_machine_qemux86-64 ?= "1f973c0fc8eea9a8f9758f47cf689ba89dbe9a25"
-SRCREV_machine ?= "1f973c0fc8eea9a8f9758f47cf689ba89dbe9a25"
-SRCREV_meta ?= "edd6461602f6c2fc27bc72997e4437f422a9dccd"
+SRCREV_machine_qemuarm ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3"
+SRCREV_machine_qemumips ?= "aa0affda03c955678b26b2fb586f1d9505127871"
+SRCREV_machine_qemuppc ?= "698eada61d9385b42dd117858b943655b565084b"
+SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
+SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
+SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
+SRCREV_meta ?= "c0851dfb8535635e1e31d4a5146d3f021e30506c"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1]
Apologies for the "no subject" email. The rest is fine, just the guy typing it up had an itchy trigger finger! Cheers, Bruce On Tue, Jun 18, 2013 at 11:20 AM, Bruce Ashfield wrote: > Richard/Saul, > > Here's the integration of a change from Khem to fix the gcc 4.8 ARM > boot issues. > > I'm still seeing some quasi random issues, but this definitely fixes > the issue at hand, gets us up and running and is much better than > what we had before. > > The patch pretty much says everything else: > > linux-yocto/3.8: fix gcc 4.8 ARM boot issues > > Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards > when gcc 4.8 is used. > > Without the following mainline backports: > > f200475 ARM: 7670/1: fix the memset fix > 8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC > (4.7.2) optimizations > > The following trap will be seen on boot: > > [] (kmem_cache_alloc_trace+0x54/0x210) from [] > (con_insert_unipair+0xcc/0x11c) > [] (con_insert_unipair+0xcc/0x11c) from [] > (con_set_default_unimap+0xfc/0x198) > [] (con_set_default_unimap+0xfc/0x198) from [] > (console_map_init+0x44/0x58) > [] (console_map_init+0x44/0x58) from [] > (vty_init+0x16c/0x1b0) > [] (vty_init+0x16c/0x1b0) from [] > (tty_init+0x108/0x148) > [] (tty_init+0x108/0x148) from [] > (chr_dev_init+0xb4/0xd8) > [] (chr_dev_init+0xb4/0xd8) from [] > (do_one_initcall+0x11c/0x18c) > [] (do_one_initcall+0x11c/0x18c) from [] > (kernel_init_freeable+0x16c/0x254) > [] (kernel_init_freeable+0x16c/0x254) from [] > (kernel_init+0x18/0x160) > [] (kernel_init+0x18/0x160) from [] > (ret_from_fork+0x14/0x20) > Code: e593a000 e35a 0a20 e5943014 (e79a1003) > ---[ end trace e6c62de166779f86 ]--- > Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b > > Moderate stress and board testing shows the fix to hold, and it is good for > broader testing. > > [YOCTO #4549] > > Signed-off-by: Khem Raj > Signed-off-by: Bruce Ashfield > > Cheers, > > Bruce > > The following changes since commit 1dd643b142c69ac9035e29bff11d02201638dc65: > > licences: Add SGI license (2013-06-17 16:45:37 +0100) > > are available in the git repository at: > > git://git.pokylinux.org/poky-contrib zedd/kernel > http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel > > Bruce Ashfield (1): > linux-yocto/3.8: fix gcc 4.8 ARM boot issues > > meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |6 +++--- > meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |4 ++-- > meta/recipes-kernel/linux/linux-yocto_3.8.bb | 14 +++--- > 3 files changed, 12 insertions(+), 12 deletions(-) > > -- > 1.7.10.4 > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1]
Richard/Saul, Here's the integration of a change from Khem to fix the gcc 4.8 ARM boot issues. I'm still seeing some quasi random issues, but this definitely fixes the issue at hand, gets us up and running and is much better than what we had before. The patch pretty much says everything else: linux-yocto/3.8: fix gcc 4.8 ARM boot issues Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards when gcc 4.8 is used. Without the following mainline backports: f200475 ARM: 7670/1: fix the memset fix 8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations The following trap will be seen on boot: [] (kmem_cache_alloc_trace+0x54/0x210) from [] (con_insert_unipair+0xcc/0x11c) [] (con_insert_unipair+0xcc/0x11c) from [] (con_set_default_unimap+0xfc/0x198) [] (con_set_default_unimap+0xfc/0x198) from [] (console_map_init+0x44/0x58) [] (console_map_init+0x44/0x58) from [] (vty_init+0x16c/0x1b0) [] (vty_init+0x16c/0x1b0) from [] (tty_init+0x108/0x148) [] (tty_init+0x108/0x148) from [] (chr_dev_init+0xb4/0xd8) [] (chr_dev_init+0xb4/0xd8) from [] (do_one_initcall+0x11c/0x18c) [] (do_one_initcall+0x11c/0x18c) from [] (kernel_init_freeable+0x16c/0x254) [] (kernel_init_freeable+0x16c/0x254) from [] (kernel_init+0x18/0x160) [] (kernel_init+0x18/0x160) from [] (ret_from_fork+0x14/0x20) Code: e593a000 e35a 0a20 e5943014 (e79a1003) ---[ end trace e6c62de166779f86 ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b Moderate stress and board testing shows the fix to hold, and it is good for broader testing. [YOCTO #4549] Signed-off-by: Khem Raj Signed-off-by: Bruce Ashfield Cheers, Bruce The following changes since commit 1dd643b142c69ac9035e29bff11d02201638dc65: licences: Add SGI license (2013-06-17 16:45:37 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-yocto/3.8: fix gcc 4.8 ARM boot issues meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |6 +++--- meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |4 ++-- meta/recipes-kernel/linux/linux-yocto_3.8.bb | 14 +++--- 3 files changed, 12 insertions(+), 12 deletions(-) -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/4] linux-yocto: consolidated pull request
Richard/Saul, Here's a collection of four patches that I've queued in the past few days. My normal smoke testing passed here. These are a collection of version refreshes, and configuration changes. Nothing major. Once these are merged, the stage is set for more 1.5 development items. Everything is pretty self explanitory, or was discussed on the mailing list, so I'll keep it to a summary here. Let me know if there are any concerns. [PATCH 1/4] linux-yocto/3.4: allow kernel feature _appends to be overriden [PATCH 2/4] linux-yocto/3.8: add USB screen configuration and net sched options [PATCH 3/4] linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247ed [PATCH 4/4] linux-yocto-dev: bump version to 3.10+ Cheers, Bruce The following changes since commit 8e9501ffa8726d69412d669580d787ffedb88d34: populate_sdk_base, adt_installer: abort install if path contains spaces (2013-06-25 17:59:17 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (4): linux-yocto/3.4: allow kernel feature _appends to be overriden linux-yocto/3.8: add USB screen configuration and net sched options linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247ed linux-yocto-dev: bump version to 3.10+ meta/recipes-kernel/linux/linux-yocto-dev.bb |2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |4 ++-- meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 17 + meta/recipes-kernel/linux/linux-yocto_3.8.bb |2 +- 7 files changed, 16 insertions(+), 15 deletions(-) -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/4] linux-yocto/3.8: add USB screen configuration and net sched options
Bumping the meta branch SRCREV for the followiong commits:
meta: enable additional NET_SCHED options
This change turns on NET_ACT_MIRRED (packet redirecting and mirroring)
and NET_CLS_U32 (universal 32bit comparisons w/ hashing classification).
Signed-off-by: Michael Barabanov
Signed-off-by: Bruce Ashfield
meta: add BSP-specific touchscreen support
Add touchscreen-composite support to machines based on common-pc and
common-pc-64, along with several other Atom boards that don't inherit
from those, thus providing those machines with the out-of-the-box
ability to make use of the set of USB touchscreen devices supported by
the composite USB driver.
Signed-off-by: Tom Zanussi
meta: add usb/touchscreen-composite feature
Add support for the 'composite' USB touchscreen driver.
Signed-off-by: Tom Zanussi
meta: add features/input/touchscreen
Add a feature enabling basic support for touchscreen input devices.
Signed-off-by: Tom Zanussi
Signed-off-by: Michael Barabanov
Signed-off-by: Tom Zanussi
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.8.bb |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
index a3001ac..c4f187f 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
@@ -10,7 +10,7 @@ KMETA = "meta"
SRCREV_machine ?= "4fb187301ca153d496b2a96293dffde34d3b1a56"
SRCREV_machine_qemuppc ?= "547c4ea570933ab7ece9f10d2c46875b460cd337"
-SRCREV_meta ?= "c0851dfb8535635e1e31d4a5146d3f021e30506c"
+SRCREV_meta ?= "f121c06ae8e2c517399c145f68ad7f2ee754f1cc"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
index d9cc82a..5c8447f 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
@@ -13,7 +13,7 @@ LINUX_VERSION ?= "3.8.13"
KMETA = "meta"
SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
-SRCREV_meta ?= "c0851dfb8535635e1e31d4a5146d3f021e30506c"
+SRCREV_meta ?= "f121c06ae8e2c517399c145f68ad7f2ee754f1cc"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
index cf5b96d..a7107e8 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
@@ -9,7 +9,7 @@ SRCREV_machine_qemuppc ?=
"698eada61d9385b42dd117858b943655b565084b"
SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
-SRCREV_meta ?= "c0851dfb8535635e1e31d4a5146d3f021e30506c"
+SRCREV_meta ?= "f121c06ae8e2c517399c145f68ad7f2ee754f1cc"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/4] linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247ed
Updating the 3.4 branches to the latest LTSI baseline.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 12 ++--
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
index d9a894a..1655da8 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
@@ -8,8 +8,8 @@ LINUX_KERNEL_TYPE = "preempt-rt"
KMETA = "meta"
-SRCREV_machine ?= "a4a8406d906163dcdab2d29420a9bc46668fc8d9"
-SRCREV_machine_qemuppc ?= "0c20eafa8b950b1180f1701ba45026ea5e713482"
+SRCREV_machine ?= "2a1d3b50a2889587d0fed92ccb09051a9e300735"
+SRCREV_machine_qemuppc ?= "0168221d2c818898b69890624e1aacbb8ec1aea9"
SRCREV_meta ?= "9473a39c59bf9c07a316486d272652bacb9ad3ac"
PR = "${INC_PR}.1"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
index 0955846..b69d9d5 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
@@ -12,7 +12,7 @@ LINUX_VERSION ?= "3.4.46"
KMETA = "meta"
-SRCREV_machine ?= "de0c0ed674dfdbd808657e299fc720d8a97cb868"
+SRCREV_machine ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
SRCREV_meta ?= "9473a39c59bf9c07a316486d272652bacb9ad3ac"
PR = "${INC_PR}.1"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
index ade96be..ae10448 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -3,12 +3,12 @@ require recipes-kernel/linux/linux-yocto.inc
KBRANCH_DEFAULT = "standard/base"
KBRANCH = "${KBRANCH_DEFAULT}"
-SRCREV_machine_qemuarm ?= "7054a5db2c1869e0e0b294459fc4770113a8df52"
-SRCREV_machine_qemumips ?= "46b3cf22c01e40ef035b78f0542a9007aa0cf507"
-SRCREV_machine_qemuppc ?= "1f2475ab9eefbb479c8a481475ddb3043d47b74a"
-SRCREV_machine_qemux86 ?= "de0c0ed674dfdbd808657e299fc720d8a97cb868"
-SRCREV_machine_qemux86-64 ?= "de0c0ed674dfdbd808657e299fc720d8a97cb868"
-SRCREV_machine ?= "de0c0ed674dfdbd808657e299fc720d8a97cb868"
+SRCREV_machine_qemuarm ?= "ccc8f93d42a56511b8867ff3eeba76290309bc2c"
+SRCREV_machine_qemumips ?= "23607b7f3ca690d62a43c58b8358fa5b75c55b2a"
+SRCREV_machine_qemuppc ?= "d48004092883cfdee8a5092b375ac635742c39cb"
+SRCREV_machine_qemux86 ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
+SRCREV_machine_qemux86-64 ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
+SRCREV_machine ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
SRCREV_meta ?= "9473a39c59bf9c07a316486d272652bacb9ad3ac"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/4] linux-yocto/3.4: allow kernel feature _appends to be overriden
Updating the linux-yocto 3.4 recipe's feature flags to match the 3.8
recipe, which has the following change:
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe doesn't allow the appended
features to be prevented in a layer without using python code and
a recipe finalize hook.
To allow easier overriding of 'extra' or 'optional' features that are
defined in the linux-yocto recipe, we create a KERNEL_EXTRA_FEATURES
variable. This variable can be set in a layer to define extra features
or cleared to prevent the recipe's extra features from being appended
to the core functionality.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto_3.4.bb |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
index 9d6d8c7..ade96be 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -23,7 +23,8 @@ KMETA = "meta"
COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemux86-64"
# Functionality flags
-KERNEL_FEATURES_append = " features/netfilter/netfilter.scc"
-KERNEL_FEATURES_append_qemux86=" cfg/sound.scc"
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", "
cfg/x32.scc", "" ,d)}"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 4/4] linux-yocto-dev: bump version to 3.10+
The linux-yocto-dev kernel is at 3.10-rcX, so we should bump the version to
reflect reality.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-dev.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 598c82c..c2ce3f6 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -33,7 +33,7 @@ python () {
d.setVar("SRCREV_meta", "${AUTOREV}")
}
-LINUX_VERSION ?= "3.8+"
+LINUX_VERSION ?= "3.10+"
LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] linux-yocto: update 3.4 to latest -stable
Saul/, Here's an update of the 3.4 SRCREVs for the latest 3.4.52 -stable version. Build and boot tested here for linux-yocto and linux-yocto-rt. Cheers, Bruce The following changes since commit dc86293f0444384e8ae5131fdd10b6cb077164b0: bitbake: HOB:Proper handle of SIGINT (2013-07-05 15:52:48 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel-oe http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe Bruce Ashfield (1): linux-yocto/3.4: update to v3.4.52 meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |8 meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |6 +++--- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 3 files changed, 15 insertions(+), 15 deletions(-) -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto/3.4: update to v3.4.52
Updating the 3.4 kernel to the latest korg -stable release.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |8
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |6 +++---
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16
3 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
index 1655da8..5e50cde 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
@@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc
KBRANCH = "standard/preempt-rt/base"
KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
-LINUX_VERSION ?= "3.4.46"
+LINUX_VERSION ?= "3.4.52"
LINUX_KERNEL_TYPE = "preempt-rt"
KMETA = "meta"
-SRCREV_machine ?= "2a1d3b50a2889587d0fed92ccb09051a9e300735"
-SRCREV_machine_qemuppc ?= "0168221d2c818898b69890624e1aacbb8ec1aea9"
-SRCREV_meta ?= "9473a39c59bf9c07a316486d272652bacb9ad3ac"
+SRCREV_machine ?= "1a7a6b495dd6f68e3e2a8a716ceabd283da7f480"
+SRCREV_machine_qemuppc ?= "0ce0666df1e29a74ccfd65bbcf8286b2e632cc3f"
+SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
index b69d9d5..a61fe70 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
@@ -8,12 +8,12 @@ KBRANCH = "${KBRANCH_DEFAULT}"
LINUX_KERNEL_TYPE = "tiny"
KCONFIG_MODE = "--allnoconfig"
-LINUX_VERSION ?= "3.4.46"
+LINUX_VERSION ?= "3.4.52"
KMETA = "meta"
-SRCREV_machine ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
-SRCREV_meta ?= "9473a39c59bf9c07a316486d272652bacb9ad3ac"
+SRCREV_machine ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
index ae10448..beb67ee 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc
KBRANCH_DEFAULT = "standard/base"
KBRANCH = "${KBRANCH_DEFAULT}"
-SRCREV_machine_qemuarm ?= "ccc8f93d42a56511b8867ff3eeba76290309bc2c"
-SRCREV_machine_qemumips ?= "23607b7f3ca690d62a43c58b8358fa5b75c55b2a"
-SRCREV_machine_qemuppc ?= "d48004092883cfdee8a5092b375ac635742c39cb"
-SRCREV_machine_qemux86 ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
-SRCREV_machine_qemux86-64 ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
-SRCREV_machine ?= "778950f1e0b5c5af7e92c43220c3c4f4e3324cb5"
-SRCREV_meta ?= "9473a39c59bf9c07a316486d272652bacb9ad3ac"
+SRCREV_machine_qemuarm ?= "89c1e24271fba1c235959cb96c91dba98c542821"
+SRCREV_machine_qemumips ?= "99e87eb8b1e985eb6addf7590c4e837ff7c7e873"
+SRCREV_machine_qemuppc ?= "62f5c50609c93c5b70736a4374cee8075ab82566"
+SRCREV_machine_qemux86 ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_machine_qemux86-64 ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_machine ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
-LINUX_VERSION ?= "3.4.46"
+LINUX_VERSION ?= "3.4.52"
PR = "${INC_PR}.5"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] kernel miscompilation with gcc 4.8 for ARMv5
On Wed, Jul 10, 2013 at 9:34 AM, Enrico Scholz wrote: > Enrico Scholz > > writes: > >> is it expected that recent gcc 4.8[1] compiles the kernel correctly? >> Kernels for ARMv5 platforms (PXA168 -> 3.4.52, MX28 -> 3.8.13) fail here >> 100% at early boot with > > Applying two upstream kernel commits > 455bd4c430b0c0a361f38e8658a0d6cb469942b5 (ARM: 7668/1: fix > memset-related crashes caused by recent GCC (4.7.2) optimizations) and > 418df63adac56841ef6b0f1fcf435bc64d4ed177 (ARM: 7670/1: fix the memset > fix) seem to fix the problem for me. Correct. Those are the same commits you'll see on linux-yocto-3.8, we've been soaking them for a while. I was waiting for LTSI and -stable to pick up the changes before updating linux-yocto-3.4, but that hasn't happened yet. If you are using linux-yocto-3.4 and can confirm that it boots for you with those patches, I can stage them in my tree while I wait for them to loop around. Cheers, Bruce > > > > Enrico > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] kernel miscompilation with gcc 4.8 for ARMv5
On Wed, Jul 10, 2013 at 11:30 AM, Enrico Scholz wrote: > Bruce Ashfield > writes: > >>> Applying two upstream kernel commits >>> 455bd4c430b0c0a361f38e8658a0d6cb469942b5 (ARM: 7668/1: fix >>> memset-related crashes caused by recent GCC (4.7.2) optimizations) and >>> 418df63adac56841ef6b0f1fcf435bc64d4ed177 (ARM: 7670/1: fix the memset >>> fix) seem to fix the problem for me. >> >> Correct. Those are the same commits you'll see on linux-yocto-3.8, >> we've been soaking them for a while. I was waiting for LTSI and -stable >> to pick up the changes before updating linux-yocto-3.4, but that hasn't >> happened yet. >> >> If you are using linux-yocto-3.4 and can confirm that it boots for you >> with those patches, > > Sorry, I am using a more or less vanilla 3.4 kernel. Patches fix > the problem there (device boots) and (after knowing about them) the > problematic code is easy to spot: No worries. I can spot the fix, since we already did this for the 3.8 kernel. I was just no where near my targets at the moment .. and if I had an independent report that things boot, I'd go ahead and push my 3.8 fixes (ported to 3.4) .. which I may do anyway, since I can drop them when they cycle through -stable and LTSI. Cheers, Bruce > > $ arm-linux-gnueabi-objdump -d mm/slub.o > > 14c4 : > ... > 14fc: e1a1mov r0, r1 > 1500: e3a0106bmov r1, #107; 0x6b > 1504: ebfebl 0 > 1508: e1a03000mov r3, r0 <<<<<<< > 150c: e5942010ldr r2, [r4, #16] > 1510: e3e0105amvn r1, #90 ; 0x5a > 1514: e0832002add r2, r3, r2 > 1518: e5421001strbr1, [r2, #-1] > > With unpatched memset, 'r0' points to end of buffer. > > > Enrico > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] kernel miscompilation with gcc 4.8 for ARMv5
On Wed, Jul 10, 2013 at 9:57 AM, Bruce Ashfield wrote: > On Wed, Jul 10, 2013 at 9:34 AM, Enrico Scholz > wrote: >> Enrico Scholz >> >> writes: >> >>> is it expected that recent gcc 4.8[1] compiles the kernel correctly? >>> Kernels for ARMv5 platforms (PXA168 -> 3.4.52, MX28 -> 3.8.13) fail here >>> 100% at early boot with >> >> Applying two upstream kernel commits >> 455bd4c430b0c0a361f38e8658a0d6cb469942b5 (ARM: 7668/1: fix >> memset-related crashes caused by recent GCC (4.7.2) optimizations) and >> 418df63adac56841ef6b0f1fcf435bc64d4ed177 (ARM: 7670/1: fix the memset >> fix) seem to fix the problem for me. > > Correct. Those are the same commits you'll see on linux-yocto-3.8, we've been > soaking them for a while. I was waiting for LTSI and -stable to pick > up the changes > before updating linux-yocto-3.4, but that hasn't happened yet. > > If you are using linux-yocto-3.4 and can confirm that it boots for you > with those patches, > I can stage them in my tree while I wait for them to loop around. > Heh. Clearly I had vacation brain when I wrote this .. I merged and pushed the two ARM gcc 4.8 fixes on June 20th, at the same time I was fixing 3.8. :) Cheers, Bruce > Cheers, > > Bruce > >> >> >> >> Enrico >> ___ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/2] linux-yocto: mips changes
This 2 patch series fixes gcc 4.8 compilation of mips in the 3.4 kernel, and corrects a mistake I made when updating the 3.8 kernel that inadvertently dropped the qemumips64 SRCREV. Cheers, Bruce The following changes since commit fd9d1042d2984aadaf59178648f0484c98250237: linux-yocto/3.8: update META srcrev (2013-07-17 13:00:19 -0400) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (2): linux-yocto/3.4: mips: fix gcc 4.8 compilation linux-yocto/3.8: restore qemumips64 SRCREV meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |4 ++-- meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 12 ++-- meta/recipes-kernel/linux/linux-yocto_3.8.bb |1 + 4 files changed, 10 insertions(+), 9 deletions(-) -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] linux-yocto/3.8: restore qemumips64 SRCREV
In commit 00e0ec6c [linux-yocto: v3.8.13 and v3.4.46], the qemumips64 SRCREV was inadvertently dropped. This patch restores the SRCREV and a booting qemumips64. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto_3.8.bb |1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb b/meta/recipes-kernel/linux/linux-yocto_3.8.bb index 03f6949..3a77cf9 100644 --- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb +++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb @@ -8,6 +8,7 @@ SRCREV_machine_qemumips ?= "aa0affda03c955678b26b2fb586f1d9505127871" SRCREV_machine_qemuppc ?= "698eada61d9385b42dd117858b943655b565084b" SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" +SRCREV_machine_qemumips64 ?= "077bff22c9951db6b35470ba17b1df2f2a91fefb" SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337" -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] linux-yocto/3.4: mips: fix gcc 4.8 compilation
Updating the SRCREVs to enable the following fix for gcc 4.8 mips
compilation:
Author: Steven J. Hill
Date: Fri Jul 6 21:56:01 2012 +0200
MIPS: Refactor 'clear_page' and 'copy_page' functions.
Remove usage of the '__attribute__((alias("...")))' hack that aliased
to integer arrays containing micro-assembled instructions. This hack
breaks when building a microMIPS kernel. It also makes the code much
easier to understand.
[r...@linux-mips.org: Added back export of the clear_page and copy_page
symbols so certain modules will work again. Also fixed build with
CONFIG_SIBYTE_DMA_PAGEOPS enabled.]
Signed-off-by: Steven J. Hill
Cc: linux-m...@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/3866/
Acked-by: David Daney
Signed-off-by: Ralf Baechle
(cherry picked from commit c022630633624a75b3b58f43dd3c6cc896a56cff)
Signed-off-by: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 12 ++--
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
index 5e50cde..ec53206 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
@@ -8,8 +8,8 @@ LINUX_KERNEL_TYPE = "preempt-rt"
KMETA = "meta"
-SRCREV_machine ?= "1a7a6b495dd6f68e3e2a8a716ceabd283da7f480"
-SRCREV_machine_qemuppc ?= "0ce0666df1e29a74ccfd65bbcf8286b2e632cc3f"
+SRCREV_machine ?= "516cc41b2f9a93d77fe6713bb6dfec20aa24f5ce"
+SRCREV_machine_qemuppc ?= "a96230572ba5bc05decb7bcaa81b02e972d6841b"
SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
PR = "${INC_PR}.1"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
index a61fe70..18c469c 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
@@ -12,7 +12,7 @@ LINUX_VERSION ?= "3.4.52"
KMETA = "meta"
-SRCREV_machine ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_machine ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
PR = "${INC_PR}.1"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
index beb67ee..8db015a 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -3,12 +3,12 @@ require recipes-kernel/linux/linux-yocto.inc
KBRANCH_DEFAULT = "standard/base"
KBRANCH = "${KBRANCH_DEFAULT}"
-SRCREV_machine_qemuarm ?= "89c1e24271fba1c235959cb96c91dba98c542821"
-SRCREV_machine_qemumips ?= "99e87eb8b1e985eb6addf7590c4e837ff7c7e873"
-SRCREV_machine_qemuppc ?= "62f5c50609c93c5b70736a4374cee8075ab82566"
-SRCREV_machine_qemux86 ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
-SRCREV_machine_qemux86-64 ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
-SRCREV_machine ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_machine_qemuarm ?= "a3bd53305c7dcd11a2683fbe5d830d44236f4cd4"
+SRCREV_machine_qemumips ?= "e142ba98038a697e3a96b8f30a16e93602eff3c7"
+SRCREV_machine_qemuppc ?= "290c3dd687145104d4e3f0e7732669c1c42b19fe"
+SRCREV_machine_qemux86 ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
+SRCREV_machine_qemux86-64 ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
+SRCREV_machine ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] linux-yocto/3.4: mips: fix gcc 4.8 compilation
Updating the SRCREVs to enable the following fix for gcc 4.8 mips
compilation:
Author: Steven J. Hill
Date: Fri Jul 6 21:56:01 2012 +0200
MIPS: Refactor 'clear_page' and 'copy_page' functions.
Remove usage of the '__attribute__((alias("...")))' hack that aliased
to integer arrays containing micro-assembled instructions. This hack
breaks when building a microMIPS kernel. It also makes the code much
easier to understand.
[r...@linux-mips.org: Added back export of the clear_page and copy_page
symbols so certain modules will work again. Also fixed build with
CONFIG_SIBYTE_DMA_PAGEOPS enabled.]
Signed-off-by: Steven J. Hill
Cc: linux-m...@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/3866/
Acked-by: David Daney
Signed-off-by: Ralf Baechle
(cherry picked from commit c022630633624a75b3b58f43dd3c6cc896a56cff)
Signed-off-by: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 12 ++--
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
index 5e50cde..ec53206 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
@@ -8,8 +8,8 @@ LINUX_KERNEL_TYPE = "preempt-rt"
KMETA = "meta"
-SRCREV_machine ?= "1a7a6b495dd6f68e3e2a8a716ceabd283da7f480"
-SRCREV_machine_qemuppc ?= "0ce0666df1e29a74ccfd65bbcf8286b2e632cc3f"
+SRCREV_machine ?= "516cc41b2f9a93d77fe6713bb6dfec20aa24f5ce"
+SRCREV_machine_qemuppc ?= "a96230572ba5bc05decb7bcaa81b02e972d6841b"
SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
PR = "${INC_PR}.1"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
index a61fe70..18c469c 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb
@@ -12,7 +12,7 @@ LINUX_VERSION ?= "3.4.52"
KMETA = "meta"
-SRCREV_machine ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_machine ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
PR = "${INC_PR}.1"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
index beb67ee..8db015a 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -3,12 +3,12 @@ require recipes-kernel/linux/linux-yocto.inc
KBRANCH_DEFAULT = "standard/base"
KBRANCH = "${KBRANCH_DEFAULT}"
-SRCREV_machine_qemuarm ?= "89c1e24271fba1c235959cb96c91dba98c542821"
-SRCREV_machine_qemumips ?= "99e87eb8b1e985eb6addf7590c4e837ff7c7e873"
-SRCREV_machine_qemuppc ?= "62f5c50609c93c5b70736a4374cee8075ab82566"
-SRCREV_machine_qemux86 ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
-SRCREV_machine_qemux86-64 ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
-SRCREV_machine ?= "cdd7a546922ca1c46c94adeec3b9c90dc9aaad2d"
+SRCREV_machine_qemuarm ?= "a3bd53305c7dcd11a2683fbe5d830d44236f4cd4"
+SRCREV_machine_qemumips ?= "e142ba98038a697e3a96b8f30a16e93602eff3c7"
+SRCREV_machine_qemuppc ?= "290c3dd687145104d4e3f0e7732669c1c42b19fe"
+SRCREV_machine_qemux86 ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
+SRCREV_machine_qemux86-64 ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
+SRCREV_machine ?= "4122d6cf3f9e1fd6d54f6e13af29c4c589289fdc"
SRCREV_meta ?= "7250de4d4afc2558082cd42b8a0d151903436e8f"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] linux-yocto/3.8: restore qemumips64 SRCREV
In commit 00e0ec6c [linux-yocto: v3.8.13 and v3.4.46], the qemumips64 SRCREV
was inadvertently dropped. This patch restores the SRCREV and a booting
qemumips64.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto_3.8.bb |1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
index 03f6949..f71af05 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
@@ -5,6 +5,7 @@ KBRANCH = "${KBRANCH_DEFAULT}"
SRCREV_machine_qemuarm ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3"
SRCREV_machine_qemumips ?= "aa0affda03c955678b26b2fb586f1d9505127871"
+SRCREV_machine_qemumips64 ?= "077bff22c9951db6b35470ba17b1df2f2a91fefb"
SRCREV_machine_qemuppc ?= "698eada61d9385b42dd117858b943655b565084b"
SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [v2 PATCH 0/3] linux-yocto: mips changes
This *3* patch series fixes gcc 4.8 compilation of mips in the 3.4 kernel, and corrects a mistake I made when updating the 3.8 kernel that inadvertently dropped the qemumips64 SRCREV. The 3rd patch, which was dropped in version 1 is meta branch changes for the latest emgd driver. Cheers, Bruce The following changes since commit 3dee534f1e25109e0bdb681de0746c336f4b8840: lib/oeqa: fix dependecy check (2013-07-16 10:04:17 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (3): linux-yocto/3.8: update META srcrev linux-yocto/3.4: mips: fix gcc 4.8 compilation linux-yocto/3.8: restore qemumips64 SRCREV meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |4 ++-- meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 12 ++-- meta/recipes-kernel/linux/linux-yocto_3.8.bb |3 ++- 6 files changed, 13 insertions(+), 12 deletions(-) -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] linux-yocto/3.8: update META srcrev
Bumping the linux-yocto-3.8 meta branch SRCREV to pick up the following
changes:
8ef9136 .gitignore: do not ignore meta directory
f846f12 uvcvideo: a new config for a webcam device driver
02014ca v4l2: config fragment for enabling v4l2 interface to camera devices
71a5cc0 media-camera: a feature to enable camera infrastructure
2396656 drm-emgd.scc: remove config for non-existing driver
aad8aa7 drm-emgd-1.18.scc: add a kernel feature for emgd-1.18 driver
fcf81f8 meta: restore NAT Feature
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.8.bb |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
index c4f187f..6d52ecc 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
@@ -10,7 +10,7 @@ KMETA = "meta"
SRCREV_machine ?= "4fb187301ca153d496b2a96293dffde34d3b1a56"
SRCREV_machine_qemuppc ?= "547c4ea570933ab7ece9f10d2c46875b460cd337"
-SRCREV_meta ?= "f121c06ae8e2c517399c145f68ad7f2ee754f1cc"
+SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
index 5c8447f..c657675 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
@@ -13,7 +13,7 @@ LINUX_VERSION ?= "3.8.13"
KMETA = "meta"
SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
-SRCREV_meta ?= "f121c06ae8e2c517399c145f68ad7f2ee754f1cc"
+SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
index a7107e8..03f6949 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
@@ -9,7 +9,7 @@ SRCREV_machine_qemuppc ?=
"698eada61d9385b42dd117858b943655b565084b"
SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
-SRCREV_meta ?= "f121c06ae8e2c517399c145f68ad7f2ee754f1cc"
+SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] linux-dtb: allow to build dtb using support from kernel
On Mon, Jul 22, 2013 at 10:02 AM, André Draszik
wrote:
> Currently, OE is unable to use the linux kernel's built-in
> support to generate a device tree blob (dtb). This is an
> issue for device tree source (dts) files that need to be run
> through CPP (dtsp).
It's not clear to me (from the commit message), why the dtc recipe can't
provide what we need. I don't object to using the in kernel tree dtc, but
all the reasons why there are no other options need to be in the commit
message.
>
> The kernel build system has built-in support for device tree
> source files that /include/ additional files and it also
> supports the source file to be pre-processed using CPP.
>
> This commits lets OE use kbuild if $KERNEL_DEVICETREE points
> to file(s) that are located in arch/${ARCH}/boot/dts/, e.g.
> KERNEL_DEVICETREE = ".dts". In this case, no
> dependency is added on dtc-native, as that is not needed any
> more.
>
What happens with SDK builds ? i.e. if nativsdk versions of the dtc recipe are
used, we'll still have the functional gap.
> The previous way of handling dts files, i.e. compilation via
> the stand-alone dtc-native, is still supported - it is triggered
> by specifying the full path to the dts file, as before, e.g.
> KERNEL_DEVICETREE = "arch/${ARCH}/boot/dts/.dts"
>
> Signed-off-by: André Draszik
> ---
> meta/recipes-kernel/linux/linux-dtb.inc | 75
> +++--
> 1 file changed, 63 insertions(+), 12 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc
> b/meta/recipes-kernel/linux/linux-dtb.inc
> index 7747718..75b8b76 100644
> --- a/meta/recipes-kernel/linux/linux-dtb.inc
> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
> @@ -1,28 +1,66 @@
> +inherit kernel-arch
> +
> # Support for device tree generation
> FILES_kernel-devicetree = "/boot/devicetree*"
> KERNEL_DEVICETREE_FLAGS ?= "-R 8 -p 0x3000"
>
> python __anonymous () {
> +from os import path
> +
> devicetree = d.getVar("KERNEL_DEVICETREE", True) or ''
> if devicetree:
> -depends = d.getVar("DEPENDS", True)
> -d.setVar("DEPENDS", "%s dtc-native" % depends)
> +S = d.getVar("S", True)
> +for DTS_FILE in devicetree.split():
> +DTS_FILE = S + "/" + DTS_FILE
> +if os.path.exists(DTS_FILE):
> +# full path given, use dtc-native
> +print "old style KERNEL_DEVICETREE, adding depend on
> dtc-native"
> +depends = d.getVar("DEPENDS", True)
> +d.setVar("DEPENDS", "%s dtc-native" % depends)
> +else:
> +# new style - it's just a file name, under
> arch/${ARCH}/boot/dts
> +# we don't need dtc-native, as we use the kernel's compiler
> +print "new style KERNEL_DEVICETREE"
There really needs to be a flag or other option to override this detection.
> packages = d.getVar("PACKAGES", True)
> d.setVar("PACKAGES", "%s kernel-devicetree" % packages)
> }
>
> -do_install_append() {
> +do_compile_append() {
> if test -n "${KERNEL_DEVICETREE}"; then
> for DTS_FILE in ${KERNEL_DEVICETREE}; do
> if [ ! -f ${DTS_FILE} ]; then
> - echo "Warning: ${DTS_FILE} is not available!"
> - continue
> + if [ ! -f arch/${ARCH}/boot/dts/${DTS_FILE}
> ]; then
> + echo "Warning: ${DTS_FILE} is not
> available!"
> + continue
> + fi
> +
> + # standard build using kbuild
> + echo "Info: standard kbuild for device tree
> blob"
> + DTS_BASE_NAME=`basename ${DTS_FILE} | awk -F
> "." '{print $1}'`
> +
> + unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
> + oe_runmake ${DTS_BASE_NAME}.dtb
> CC="${KERNEL_CC}" LD="${KERNEL_LD}" ${KERNEL_EXTRA_ARGS}
> fi
> + done
> + fi
> +}
> +
> +do_install_append() {
> + if test -n "${KERNEL_DEVICETREE}"; then
> + for DTS_FILE in ${KERNEL_DEVICETREE}; do
> DTS_BASE_NAME=`basename ${DTS_FILE} | awk -F "."
> '{print $1}'`
> - DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed
> "s/${MACHINE}/${DTS_BASE_NAME}/g"`
> DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} |
> sed "s/${MACHINE}/${DTS_BASE_NAME}/g"`
> - dtc -I dts -O dtb ${KERNEL_DEVICETREE_FLAGS} -o
> ${DTS_BASE_NAME} ${DTS_FILE}
> - install -m 0644 ${DTS_BASE_NAME}
> ${D}/boot/devicetree-${DTB_SYMLINK_NAME}.dtb
> + if [ ! -f ${DTS_FILE} ]; then
Since install comes after compile, it would be better to test on the results of
the compile phase (i.e. is there a dtb al
[OE-core] [PATCH 0/1] linux-yocto/3.8: fix tree patching
The xilinx guys noticed that my recent commit to the kernel's meta branch to ensure that modified files were tracked was a bit premature and caused a mismatch in the .gitignore between the meta branch and the BSP branches. Which meant that a dirty file was present in the BSP branches, breaking git application of patches to the tree. I'm reverting the change for now, and will fix it properly with the new yocto 1.5 kernel and tools. Cheers, Bruce The following changes since commit 31e6eee860b5f9f4ac9ef0889bcff5648de6e3f9: poky-tiny.conf: blacklist core-image-weston option (2013-07-18 21:26:58 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-yocto/3.8: revert .gitignore: do not ignore meta directory meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.8.bb |2 +- 3 files changed, 3 insertions(+), 3 deletions(-) -- 1.7.10.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto/3.8: revert .gitignore: do not ignore meta directory
We made a change to allow meta branch/directory changes to be visible
when working with the kernel tree. But without associated tool changes
.gitignore is different between branches and hence causes errors when
changing branches and processing the tree.
The tools changes are not ready yet, so to avoid patching issues,
temporarily reverting the change.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.8.bb |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
index 6d52ecc..adb29e7 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
@@ -10,7 +10,7 @@ KMETA = "meta"
SRCREV_machine ?= "4fb187301ca153d496b2a96293dffde34d3b1a56"
SRCREV_machine_qemuppc ?= "547c4ea570933ab7ece9f10d2c46875b460cd337"
-SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337"
+SRCREV_meta ?= "375cb6ebfdb23b0e81cc557bdd4dd39fab29bc50"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
index c657675..8a91e2c 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
@@ -13,7 +13,7 @@ LINUX_VERSION ?= "3.8.13"
KMETA = "meta"
SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
-SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337"
+SRCREV_meta ?= "375cb6ebfdb23b0e81cc557bdd4dd39fab29bc50"
PR = "${INC_PR}.1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
index f71af05..d389d6b 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
@@ -10,7 +10,7 @@ SRCREV_machine_qemuppc ?=
"698eada61d9385b42dd117858b943655b565084b"
SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87"
-SRCREV_meta ?= "8ef9136539464c145963ac2b8ee0196fea1c2337"
+SRCREV_meta ?= "375cb6ebfdb23b0e81cc557bdd4dd39fab29bc50"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto: support externalsrc builds
There are a few extra task that modify the source tree that should
be removed when externalsrc is inherited by a recipe that uses a
linux-yocto tree.
Adding those tasks to SRCTREECOVEREDTASKS means that they are skipped
and externalsrc works as intended.
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel-yocto.bbclass |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index ce125b4..b7e8b32 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -1,5 +1,7 @@
S = "${WORKDIR}/linux"
+# remove tasks that modify the source tree in case externalsrc is inherited
+SRCTREECOVEREDTASKS += "do_kernel_link_vmlinux do_kernel_configme
do_validate_branches do_kernel_configcheck do_kernel_checkout do_patch"
# returns local (absolute) path names for all valid patches in the
# src_uri
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] linux-yocto: fix externalsrc builds
Richard/Saul, This is a fix for externalsrc builds when the linux-yocto bbclass is used. The commit tells most of the story: - There are a few extra task that modify the source tree that should be removed when externalsrc is inherited by a recipe that uses a linux-yocto tree. Adding those tasks to SRCTREECOVEREDTASKS means that they are skipped and externalsrc works as intended. - You'll note that do_patch is repeated in SRCTREECOVEREDTASKS here, since my tested showed that only having it in externalsrc.bbclass did not inhibit the kernel-yocto.bbclass variant from running There's no impact if externalsrc isn't being used, so this is a safe change (from where I stand :) Cheers, Bruce The following changes since commit 7b01671f54f70c28c98457058c51ffefcb07c0e8: nspr 4.8.9: failed to build on x86_64 board (2012-03-27 13:26:37 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-yocto: support externalsrc builds meta/classes/kernel-yocto.bbclass |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-core][PATCH 1/2] kernel.bbclass: merge uboot_mkimage improvements from meta-oe
On Thu, Mar 29, 2012 at 2:24 AM, Martin Jansa wrote:
> Signed-off-by: Martin Jansa
> ---
> meta/classes/kernel.bbclass | 39 +++
> 1 files changed, 23 insertions(+), 16 deletions(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 3519e7c..8cd5fc7 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -502,32 +502,39 @@ do_sizecheck() {
>
> addtask sizecheck before do_install after do_compile
>
> -KERNEL_IMAGE_BASE_NAME ?=
> "${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}-${DATETIME}"
> -# Don't include the DATETIME variable in the sstate package signatures
> -KERNEL_IMAGE_BASE_NAME[vardepsexclude] = "DATETIME"
> -KERNEL_IMAGE_SYMLINK_NAME ?= "${KERNEL_IMAGETYPE}-${MACHINE}"
> -
> -kernel_do_deploy() {
> - install -m 0644 ${KERNEL_OUTPUT}
> ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
> - if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
> - tar -cvzf
> ${DEPLOYDIR}/modules-${KERNEL_VERSION}-${PR}-${MACHINE}.tgz -C ${D} lib
> - fi
> -
> +do_uboot_mkimage() {
> if test "x${KERNEL_IMAGETYPE}" = "xuImage" ; then
> - if test -e arch/${ARCH}/boot/uImage ; then
> - cp arch/${ARCH}/boot/uImage
> ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
We continually try and remove this, but it is a valid use case where some
people do want the kernel's uImage to be used and not regenerate it outside
of the kernel build process.
The last time this was discussed, it concluded that rather than making this
a simple test, we should do it via a flag .. and I'm still of the
opinion that would
be the right approach here. There's no reason to break either use case.
Cheers,
Bruce
> - elif test -e arch/${ARCH}/boot/compressed/vmlinux ; then
> + ENTRYPOINT=${UBOOT_ENTRYPOINT}
> + if test -n "${UBOOT_ENTRYSYMBOL}"; then
> + ENTRYPOINT=`${HOST_PREFIX}nm ${S}/vmlinux | \
> + awk '$3=="${UBOOT_ENTRYSYMBOL}" {print $1}'`
> + fi
> + if test -e arch/${ARCH}/boot/compressed/vmlinux ; then
> ${OBJCOPY} -O binary -R .note -R .comment -S
> arch/${ARCH}/boot/compressed/vmlinux linux.bin
> - uboot-mkimage -A ${ARCH} -O linux -T kernel -C none
> -a ${UBOOT_ENTRYPOINT} -e ${UBOOT_ENTRYPOINT} -n
> "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin
> ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
> + uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C
> none -a ${UBOOT_LOADADDRESS} -e $ENTRYPOINT -n
> "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin arch/${ARCH}/boot/uImage
> rm -f linux.bin
> else
> ${OBJCOPY} -O binary -R .note -R .comment -S vmlinux
> linux.bin
> rm -f linux.bin.gz
> gzip -9 linux.bin
> - uboot-mkimage -A ${ARCH} -O linux -T kernel -C gzip
> -a ${UBOOT_ENTRYPOINT} -e ${UBOOT_ENTRYPOINT} -n
> "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin.gz
> ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
> + uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C
> gzip -a ${UBOOT_LOADADDRESS} -e $ENTRYPOINT -n
> "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin.gz arch/${ARCH}/boot/uImage
> rm -f linux.bin.gz
> fi
> fi
> +}
> +
> +addtask uboot_mkimage before do_install after do_compile
> +
> +KERNEL_IMAGE_BASE_NAME ?=
> "${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}-${DATETIME}"
> +# Don't include the DATETIME variable in the sstate package signatures
> +KERNEL_IMAGE_BASE_NAME[vardepsexclude] = "DATETIME"
> +KERNEL_IMAGE_SYMLINK_NAME ?= "${KERNEL_IMAGETYPE}-${MACHINE}"
> +
> +kernel_do_deploy() {
> + install -m 0644 ${KERNEL_OUTPUT}
> ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
> + if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
> + tar -cvzf
> ${DEPLOYDIR}/modules-${KERNEL_VERSION}-${PR}-${MACHINE}.tgz -C ${D} lib
> + fi
>
> cd ${DEPLOYDIR}
> rm -f ${KERNEL_IMAGE_SYMLINK_NAME}.bin
> --
> 1.7.8.5
>
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-core][PATCHv2 1/2] kernel.bbclass: merge uboot_mkimage improvements from meta-oe
On 12-03-29 10:08 AM, Martin Jansa wrote:
* allows to detect ENTRYPOINT from kernel binary marked with UBOOT_ENTRYSYMBOL
used e.g. by ben-nanonote
Nice to see the big benefit called out, definitely helps the
casual reader :)
Looks like we've got all the use cases preserved, so I have no objections.
Acked-by: Bruce Ashfield
Cheers,
Bruce
Signed-off-by: Martin Jansa
---
meta/classes/kernel.bbclass | 41 +
1 files changed, 25 insertions(+), 16 deletions(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 3519e7c..0ae9bed 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -507,28 +507,37 @@ KERNEL_IMAGE_BASE_NAME ?=
"${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}-${DATETIME
KERNEL_IMAGE_BASE_NAME[vardepsexclude] = "DATETIME"
KERNEL_IMAGE_SYMLINK_NAME ?= "${KERNEL_IMAGETYPE}-${MACHINE}"
+do_uboot_mkimage() {
+ if test "x${KERNEL_IMAGETYPE}" = "xuImage" ; then
+ if test ! -e arch/${ARCH}/boot/uImage ; then
+ ENTRYPOINT=${UBOOT_ENTRYPOINT}
+ if test -n "${UBOOT_ENTRYSYMBOL}"; then
+ ENTRYPOINT=`${HOST_PREFIX}nm ${S}/vmlinux | \
+ awk '$3=="${UBOOT_ENTRYSYMBOL}" {print
$1}'`
+ fi
+ if test -e arch/${ARCH}/boot/compressed/vmlinux ; then
+ ${OBJCOPY} -O binary -R .note -R .comment -S
arch/${ARCH}/boot/compressed/vmlinux linux.bin
+ uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C none
-a ${UBOOT_LOADADDRESS} -e $ENTRYPOINT -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d
linux.bin arch/${ARCH}/boot/uImage
+ rm -f linux.bin
+ else
+ ${OBJCOPY} -O binary -R .note -R .comment -S
vmlinux linux.bin
+ rm -f linux.bin.gz
+ gzip -9 linux.bin
+ uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C gzip
-a ${UBOOT_LOADADDRESS} -e $ENTRYPOINT -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d
linux.bin.gz arch/${ARCH}/boot/uImage
+ rm -f linux.bin.gz
+ fi
+ fi
+ fi
+}
+
+addtask uboot_mkimage before do_install after do_compile
+
kernel_do_deploy() {
install -m 0644 ${KERNEL_OUTPUT}
${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
tar -cvzf
${DEPLOYDIR}/modules-${KERNEL_VERSION}-${PR}-${MACHINE}.tgz -C ${D} lib
fi
- if test "x${KERNEL_IMAGETYPE}" = "xuImage" ; then
- if test -e arch/${ARCH}/boot/uImage ; then
- cp arch/${ARCH}/boot/uImage
${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
- elif test -e arch/${ARCH}/boot/compressed/vmlinux ; then
- ${OBJCOPY} -O binary -R .note -R .comment -S
arch/${ARCH}/boot/compressed/vmlinux linux.bin
- uboot-mkimage -A ${ARCH} -O linux -T kernel -C none -a
${UBOOT_ENTRYPOINT} -e ${UBOOT_ENTRYPOINT} -n "${DISTRO_NAME}/${PV}/${MACHINE}"
-d linux.bin ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
- rm -f linux.bin
- else
- ${OBJCOPY} -O binary -R .note -R .comment -S vmlinux
linux.bin
- rm -f linux.bin.gz
- gzip -9 linux.bin
- uboot-mkimage -A ${ARCH} -O linux -T kernel -C gzip -a
${UBOOT_ENTRYPOINT} -e ${UBOOT_ENTRYPOINT} -n "${DISTRO_NAME}/${PV}/${MACHINE}"
-d linux.bin.gz ${DEPLOYDIR}/${KERNEL_IMAGE_BASE_NAME}.bin
- rm -f linux.bin.gz
- fi
- fi
-
cd ${DEPLOYDIR}
rm -f ${KERNEL_IMAGE_SYMLINK_NAME}.bin
ln -sf ${KERNEL_IMAGE_BASE_NAME}.bin ${KERNEL_IMAGE_SYMLINK_NAME}.bin
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Fetch time optimization (svn : gcc/eglibc - git : linux-yocto)
On Thu, Mar 29, 2012 at 6:03 PM, Richard Purdie wrote: > On Thu, 2012-03-29 at 22:53 +0200, Eric Bénard wrote: >> I noticed in from scratch builds for qemuarm that the longest time is >> taken in fetching sources, especially those fetched using git >> (linux-yocto for example) & svn (gcc, eglibc & co). > > Are you timing these as fetches from the source control systems or from > the mirror tarballs of the repositories. The tarballs should be > faster... > >> To reduce the fetch time would that make sense to >> - fetch gcc/glibc & co from the archive of a stable version and then >> apply patches on top of it (maybe patches stored in an archive >> fetched from oe's website and applied in bulk or patches stored in OE) > > Unfortunately the patches tend to get unwieldy. The tarballs of the svn > repos on the mirror should be about equal in size to the upstream > archive in this case. > >> - do the same thing for the linux-yocto kernel or add a --reference >> option to the git fetcher so that we can provide a local tree as a >> reference ? > > This is effectively how the repositories in DL_DIR are used. If you > place a tree in the right place there, it should reuse references... Agreed .. they definitely do here. Richard probably recalls me asking for a --reference option several years ago as well .. but in the end, at some point the initial fetch happens and then the blobs are re-used. So setting up local mirrors, or pre-fetching are options to make sure that the first download is primed and ready to go. For most builds I do, any time fetching just happens in the background and doesn't get in the way. > >> Do you have other ideas (appart from using a local mirror) to optimize >> the fetch time ? > > I'd be interested firstly to understand if you're using the SCM directly > or using the mirror tarballs as that should make a big difference. In > the standard configuration it should be using mirror tarballs... As would I, since there are some ideas, but they either break workflows, don't follow best practices or compromise the completeness of the data. Cheers, Bruce > > Cheers, > > Richard > > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Fetch time optimization (svn : gcc/eglibc - git : linux-yocto)
On Fri, Mar 30, 2012 at 11:24 AM, Eric Bénard wrote: > Le Fri, 30 Mar 2012 16:12:44 +0100, > Richard Purdie a écrit : >> On Fri, 2012-03-30 at 10:50 +0200, Eric Bénard wrote: >> > the default configuration seems to fetch from source control systems >> > as I always see very long time to fetch gcc/eglibc/linux-yocto >> > (despite having a 2.2 MBytes/s downlink DSL line). >> >> If you're hitting the SCMs I can understand the frustration. >> > that's not a frustration, that's a feedback on the default > behaviour. But I agree with you that could be a frustration for someone > trying OE-core for the first time ;-) > >> Try adding this to your configuration: >> >> PREMIRRORS = "\ >> git://.*/.* http://downloads.yoctoproject.org/mirror/sources/ \n \ >> svn://.*/.* http://downloads.yoctoproject.org/mirror/sources/ \n" >> >> and see if that helps the performance. It might be we consider making >> this the default for OE-Core although some people are nervous about >> doing this... >> > sure that will help : in my work setup I have my own mirrors configured > but here again, that's not what a new user will have and in that > case, I'm testing the plain default configuration to help finding bugs > or things to improve the release. > > I think fetching from git or svn should not be the first thing to do in > recipes like gcc, eglibc, linux & co where we are based on a > stable released version : this doesn't bring real added value to the > user in OE context and this wastes bandwidth (a tbz2 kernel is around s/user/developer/ and there is value in having git history. I know we'd never do without it in our shop. I suggested shallow clones and some other options to Richard a few weeks ago, or some other hybrid models. They all vary in terms of nastiness and have some good and bad points. But from a kernel guy's point of view, you definitely want to work inside git, but I can see from non-kernel point of view, build and boot is all that really matters. Cheers, Bruce > 75MB, a git one is around 600MB). > > Eric > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Fetch time optimization (svn : gcc/eglibc - git : linux-yocto)
On Fri, Mar 30, 2012 at 12:17 PM, Eric Bénard wrote: > Le Fri, 30 Mar 2012 17:02:24 +0100, > Richard Purdie a écrit : >> The linux-yocto kernel recipe heavily uses the SCM to do things so >> whilst it does have a higher download cost, it as adds value and is >> ultimately a maintainers choice too. >> > OK now that I've given a closer look at the linux-yocto recipes & > bbclass I understand better why you need it in that recipe and that > this recipe is heavily based on git's features. There are alternatives that I'm going to be exploring going forward, just nothing that we can bring in during the stabilization cycle. The recipes manipulate git and use it to construct what you build, they don't absolutely require a full git history, so there are some potential savings to be had. It just obviously limits flexibility if a derived recipe wants to merge branches and histories to construct what is built. So having a simple/shallow history for basic builds while not breaking more complex cases probably hits the sweet spot. Cheers, Bruce > >> So whilst I hear what you're saying, I don't think we can change >> anything other than the PREMIRROR... >> > then maybe for the new users testing OE, having PREMIRRORs set in the > default configuration would be a great thing so that they don't believe > OE is a big slow beast just because they have to wait hours for git or > svn to fetch sources. > > Eric > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto: update tiny meta and configuration for kernel 3.2
Updating the META SRCREV to pickup these commits:
59f350e meta: Add common-pc-tiny.scc
0996ca9 tiny: Minimize the tiny config
d6b57bb meta: common-pc add dependencies to cfg
Which update the configuration for the tiny profile of the kernel
for the 3.2 release.
cc: Darren Hart
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index 6184e46..94ada7e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -16,7 +16,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
SRCREV_machine ?= "32ecb53e9ff759bbd297a10712b62a6575daaf86"
SRCREV_machine_qemuppc ?= "0d5625bb868cc2471d5dd49eb7abe7eb5fe1044b"
-SRCREV_meta ?= "867fc7a19f2ea74253d1f20c3d61b7829635175b"
+SRCREV_meta ?= "59f350ec3794e19fa806c1b73749d851f8ebf364"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index 5658d25..b2a37c0 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemuppc ?=
"92de4e2f3c6b397c8b363e079cc4d5e9bcadf877"
SRCREV_machine_qemux86 ?= "8ada1bb97415fe959a57a08504be4eb8a656ed30"
SRCREV_machine_qemux86-64 ?= "4ca7e2c5d42e755e1b4c3e1478128f047a8ed2a8"
SRCREV_machine ?= "01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a"
-SRCREV_meta ?= "867fc7a19f2ea74253d1f20c3d61b7829635175b"
+SRCREV_meta ?= "59f350ec3794e19fa806c1b73749d851f8ebf364"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] linux-yocto: update tiny configuration for 3.2
Richard/Saul, Here's an update of the tiny kernel configuration for 3.2. Darren and I have both tested this, and there's no impact on existing configurations (outside of minor tweaks to common-pc), so there's little risk in this pull request. Cheers, Bruce The following changes since commit 8691a588267472eb5a32b978a0eb9ddfd0c91733: cross-canadian.bbclass: fix rpath for sdk executables (2012-03-31 18:00:59 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-yocto: update tiny meta and configuration for kernel 3.2 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.2.bb|2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1] tiny: Update linux-yocto-tiny to 3.2
On 12-04-01 3:19 AM, Darren Hart wrote: The following changes since commit c97f7f4e4ecd6c431712059c34ebc17b68b055ae: cross-canadian.bbclass: fix rpath for sdk executables (2012-03-31 18:00:36 +0100) Acked-by: Bruce Ashfield are available in the git repository at: git://git.infradead.org/users/dvhart/oe-core.git dvhart/tiny http://git.infradead.org/users/dvhart/oe-core.git/shortlog/refs/heads/dvhart/tiny Darren Hart (1): tiny: Update linux-yocto-tiny to 3.2 meta/recipes-kernel/linux/linux-yocto-tiny/ata.cfg |9 - .../recipes-kernel/linux/linux-yocto-tiny/core.cfg | 19 - .../linux/linux-yocto-tiny/debug.cfg |5 - .../linux/linux-yocto-tiny/devtmpfs.cfg|6 - .../linux/linux-yocto-tiny/e1000.cfg |7 - .../recipes-kernel/linux/linux-yocto-tiny/ext2.cfg |1 - .../recipes-kernel/linux/linux-yocto-tiny/ext3.cfg |2 - .../recipes-kernel/linux/linux-yocto-tiny/lzma.cfg |3 - meta/recipes-kernel/linux/linux-yocto-tiny/net.cfg | 26 - .../linux/linux-yocto-tiny/qemux86/defconfig | 613 .../linux/linux-yocto-tiny/ramfs.cfg |6 - .../linux/linux-yocto-tiny/rtc-pc.cfg | 13 - .../linux/linux-yocto-tiny/serial.cfg |7 - meta/recipes-kernel/linux/linux-yocto-tiny/smp.cfg |7 - meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb | 39 -- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb | 25 + 16 files changed, 25 insertions(+), 763 deletions(-) delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ata.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/core.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/debug.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/devtmpfs.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/e1000.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ext2.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ext3.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/lzma.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/net.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/qemux86/defconfig delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ramfs.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/rtc-pc.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/serial.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/smp.cfg delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] linux-yocto/3.2: add igb support to romley
Updating the 3.2 recipe SRCREVs to pickup the following meta change:
[
meta: Add igb.scc to Romley
Romley machine has 82580 Giga bit Ethernet Controller.
Add the relavent Nic driver to it.
Signed-off-by: Kishore Bodke
]
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index 94ada7e..efc4611 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -16,7 +16,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
SRCREV_machine ?= "32ecb53e9ff759bbd297a10712b62a6575daaf86"
SRCREV_machine_qemuppc ?= "0d5625bb868cc2471d5dd49eb7abe7eb5fe1044b"
-SRCREV_meta ?= "59f350ec3794e19fa806c1b73749d851f8ebf364"
+SRCREV_meta ?= "135c75bf9615334b5b8bb9108d612fe7dfbdb901"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index d2c8bf7..fbff706 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -12,7 +12,7 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.11"
SRCREV_machine ?= "ec236058dc254183dbfb3744bf21f110c37af30b"
-SRCREV_meta ?= "59f350ec3794e19fa806c1b73749d851f8ebf364"
+SRCREV_meta ?= "135c75bf9615334b5b8bb9108d612fe7dfbdb901"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index b2a37c0..8bea0a0 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemuppc ?=
"92de4e2f3c6b397c8b363e079cc4d5e9bcadf877"
SRCREV_machine_qemux86 ?= "8ada1bb97415fe959a57a08504be4eb8a656ed30"
SRCREV_machine_qemux86-64 ?= "4ca7e2c5d42e755e1b4c3e1478128f047a8ed2a8"
SRCREV_machine ?= "01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a"
-SRCREV_meta ?= "59f350ec3794e19fa806c1b73749d851f8ebf364"
+SRCREV_meta ?= "135c75bf9615334b5b8bb9108d612fe7dfbdb901"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/2] linux-yocto: (hopefully) final fixes
Richard/Saul, Here are two last commits for linux-yocto. One is a pending SRCREV update for the romley. It's included to make sure that the meta branch head matches the SRCREVs. Otherwise, we are relying on branch renaming for everyone. There's no risk, and this is already in use by the BSP layer. The second commit is a change that I've been working on all week with Andrea and his work on extending linux-yocto-tiny. The work that was done to support out of tree features was missing .cfg and defconfig support. This meant that you could run into patching issues. To fix it, I pulled back changes that I made a few weeks ago to allow all types of fragments, features, and defconfigs to be supported. The diffstat is largely a movement of code from the recipe back to the tools (where it belonged), but the intent stays the same. I've tested this on every use case I could find .. - core BSPs - Nitin's x32 use case - Andrea's use case - kernel.org test case - Constructed tests with fragments, nested features, etc. Andrea has also tested his use case. These all pass, and the code fixes an intended feature for 1.2 as well as fixing the immediate bug in question. This is for YOCTO 2250. Cheers, Bruce cc: andrea.ad...@gmail.com The following changes since commit 023a12b70b1bbbd3625ab5a6df2ae9943a14bea5: linux-yocto/meta-yocto: update hardware reference SRCREVs (2012-04-13 16:35:59 -0400) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel-oe http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe Bruce Ashfield (2): linux-yocto/3.2: add igb support to romley linux-yocto: allow .cfg, .scc, .patch and defconfigs to be processed in order meta/classes/kernel-yocto.bbclass | 74 ++-- .../kern-tools/kern-tools-native_git.bb|2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb|2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +- 5 files changed, 11 insertions(+), 71 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] linux-yocto: allow .cfg, .scc, .patch and defconfigs to be processed in order
During testing/extension of the linux-yocto-tiny kernel it was found that
defconfigs were not always properly applied. This was due to two issues:
- not being able to fully control the order of objects applied to the
git tree on the SRC_URI
- defconfigs triggering --allnoconfig before being applied
To fix this, the recipe space code that previously detected and generated
automatic features moves back to the kernel tools (where it was before) and
is updated to also process .cfg and defconfigs. Moving this back to the
tools allow other recipes to automatically benefit from the additional
support.
The second issue is addressed by allowing configme to take --alldefconfig
when a recipe wishes to pass a defconfig and override the default
behaviour.
Fixes [YOCTO: 2250]
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel-yocto.bbclass | 74 ++--
.../kern-tools/kern-tools-native_git.bb|2 +-
2 files changed, 8 insertions(+), 68 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index b7e8b32..0caf6a6 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -20,7 +20,9 @@ def find_sccs(d):
sources_list=[]
for s in sources:
base, ext = os.path.splitext(os.path.basename(s))
- if ext and ext in ('.scc'):
+ if ext and ext in ('.scc' '.cfg' '.patch'):
+ sources_list.append(s)
+ elif base and base in 'defconfig':
sources_list.append(s)
return sources_list
@@ -73,72 +75,9 @@ do_patch() {
fi
sccs="${@" ".join(find_sccs(d))}"
- patches_and_dirs="${@" ".join(find_urls(d))}"
-
- # This loops through all patches, and looks for directories that do
- # not already have feature descriptions. If a directory doesn't have
- # a feature description, we switch to the ${WORKDIR} variant of the
- # feature (so we can write to it) and generate a feature for those
- # patches. The generated feature will respect the patch order.
- #
- # By leaving source patch directories that already have .scc files
- # as-is it means that a SRC_URI can only contain a .scc file, and all
- # patches that the .scc references will be picked up, without having
- # to be repeated on the SRC_URI line .. which is more intutive
- set +e
- patch_dirs=
- for pp in ${patches_and_dirs}; do
- p=`echo $pp | cut -f1 -d:`
- wp=`echo $pp | cut -f2 -d:`
- pdir=`dirname ${p}`
- pname=`basename ${p}`
- scc=`find ${pdir} -maxdepth 1 -name '*.scc'`
- if [ -z "${scc}" ]; then
- # there is no scc file. We need to switch to someplace
that we know
- # we can create content (the workdir)
- workdir_subdir=`dirname ${wp}`
- suggested_dir="${WORKDIR}/${workdir_subdir}"
- echo ${gen_feature_dirs} | grep -q ${suggested_dir}
- if [ $? -ne 0 ]; then
- gen_feature_dirs="${gen_feature_dirs}
${suggested_dir}"
- fi
- # we call the file *.scc_tmp, so the test above will
continue to find
- # that patches from a common subdirectory don't have a
scc file and
- # they'll be placed in order, into this file. We'll
rename it later.
- gen_feature_name="gen_`echo ${workdir_subdir} | sed
's%/%%g'`_desc.scc_tmp"
- echo "patch ${pname}" >>
${WORKDIR}/${workdir_subdir}/${gen_feature_name}
- else
- suggested_dir="${pdir}"
- fi
- echo ${patch_dirs} | grep -q ${suggested_dir}
- if [ $? -ne 0 ]; then
- patch_dirs="${patch_dirs} ${suggested_dir}"
- fi
- done
-
- # look for any found scc files, and ensure they are added to the list
- # of directories passsed to updateme
- for s in ${sccs}; do
- sdir=`dirname ${s}`
- echo ${patch_dirs} | grep -q ${sdir}
- if [ $? -ne 0 ]; then
- patch_dirs="${patch_dirs} ${sdir}"
- fi
- done
-
- # go through the patch directories and look for any scc feature files
- # that were constructed above. If one is found, rename it to ".scc" so
- # the kernel patching can see it.
- for pdir in ${patch_dirs}; do
- scc=`find ${pdir} -maxdepth 1 -name '
[OE-core] [PATCH 0/3] linux-yocto: -rc4 pull request
Richard/Saul, Here's a set of 3 fixes that should be considered for -rc4. I split things up as much as I could, in the order that they should be taken. 1/3: linux-yocto: .diff is a valid patch extension This was reported on IRC today, it was an easy fix to an obvious problem. I doubled check the old cases and the new .diff case. I've also confirmed that patch.bbclass and these patch extensions agree. 2/3: linux-yocto/meta: beagleboard: disable CONFIG_PREEMPT This is the merge of Denys' fix for the beagleboard boot issue (aka YOCTO 1892]. With this booting on the xM is fixed. I've merged it into the tree in a named config, so we'll be able to easily identify it in the future. This same change is in the 3.0 kernel, and staged in the 3.2 and 3.4 trees as well. 3/3: linux-yocto/meta: remove kernel config audit warnings This is from Yang Shi @ Wind River. It fixes the issues reporting on the mailing list during the beta testing. The qemu* BSPs on 3.2 and the hardware references on 3.0 now audit cleanly during the kernel build. This is one of those items we promise with each release, and it took a bit longer to acheive this time. Yang and I looked at these and only obselete / invalid options are removed or are tagged as 'hardware' to declare them valid and remove a warning. The functional changes limited. Yang boot tested the changes and I've re-run the audit testing here. (my master branch is a bit out of date, but I had to switch to my secondary builder for testing, and didn't want to disturb it. There are no changes in master that would impact this testing). cc: Yang Shi cc: Denys Dmytriyenko Cheers, Bruce The following changes since commit 5326847ef821c382aac26b474ab0e35939c463b7: Hob: fixed a little view issue about package selection page (2012-04-16 12:56:25 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (3): linux-yocto: .diff is a valid patch extension linux-yocto/meta: beagleboard: disable CONFIG_PREEMPT linux-yocto/meta: remove kernel config audit warnings meta/classes/kernel-yocto.bbclass |2 +- .../kern-tools/kern-tools-native_git.bb|2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb|2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb|2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.0.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +- 7 files changed, 7 insertions(+), 7 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] linux-yocto/meta: remove kernel config audit warnings
Updating the meta SRCREVs to pickup the following meta change for the
3.0 and 3.2 kernels:
[
meta: Clean up BSPs kernel config
Clean up some QEMU and non-x86 BSPs kernel config, including
qemuarm
qemuppc
qemux86
beagleboard
mpc8315e_rdb
Only obsolete/invalid kernel configs are removed.
Signed-off-by: Yang Shi
]
With this commit, the configuration audit for the qemu and hardware
reference boards is (largely) warning free.
Signed-off-by: Yang Shi
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.0.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
index 10459f3..36dcb6e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
@@ -16,7 +16,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
SRCREV_machine ?= "cf280f1dc5877d4ca43d21307222326efa68bb27"
SRCREV_machine_qemuppc ?= "afaa5baa6a9ca9c8a03a9a3eee2ba9fba089f416"
-SRCREV_meta ?= "bb4fff95b3d28c8ab87cd6905eaef86e1f46db6e"
+SRCREV_meta ?= "34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23"
PR = "r2"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index aae4ce0..05674ef 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -16,7 +16,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
SRCREV_machine ?= "32ecb53e9ff759bbd297a10712b62a6575daaf86"
SRCREV_machine_qemuppc ?= "0d5625bb868cc2471d5dd49eb7abe7eb5fe1044b"
-SRCREV_meta ?= "ad5a00b6c5bcdd1740d8fa42be122fc8ff2c579f"
+SRCREV_meta ?= "b14a08f5c7b469a5077c10942f4e1aec171faa9d"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index 6c65707..4957e33 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -12,7 +12,7 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.11"
SRCREV_machine ?= "ec236058dc254183dbfb3744bf21f110c37af30b"
-SRCREV_meta ?= "ad5a00b6c5bcdd1740d8fa42be122fc8ff2c579f"
+SRCREV_meta ?= "b14a08f5c7b469a5077c10942f4e1aec171faa9d"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
index 0d98074..074b1ed 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
@@ -18,7 +18,7 @@ SRCREV_machine_qemuppc ?=
"7528f1d06ef5665eed8c1498f62d5403b82bbbd6"
SRCREV_machine_qemux86 ?= "f153b0eb8264dc1e69f59d4c9173619feb4d5bd9"
SRCREV_machine_qemux86-64 ?= "aac580659dc0ce083f250fb05abf82e58d7f4531"
SRCREV_machine ?= "da7c40006b08916ff3a3db104def82aaf9ac2716"
-SRCREV_meta ?= "bb4fff95b3d28c8ab87cd6905eaef86e1f46db6e"
+SRCREV_meta ?= "34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23"
PR = "r4"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index 54361a2..d81f6b5 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemuppc ?=
"92de4e2f3c6b397c8b363e079cc4d5e9bcadf877"
SRCREV_machine_qemux86 ?= "8ada1bb97415fe959a57a08504be4eb8a656ed30"
SRCREV_machine_qemux86-64 ?= "4ca7e2c5d42e755e1b4c3e1478128f047a8ed2a8"
SRCREV_machine ?= "01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a"
-SRCREV_meta ?= "ad5a00b6c5bcdd1740d8fa42be122fc8ff2c579f"
+SRCREV_meta ?= "b14a08f5c7b469a5077c10942f4e1aec171faa9d"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] linux-yocto: .diff is a valid patch extension
In fixing an existing patch migration bug, the list of valid extensions
got out of sync from the core patch class. As a result, valid patches
were not being applied to the tree.
Updating the tools to migrate .diff files fixes the issue.
Also in this fix is the removal of .patch in the find_sccs() routine, since
it will never be returned by patch.bbclass when all non-patches are
requested, it is simply confusing.
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel-yocto.bbclass |2 +-
.../kern-tools/kern-tools-native_git.bb|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index 0caf6a6..c995a2e 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -20,7 +20,7 @@ def find_sccs(d):
sources_list=[]
for s in sources:
base, ext = os.path.splitext(os.path.basename(s))
- if ext and ext in ('.scc' '.cfg' '.patch'):
+ if ext and ext in ('.scc' '.cfg'):
sources_list.append(s)
elif base and base in 'defconfig':
sources_list.append(s)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index d1c2ee4..754ebe5 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM =
"file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
DEPENDS = "git-native guilt-native"
-SRCREV = "67bcedda582b2b191f26ec47dd1d4eac37f1305c"
+SRCREV = "2bbbaaa00cc70887d6d6f745b9425890d522d240"
PR = "r12"
PV = "0.1+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] linux-yocto/meta: beagleboard: disable CONFIG_PREEMPT
Updating the meta SRCREV for both the 3.0 and 3.2 kernel trees to
pickup the beagleboard xM boot fix:
[
meta/beagleboard: disable CONFIG_PREEMPT
The boot hangs with the message:
mmc0: error -110 whilst initialising SD card
The MMC driver has issues initializing when PREEMPT is enabled (either
forced
or voluntary). Unplugging and then plugging the card back will reset the
driver and continue booting. Alternatively, disable preemption.
]
[YOCTO: #1892]
Signed-off-by: Denys Dmytriyenko
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.0.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
index d8644b7..10459f3 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
@@ -16,7 +16,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
SRCREV_machine ?= "cf280f1dc5877d4ca43d21307222326efa68bb27"
SRCREV_machine_qemuppc ?= "afaa5baa6a9ca9c8a03a9a3eee2ba9fba089f416"
-SRCREV_meta ?= "a4ac64fe873f08ef718e2849b88914725dc99c1c"
+SRCREV_meta ?= "bb4fff95b3d28c8ab87cd6905eaef86e1f46db6e"
PR = "r2"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index efc4611..aae4ce0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -16,7 +16,7 @@ LINUX_KERNEL_TYPE = "preempt-rt"
SRCREV_machine ?= "32ecb53e9ff759bbd297a10712b62a6575daaf86"
SRCREV_machine_qemuppc ?= "0d5625bb868cc2471d5dd49eb7abe7eb5fe1044b"
-SRCREV_meta ?= "135c75bf9615334b5b8bb9108d612fe7dfbdb901"
+SRCREV_meta ?= "ad5a00b6c5bcdd1740d8fa42be122fc8ff2c579f"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index fbff706..6c65707 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -12,7 +12,7 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.11"
SRCREV_machine ?= "ec236058dc254183dbfb3744bf21f110c37af30b"
-SRCREV_meta ?= "135c75bf9615334b5b8bb9108d612fe7dfbdb901"
+SRCREV_meta ?= "ad5a00b6c5bcdd1740d8fa42be122fc8ff2c579f"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
index e56e1d7..0d98074 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
@@ -18,7 +18,7 @@ SRCREV_machine_qemuppc ?=
"7528f1d06ef5665eed8c1498f62d5403b82bbbd6"
SRCREV_machine_qemux86 ?= "f153b0eb8264dc1e69f59d4c9173619feb4d5bd9"
SRCREV_machine_qemux86-64 ?= "aac580659dc0ce083f250fb05abf82e58d7f4531"
SRCREV_machine ?= "da7c40006b08916ff3a3db104def82aaf9ac2716"
-SRCREV_meta ?= "a4ac64fe873f08ef718e2849b88914725dc99c1c"
+SRCREV_meta ?= "bb4fff95b3d28c8ab87cd6905eaef86e1f46db6e"
PR = "r4"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index 8bea0a0..54361a2 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemuppc ?=
"92de4e2f3c6b397c8b363e079cc4d5e9bcadf877"
SRCREV_machine_qemux86 ?= "8ada1bb97415fe959a57a08504be4eb8a656ed30"
SRCREV_machine_qemux86-64 ?= "4ca7e2c5d42e755e1b4c3e1478128f047a8ed2a8"
SRCREV_machine ?= "01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a"
-SRCREV_meta ?= "135c75bf9615334b5b8bb9108d612fe7dfbdb901"
+SRCREV_meta ?= "ad5a00b6c5bcdd1740d8fa42be122fc8ff2c579f"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [oe] [meta-oe][PATCH] kernel bbclass: recreate uImage unless KEEPUIMAGE is set
On 12-04-27 4:06 AM, Koen Kooi wrote:
The intent of the uImage code in this class includes the following
1) be able to specify custom load addresses without needing to patch the kernel
2) add better information to the uImage description field
The current state is a NOP anyway, the kernel will always build a uImage when
you tell it to 'make uImage'.
Signed-off-by: Koen Kooi
---
meta-oe/classes/kernel.bbclass |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/classes/kernel.bbclass b/meta-oe/classes/kernel.bbclass
index b7e9f54..98320fe 100644
--- a/meta-oe/classes/kernel.bbclass
+++ b/meta-oe/classes/kernel.bbclass
@@ -512,7 +512,7 @@ KERNEL_IMAGE_SYMLINK_NAME ?=
"${KERNEL_IMAGETYPE}-${MACHINE}"
do_uboot_mkimage() {
if test "x${KERNEL_IMAGETYPE}" = "xuImage" ; then
- if test ! -e arch/${ARCH}/boot/uImage ; then
+ if test "x${KEEPUIMAGE}" = "x" ; then
I realize this is targeted meta-oe, and not directly to oe-core (but
openembedded-core is cc'd + it's Saturday morning with no coffee here
yet which means I may be misreading) .. so I thought I'd comment as
this whizzed past.
The existing users on top of the oe-core class expect (whether they
know it or not) the opposite of this (i.e. do nothing, get the kernel's
uImage). To keep their old behaviour, they now need to explicitly set a
flag. I know that I'd have quite a few layers to update if this went
directly into oe-core.
How are the current meta-oe and related BSPs currently overriding
the behaviour (I didn't go look, I'm invoking my Saturday morning clause
again :) ? Is it a class override ? If so, can the layers that
currently have an override set a flag (which is a simpler override) to
get the behaviour they used to have, while leaving the boards with no
override the behaviour that they used to have ?
Cheers,
Bruce
ENTRYPOINT=${UBOOT_ENTRYPOINT}
if test -n "${UBOOT_ENTRYSYMBOL}"; then
ENTRYPOINT=`${HOST_PREFIX}nm ${S}/vmlinux | \
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [oe] [meta-oe][PATCH] kernel bbclass: recreate uImage unless KEEPUIMAGE is set
On Sat, Apr 28, 2012 at 10:57 AM, Koen Kooi wrote:
>
> Op 28 apr. 2012, om 16:32 heeft Bruce Ashfield het volgende geschreven:
>
>> On 12-04-27 4:06 AM, Koen Kooi wrote:
>>> The intent of the uImage code in this class includes the following
>>>
>>> 1) be able to specify custom load addresses without needing to patch the
>>> kernel
>>> 2) add better information to the uImage description field
>>>
>>> The current state is a NOP anyway, the kernel will always build a uImage
>>> when you tell it to 'make uImage'.
>>>
>>> Signed-off-by: Koen Kooi
>>> ---
>>> meta-oe/classes/kernel.bbclass | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/meta-oe/classes/kernel.bbclass b/meta-oe/classes/kernel.bbclass
>>> index b7e9f54..98320fe 100644
>>> --- a/meta-oe/classes/kernel.bbclass
>>> +++ b/meta-oe/classes/kernel.bbclass
>>> @@ -512,7 +512,7 @@ KERNEL_IMAGE_SYMLINK_NAME ?=
>>> "${KERNEL_IMAGETYPE}-${MACHINE}"
>>>
>>> do_uboot_mkimage() {
>>> if test "x${KERNEL_IMAGETYPE}" = "xuImage" ; then
>>> - if test ! -e arch/${ARCH}/boot/uImage ; then
>>> + if test "x${KEEPUIMAGE}" = "x" ; then
>>
>> I realize this is targeted meta-oe, and not directly to oe-core (but
>> openembedded-core is cc'd + it's Saturday morning with no coffee here
>> yet which means I may be misreading) .. so I thought I'd comment as
>> this whizzed past.
>>
>> The existing users on top of the oe-core class expect (whether they
>> know it or not) the opposite of this (i.e. do nothing, get the kernel's
>> uImage). To keep their old behaviour, they now need to explicitly set a
>> flag. I know that I'd have quite a few layers to update if this went
>> directly into oe-core.
>>
>> How are the current meta-oe and related BSPs currently overriding
>> the behaviour (I didn't go look, I'm invoking my Saturday morning clause
>> again :) ? Is it a class override ? If so, can the layers that
>> currently have an override set a flag (which is a simpler override) to
>> get the behaviour they used to have, while leaving the boards with no
>> override the behaviour that they used to have ?
>
> "used to have" is quite vague, since the OE-classic behaviour is to always
> replace the uImage. And that's where I'm migrating machines from.
That's why I referenced oe-core, that's all I'm talking about. It's
behaviour for
every tagged release has been what I'm talking about. This is a change in
that behaviour, and if that's the intended target for this, it is relevant.
Cheers,
Bruce
>
>
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto/3.2: configuration and pch merge
Updating the 3.2 SRCREVs to import the following meta/config
changes:
6b3d4e0 meta: add mei feature
519abac meta: add usb/uhci-hcd feature
a67c5a3 meta/crownbay: use usb features
0855066 meta: add usb/ohci-hcd feature
15f1a99 meta: add usb/ehci-hcd feature
8fa6408 meta: add usb/xhci-hcd feature
c724a55 meta: add usb/base feature
b55b3a1 sys940x: Cleanup sys940x.scc
93f2e97 sys940x: Use PHYSICAL_START of 0x20 to boot
aaa034b sys940x: Add common standard and preempt-rt features
e2b1286 sys940x: Add efi-ext to standard and preempt-rt configs
d188c21 sys940x: Move emgd-1.10 data to the standard scc file
72d9369 fri2: Cleanup fri2-$KTYPE.scc files re efi-ext.scc
dbcb120 fri2: Use emgd-1.10 feature and branch
And the following driver fix:
f39a0a9 pch_gbe: Do not abort probe on bad MAC
Signed-off-by: Darren Hart
Signed-off-by: Tom Zanussi
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |4 ++--
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 14 +++---
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index 05674ef..7e01efb 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -14,9 +14,9 @@ KBRANCH_qemuppc = "standard/preempt-rt/qemu-ppc32"
LINUX_VERSION ?= "3.2.11"
LINUX_KERNEL_TYPE = "preempt-rt"
-SRCREV_machine ?= "32ecb53e9ff759bbd297a10712b62a6575daaf86"
-SRCREV_machine_qemuppc ?= "0d5625bb868cc2471d5dd49eb7abe7eb5fe1044b"
-SRCREV_meta ?= "b14a08f5c7b469a5077c10942f4e1aec171faa9d"
+SRCREV_machine ?= "3ebf4d172cf4a41d2abf09e4036f0850e08064e7"
+SRCREV_machine_qemuppc ?= "7cebfe717987f4ffa9ae90558c28f45049847c1c"
+SRCREV_meta ?= "6b3d4e09aa2531e9649f3f03827b7efbccfcec03"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index 4957e33..27de229 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -11,8 +11,8 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.11"
-SRCREV_machine ?= "ec236058dc254183dbfb3744bf21f110c37af30b"
-SRCREV_meta ?= "b14a08f5c7b469a5077c10942f4e1aec171faa9d"
+SRCREV_machine ?= "61960ba8e910d54b5525d5e9b6a7469bc399c246"
+SRCREV_meta ?= "6b3d4e09aa2531e9649f3f03827b7efbccfcec03"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index d81f6b5..51119bb 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -17,13 +17,13 @@ KBRANCH_qemuarm = "standard/default/arm-versatile-926ejs"
LINUX_VERSION ?= "3.2.11"
-SRCREV_machine_qemuarm ?= "dfbba772cbee84125ac1558c904a7dc181445f5f"
-SRCREV_machine_qemumips ?= "0e0c67635b74199d534f75500e5c1654a1219bc6"
-SRCREV_machine_qemuppc ?= "92de4e2f3c6b397c8b363e079cc4d5e9bcadf877"
-SRCREV_machine_qemux86 ?= "8ada1bb97415fe959a57a08504be4eb8a656ed30"
-SRCREV_machine_qemux86-64 ?= "4ca7e2c5d42e755e1b4c3e1478128f047a8ed2a8"
-SRCREV_machine ?= "01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a"
-SRCREV_meta ?= "b14a08f5c7b469a5077c10942f4e1aec171faa9d"
+SRCREV_machine_qemuarm ?= "ba47a1cc9bb6ad576b2ac7adb3036bcfa569fe2e"
+SRCREV_machine_qemumips ?= "3b2fd654392a2f33aed12748548c04e9b169591b"
+SRCREV_machine_qemuppc ?= "cf3e188cf2a18c48a0e6f9ca54c36e6ac39512ec"
+SRCREV_machine_qemux86 ?= "46f1007ad22b6790224c66a8dc4e80fdbd21eea1"
+SRCREV_machine_qemux86-64 ?= "00e5ec2393bada6723bd9a07ded3d001c02fa727"
+SRCREV_machine ?= "f4f8ba730e7783e09413872414d0a17c142c816d"
+SRCREV_meta ?= "6b3d4e09aa2531e9649f3f03827b7efbccfcec03"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] linux-yocto/3.2: queued config and driver fixes
Richard/Saul, I'm clearning out my queued fixes for the 3.2 kernel before following up with my new functional changes and the 3.4 kernel recipe. These have been brewing for a week, and will be used for async layer releases The following changes since commit 7a49d88d22395afffb211045049a17b906219d82: Hob: Clear the building status if command failed (2012-05-07 11:03:01 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-yocto/3.2: configuration and pch merge meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |6 +++--- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |4 ++-- meta/recipes-kernel/linux/linux-yocto_3.2.bb | 14 +++--- 3 files changed, 12 insertions(+), 12 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] kern-tools: integrate minor fixes
Updating the SRCREV to pick up two minor fixes:
1/2:
kgit-init: correct spelling of createme
kgit-init copies the kern-tools scripts and intends to copy createme.
The typo is in the usage() of updateme as well.
Signed-off-by: Michel Thebeau
2/2:
kconf_check: fix bad quoting around missing_required.cfg
missing_required.cfg won't have it's path truncated (if applicable), since
the quoting it wrong.
Signed-off-by: Andrea Adami
Signed-off-by: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
.../kern-tools/kern-tools-native_git.bb|2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 1af22f6..b6fab39 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM =
"file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
DEPENDS = "git-native guilt-native"
-SRCREV = "369e67046a1b72b6447c208babd4d2065265a95e"
+SRCREV = "9bb704df0a86578b8ae1f4c85e45089bef28e026"
PR = "r12"
PV = "0.1+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/2] linux-yocto: streamlined repository support + fixes
Richard/Saul, This pull requests represents some changes that I've been running here for the past 1.5 months. It is a re-working of the tools and recipes to allow more repository types to support the kern tools (branching and fragments). It's one largish patch that consolidates recipe updates, tool changes and streamlining of the patching phase. This is step one, there are several more to follow after this merges into the tree. Namely: - updated documents on what an inheriting recipe needs to do - movement of the linux-yocto-custom recipe from meta-kernel-dev to somewhere more visible - updates to meta-kernel-dev to fix those recipes - removal of the 2.6.37 recipe and introduction of the 3.4 kernel recipe - additional streamlining of the tools (more code deleted!). I've converted the linux-yocto* recipes (except for 2.6.37, since I'll be removing it shortly) and have built 3.0, 3.2 and -dev kernels for all the boards I can. It's ready to go, but can also use a run through a nightly build before it merged (the changes were a bit tricky with a lot of existing use cases to ensure were not broken). FYI: I stacked this on top of my last pull request, let me know if this needs to be rebased. Cheers, Bruce The following changes since commit e116928e3a1af803b9c6fa06236902ad730f7bf8: linux-yocto/3.0: mm/msync: tweak tmpfs patch for syscall msync (2012-05-08 10:18:56 -0400) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel-dev http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-dev Bruce Ashfield (2): linux-yocto: streamline support for multiple upstream repo types kern-tools: integrate minor fixes meta/classes/kernel-yocto.bbclass | 115 ++-- .../kern-tools/kern-tools-native_git.bb|2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb|1 + meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb|2 + meta/recipes-kernel/linux/linux-yocto.inc |7 +- meta/recipes-kernel/linux/linux-yocto_2.6.37.bb|2 + meta/recipes-kernel/linux/linux-yocto_3.0.bb | 23 +++-- meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 + 8 files changed, 86 insertions(+), 68 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] linux-yocto: streamline support for multiple upstream repo types
In order to support repositories of various types (with or without
meta data, branched, pristine, custom, etc) information about the
type of processing that is required was passed to the processing
phases via variables.
The combination of variables involved in coordinating the processing
creates a learning curve and overly complicates recipe extensions.
With minor tweaks to the kern-tools, adding flexibility and keying
off the existence of the meta branch it is possible to remove all
of the variables that were added to support different repository
types.
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel-yocto.bbclass | 115 ++--
.../kern-tools/kern-tools-native_git.bb|2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb|1 +
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb|2 +
meta/recipes-kernel/linux/linux-yocto.inc |7 +-
meta/recipes-kernel/linux/linux-yocto_2.6.37.bb|2 +
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 23 +++--
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +
8 files changed, 86 insertions(+), 68 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index c995a2e..c6425b2 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -45,9 +45,6 @@ def find_urls(d):
do_patch() {
cd ${S}
- if [ -f ${WORKDIR}/defconfig ]; then
- defconfig=${WORKDIR}/defconfig
- fi
# if kernel tools are available in-tree, they are preferred
# and are placed on the path before any external tools. Unless
@@ -59,16 +56,13 @@ do_patch() {
fi
kbranch=${KBRANCH}
- if [ -n "${YOCTO_KERNEL_EXTERNAL_BRANCH}" ]; then
- # switch from a generic to a specific branch
- kbranch=${YOCTO_KERNEL_EXTERNAL_BRANCH}
- fi
- # simply ensures that a branch of the right name has been created
- if [ -n "${YOCTO_KERNEL_META_DATA}" ]; then
+ # if we have a defined/set meta branch we should not be generating
+ # any meta data. The passed branch has what we need.
+ if [ -n "${KMETA}" ]; then
createme_flags="--disable-meta-gen"
fi
- createme ${createme_flags} ${ARCH} ${kbranch} ${defconfig}
+ createme ${createme_flags} ${ARCH} ${kbranch}
if [ $? -ne 0 ]; then
echo "ERROR. Could not create ${kbranch}"
exit 1
@@ -95,7 +89,7 @@ do_patch() {
fi
# executes and modifies the source tree as required
- patchme ${kbranch}
+ patchme ${KMACHINE}
if [ $? -ne 0 ]; then
echo "ERROR. Could not modify ${kbranch}"
exit 1
@@ -122,7 +116,7 @@ do_kernel_checkout() {
mv ${WORKDIR}/git/.git ${S}
rm -rf ${WORKDIR}/git/
cd ${S}
- if [ -n "${YOCTO_KERNEL_META_DATA}" ] && [ -n "${KMETA}" ]; then
+ if [ -n "${KMETA}" ]; then
git branch -a | grep -q ${KMETA}
if [ $? -ne 0 ]; then
echo "ERROR. The branch '${KMETA}' is required
and was not"
@@ -131,15 +125,6 @@ do_kernel_checkout() {
exit 1
fi
fi
- if [ -z "${YOCTO_KERNEL_EXTERNAL_BRANCH}" ] && [ -n
"${KBRANCH}" ] ; then
- git branch -a | grep -q ${KBRANCH}
- if [ $? -ne 0 ]; then
- echo "ERROR. The branch '${KBRANCH}' is
required and was not"
- echo "found. Ensure that the SRC_URI points to
a valid linux-yocto"
- echo "kernel repository"
- exit 1
- fi
- fi
fi
if [ -d "${WORKDIR}/git/" ] && [ ! -d "${WORKDIR}/git/.git" ]; then
# we build out of {S}, so ensure that ${S} is clean and present
@@ -192,7 +177,7 @@ do_kernel_configme() {
cd ${S}
PATH=${PATH}:${S}/scripts/util
- configme ${configmeflags} --reconfig --output ${B} ${KBRANCH}
${KMACHINE}
+ configme ${configmeflags} --reconfig --output ${B} ${LINUX_KERNEL_TYPE}
${KMACHINE}
if [ $? -ne 0 ]; then
echo "ERROR. Could not configure
${KMACHINE}-${LINUX_KERNEL_TYPE}"
exit 1
@@ -221,51 +206,71 @@ python do_kernel_configcheck() {
do_validate_branches() {
cd ${S}
- # nothing to do if bootstrapping
- if [ -n "${YOCTO_KERNEL_EXTERNAL_BRANCH}" ]; then
- return
- fi
-
- # nothing to do if SRC
[OE-core] [PATCH 0/1] kernel-yocto: export GUILT_BASE
Richard/Saul, As Frans Meulenbroeks noted this morning, guilt wasn't functional in the devshell. The fix was simple enough, and by ensuring that GUILT_BASE is exported, it works without any extra steps now. I wasn't sure if there a better way to call 'up' to the base method, so I repeated the call to oe_terminal in the do_devshell() in kernel-yocto.bbclass. If there's another approach, let me know and I'll respin the patch. Cheers, Bruce The following changes since commit b1867950831ab6edb00b819f4cde81d40007f22e: Bruce Ashfield (1): meta-yocto/linux-yocto-3.0: update branch mappings for new tools are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): kernel-yocto: export GUILT_BASE meta/classes/kernel-yocto.bbclass |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] kernel-yocto: export GUILT_BASE
One of the patch backends to linux-yocto is guilt, which normally
tracks patches under .git. But .git isn't something that can be
checked into a SCM and repeated. So it has been moved under meta/patches
and committed to the meta branch.
If devshell is used, GUILT_BASE isn't set, so patch manipulations will
fail. We export GUILT_BASE and point it at the meta directory when
devshell is invoked for linux-yocto.
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel-yocto.bbclass |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index c6425b2..fb9dce1 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -290,4 +290,10 @@ do_kernel_link_vmlinux() {
ln -sf ../../../vmlinux
}
+OE_TERMINAL_EXPORTS += "GUILT_BASE"
+python do_devshell () {
+d.setVar("GUILT_BASE", "meta")
+oe_terminal( d.getVar('SHELL', True), 'OpenEmbedded Developer Shell', d)
+}
+
--
1.7.0.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] kern-tools: fix meta-intel builds
Richard/Saul, This fixes a problem reported by Tom and Darren when the latest tools updates were used against meta intel. Some optional code that supported merge meta and BSP branches wasn't handling the case where a BSP layer might not be tracking the HEAD of the meta branch, and hence blowing up its test to see if the meta branch needs to be thawed. The fix was simple. Adjust the threshold for declaring the meta content global. cc: Tom Zanussi cc: Darren Hart Cheers, Bruce The following changes since commit 8afd5747802c4eb0e8296e440bd7366393595f8e: Bruce Ashfield (1): kernel-yocto: export GUILT_BASE are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kern-tools http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kern-tools Bruce Ashfield (1): kern-tools: checkpoint restoration for reset branches .../kern-tools/kern-tools-native_git.bb|2 +- 1 files changed, 1 insertions(+), 1 deletions(-) ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] kern-tools: checkpoint restoration for reset branches
Updating the SRCREV to pickup the following fix:
createme: fix checkpoint restoration for reset branches
The meta branch can optionally be merged out to BSP branches. This removes
the need to restore the checkpoint when working with the tree. The way
it detects the merge is by checking to see how many branches contain the
meta data. If there's more than one, the branch was was merged out.
Unless you are a BSP that isn't tracking the latest meta, and you get
meta and meta-orig created. That's two branches and the code opts to not
restore the checkpoint, which leads to configuration errors.
The fix is simple. We allow for 2 or less branches with meta, and will
still restore the checkpoint. Three and up, we won't.
Signed-off-by: Bruce Ashfield
---
.../kern-tools/kern-tools-native_git.bb|2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index b6fab39..b5e203e 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM =
"file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
DEPENDS = "git-native guilt-native"
-SRCREV = "9bb704df0a86578b8ae1f4c85e45089bef28e026"
+SRCREV = "de3649840e8e3ca25bc79d2444f04a1b158a1769"
PR = "r12"
PV = "0.1+git${SRCPV}"
--
1.7.0.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1] kernel-yocto: export GUILT_BASE
On Wed, May 9, 2012 at 2:51 AM, Richard Purdie wrote: > On Tue, 2012-05-08 at 15:23 -0400, Bruce Ashfield wrote: >> Richard/Saul, >> >> As Frans Meulenbroeks noted this morning, guilt wasn't functional >> in the devshell. The fix was simple enough, and by ensuring that >> GUILT_BASE is exported, it works without any extra steps now. >> >> I wasn't sure if there a better way to call 'up' to the base >> method, so I repeated the call to oe_terminal in the do_devshell() >> in kernel-yocto.bbclass. >> >> If there's another approach, let me know and I'll respin the patch. > > Can't you just set: > > GUILT_BASE = "meta" Will that export to the subshell ? I didn't try it .. since I didn't think it would. I'll give that a go here :) Bruce > > ? > > Cheers, > > Richard > > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-commits] Bruce Ashfield : kern-tools: integrate minor fixes
On Wed, May 9, 2012 at 6:58 AM, Martin Jansa wrote: > On Tue, May 08, 2012 at 03:14:10PM +, g...@git.openembedded.org wrote: >> Module: openembedded-core.git >> Branch: master >> Commit: 043871d7e5d2d19c2ff43e54d2ff180c09e8903e >> URL: >> http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=043871d7e5d2d19c2ff43e54d2ff180c09e8903e >> >> Author: Bruce Ashfield >> Date: Mon Apr 30 00:02:17 2012 -0400 >> >> kern-tools: integrate minor fixes >> >> Updating the SRCREV to pick up two minor fixes: >> >> 1/2: >> kgit-init: correct spelling of createme >> >> kgit-init copies the kern-tools scripts and intends to copy createme. >> >> The typo is in the usage() of updateme as well. >> >> Signed-off-by: Michel Thebeau >> >> 2/2: >> kconf_check: fix bad quoting around missing_required.cfg >> >> missing_required.cfg won't have it's path truncated (if applicable), >> since >> the quoting it wrong. >> >> Signed-off-by: Andrea Adami >> Signed-off-by: Bruce Ashfield >> >> Signed-off-by: Bruce Ashfield > > No idea if this is new issue or just old issue now revealed by those > fixes, but linux-yocto-3.2 now fails to build for qemux86-64 (at > least here). It's an old issue, but the second patch I sent last night is the fix. Bruce > > NOTE: package > linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1: > task do_patch: Started > ERROR: Function failed: do_patch (see > /OE/shr-core/tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto/linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1/temp/log.do_patch.32134 > for further information) > ERROR: Logfile of failure stored in: > /OE/shr-core/tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto/linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1/temp/log.do_patch.32134 > Log data follows: > | ERROR: Function failed: do_patch (see > /OE/shr-core/tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto/linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1/temp/log.do_patch.32134 > for further information) > | WARNING: addon feature "features/netfilter" was not found > | WARNING: addon feature "features/taskstats" was not found > | WARNING: addon feature "cfg/sound" was not found > | ERROR: required features were not found. aborting > | ERROR. Could not update standard/default/common-pc-64/base > NOTE: package > linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1: > task do_patch: Failed > > Cheers, > > -- > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-commits] Bruce Ashfield : kern-tools: integrate minor fixes
On Wed, May 9, 2012 at 8:55 AM, Martin Jansa wrote: > On Wed, May 09, 2012 at 08:43:50AM -0400, Bruce Ashfield wrote: >> On Wed, May 9, 2012 at 6:58 AM, Martin Jansa wrote: >> > On Tue, May 08, 2012 at 03:14:10PM +, g...@git.openembedded.org wrote: >> >> Module: openembedded-core.git >> >> Branch: master >> >> Commit: 043871d7e5d2d19c2ff43e54d2ff180c09e8903e >> >> URL: >> >> http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=043871d7e5d2d19c2ff43e54d2ff180c09e8903e >> >> >> >> Author: Bruce Ashfield >> >> Date: Mon Apr 30 00:02:17 2012 -0400 >> >> >> >> kern-tools: integrate minor fixes >> >> >> >> Updating the SRCREV to pick up two minor fixes: >> >> >> >> 1/2: >> >> kgit-init: correct spelling of createme >> >> >> >> kgit-init copies the kern-tools scripts and intends to copy createme. >> >> >> >> The typo is in the usage() of updateme as well. >> >> >> >> Signed-off-by: Michel Thebeau >> >> >> >> 2/2: >> >> kconf_check: fix bad quoting around missing_required.cfg >> >> >> >> missing_required.cfg won't have it's path truncated (if applicable), >> >> since >> >> the quoting it wrong. >> >> >> >> Signed-off-by: Andrea Adami >> >> Signed-off-by: Bruce Ashfield >> >> >> >> Signed-off-by: Bruce Ashfield >> > >> > No idea if this is new issue or just old issue now revealed by those >> > fixes, but linux-yocto-3.2 now fails to build for qemux86-64 (at >> > least here). >> >> It's an old issue, but the second patch I sent last night is the fix. > > This one? > http://patchwork.openembedded.org/patch/27337/ Yep. I built several hundred (no exaggeration) qemu* builds with the series in place, and of course, my meta SRCREV always matches the head of the meta branch, so that never triggered. A clean build works here for all boards with that in place. If that doesn't fix it for you .. I'll definitely want to hear. Bruce > > Thanks > >> >> Bruce >> >> > >> > NOTE: package >> > linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1: >> > task do_patch: Started >> > ERROR: Function failed: do_patch (see >> > /OE/shr-core/tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto/linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1/temp/log.do_patch.32134 >> > for further information) >> > ERROR: Logfile of failure stored in: >> > /OE/shr-core/tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto/linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1/temp/log.do_patch.32134 >> > Log data follows: >> > | ERROR: Function failed: do_patch (see >> > /OE/shr-core/tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto/linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1/temp/log.do_patch.32134 >> > for further information) >> > | WARNING: addon feature "features/netfilter" was not found >> > | WARNING: addon feature "features/taskstats" was not found >> > | WARNING: addon feature "cfg/sound" was not found >> > | ERROR: required features were not found. aborting >> > | ERROR. Could not update standard/default/common-pc-64/base >> > NOTE: package >> > linux-yocto-3.2.11+git10+6b3d4e09aa2531e9649f3f03827b7efbccfcec03_7+00e5ec2393bada6723bd9a07ded3d001c02fa727-r1: >> > task do_patch: Failed >> > >> > Cheers, >> > >> > -- >> > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com >> > >> > ___ >> > Openembedded-core mailing list >> > Openembedded-core@lists.openembedded.org >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> > >> >> >> >> -- >> "Thou shalt not follow the NULL pointer, for chaos and madness await >> thee at its end" >> >> ___ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > > -- > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1] kernel-yocto: export GUILT_BASE
On Wed, May 9, 2012 at 8:42 AM, Bruce Ashfield wrote: > On Wed, May 9, 2012 at 2:51 AM, Richard Purdie > wrote: >> On Tue, 2012-05-08 at 15:23 -0400, Bruce Ashfield wrote: >>> Richard/Saul, >>> >>> As Frans Meulenbroeks noted this morning, guilt wasn't functional >>> in the devshell. The fix was simple enough, and by ensuring that >>> GUILT_BASE is exported, it works without any extra steps now. >>> >>> I wasn't sure if there a better way to call 'up' to the base >>> method, so I repeated the call to oe_terminal in the do_devshell() >>> in kernel-yocto.bbclass. >>> >>> If there's another approach, let me know and I'll respin the patch. >> >> Can't you just set: >> >> GUILT_BASE = "meta" > > Will that export to the subshell ? I didn't try it .. since I didn't > think it would. > I'll give that a go here :) With just that set in kernel-yocto.bbclass, and I launch devshell, I get this: % guilt applied Patches directory doesn't exist, try guilt-init So unless I misunderstood what you are suggesting, I still need that explicit export. Cheers, Bruce > > Bruce > >> >> ? >> >> Cheers, >> >> Richard >> >> >> ___ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] kern-tools: checkpoint restoration for reset branches
On Wed, May 9, 2012 at 11:40 AM, Darren Hart wrote:
>
>
> On 05/08/2012 08:48 PM, Bruce Ashfield wrote:
>> Updating the SRCREV to pickup the following fix:
>>
>> createme: fix checkpoint restoration for reset branches
>>
>> The meta branch can optionally be merged out to BSP branches. This
>> removes
>> the need to restore the checkpoint when working with the tree. The way
>> it detects the merge is by checking to see how many branches contain the
>> meta data. If there's more than one, the branch was was merged out.
>>
>> Unless you are a BSP that isn't tracking the latest meta, and you get
>> meta and meta-orig created. That's two branches and the code opts to not
>> restore the checkpoint, which leads to configuration errors.
>>
>> The fix is simple. We allow for 2 or less branches with meta, and will
>> still restore the checkpoint. Three and up, we won't.
>>
>
> Uhm... am I the only one for whom this language is really confusing?
> "merged out" ?
> "restore the checkpoint" ?
I could be more verbose, but it's like reading a kernel -mm commit. I
don't grok everything they write, but they aren't writing it for me as a
-mm newbie.
> Why does a BSP using a different meta SRCREV get two meta branches?
>
> The fix of incrementing the allowed count of meta branches honestly
> feels like a bandaid. Why do we create two in the first place?
do_validate_branches() has to check if the HEAD of meta matches the meta
SRCREV that the BSP defines. If they don't match, it saves the old branch
as $branch-orig. So you have two branches, with the base meta commit
(which is what is tested). I don't want to destroy any branches, since there
is value in keeping them around.
The tools are actually separate to the bitbake bindings, so they don't expect
this to happen. I could destroy the old branch in do_validate_branches, but
that's not a solution I particularly liked. It was easier to add some
flexibility to
the tools.
Cheers,
Bruce
>
> Regardless, this is a blocker for working with meta-intel, so we need
> this in. But it does seem to me that a more direct solution may be
> needed. Bruce, can you help fill me in re. the above?
>
> --
> Darren
>
>> Signed-off-by: Bruce Ashfield
>> ---
>> .../kern-tools/kern-tools-native_git.bb | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> index b6fab39..b5e203e 100644
>> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM =
>> "file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
>>
>> DEPENDS = "git-native guilt-native"
>>
>> -SRCREV = "9bb704df0a86578b8ae1f4c85e45089bef28e026"
>> +SRCREV = "de3649840e8e3ca25bc79d2444f04a1b158a1769"
>> PR = "r12"
>> PV = "0.1+git${SRCPV}"
>>
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] kern-tools: checkpoint restoration for reset branches
On Wed, May 9, 2012 at 12:02 PM, Phil Blundell wrote: > On Wed, 2012-05-09 at 11:48 -0400, Bruce Ashfield wrote: >> On Wed, May 9, 2012 at 11:40 AM, Darren Hart wrote: >> > >> > >> > On 05/08/2012 08:48 PM, Bruce Ashfield wrote: >> >> Updating the SRCREV to pickup the following fix: >> >> >> >> createme: fix checkpoint restoration for reset branches >> >> >> >> The meta branch can optionally be merged out to BSP branches. This >> >> removes >> >> the need to restore the checkpoint when working with the tree. The >> >> way >> >> it detects the merge is by checking to see how many branches contain >> >> the >> >> meta data. If there's more than one, the branch was was merged out. >> >> >> >> Unless you are a BSP that isn't tracking the latest meta, and you get >> >> meta and meta-orig created. That's two branches and the code opts to >> >> not >> >> restore the checkpoint, which leads to configuration errors. >> >> >> >> The fix is simple. We allow for 2 or less branches with meta, and will >> >> still restore the checkpoint. Three and up, we won't. >> >> >> > >> > Uhm... am I the only one for whom this language is really confusing? >> > "merged out" ? >> > "restore the checkpoint" ? >> >> I could be more verbose, but it's like reading a kernel -mm commit. I >> don't grok everything they write, but they aren't writing it for me as a >> -mm newbie. > > So, who exactly is the target audience for the above text? I'm not sure > that "really confusing" does it justice: from my point of view (though > admittedly I am very far from being an eleet k3rn3l h4x0r) it just looks > like gibberish. If it's going into oe-core then I would have hoped that > the checkin comment would be intelligible to oe-core users at large, not > just those who are schooled in the mysterious ways of some particular > subgroup. It's a quote from the kern-tools commit log. I could just put: 'fixes stuff', but that's not good either. Writing a novel isn't good either. I'm not sure why everyone is having such an issue with this, there's many other examples of commits like this, and everyone sits in a glass house in this regard. I can re-work it of course, I wrote it very late at night to fix a fairly blocking bug, so everyone cutting a little bit of slack would be appreciated. Cheers, Bruce > > p. > > > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] kern-tools: checkpoint restoration for reset branches
On Wed, May 9, 2012 at 12:11 PM, Bruce Ashfield wrote: > On Wed, May 9, 2012 at 12:02 PM, Phil Blundell wrote: >> On Wed, 2012-05-09 at 11:48 -0400, Bruce Ashfield wrote: >>> On Wed, May 9, 2012 at 11:40 AM, Darren Hart wrote: >>> > >>> > >>> > On 05/08/2012 08:48 PM, Bruce Ashfield wrote: >>> >> Updating the SRCREV to pickup the following fix: >>> >> >>> >> createme: fix checkpoint restoration for reset branches >>> >> >>> >> The meta branch can optionally be merged out to BSP branches. This >>> >> removes >>> >> the need to restore the checkpoint when working with the tree. The >>> >> way >>> >> it detects the merge is by checking to see how many branches contain >>> >> the >>> >> meta data. If there's more than one, the branch was was merged out. >>> >> >>> >> Unless you are a BSP that isn't tracking the latest meta, and you get >>> >> meta and meta-orig created. That's two branches and the code opts to >>> >> not >>> >> restore the checkpoint, which leads to configuration errors. >>> >> >>> >> The fix is simple. We allow for 2 or less branches with meta, and >>> >> will >>> >> still restore the checkpoint. Three and up, we won't. >>> >> >>> > >>> > Uhm... am I the only one for whom this language is really confusing? >>> > "merged out" ? >>> > "restore the checkpoint" ? >>> >>> I could be more verbose, but it's like reading a kernel -mm commit. I >>> don't grok everything they write, but they aren't writing it for me as a >>> -mm newbie. >> >> So, who exactly is the target audience for the above text? I'm not sure >> that "really confusing" does it justice: from my point of view (though >> admittedly I am very far from being an eleet k3rn3l h4x0r) it just looks >> like gibberish. If it's going into oe-core then I would have hoped that >> the checkin comment would be intelligible to oe-core users at large, not >> just those who are schooled in the mysterious ways of some particular >> subgroup. > > It's a quote from the kern-tools commit log. I could just put: 'fixes stuff', > but that's not good either. Writing a novel isn't good either. > > I'm not sure why everyone is having such an issue with this, there's many > other examples of commits like this, and everyone sits in a glass house > in this regard. > > I can re-work it of course, I wrote it very late at night to fix a I rewrote the SRCREV update commit into something more legible. It's on the same branch as the original pull request. Cheers, Bruce > fairly blocking > bug, so everyone cutting a little bit of slack would be appreciated. > > Cheers, > > Bruce > >> >> p. >> >> >> >> ___ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1] kernel-yocto: export GUILT_BASE
On Wed, May 9, 2012 at 4:04 PM, Richard Purdie wrote: > On Wed, 2012-05-09 at 09:08 -0400, Bruce Ashfield wrote: >> On Wed, May 9, 2012 at 8:42 AM, Bruce Ashfield >> wrote: >> > On Wed, May 9, 2012 at 2:51 AM, Richard Purdie >> > wrote: >> >> On Tue, 2012-05-08 at 15:23 -0400, Bruce Ashfield wrote: >> >>> Richard/Saul, >> >>> >> >>> As Frans Meulenbroeks noted this morning, guilt wasn't functional >> >>> in the devshell. The fix was simple enough, and by ensuring that >> >>> GUILT_BASE is exported, it works without any extra steps now. >> >>> >> >>> I wasn't sure if there a better way to call 'up' to the base >> >>> method, so I repeated the call to oe_terminal in the do_devshell() >> >>> in kernel-yocto.bbclass. >> >>> >> >>> If there's another approach, let me know and I'll respin the patch. >> >> >> >> Can't you just set: >> >> >> >> GUILT_BASE = "meta" >> > >> > Will that export to the subshell ? I didn't try it .. since I didn't >> > think it would. >> > I'll give that a go here :) >> >> With just that set in kernel-yocto.bbclass, and I launch devshell, I get >> this: >> >> % guilt applied >> Patches directory doesn't exist, try guilt-init >> >> So unless I misunderstood what you are suggesting, I still need that explicit >> export. > > Sorry, let me be more clear. I meant does: > > OE_TERMINAL_EXPORTS += "GUILT_BASE" > GUILT_BASE = "meta" Aha. Yes. That does work, since the setVar does that same thing :) I can drop my devshell override and it works. I'll update my patch and push it back to the branch in the pull request. Bruce > > work? > > I'm not sure we need everything in the original patch... > > Cheers, > > Richard > > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] linux-yocto: intel BSP config changes
Updating the meta SRCREV for the following fixes:
1dfd60f meta/fishriver: move smp options from recipe-space
012780a meta/emenlow: move smp options from recipe-space
b59b1a5 meta/crownbay: move smp options from recipe-space
74dc6ac meta/sugarbay: remove boot-live options
a4bedcb meta/jasperforest: remove boot-live options
4ae7b81 meta/sugarbay: use usb features
30e7e8c meta/jasperforest: use usb features
22d0c5d meta/fishriver: use usb features
e262965 meta/emenlow: use usb features
Signed-off-by: Tom Zanussi
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index 8ec366c..4a1101e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -18,7 +18,7 @@ KMETA = "meta"
SRCREV_machine ?= "3ebf4d172cf4a41d2abf09e4036f0850e08064e7"
SRCREV_machine_qemuppc ?= "7cebfe717987f4ffa9ae90558c28f45049847c1c"
-SRCREV_meta ?= "6b3d4e09aa2531e9649f3f03827b7efbccfcec03"
+SRCREV_meta ?= "1dfd60fa1250259eed38ae5b2840eb37e3758a1b"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index 27de229..5d6450e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -12,7 +12,7 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.11"
SRCREV_machine ?= "61960ba8e910d54b5525d5e9b6a7469bc399c246"
-SRCREV_meta ?= "6b3d4e09aa2531e9649f3f03827b7efbccfcec03"
+SRCREV_meta ?= "1dfd60fa1250259eed38ae5b2840eb37e3758a1b"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index 71290bd..cdd59f0 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemuppc ?=
"cf3e188cf2a18c48a0e6f9ca54c36e6ac39512ec"
SRCREV_machine_qemux86 ?= "46f1007ad22b6790224c66a8dc4e80fdbd21eea1"
SRCREV_machine_qemux86-64 ?= "00e5ec2393bada6723bd9a07ded3d001c02fa727"
SRCREV_machine ?= "f4f8ba730e7783e09413872414d0a17c142c816d"
-SRCREV_meta ?= "6b3d4e09aa2531e9649f3f03827b7efbccfcec03"
+SRCREV_meta ?= "1dfd60fa1250259eed38ae5b2840eb37e3758a1b"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/3] linux-yocto/tools: consolidated pull request
Richard/Saul, Just clearing my queue before I head out of the office next week, and I want all the stable updates + 3.4 introduction to be clear of these smaller changes. These have been cooking for a bit, and are largely configuration cleanup and factoring done by Tom. The other is a minor license tweak for the kern-tools package. Everything builds and looks sane here. Cheers, Bruce (this is based on my poky-contrib, since my oe-core clone to this machine has stalled and I'm done waiting for it :). The following changes since commit d4e265661517f8dd4e1648fdc56bac5973f986f6: poky.conf: Change WARNS -> ERRORS (2012-05-16 07:35:20 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (3): linux-yocto: intel BSP config changes kern-tools: update LICENSE field to GPLv2 linux-yocto: policy cleanups .../kern-tools/kern-tools-native_git.bb|2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb|2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +- meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +- 4 files changed, 4 insertions(+), 4 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] linux-yocto: policy cleanups
Updating the meta SRCREVs to pickup configuration policy cleanups:
49f931b meta/fishriver: remove redundant features and options
51a6d3f meta/emenlow: remove redundant features and options
101dd7f meta/crownbay: remove redundant features and options
4110ecd meta/sugarbay: remove redundant features and options
0f1304a meta/jasperforest: remove redundant features and options
0a56a3b meta/common-pc-64: factor out SCSI CDROM option
b71938a meta/common-pc-64: use usb-mass-storage feature
0724f40 meta: add scsi cdrom feature
438bca8 meta/common-pc: use usb-mass-storage feature
c970881 meta: factor out SCSI options from the usb-mass-storage feature
4c8135e meta: add scsi disk feature
6872a81 meta: add scsi feature
e706ec5 meta/sugarbay: factor out policy-related options
8b7fbc2 meta/jasperforest: factor out policy-related options
fea1b0e meta/fishriver: factor out policy-related options
13bf9ab meta/emenlow: factor out policy-related options
4748d50 meta/crownbay: factor out policy-related options
44f592f meta/common-pc-64: factor out policy-related options
5a3f5c7 meta/common-pc: factor out policy-related options
1f5a10b meta/common-pc-64: use usb features
4b87723 meta/common-pc: use usb features
594ba05 meta: add ROOT_HUB_TT config option to the usb/ehci-hcd feature
Signed-off-by: Tom Zanussi
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index 4a1101e..b275ad4 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -18,7 +18,7 @@ KMETA = "meta"
SRCREV_machine ?= "3ebf4d172cf4a41d2abf09e4036f0850e08064e7"
SRCREV_machine_qemuppc ?= "7cebfe717987f4ffa9ae90558c28f45049847c1c"
-SRCREV_meta ?= "1dfd60fa1250259eed38ae5b2840eb37e3758a1b"
+SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index 5d6450e..f50e12e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -12,7 +12,7 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.11"
SRCREV_machine ?= "61960ba8e910d54b5525d5e9b6a7469bc399c246"
-SRCREV_meta ?= "1dfd60fa1250259eed38ae5b2840eb37e3758a1b"
+SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index cdd59f0..14de6f4 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemuppc ?=
"cf3e188cf2a18c48a0e6f9ca54c36e6ac39512ec"
SRCREV_machine_qemux86 ?= "46f1007ad22b6790224c66a8dc4e80fdbd21eea1"
SRCREV_machine_qemux86-64 ?= "00e5ec2393bada6723bd9a07ded3d001c02fa727"
SRCREV_machine ?= "f4f8ba730e7783e09413872414d0a17c142c816d"
-SRCREV_meta ?= "1dfd60fa1250259eed38ae5b2840eb37e3758a1b"
+SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] kern-tools: update LICENSE field to GPLv2
The LICENSE field for kern-tools was generic and leads to QA warnings from the license classs: "No generic license file exists for: GPL in any provider" Updating to a specific GPL version that matches the source fixes the warning. Signed-off-by: Bruce Ashfield --- .../kern-tools/kern-tools-native_git.bb|2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb index b5e203e..9ef1a20 100644 --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb @@ -1,5 +1,5 @@ DESCRIPTION = "Scripts and utilities for managing Yocto branched kernels." -LICENSE = "GPL" +LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d843f43d2e22b0d91a6fee" DEPENDS = "git-native guilt-native" -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzan wrote: > Today i ran into an issue that Florin Sarbu signaled sometime last week. It > seems like do_patch crashes while compiling linux 3.0: The tools fixes are in place for this, can you send your full configuration ? i.e. what layers, their head commits, and machine config. Bruce > > ERROR: Logfile of failure stored in: > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/work/vexpressa9-poky-linux-gnueabi/linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4/temp/log.do_patch.10864 > Log data follows: > | Branch meta-temp set up to track remote branch meta from origin. > | git reset --mixed 620917de59eeb934b9f8cf35cc2d95c1ac8ed0fc > | Deleted branch meta-temp (was 620917d). > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 434: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 436: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 437: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 438: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 441: yocto/standard/beagleboard-standard.scc: No such file or directory > | readlink: missing operand > | Try `readlink --help' for more information. > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmERROR: Function failed: > do_patch (see > /media/HDD-WRS/yocto/2012
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzan wrote: > Today i ran into an issue that Florin Sarbu signaled sometime last week. It > seems like do_patch crashes while compiling linux 3.0: > > ERROR: Logfile of failure stored in: > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/work/vexpressa9-poky-linux-gnueabi/linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4/temp/log.do_patch.10864 > Log data follows: > | Branch meta-temp set up to track remote branch meta from origin. > | git reset --mixed 620917de59eeb934b9f8cf35cc2d95c1ac8ed0fc > | Deleted branch meta-temp (was 620917d). > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 434: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 436: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 437: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 438: yocto/standard/beagleboard-standard.scc: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme: > line 441: yocto/standard/beagleboard-standard.scc: No such file or directory > | readlink: missing operand > | Try `readlink --help' for more information. > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc: > line 399: yocto/standard/beagleboard-standard: No such file or directory > | /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmERROR: Function failed: > do_patch (see > /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/work/vexpressa9-poky-linux-gnueabi/linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d16
Re: [OE-core] [RFC][PATCH 00/14] mips64 support and sh4 support
On Mon, May 21, 2012 at 12:35 AM, Khem Raj wrote:
> This patchset adds required bits into metadata for having
> mips64/n64 support. I have tested the core-image-sato and core-image-minimal
> builds and boots on qemumips64 and runs gcc regression testsuite.
> It needs linux-yocto-dev kernel for now which can be obtained from
And as an extra point on this, I have a full _3.4 recipe prep'd, but
vacation reared
it's ugly head. I'll send the changes out when I return (or sooner if
I sneak away
to a decent computer and internet connection :).
The series looks good to me, thanks Khem!
Bruce
> poky-extra repo. Additionally systemd-image on angstrom-next builds and boots
> fine on qemumips64 as well.
>
> Additionally it also adds bits to have SH4 root file systems to be
> able to built and again core-image-sato builds for sh4 however qemu
> machine support is not yet done but root file sytem boots fine on
> real hardware.
>
> The images are tested on both eglibc and uclibc.
>
> Any help in providing feedback or testing these patches is welcome.
>
> I have tested them enough for over a month now.
>
> The following changes since commit 326563d5a897ae2dba7cfd8d73579d3d979d72c8:
>
> sstate.bbclass: Make sure we don't have an empty fixmepath file (2012-05-18
> 15:24:45 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib kraj/mips64
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/mips64
>
> Khem Raj (14):
> insane.bbclass: Add mips64{el} to known machines
> site: Add mips64 eglibc and uclibc site files
> gcc-4.6, gcc-4.7: Add support for building mips64 cross compiler
> binutils: Default to n64 when configured for mips64
> kernel-arch.bbclass: Map mips64{el} to mips KARCH
> eglibc-2.15: Support mips64
> libc-package: Add sh4 and mips64 to arch options
> runqemu: Add qemush4 and qemumips64 knowledge
> netbase: Add interface files for qemumips64 and qemush4
> site/sh-common: Add missing caches variables to build glib-2.32
> xserver-xorg: Fix build for mips64
> tune-mips64.inc: Add new tune file for mips64 big-endian
> qemumips64.conf: Add machine configuration for mips64(eb)
> qemush4.conf: Add machine configuration for qemush4
>
> meta/classes/insane.bbclass | 4 +
> meta/classes/kernel-arch.bbclass | 2 +-
> meta/classes/libc-package.bbclass | 3 +
> meta/conf/machine/include/tune-mips64.inc | 3 +
> meta/conf/machine/qemumips64.conf | 13 +++
> meta/conf/machine/qemush4.conf | 13 +++
> meta/recipes-core/eglibc/eglibc-locale.inc | 2 +-
> meta/recipes-core/eglibc/eglibc_2.15.bb | 2 +-
> .../netbase/netbase-4.47/qemumips64/interfaces | 8 ++
> .../netbase/netbase-4.47/qemush4/interfaces | 8 ++
> meta/recipes-core/netbase/netbase_4.47.bb | 4 +-
> .../binutils/mips64-default-ld-emulation.patch | 49 +
> meta/recipes-devtools/binutils/binutils_2.22.bb | 3 +-
> meta/recipes-devtools/gcc/gcc-4.6.inc | 1 +
> .../gcc/gcc-4.6/mips64-default-n64.patch | 32 ++
> meta/recipes-devtools/gcc/gcc-4.7.inc | 1 +
> .../gcc/gcc-4.7/mips64-default-n64.patch | 19
> meta/recipes-devtools/gcc/gcc-configure-common.inc | 4 +
> .../xorg-xserver/xserver-xorg-1.11.2.inc | 1 +
> .../xserver-xorg-1.11.2/mips64-compiler.patch | 29 +
> meta/site/mips64-linux | 82 +++
> meta/site/mips64-linux-uclibc | 83 +++
> meta/site/mips64el-linux | 82 +++
> meta/site/mips64el-linux-uclibc | 108
>
> meta/site/sh-common | 4 +
> scripts/runqemu | 10 ++-
> scripts/runqemu-internal | 35 ++-
> 27 files changed, 594 insertions(+), 11 deletions(-)
> create mode 100644 meta/conf/machine/include/tune-mips64.inc
> create mode 100644 meta/conf/machine/qemumips64.conf
> create mode 100644 meta/conf/machine/qemush4.conf
> create mode 100644
> meta/recipes-core/netbase/netbase-4.47/qemumips64/interfaces
> create mode 100644 meta/recipes-core/netbase/netbase-4.47/qemush4/interfaces
> create mode 100644
> meta/recipes-devtools/binutils/binutils/mips64-default-ld-emulation.patch
> create mode 100644 meta/recipes-devtools/gcc/gcc-4.6/mips64-default-n64.patch
> create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/mips64-default-n64.patch
> create mode 100644
> meta/recipes-graphics/xorg-xserver/xserver-xorg-1.11.2/mips64-compiler.patch
> create mode 100644 meta/site/mips64-linux
> create mode 100644 meta/site/mips64-linux-uclibc
> create mode 100644 meta/site/mips64el-linux
> create mode 100644 meta/site/mip
Re: [OE-core] [PATCH] cmd1.bbclass: Ensure ncurses is built and used for menuconfig tasks
On 12-05-31 09:29 AM, Richard Purdie wrote:
Currently, the task just exits if something goes wrong. This adds the
ncurses-native dependency. It also adds a small delay before closing the
window so any messages displayed there can be seen.
Trying to get the kernel build system to correctly find and link with
our copy of ncurses is some kind of nightmare. I ended up having to add
it to HOST_LOADLIBES globally for this task which is rather nasty but I
couldn't find any other way.
Agreed, and my much more limited knowledge of the options can't come
up with something different either.
Is there an option to move those flags to the kernel class, so they'd
only be set when it is in play ? That would at least isolate the data
a bit more. Alternatively there's the less palatable kernel specific
do_menuconfig option (ech).
Otherwise, no concerns or big comments from me.
Bruce
[YOCTO #2513]
Signed-off-by: Richard Purdie
---
diff --git a/meta/classes/cml1.bbclass b/meta/classes/cml1.bbclass
index d429188..bd25311 100644
--- a/meta/classes/cml1.bbclass
+++ b/meta/classes/cml1.bbclass
@@ -9,9 +9,15 @@ addtask configure after do_unpack do_patch before do_compile
inherit terminal
+OE_TERMINAL_EXPORTS += "HOST_EXTRACFLAGS HOSTLDFLAGS HOST_LOADLIBES"
+HOST_EXTRACFLAGS = "${BUILD_CFLAGS} ${BUILD_LDFLAGS}"
+HOSTLDFLAGS = "${BUILD_LDFLAGS}"
+HOST_LOADLIBES = "-lncurses"
+
python do_menuconfig() {
-oe_terminal("make menuconfig", '${PN} Configuration', d)
+oe_terminal("${SHELL} -c \"make menuconfig; echo 'Pausing for 5 seconds'; sleep
5\"", '${PN} Configuration', d)
}
+do_menuconfig[depends] += "ncurses-native:do_populate_sysroot"
do_menuconfig[nostamp] = "1"
addtask menuconfig after do_configure
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [meta-xilinx] Creating a QEMU for Xilinx ARM for Zynq 7020 device
On Mon, Jun 4, 2012 at 3:12 AM, Elvis Dowson wrote: > Hi, > I'd like to add support for qemuxarm and build a core-image-sato image, > so that I can emulate the ARM processor on the Xilinx Zynq 7020 device using > Yocto. > > The sources for qemuxarm are located below: > > http://git.xilinx.com/?p=qemu-xarm.git;a=summary > > I haven't done this before, so if someone could guide me as to what I should > do, and the recipes I should take a look at, it would be great! I'd start from here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-zynq/tree/README.qemu Bruce > > Best regards, > > Elvis Dowson > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/9] linux-yocto/3.0: update to v3.0.32
Updating the 3.0 kernel SRCREVs to integrate the v3.0.32 -stable release. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |6 +++--- meta/recipes-kernel/linux/linux-yocto_3.0.bb| 16 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb index 14af91d..929aa85 100644 --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb @@ -11,12 +11,12 @@ KMACHINE_qemumips = "mti-malta32-be" KBRANCH = "yocto/standard/preempt-rt/base" KBRANCH_qemuppc = "yocto/standard/preempt-rt/qemu-ppc32" -LINUX_VERSION ?= "3.0.24" +LINUX_VERSION ?= "3.0.32" LINUX_KERNEL_TYPE = "preempt-rt" KMETA = "meta" -SRCREV_machine ?= "cf280f1dc5877d4ca43d21307222326efa68bb27" -SRCREV_machine_qemuppc ?= "afaa5baa6a9ca9c8a03a9a3eee2ba9fba089f416" +SRCREV_machine ?= "e67428d9966eecec4c081993dc64ceb5c0e64643" +SRCREV_machine_qemuppc ?= "dcca458cb92cc287f70e4062f02460f36a881b16" SRCREV_meta ?= "34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23" PR = "r2" diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb b/meta/recipes-kernel/linux/linux-yocto_3.0.bb index 82a7224..0f1be83 100644 --- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb +++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb @@ -17,14 +17,14 @@ KMACHINE_qemuarm = "arm-versatile-926ejs" KMETA = "meta" -LINUX_VERSION ?= "3.0.24" - -SRCREV_machine_qemuarm ?= "62bbe1d7a0e5c1200a99dabca889a52c9417b96b" -SRCREV_machine_qemumips ?= "66de88919f24f1e590a48dae6de752a68fed2353" -SRCREV_machine_qemuppc ?= "7528f1d06ef5665eed8c1498f62d5403b82bbbd6" -SRCREV_machine_qemux86 ?= "f153b0eb8264dc1e69f59d4c9173619feb4d5bd9" -SRCREV_machine_qemux86-64 ?= "aac580659dc0ce083f250fb05abf82e58d7f4531" -SRCREV_machine ?= "da7c40006b08916ff3a3db104def82aaf9ac2716" +LINUX_VERSION ?= "3.0.32" + +SRCREV_machine_qemuarm ?= "b8b6c3b6b3edf129ac26a27d779dd972c36e8ebd" +SRCREV_machine_qemumips ?= "33a643547e983adb442ff8e15645881816b17a7d" +SRCREV_machine_qemuppc ?= "bd9a3c4c066bd4b9f52b51aaaec9b029a7abe793" +SRCREV_machine_qemux86 ?= "70342faea067476774eb55f4e3098af0bcc48782" +SRCREV_machine_qemux86-64 ?= "cba836a545fbeb96f6f2392c3ecbac9d7735fa65" +SRCREV_machine ?= "bd6ad607c754dea30d91502a237870b4c45e0f1b" SRCREV_meta ?= "34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23" PR = "r4" -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/9] kern-tools: remove unused code, meta branch and directory assumptions
Updating the kern-tools SRCREV to pick up fixes that remove unused
code, transition code (tree format changes) and to remove assumptions
about branch and directory naming.
There are no user visible changes with this update, but the plumbing
changes will be used in future updates for more generalized support.
The commit details are below:
Author: Bruce Ashfield
Date: Fri May 11 12:13:12 2012 -0400
kgit-publish: remove --remote option
The ability to publish and automatically push a repository was
never used, and is error prone. The complexit isn't needed in
the script, so removing it is the best option.
An explicit push after tree publication is suggested, or a
wrapper script (specific to a particular infrastructure) around
this script.
Signed-off-by: Bruce Ashfield
Author: Bruce Ashfield
Date: Fri May 11 12:04:09 2012 -0400
kern-tools: remove unused code, scripts and transition code
The period of supporting old trees with a different meta
branch name and directory structure are gone. So the cleanup
and removal of the old structure can be completed.
The meta branch and directory are now controlled via command line,
or via the KMETA environment variable. No testing and conditional
processing of the tree are required.
Additionally, the generate_cfg script is no longer used, or is the
branch conditing code in createme. So they can be safely removed
from the tools and repository.
Signed-off-by: Bruce Ashfield
Author: Bruce Ashfield
Date: Thu May 10 12:18:19 2012 -0400
kern-tools: remove meta tag and directory assumptions
During repository sanity checks (createme) and during the
checkpoint process, there were several assumptions about the tree
that either relied on a tag, or a particular directory name.
With this set of changes, simply passing the meta branch name is
enough to sanitize and restore the checkpoint. If no meta branch
name is passed, the default of 'meta' is used for both the branch
and meta data directory name.
Signed-off-by: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
.../kern-tools/kern-tools-native_git.bb|4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 9ef1a20..becb0de 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -1,10 +1,10 @@
DESCRIPTION = "Scripts and utilities for managing Yocto branched kernels."
LICENSE = "GPLv2"
-LIC_FILES_CHKSUM =
"file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d843f43d2e22b0d91a6fee"
+LIC_FILES_CHKSUM =
"file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70cd5f52972f8884b80743d"
DEPENDS = "git-native guilt-native"
-SRCREV = "de3649840e8e3ca25bc79d2444f04a1b158a1769"
+SRCREV = "0859d2f73cc6f6973835fa5713b5a98a43ed43ff"
PR = "r12"
PV = "0.1+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/9] linux-yocto: consolidated pull request
Richard/Saul, Here's a 9 patch series that is a collection of work that's been brewing for about three weeks. Highlights include: - removal of the 2.6.37 recipe, it's time is now gone - addition of the 3.4 kernel recipe - configuration fixups and audits within that 3.4 kernel - kernel *only* support for mips64 mti emulation - -stable updates for supported kernels 3.2.18, 3.0.32 - machine fixes/configurations for the 3.2 and 3.0 kernels - kern tool updates, streamlining and fixes I've built and booted the qemu* machines on 3.4, and have been doing this for several weeks now. Built and boot tests have also happened on the 3.0 and 3.2 trees as well. Some BSP layers are already using these changes. The tools changes set the stage for some follow on changes that I'm nearly done for the next oe-core/yocto release, but they are useful by themselves, so I'm getting them out of my queue. I'll follow up to other lists with updates to recipes and configs that reference the modified kernels. BSP layers can be updated as appropriate, since all these changes have been pushed to the various kernel trees. Cheers, Bruce The following changes since commit df8f55a919b3cc602ce1f1c51630c7edf6e36b55: ltp: Add patch to correct failing build (2012-06-05 23:05:00 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel-oe http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe Bruce Ashfield (9): kern-tools: remove unused code, meta branch and directory assumptions linux-yocto/3.2: update to v3.2.18 linux-yocto/3.0: update to v3.0.32 linux-yocto: remove v2.6.37 recipe linux-yocto: add machine aliases for yocto BSPs linux-yocto: add 3.4 recipe linux-yocto/3.2: fri2 and chiefriver machine updates linux-yocto/3.0: add cedartrail kernel features kern-tools: anchor KMACHINE test .../kern-tools/kern-tools-native_git.bb|4 +- meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb| 15 ++-- meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb| 15 ++-- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |7 ++-- meta/recipes-kernel/linux/linux-yocto_2.6.37.bb| 38 meta/recipes-kernel/linux/linux-yocto_3.0.bb | 23 meta/recipes-kernel/linux/linux-yocto_3.2.bb | 23 meta/recipes-kernel/linux/linux-yocto_3.4.bb | 38 8 files changed, 67 insertions(+), 96 deletions(-) delete mode 100644 meta/recipes-kernel/linux/linux-yocto_2.6.37.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.4.bb -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 4/9] linux-yocto: remove v2.6.37 recipe
With the introduction of the 3.4 kernel recipe, the 2.6.37 kernel
recipe is removed, keeping the supported list at three kernels.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto_2.6.37.bb | 38 ---
1 files changed, 0 insertions(+), 38 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-yocto_2.6.37.bb
diff --git a/meta/recipes-kernel/linux/linux-yocto_2.6.37.bb
b/meta/recipes-kernel/linux/linux-yocto_2.6.37.bb
deleted file mode 100644
index 3968c62..000
--- a/meta/recipes-kernel/linux/linux-yocto_2.6.37.bb
+++ /dev/null
@@ -1,38 +0,0 @@
-inherit kernel
-require linux-yocto.inc
-
-KMACHINE = "yocto/standard/base"
-KMACHINE_qemux86 = "yocto/standard/common-pc/base"
-KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
-KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
-KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
-KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
-
-KBRANCH = "${KMACHINE}"
-
-KMETA = "meta"
-
-LINUX_VERSION ?= "2.6.37"
-
-SRCREV_machine_qemuarm = "b3e53a090eaa23aa82e64fa0a563a93a2b4dbb5d"
-SRCREV_machine_qemumips = "91f2eb4a3b447476b36aac8e6e198d08c98e0680"
-SRCREV_machine_qemuppc = "862faf3666b3a4e4bc1d469ff5fb3fb90c25f621"
-SRCREV_machine_qemux86 = "27ad78e1f6378da554775a7d6760730c92f8c5a7"
-SRCREV_machine_qemux86-64 = "af2bfbe5f757361b5b027a24d67a93bfdfaaf33c"
-SRCREV_machine = "4ae8f8605c81c39b959948e23f7123294a5dfb3f"
-SRCREV_meta = "aeea99683c7283f1f3320bf2ee7085ee252d4e7e"
-
-PR = "r23"
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-SRC_URI =
"git://git.yoctoproject.org/linux-yocto-2.6.37;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
-
-COMPATIBLE_MACHINE = "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64)"
-
-# Functionality flags
-KERNEL_FEATURES = "features/netfilter"
-KERNEL_FEATURES_append = " features/taskstats"
-KERNEL_FEATURES_append_qemux86 = " cfg/sound"
-KERNEL_FEATURES_append_qemux86-64 = " cfg/sound"
-
-require linux-tools.inc
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/9] linux-yocto/3.2: update to v3.2.18
Updating the 3.2 kernel SRCREVs to pickup the -stable update to v3.2.18. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |6 +++--- meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |4 ++-- meta/recipes-kernel/linux/linux-yocto_3.2.bb | 16 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb index b275ad4..f881c1f 100644 --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb @@ -11,13 +11,13 @@ KMACHINE_qemumips = "mti-malta32-be" KBRANCH = "standard/preempt-rt/base" KBRANCH_qemuppc = "standard/preempt-rt/qemu-ppc32" -LINUX_VERSION ?= "3.2.11" +LINUX_VERSION ?= "3.2.18" LINUX_KERNEL_TYPE = "preempt-rt" KMETA = "meta" -SRCREV_machine ?= "3ebf4d172cf4a41d2abf09e4036f0850e08064e7" -SRCREV_machine_qemuppc ?= "7cebfe717987f4ffa9ae90558c28f45049847c1c" +SRCREV_machine ?= "fe2630b38159ea7b9cf977b5fed40a9917002087" +SRCREV_machine_qemuppc ?= "0259e5a3ef568c6979f2cb31280a43c55c784f4f" SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235" PR = "r1" diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb index f50e12e..80be112 100644 --- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb @@ -9,9 +9,9 @@ KBRANCH = "standard/tiny" LINUX_KERNEL_TYPE = "tiny" KCONFIG_MODE = "--allnoconfig" -LINUX_VERSION ?= "3.2.11" +LINUX_VERSION ?= "3.2.18" -SRCREV_machine ?= "61960ba8e910d54b5525d5e9b6a7469bc399c246" +SRCREV_machine ?= "8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c" SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235" PR = "r0" diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb b/meta/recipes-kernel/linux/linux-yocto_3.2.bb index 14de6f4..665ddca 100644 --- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb +++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb @@ -15,14 +15,14 @@ KBRANCH_qemuppc = "standard/default/qemu-ppc32" KBRANCH_qemumips = "standard/default/mti-malta32-be" KBRANCH_qemuarm = "standard/default/arm-versatile-926ejs" -LINUX_VERSION ?= "3.2.11" - -SRCREV_machine_qemuarm ?= "ba47a1cc9bb6ad576b2ac7adb3036bcfa569fe2e" -SRCREV_machine_qemumips ?= "3b2fd654392a2f33aed12748548c04e9b169591b" -SRCREV_machine_qemuppc ?= "cf3e188cf2a18c48a0e6f9ca54c36e6ac39512ec" -SRCREV_machine_qemux86 ?= "46f1007ad22b6790224c66a8dc4e80fdbd21eea1" -SRCREV_machine_qemux86-64 ?= "00e5ec2393bada6723bd9a07ded3d001c02fa727" -SRCREV_machine ?= "f4f8ba730e7783e09413872414d0a17c142c816d" +LINUX_VERSION ?= "3.2.18" + +SRCREV_machine_qemuarm ?= "259cff0813417d16bf44b00a9f75103ebfcb" +SRCREV_machine_qemumips ?= "9a803ecc05b3af481036a6d9bb0da3a899be3074" +SRCREV_machine_qemuppc ?= "466746d1fe6370957ba087f9ca6f2e31201b2162" +SRCREV_machine_qemux86 ?= "c228cadee60f0ada73d11a36f6932f50a1c52d48" +SRCREV_machine_qemux86-64 ?= "b95a0ae3773545fa0ed9a47088d0361527c42e6c" +SRCREV_machine ?= "8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c" SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235" PR = "r1" -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 5/9] linux-yocto: add machine aliases for yocto BSPs
To avoid mapping machine names to kernel machine names in recipes,
we can define multiple KMACHINE names for a single in tree board.
This allows the tools to match a board description to multiple
different MACHINEs.
As a result, we can remove the explicit KMACHINE mappings from
the linux-yocto recipes and allow the KMACHINE=${MACHINE} default
to handle mappings. Individual recipes an bbappends can override
this as required.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |9 +
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |9 +
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |3 +--
meta/recipes-kernel/linux/linux-yocto_3.0.bb |9 +
meta/recipes-kernel/linux/linux-yocto_3.2.bb |9 +
5 files changed, 5 insertions(+), 34 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
index 929aa85..508beb1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
@@ -1,13 +1,6 @@
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
-KMACHINE = "common-pc"
-KMACHINE_qemux86 = "common-pc"
-KMACHINE_qemux86-64 = "common-pc-64"
-KMACHINE_qemuarm = "arm-versatile-926ejs"
-KMACHINE_qemuppc = "qemu-ppc32"
-KMACHINE_qemumips = "mti-malta32-be"
-
KBRANCH = "yocto/standard/preempt-rt/base"
KBRANCH_qemuppc = "yocto/standard/preempt-rt/qemu-ppc32"
@@ -17,7 +10,7 @@ KMETA = "meta"
SRCREV_machine ?= "e67428d9966eecec4c081993dc64ceb5c0e64643"
SRCREV_machine_qemuppc ?= "dcca458cb92cc287f70e4062f02460f36a881b16"
-SRCREV_meta ?= "34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23"
+SRCREV_meta ?= "b040132c19d70b00fc49f3b7e08c2ed52ac59f92"
PR = "r2"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index f881c1f..f27e39e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -1,13 +1,6 @@
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
-KMACHINE = "common-pc"
-KMACHINE_qemux86 = "common-pc"
-KMACHINE_qemux86-64 = "common-pc-64"
-KMACHINE_qemuarm = "arm-versatile-926ejs"
-KMACHINE_qemuppc = "qemu-ppc32"
-KMACHINE_qemumips = "mti-malta32-be"
-
KBRANCH = "standard/preempt-rt/base"
KBRANCH_qemuppc = "standard/preempt-rt/qemu-ppc32"
@@ -18,7 +11,7 @@ KMETA = "meta"
SRCREV_machine ?= "fe2630b38159ea7b9cf977b5fed40a9917002087"
SRCREV_machine_qemuppc ?= "0259e5a3ef568c6979f2cb31280a43c55c784f4f"
-SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235"
+SRCREV_meta ?= "0a18db9fc89a0e030e8c7b8d01fe03c5ca4197e3"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index 80be112..81aefb1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -4,7 +4,6 @@ require recipes-kernel/linux/linux-yocto.inc
# We need lzma (as CONFIG_KERNEL_LZMA=y)
DEPENDS += "xz-native"
-KMACHINE = "common-pc"
KBRANCH = "standard/tiny"
LINUX_KERNEL_TYPE = "tiny"
KCONFIG_MODE = "--allnoconfig"
@@ -12,7 +11,7 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.18"
SRCREV_machine ?= "8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c"
-SRCREV_meta ?= "49f931bc294d5b6be60502bbd448cff5aa766235"
+SRCREV_meta ?= "0a18db9fc89a0e030e8c7b8d01fe03c5ca4197e3"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
index 0f1be83..cfae247 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
@@ -8,13 +8,6 @@ KBRANCH_qemuppc = "yocto/standard/qemu-ppc32"
KBRANCH_qemumips = "yocto/standard/mti-malta32-be"
KBRANCH_qemuarm = "yocto/standard/arm-versatile-926ejs"
-# Temporary until 3.0 kernel tree is updated with machine mappings
-KMACHINE_qemux86 = "common-pc"
-KMACHINE_qemux86-64 = "common-pc-64"
-KMACHINE_qemuppc = "qemu-ppc32"
-KMACHINE_qemumips = "mti-malta32-be"
-KMACHINE_qemuarm = "arm-versatile-926ejs"
-
KMETA = "meta"
LINUX_VERSION ?= "3.0.32"
@@ -25,7 +18,7 @@ SRCREV_machine_qemuppc ?=
"bd9a3c4c066bd4b9f52b51aaaec9b029a7abe793"
SRCREV_machine_qemux86 ?= "70342faea067476
[OE-core] [PATCH 8/9] linux-yocto/3.0: add cedartrail kernel features
Updating meta to move Kernel Features out of the BSP and add to
the Cedartrail Machine branch.
Signed-off-by: Kishore Bodke
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |2 +-
meta/recipes-kernel/linux/linux-yocto_3.0.bb|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
index 508beb1..a39b966 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb
@@ -10,7 +10,7 @@ KMETA = "meta"
SRCREV_machine ?= "e67428d9966eecec4c081993dc64ceb5c0e64643"
SRCREV_machine_qemuppc ?= "dcca458cb92cc287f70e4062f02460f36a881b16"
-SRCREV_meta ?= "b040132c19d70b00fc49f3b7e08c2ed52ac59f92"
+SRCREV_meta ?= "46e8fc2bbbe73514e8d99101adaaa373f760ffa7"
PR = "r2"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
index cfae247..440821c 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
@@ -18,7 +18,7 @@ SRCREV_machine_qemuppc ?=
"bd9a3c4c066bd4b9f52b51aaaec9b029a7abe793"
SRCREV_machine_qemux86 ?= "70342faea067476774eb55f4e3098af0bcc48782"
SRCREV_machine_qemux86-64 ?= "cba836a545fbeb96f6f2392c3ecbac9d7735fa65"
SRCREV_machine ?= "bd6ad607c754dea30d91502a237870b4c45e0f1b"
-SRCREV_meta ?= "b040132c19d70b00fc49f3b7e08c2ed52ac59f92"
+SRCREV_meta ?= "46e8fc2bbbe73514e8d99101adaaa373f760ffa7"
PR = "r4"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 6/9] linux-yocto: add 3.4 recipe
Introducing the 3.4 kernel recipe. At this point there are three
supported kernel 3.4, 3.2 and 3.0.
Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and
qemuppc
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 38 ++
1 files changed, 38 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.4.bb
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
new file mode 100644
index 000..81816b1
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -0,0 +1,38 @@
+inherit kernel
+require recipes-kernel/linux/linux-yocto.inc
+
+KBRANCH = "standard/base"
+KBRANCH_qemux86 = "standard/common-pc/base"
+KBRANCH_qemux86-64 = "standard/common-pc-64/base"
+KBRANCH_qemuppc = "standard/qemuppc"
+KBRANCH_qemumips = "standard/mti-malta32"
+KBRANCH_qemumips64 = "standard/mti-malta64"
+KBRANCH_qemumips64el = "standard/mti-malta64"
+KBRANCH_qemuarm = "standard/arm-versatile-926ejs"
+
+SRCREV_machine_qemuarm ?= "bc7dd2ebe7f5443fb9d89d46106053cfc69b5d7f"
+SRCREV_machine_qemumips ?= "5a2ad0078de3d24a6e8e3f3c9a7426a08a86717d"
+SRCREV_machine_qemuppc ?= "f92ab2a332627c0213ecfdfc873d470be008f86b"
+SRCREV_machine_qemux86 ?= "780ab7e11f03931295e8f0e29707f2abb688e9ad"
+SRCREV_machine_qemux86-64 ?= "780ab7e11f03931295e8f0e29707f2abb688e9ad"
+SRCREV_machine ?= "780ab7e11f03931295e8f0e29707f2abb688e9ad"
+SRCREV_meta ?= "3fd089debe624c642d7b4d9363f853021d1675b2"
+
+SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
+
+LINUX_VERSION ?= "3.4.1"
+
+PR = "r0"
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "meta"
+
+COMPATIBLE_MACHINE = "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64)"
+
+# Functionality flags
+KERNEL_REVISION_CHECKING=""
+KERNEL_FEATURES="features/netfilter"
+KERNEL_FEATURES_append_qemux86=" cfg/sound"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
+
+require recipes-kernel/linux/linux-tools.inc
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 7/9] linux-yocto/3.2: fri2 and chiefriver machine updates
Bumping the 3.2 SRCREVs to pickup the following configuration changes for
the new chiefriver BSP and the existing fri2 machines:
5b4c9dc fri2: update base config
cdfbb50 fri2: add usb-mass-storage to standard and preempt-rt
3c1af06 fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi
feature
26a4d79 iwlagn: Correct a comment typo
ade9c57 iwlwifi: Add a feature for iwlwifi
571b6cb fri2: Configuration update (usb, wifi, i2c)
b257485 meta: add tmp/rc6 feature
24c6494 chiefriver: create initial BSP infrastructure
All branches are also updated with the following fix:
1ce6700 efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
Signed-off-by: Darren Hart
Signed-off-by: Tom Zanussi
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |4 ++--
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 14 +++---
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
index f27e39e..a07b27a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
@@ -9,9 +9,9 @@ LINUX_KERNEL_TYPE = "preempt-rt"
KMETA = "meta"
-SRCREV_machine ?= "fe2630b38159ea7b9cf977b5fed40a9917002087"
-SRCREV_machine_qemuppc ?= "0259e5a3ef568c6979f2cb31280a43c55c784f4f"
-SRCREV_meta ?= "0a18db9fc89a0e030e8c7b8d01fe03c5ca4197e3"
+SRCREV_machine ?= "c413f23eafb3e91ff98653e578e771532fd71be9"
+SRCREV_machine_qemuppc ?= "d7020ba154df03cba5351011ff664f5e3e1ce678"
+SRCREV_meta ?= "ee78519365bdb25287703bbc31c06b193263c654"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
index 81aefb1..546971b 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
@@ -10,8 +10,8 @@ KCONFIG_MODE = "--allnoconfig"
LINUX_VERSION ?= "3.2.18"
-SRCREV_machine ?= "8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c"
-SRCREV_meta ?= "0a18db9fc89a0e030e8c7b8d01fe03c5ca4197e3"
+SRCREV_machine ?= "27b68a93eb791e830da8d3a2c0fc99780897ad89"
+SRCREV_meta ?= "ee78519365bdb25287703bbc31c06b193263c654"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index ac4e454..85c0096 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -10,13 +10,13 @@ KBRANCH_qemuarm = "standard/default/arm-versatile-926ejs"
LINUX_VERSION ?= "3.2.18"
-SRCREV_machine_qemuarm ?= "259cff0813417d16bf44b00a9f75103ebfcb"
-SRCREV_machine_qemumips ?= "9a803ecc05b3af481036a6d9bb0da3a899be3074"
-SRCREV_machine_qemuppc ?= "466746d1fe6370957ba087f9ca6f2e31201b2162"
-SRCREV_machine_qemux86 ?= "c228cadee60f0ada73d11a36f6932f50a1c52d48"
-SRCREV_machine_qemux86-64 ?= "b95a0ae3773545fa0ed9a47088d0361527c42e6c"
-SRCREV_machine ?= "8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c"
-SRCREV_meta ?= "0a18db9fc89a0e030e8c7b8d01fe03c5ca4197e3"
+SRCREV_machine_qemuarm ?= "ebb5e65d02a352e3e8601096e1674ffc261345f2"
+SRCREV_machine_qemumips ?= "62aeb307e9a731c4bba05ce4d57b9cece41a2a01"
+SRCREV_machine_qemuppc ?= "1396a8f7b62f8926dc1fa474c7d94ae920d81852"
+SRCREV_machine_qemux86 ?= "9d32bb075e349cc69c7af42b60f6715c5d8c972e"
+SRCREV_machine_qemux86-64 ?= "dd488f551fa0f8e3bf1aadd78083b8547bba8bdf"
+SRCREV_machine ?= "76133a1cadf0de417c29ed15d6fbb12c41c0802b"
+SRCREV_meta ?= "ee78519365bdb25287703bbc31c06b193263c654l"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 9/9] kern-tools: anchor KMACHINE test
Updating the kern-tools SRCREV to pick up the following fix:
Out of tree feature descriptions (.scc files) take two forms: normal
features and BSP descriptions.
A normal feature is detected and added to the end of the current machine
being processed. During tree processing, it's configuration and patches
will be applied.
A BSP description on the other hand must be matched based on three
critera (which are in the .scc file via "define "):
- machine
- kernel type
- architecture
Since features that define machines are only explicitly added, they
are removed from the list of features that should be automatically
added.
The criteria for removing them from the auto-add list is the
definitions found in the .scc file. The existing check was simply
for KMACHINE anywhere in the file. This meant that a conditional
or even a comment containing that phrase would exclude a file.
Properly anchoring the KMACHINE test to "^define.*KMACHINE" fixes the
problem of overly agreesive exclusions.
Signed-off-by: Bruce Ashfield
---
.../kern-tools/kern-tools-native_git.bb|2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index becb0de..2329ab9 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM =
"file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
DEPENDS = "git-native guilt-native"
-SRCREV = "0859d2f73cc6f6973835fa5713b5a98a43ed43ff"
+SRCREV = "4b1fef0a85db38bad6db7f14d44ea59713a64fdb"
PR = "r12"
PV = "0.1+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] ERROR: ExpansionError during parsing /tool/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb: Failure expanding variable SRCPV
On Fri, Jun 8, 2012 at 9:59 AM, Elvis Dowson wrote:
> Hi,
>
> On Jun 8, 2012, at 12:58 PM, Richard Purdie wrote:
>
>> On Thu, 2012-06-07 at 15:59 -0400, Bruce Ashfield wrote:
>>> Richard/Saul,
>>>
>>> Here's a 9 patch series that is a collection of work that's been
>>> brewing for about three weeks.
>>>
>>> Highlights include:
>>>
>>> - removal of the 2.6.37 recipe, it's time is now gone
>>> - addition of the 3.4 kernel recipe
>>> - configuration fixups and audits within that 3.4 kernel
>>> - kernel *only* support for mips64 mti emulation
>>> - -stable updates for supported kernels 3.2.18, 3.0.32
>>> - machine fixes/configurations for the 3.2 and 3.0 kernels
>>> - kern tool updates, streamlining and fixes
>
> I just updated my poky installation, and tried to build the meta-toolchain,
> and I got a bunch of errors. This is related to the recent updates to the
> linux-yocto_3.2.bb kernel.
I'm already finishing up a patch, since this started blowing up here as well
this morning.
Bruce
>
> elvis@eos:/tool/yocto/poky/build$ bitbake meta-toolchain
> Pseudo is not present but is required, building this first before the main
> build
> WARNING: Unable to get checksum for python-numpy SRC_URI entry config.h: file
> could not be found | ETA:
> 00:00:43
> WARNING: Unable to get checksum for python-numpy SRC_URI entry numpyconfig.h:
> file could not be found
> ERROR: ExpansionError during parsing
> /tool/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb: Failure
> expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which
> triggered exception FetchError: Fetcher failure for URL:
> 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/base,meta;name=machine,meta'.
> The command git ls-remote git://git.yoctoproject.org/linux-yocto-3.2
> ee78519365bdb25287703bbc31c06b193263c654l gave empty output unexpectedly
> ERROR: No recipes available for:
> /tool/yocto/poky/meta-yocto/recipes-core/uclibc/uclibc_git.bbappend
> /tool/yocto/poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend
> /tool/yocto/meta-xilinx/recipes-core/util-linux/util-linux_2.21.1.bbappend
> /tool/yocto/poky/meta-yocto/recipes-core/psplash/psplash_git.bbappend
> /tool/yocto/poky/meta-yocto/recipes-core/netbase/netbase_4.47.bbappend
> /tool/yocto/meta-openembedded/meta-oe/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bbappend
> /tool/yocto/meta-openembedded/meta-oe/recipes-core/dropbear/dropbear_2012.55.bbappend
> /tool/yocto/poky/meta-yocto/recipes-core/tasks/task-core-tools-profile.bbappend
> /tool/yocto/meta-xilinx/recipes-core/initscripts/initscripts_1.0.bbappend
> /tool/yocto/meta-openembedded/meta-oe/recipes-core/busybox/busybox_1.19.4.bbappend
> ERROR: Command execution failed: Exited with 1
>
> Summary: There were 2 WARNING messages shown.
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
>
>
> best regards,
>
> Elvis Dowson
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-yocto/3.2: fix meta SRCREV typo
Never underestimate the power of a rebase for inserting fat finger
errors that are hidden by local layers.
An extraneous character made it into the 3.2 meta SRCREV, which makes
the fetcher error, even when the kernel isn't being built.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
index 85c0096..e6cf9bb 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
@@ -16,7 +16,7 @@ SRCREV_machine_qemuppc ?=
"1396a8f7b62f8926dc1fa474c7d94ae920d81852"
SRCREV_machine_qemux86 ?= "9d32bb075e349cc69c7af42b60f6715c5d8c972e"
SRCREV_machine_qemux86-64 ?= "dd488f551fa0f8e3bf1aadd78083b8547bba8bdf"
SRCREV_machine ?= "76133a1cadf0de417c29ed15d6fbb12c41c0802b"
-SRCREV_meta ?= "ee78519365bdb25287703bbc31c06b193263c654l"
+SRCREV_meta ?= "ee78519365bdb25287703bbc31c06b193263c654"
PR = "r1"
PV = "${LINUX_VERSION}+git${SRCPV}"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] linux-yocto/3.2: fix meta SRCREV typo
Richard/Saul, Argh. I need a brown paper bag being focused on 3.4 hid thsi from me. Never underestimate the power of a rebase for inserting fat finger errors that are hidden by local layers. An extraneous character made it into the 3.2 meta SRCREV, which makes the fetcher error, even when the kernel isn't being built. Cheers, Bruce The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b: hob2: create a standalone deploy image tool (2012-06-08 12:13:43 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-yocto/3.2: fix meta SRCREV typo meta/recipes-kernel/linux/linux-yocto_3.2.bb |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] ERROR: ExpansionError during parsing /tool/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb: Failure expanding variable SRCPV
On Fri, Jun 8, 2012 at 10:05 AM, Tom Zanussi wrote:
> On Fri, 2012-06-08 at 15:59 +0200, Elvis Dowson wrote:
>> Hi,
>>
>> On Jun 8, 2012, at 12:58 PM, Richard Purdie wrote:
>>
>> > On Thu, 2012-06-07 at 15:59 -0400, Bruce Ashfield wrote:
>> >> Richard/Saul,
>> >>
>> >> Here's a 9 patch series that is a collection of work that's been
>> >> brewing for about three weeks.
>> >>
>> >> Highlights include:
>> >>
>> >> - removal of the 2.6.37 recipe, it's time is now gone
>> >> - addition of the 3.4 kernel recipe
>> >> - configuration fixups and audits within that 3.4 kernel
>> >> - kernel *only* support for mips64 mti emulation
>> >> - -stable updates for supported kernels 3.2.18, 3.0.32
>> >> - machine fixes/configurations for the 3.2 and 3.0 kernels
>> >> - kern tool updates, streamlining and fixes
>>
>> I just updated my poky installation, and tried to build the meta-toolchain,
>> and I got a bunch of errors. This is related to the recent updates to the
>> linux-yocto_3.2.bb kernel.
>>
>
> I just posted a patch to fix this - it was a SRCREV typo.
>
> Building fine here now with that simple fix...
Yah. Last minute rebase, and some masking to speed up my 3.4 builds hid it
from me.
You beat me by a couple of minutes. Two series to chose from.
I'll go back into hiding now.
Bruce
>
> Tom
>
>> elvis@eos:/tool/yocto/poky/build$ bitbake meta-toolchain
>> Pseudo is not present but is required, building this first before the main
>> build
>> WARNING: Unable to get checksum for python-numpy SRC_URI entry config.h:
>> file could not be found | ETA:
>> 00:00:43
>> WARNING: Unable to get checksum for python-numpy SRC_URI entry
>> numpyconfig.h: file could not be found
>> ERROR: ExpansionError during parsing
>> /tool/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb: Failure
>> expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which
>> triggered exception FetchError: Fetcher failure for URL:
>> 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/base,meta;name=machine,meta'.
>> The command git ls-remote git://git.yoctoproject.org/linux-yocto-3.2
>> ee78519365bdb25287703bbc31c06b193263c654l gave empty output unexpectedly
>> ERROR: No recipes available for:
>> /tool/yocto/poky/meta-yocto/recipes-core/uclibc/uclibc_git.bbappend
>> /tool/yocto/poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> /tool/yocto/meta-xilinx/recipes-core/util-linux/util-linux_2.21.1.bbappend
>> /tool/yocto/poky/meta-yocto/recipes-core/psplash/psplash_git.bbappend
>> /tool/yocto/poky/meta-yocto/recipes-core/netbase/netbase_4.47.bbappend
>>
>> /tool/yocto/meta-openembedded/meta-oe/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bbappend
>>
>> /tool/yocto/meta-openembedded/meta-oe/recipes-core/dropbear/dropbear_2012.55.bbappend
>>
>> /tool/yocto/poky/meta-yocto/recipes-core/tasks/task-core-tools-profile.bbappend
>> /tool/yocto/meta-xilinx/recipes-core/initscripts/initscripts_1.0.bbappend
>>
>> /tool/yocto/meta-openembedded/meta-oe/recipes-core/busybox/busybox_1.19.4.bbappend
>> ERROR: Command execution failed: Exited with 1
>>
>> Summary: There were 2 WARNING messages shown.
>> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
>>
>>
>> best regards,
>>
>> Elvis Dowson
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] linux-libc-headers: set default LINUXLIBCVERSION to 3.4
Richard/Saul, Fresh of my typo success of my last series .. I rebuilt core-image-minal for all qemu machines from scratch with this in place. No issues were seen here, and I'm not sufficiently paranoid for 10 people. The 3.4 kernel is released, and is the default for qemu* builds, so we can safely update the default libc-headers version to 3.4. Cheers, Bruce The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b: Kang Kai (1): hob2: create a standalone deploy image tool are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/libc-headers http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/libc-headers Bruce Ashfield (1): linux-libc-headers: set default LINUXLIBCVERSION to 3.4 meta/conf/distro/include/tcmode-default.inc|2 +- .../linux-libc-headers/linux-libc-headers_3.4.bb |6 ++ 2 files changed, 7 insertions(+), 1 deletions(-) create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-libc-headers: set default LINUXLIBCVERSION to 3.4
The 3.4 kernel is released, and is the default for qemu* builds, so
we can safely update the default libc-headers version to 3.4.
Built and booted for qemu*
Signed-off-by: Bruce Ashfield
---
meta/conf/distro/include/tcmode-default.inc|2 +-
.../linux-libc-headers/linux-libc-headers_3.4.bb |6 ++
2 files changed, 7 insertions(+), 1 deletions(-)
create mode 100644
meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 469233d..89c72c5 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
BINUVERSION ?= "2.22"
EGLIBCVERSION ?= "2.15"
UCLIBCVERSION ?= "0.9.33"
-LINUXLIBCVERSION ?= "3.2"
+LINUXLIBCVERSION ?= "3.4"
PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
new file mode 100644
index 000..9cedd52
--- /dev/null
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
@@ -0,0 +1,6 @@
+require linux-libc-headers.inc
+
+PR = "r1"
+
+SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
+SRC_URI[sha256sum] =
"a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
--
1.7.0.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] linux-libc-headers: set default LINUXLIBCVERSION to 3.4
On Fri, Jun 8, 2012 at 11:42 AM, Bruce Ashfield
wrote:
> The 3.4 kernel is released, and is the default for qemu* builds, so
> we can safely update the default libc-headers version to 3.4.
>
> Built and booted for qemu*
>
> Signed-off-by: Bruce Ashfield
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../linux-libc-headers/linux-libc-headers_3.4.bb | 6 ++
> 2 files changed, 7 insertions(+), 1 deletions(-)
> create mode 100644
> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> index 469233d..89c72c5 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
> BINUVERSION ?= "2.22"
> EGLIBCVERSION ?= "2.15"
> UCLIBCVERSION ?= "0.9.33"
> -LINUXLIBCVERSION ?= "3.2"
> +LINUXLIBCVERSION ?= "3.4"
>
> PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
> PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
> diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
> new file mode 100644
> index 000..9cedd52
> --- /dev/null
> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
> @@ -0,0 +1,6 @@
> +require linux-libc-headers.inc
> +
> +PR = "r1"
FYI: this r1 came from the reference libc-headers that I used .. but
now that I think
about it, it should be r0.
I can make that change on my topic branch.
Cheers,
Bruce
> +
> +SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
> +SRC_URI[sha256sum] =
> "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
> --
> 1.7.0.4
>
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] initial setup on my laptop
On Fri, Jun 8, 2012 at 1:12 PM, Radu Moisan wrote:
> I'm trying to setup everything on my laptop and I cannot start any build. I
> must have missed something, the following is the error I get:
See the patches on the list from a few hours ago. I had a bad SRCREV in one
meta branch update, and due to the way the fetcher has to work, it breaks
everyone's build.
Hopefully the fix merges soon ..
Bruce
>
> radu@elitebook> bitbake core-image-minimal
> Pseudo is not present but is required, building this first before the main
> build
> Loading cache: 100%
> |##|
> ETA: 00:00:00
> Loaded 1146 entries from dependency cache.
> NOTE: Error expanding variable
> do_patch
> | ETA: --:--:--
> NOTE: Error during finalise of
> /home/radu/Documents/Development/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb
> ERROR: ExpansionError during parsing
> /home/radu/Documents/Development/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb:
> Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)}
> which triggered exception FetchError: Fetcher failure for URL:
> 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/base,meta;name=machine,meta'.
> The command git ls-remote git://git.yoctoproject.org/linux-yocto-3.2
> ee78519365bdb25287703bbc31c06b193263c654l gave empty output unexpectedly
> ERROR: No recipes available for:
>
> /home/radu/Documents/Development/Yocto/poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend
> ERROR: Command execution failed: Exited with 1
>
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
>
>
> Thanks,
> Radu
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1] linux-yocto/3.2: fix meta SRCREV typo
On 12-06-11 08:52 AM, Richard Purdie wrote: On Fri, 2012-06-08 at 10:10 -0400, Bruce Ashfield wrote: Richard/Saul, Argh. I need a brown paper bag being focused on 3.4 hid thsi from me. Never underestimate the power of a rebase for inserting fat finger errors that are hidden by local layers. An extraneous character made it into the 3.2 meta SRCREV, which makes the fetcher error, even when the kernel isn't being built. I came to Tom's patch first but a fix has been merged. No worries, I'm glad it's in. I can take the paper bag off my head now. Cheers, Bruce Cheers, Richard ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Missing Patch Headers
On Mon, Jun 11, 2012 at 11:23 AM, Saul Wold wrote: > > Folks, > > We recently had a spat of new patches added without patch headers, ie no > patch comment, Signed-off-by or Upstream-Status. > > Please review this list and update the patch and submit a new commit. > > Zhai Edwin - > meta/recipes-graphics/pango/pango-1.28.4/multilib-fix-clean.patch > Laurentiu Palcu - > meta/recipes-graphics/directfb/directfb/libdirect-remove-include-of-linux-config.h.patch > Cristian Iorga - > meta/recipes-extended/ltp/ltp/fix_building_fom_archive.patch > Xiaofeng Yan - meta/recipes-extended/lsb/lsbinitscripts/functions.patch > Mark Hatle - meta/recipes-devtools/binutils/binutils/binutils-armv5e.patch > Mark Hatle - meta/recipes-devtools/rpm/rpm/rpm-resolvedep.patch > Andreas Müller - > meta/recipes-kernel/systemtap/systemtap/runtime-staprun-configure.ac-support-without-nss-for.patch > Bruce Ashfield - > meta/recipes-kernel/lttng-2.0/lttng-modules/lttng-sycalls-protect-is_compat_task-from-redefiniti.patch Your script is wrong here. That patch has everything you'd expect, since it follows kernel patch conventions. Subject, shortlog, log log and sign-off. So don't expect any resubmission from me on this one, since I won't be putting an upstream status directly in the patch. Bruce > > > Thanks > -- > Sau! > > Saul Wold > Yocto Component Wrangler @ Intel > Yocto Project / Poky Build System > > > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Missing Patch Headers
On Mon, Jun 11, 2012 at 12:44 PM, Saul Wold wrote: > On 06/11/2012 08:34 AM, Bruce Ashfield wrote: >> >> On Mon, Jun 11, 2012 at 11:23 AM, Saul Wold wrote: >>> >>> >>> Folks, >>> >>> We recently had a spat of new patches added without patch headers, ie no >>> patch comment, Signed-off-by or Upstream-Status. >>> >>> Please review this list and update the patch and submit a new commit. >>> >>> Zhai Edwin - >>> meta/recipes-graphics/pango/pango-1.28.4/multilib-fix-clean.patch >>> Laurentiu Palcu - >>> >>> meta/recipes-graphics/directfb/directfb/libdirect-remove-include-of-linux-config.h.patch >>> Cristian Iorga - >>> meta/recipes-extended/ltp/ltp/fix_building_fom_archive.patch >>> Xiaofeng Yan - meta/recipes-extended/lsb/lsbinitscripts/functions.patch >>> Mark Hatle - >>> meta/recipes-devtools/binutils/binutils/binutils-armv5e.patch >>> Mark Hatle - meta/recipes-devtools/rpm/rpm/rpm-resolvedep.patch >>> Andreas Müller - >>> >>> meta/recipes-kernel/systemtap/systemtap/runtime-staprun-configure.ac-support-without-nss-for.patch >>> Bruce Ashfield - >>> >>> meta/recipes-kernel/lttng-2.0/lttng-modules/lttng-sycalls-protect-is_compat_task-from-redefiniti.patch >> >> >> Your script is wrong here. That patch has everything you'd expect, >> since it follows kernel >> patch conventions. Subject, shortlog, log log and sign-off. >> >> So don't expect any resubmission from me on this one, since I won't be >> putting an upstream >> status directly in the patch. >> > This is a patch in OE-Core, not in the kernel, there is no reason you can't > update this patch to include the Upstream-Status:? What is the status of > this patch anyway? Is it a backport? It's still patching kernel code, that's always been the distinction we've drawn. Simply because it is being pushed (temporarily) via quilt or sits out of tree for a time, doesn't change the fact that if the patch is merged into the kernel tree, you'd have to strip those parts of the commit/header. I've always said that kernel patches would follow korg guidelines. That's the same reason why you don't see any YOCTO or other bug tracking information within the kernel patches. I've been consistent in this request since the dawn of time :) It seems to me that you are asking for the patch on disk: meta/recipes-kernel/lttng-2.0/lttng-modules/lttng-sycalls-protect-is_compat_task-from-redefiniti.patch To be modified with that information .. which isn't what I'd want to do. If we want to track that, it can be tracked as part of the commit to oe-core, but not in the patch itself. As for whether or not is upstream or not and the compatibility, it was captured as part of the commit to oe-core: lttng-modules: fix compliation error with 3.2.x -stable kernels The point is taken that the information should be standardized, and that this patch falls into a grey area. That original commit header should have used better language to track the status, but I recall there being quite the rush to get it fixed. We need some flexibility in the tracking, since there is no such thing as one size fits all, since everything is tracked in a SCM, putting the information within the SCM itself is a valid option (and what I'm suggesting here). The lttng2 modules need a complete refresh and rework, which will happen against the 3.4 kernel, so this will be fixed as part of that effort. Cheers, Bruce > > Sau! > > > > >> Bruce >> >>> >>> >>> Thanks >>> -- >>> Sau! >>> >>> Saul Wold >>> Yocto Component Wrangler @ Intel >>> Yocto Project / Poky Build System >>> >>> >>> ___ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> >> >> >> > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] linux-yocto/meta-yocto: update yaffs2 and drop rc6
Updating the 3.4 SRCREVs to pickup a yaffs2 update and the removal of a feature that was required in the 3.2 kernel tree. 1/2 [ meta: rc6: remove rc6 patches for snb The sandybridge rc6 patches are part of the released v3.4 kernel. Hence there is no need to keep these patches in the 3.4 linux yocto kernel repository. Signed-off-by: Nitin A Kamble ] 2/2 [ yaffs2: update core support Uprev yaffs2 to latest version as of 2012-05-29 ] Signed-off-by: Bruce Ashfield --- .../recipes-kernel/linux/linux-yocto_3.4.bbappend |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend index cb8c3aa..6d7d54d 100644 --- a/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend +++ b/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend @@ -3,10 +3,10 @@ KBRANCH_routerstationpro = "standard/routerstationpro" KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb" KBRANCH_beagleboard = "standard/beagleboard" -SRCREV_machine_atom-pc ?= "780ab7e11f03931295e8f0e29707f2abb688e9ad" -SRCREV_machine_routerstationpro ?= "780ab7e11f03931295e8f0e29707f2abb688e9ad" -SRCREV_machine_mpc8315e-rdb ?= "2d99f67fe6b4301cefd4e6f9a5ce75a9cc84686b" -SRCREV_machine_beagleboard ?= "780ab7e11f03931295e8f0e29707f2abb688e9ad" +SRCREV_machine_atom-pc ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72" +SRCREV_machine_routerstationpro ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72" +SRCREV_machine_mpc8315e-rdb ?= "a371ff9dc5cbf9629fd3257d57120d5182e0d981" +SRCREV_machine_beagleboard ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72" COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb" # COMPATIBLE_MACHINE_routerstationpro = "routerstationpro" -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/2] linux-yocto/linux-yocto-rt: updats and 3.4-rt support
Richard/Saul, When I sent the initial 3.4 kernel and kernel recipes -rt wasn't building, so I didn't include it. I've since refreshed the patch, and done build/boot testing. 3.4.1-rt9 is up and running. I've also got a yaffs2 update, and rc6 cleanup from nitin for the 3.4 kernel repository in this pull request. cc: Darren Hart Cheers, Bruce The following changes since commit a9c48f05ea9eb0901715cd628280eff22da766aa: linux-yocto/3.4: update yaffs2 and drop rc6 (2012-06-12 13:14:36 -0400) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (2): linux-yocto/3.4: create linux-yocto-rt recipe linux-yocto/meta-yocto: update yaffs2 and drop rc6 .../recipes-kernel/linux/linux-yocto_3.4.bbappend |8 ++-- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb| 32 meta/recipes-kernel/linux/linux-yocto_3.4.bb |2 +- 3 files changed, 37 insertions(+), 5 deletions(-) create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb -- 1.7.5.4 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] linux-yocto/3.4: create linux-yocto-rt recipe
Adding the 3.4 variant of the linux-yocto-rt recipe. This updates
to 3.4.1-rt9, and builds and boots on the supported targets.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 32 +++
meta/recipes-kernel/linux/linux-yocto_3.4.bb|2 +-
2 files changed, 33 insertions(+), 1 deletions(-)
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
new file mode 100644
index 000..d7de4b6
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb
@@ -0,0 +1,32 @@
+inherit kernel
+require recipes-kernel/linux/linux-yocto.inc
+
+KBRANCH = "standard/preempt-rt/base"
+KBRANCH_qemuppc = "standard/preempt-rt/qemu-ppc32"
+
+LINUX_VERSION ?= "3.4.1"
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+KMETA = "meta"
+
+SRCREV_machine_machine ?= "9dc5e97d144abb03deec411acb9c64883602cff9"
+SRCREV_machine_qemuppc ?= "241a41d6104df6916280f1273894bbd7fa7cdd71"
+SRCREV_meta ?= "aa226dcc5a1351fae49da40d77b718c4c3a76e7c"
+
+PR = "r0"
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
+
+# Omit broken machines from COMPATIBLE_MACHINE
+# qemuppc hangs at boot
+# qemumips panics at boot
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
+
+# Functionality flags
+KERNEL_FEATURES = "features/netfilter"
+KERNEL_FEATURES_append = " features/taskstats"
+KERNEL_FEATURES_append_qemux86 = " cfg/sound"
+KERNEL_FEATURES_append_qemux86-64 = " cfg/sound"
+
+require recipes-kernel/linux/linux-tools.inc
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
index 9205901..af6130d 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
@@ -16,7 +16,7 @@ SRCREV_machine_qemuppc ?=
"4988a7e34bccd531b511c57f93358de9fcc672a0"
SRCREV_machine_qemux86 ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72"
SRCREV_machine_qemux86-64 ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72"
SRCREV_machine ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72"
-SRCREV_meta ?= "978f876e4368cdd0ef781e74ea28a6771bf69b79"
+SRCREV_meta ?= "aa226dcc5a1351fae49da40d77b718c4c3a76e7c"
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
--
1.7.5.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
