Debugging u-boot

Debugging u-boot

[Bernard Mentink]

Hi All,

Can some one please tell me how to debug u-boot  on my target. I have
built u-boot for similar hardware and I want to debug with gdb, but
cannot even find the cross-compile version of gdb,
It does not exist in the directory
"build/tmp/sysroots/i686-linux/usr/armv6/bin/" where the other
cross-compile tools live ..

I want to execute "${CROSS_COMPILE}gdb u-boot"
 .. and breakpoint at some very early symbol ..... Some steps to
achieving this would be much appreciated ..

Many Thanks,
Bernie

Re: Debugging u-boot

[Charles Manning]

Bernie

What toolchain are you building?

If you build meta-toolchain that should build all the stuff you can put into
/usr/local/angstrom/arm/... which includes gdb.

That should then work with a JTAG debugger etc.

-- Charles


On Thu, Jul 7, 2011 at 11:25 AM, Bernard Mentink
<Bernard_Mentink@trimble.com> wrote:
> Hi All,
>
> Can some one please tell me how to debug u-boot  on my target. I have
> built u-boot for similar hardware and I want to debug with gdb, but
> cannot even find the cross-compile version of gdb,
> It does not exist in the directory
> "build/tmp/sysroots/i686-linux/usr/armv6/bin/" where the other
> cross-compile tools live ..
>
> I want to execute "${CROSS_COMPILE}gdb u-boot"
>  .. and breakpoint at some very early symbol ..... Some steps to
> achieving this would be much appreciated ..
>
> Many Thanks,
> Bernie
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: Debugging u-boot

[Bernard Mentink]

Hi Charles,

Didn't know you were lurking on this list ... ;-) 

I have built for the angstom distro (arm-angstrom-linux-gnueabi-*), but the tools got put in my project path I described in my earlier email, but
There was no GDB included for some reason ..

How do you build the meta-toolchain, and how will that help.

Cheers,
Bernie


------------------------------------------------------------------------------------------
I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car.

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Charles Manning
Sent: Thursday, 7 July 2011 12:38 p.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Debugging u-boot

Bernie

What toolchain are you building?

If you build meta-toolchain that should build all the stuff you can put into /usr/local/angstrom/arm/... which includes gdb.

That should then work with a JTAG debugger etc.

-- Charles


On Thu, Jul 7, 2011 at 11:25 AM, Bernard Mentink <Bernard_Mentink@trimble.com> wrote:
> Hi All,
>
> Can some one please tell me how to debug u-boot  on my target. I have 
> built u-boot for similar hardware and I want to debug with gdb, but 
> cannot even find the cross-compile version of gdb, It does not exist 
> in the directory "build/tmp/sysroots/i686-linux/usr/armv6/bin/" where 
> the other cross-compile tools live ..
>
> I want to execute "${CROSS_COMPILE}gdb u-boot"
>  .. and breakpoint at some very early symbol ..... Some steps to 
> achieving this would be much appreciated ..
>
> Many Thanks,
> Bernie
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Debugging u-boot

[Charles Manning]

On Thu, Jul 7, 2011 at 1:13 PM, Bernard Mentink
<Bernard_Mentink@trimble.com> wrote:
> Hi Charles,
>
> Didn't know you were lurking on this list ... ;-)

You can run but you can't hide.

>
> I have built for the angstom distro (arm-angstrom-linux-gnueabi-*), but the tools got put in my project path I described in my earlier email, but
> There was no GDB included for some reason ..

The regular toolchian than oe builds for its own purposes does not use
gdb because gdb is not needed for building. That toolchain is intended
for use within OE bitbakery only.

A meta-toolchain is built as a standalone toolchain intended for use
outside of OE (eg. if you pull u-boot to a standalone directory for
development purposes or want to do your own app development outside of
OE.)

>
> How do you build the meta-toolchain, and how will that help.


bitbake meta-toolchain.

This makes a toolchain which you can unpack thus:

$ cd /
$ sudo tar xvjf
${OETOP}/tmp/deploy/glibc/sdk/angstrom-2009.X-test-20110301-armv7a-linux-gnueabi-toolchain.tar.bz2

[NB your toolchain name will be something different]


To set up all the paths etc use

. /usr/local/angstrom/arm/environment-setup

Google openembedded metatoolchain will also give some interesting info.

NB If you're building apps and need extra libraries you will need to
make your own SDK. That's a bit more effort and you don't need all
that just for gdbing u-boot

-- Charles

>
> Cheers,
> Bernie
>
>
> ------------------------------------------------------------------------------------------
> I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car.
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Charles Manning
> Sent: Thursday, 7 July 2011 12:38 p.m.
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] Debugging u-boot
>
> Bernie
>
> What toolchain are you building?
>
> If you build meta-toolchain that should build all the stuff you can put into /usr/local/angstrom/arm/... which includes gdb.
>
> That should then work with a JTAG debugger etc.
>
> -- Charles
>
>
> On Thu, Jul 7, 2011 at 11:25 AM, Bernard Mentink <Bernard_Mentink@trimble.com> wrote:
>> Hi All,
>>
>> Can some one please tell me how to debug u-boot  on my target. I have
>> built u-boot for similar hardware and I want to debug with gdb, but
>> cannot even find the cross-compile version of gdb, It does not exist
>> in the directory "build/tmp/sysroots/i686-linux/usr/armv6/bin/" where
>> the other cross-compile tools live ..
>>
>> I want to execute "${CROSS_COMPILE}gdb u-boot"
>>  .. and breakpoint at some very early symbol ..... Some steps to
>> achieving this would be much appreciated ..
>>
>> Many Thanks,
>> Bernie
>>
>>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: Debugging u-boot

[Bernard Mentink]

Hi Charles,

Tried that but got the following linker error:

---------------------------------------------------------- error ---------------------------------------
| /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: failed to merge target specific data of file emutls_s.o
| /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: error: /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o uses VFP register arguments, ./libgcc_s.so.1.tmp does not
| /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: failed to merge target specific data of file /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o
| collect2: ld returned 1 exit status
| make[2]: *** [libgcc_s.so] Error 1
| make[2]: Leaving directory `/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgcc'
| make[1]: *** [all-target-libgcc] Error 2
| make[1]: Leaving directory `/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi'
| make: *** [all] Error 2
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL
NOTE: package gcc-cross-sdk-4.5-r36.2+svnr170880: task do_compile: Failed
ERROR: Function 'do_compile' failed (see /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/temp/log.do_compile.14514 for further information)
ERROR: Task 594 (/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb, do_compile) failed with exit code '1'
ERROR: '/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb' failed
-----------------------------------------------------------------------------------------------------

Any idea what it could be? 

Cheers,
bernie

 


------------------------------------------------------------------------------------------
I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car.

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Charles Manning
Sent: Thursday, 7 July 2011 1:52 p.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Debugging u-boot

On Thu, Jul 7, 2011 at 1:13 PM, Bernard Mentink <Bernard_Mentink@trimble.com> wrote:
> Hi Charles,
>
> Didn't know you were lurking on this list ... ;-)

You can run but you can't hide.

>
> I have built for the angstom distro (arm-angstrom-linux-gnueabi-*), 
> but the tools got put in my project path I described in my earlier email, but There was no GDB included for some reason ..

The regular toolchian than oe builds for its own purposes does not use gdb because gdb is not needed for building. That toolchain is intended for use within OE bitbakery only.

A meta-toolchain is built as a standalone toolchain intended for use outside of OE (eg. if you pull u-boot to a standalone directory for development purposes or want to do your own app development outside of
OE.)

>
> How do you build the meta-toolchain, and how will that help.


bitbake meta-toolchain.

This makes a toolchain which you can unpack thus:

$ cd /
$ sudo tar xvjf
${OETOP}/tmp/deploy/glibc/sdk/angstrom-2009.X-test-20110301-armv7a-linux-gnueabi-toolchain.tar.bz2

[NB your toolchain name will be something different]


To set up all the paths etc use

. /usr/local/angstrom/arm/environment-setup

Google openembedded metatoolchain will also give some interesting info.

NB If you're building apps and need extra libraries you will need to make your own SDK. That's a bit more effort and you don't need all that just for gdbing u-boot

-- Charles

>
> Cheers,
> Bernie
>
>
> ----------------------------------------------------------------------
> -------------------- I want to die peacefully in my sleep, like my 
> grandfather, not screaming and yelling like the passengers in his car.
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org 
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf 
> Of Charles Manning
> Sent: Thursday, 7 July 2011 12:38 p.m.
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] Debugging u-boot
>
> Bernie
>
> What toolchain are you building?
>
> If you build meta-toolchain that should build all the stuff you can put into /usr/local/angstrom/arm/... which includes gdb.
>
> That should then work with a JTAG debugger etc.
>
> -- Charles
>
>
> On Thu, Jul 7, 2011 at 11:25 AM, Bernard Mentink <Bernard_Mentink@trimble.com> wrote:
>> Hi All,
>>
>> Can some one please tell me how to debug u-boot  on my target. I have 
>> built u-boot for similar hardware and I want to debug with gdb, but 
>> cannot even find the cross-compile version of gdb, It does not exist 
>> in the directory "build/tmp/sysroots/i686-linux/usr/armv6/bin/" where 
>> the other cross-compile tools live ..
>>
>> I want to execute "${CROSS_COMPILE}gdb u-boot"
>>  .. and breakpoint at some very early symbol ..... Some steps to 
>> achieving this would be much appreciated ..
>>
>> Many Thanks,
>> Bernie
>>
>>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-deve
>> l
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Debugging u-boot

[Khem Raj]

On 07/07/2011 12:25 PM, Bernard Mentink wrote:
> Hi Charles,
>
> Tried that but got the following linker error:
>
> ---------------------------------------------------------- error ---------------------------------------
> | /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: failed to merge target specific data of file emutls_s.o
> | /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: error: /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o uses VFP register arguments, ./libgcc_s.so.1.tmp does not
> | /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: failed to merge target specific data of file /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o
> | collect2: ld returned 1 exit status
> | make[2]: *** [libgcc_s.so] Error 1

this means there is fp ABI gotcha is it on latest oe.dev ? I remember 
fixing the hard FP build on oe.dev  see commit 
888c1f3a2e103793bc03488d2051ee4683f7516a

I dont know if that was picked for 2011.03 release branch

Re: Debugging u-boot

[Bernard Mentink]

Hi Charles,

Building for Angstom and imx31 ..

Cheers,
Bernie 


------------------------------------------------------------------------------------------
I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car.

-----Original Message-----
From: Charles Manning [mailto:manningc2@actrix.gen.nz] 
Sent: Tuesday, 12 July 2011 10:17 a.m.
To: openembedded-devel@lists.openembedded.org
Cc: Bernard Mentink
Subject: Re: [oe] Debugging u-boot

Hmmm.

What are you building for?
Works fine for me using the Angstrom build for omap3 (beagleboard, overo etc).



On Friday 08 July 2011 07:25:04 Bernard Mentink wrote:
> Hi Charles,
>
> Tried that but got the following linker error:
>
> ---------------------------------------------------------- error
> ---------------------------------------
>
> | 
> |/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstr
> |om-l
> |inux-gnueabi/bin/ld: failed to merge target specific data of file  
> |emutls_s.o  
> |/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstr
> |om-l
> |inux-gnueabi/bin/ld: error:
> | 
> |/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnuea
> |bi/g 
> |cc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm
> |-angs trom-linux-gnueabi/./gcc/crtendS.o uses VFP register arguments,  
> |./libgcc_s.so.1.tmp does not  
> |/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstr
> |om-l
> |inux-gnueabi/bin/ld: failed to merge target specific data of file  
> |/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnuea
> |bi/g 
> |cc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm
> |-angs trom-linux-gnueabi/./gcc/crtendS.o collect2: ld returned 1 exit 
> |status
> | make[2]: *** [libgcc_s.so] Error 1
> | make[2]: Leaving directory
> | 
> |`/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnue
> |abi/ 
> |gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.ar
> |m-ang strom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgcc' make[1]: 
> |***  [all-target-libgcc] Error 2
> | make[1]: Leaving directory
> | 
> |`/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnue
> |abi/ 
> |gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.ar
> |m-ang strom-linux-gnueabi' make: *** [all] Error 2
> | + die 'oe_runmake failed'
> | + oefatal 'oe_runmake failed'
> | + echo FATAL
>
> NOTE: package gcc-cross-sdk-4.5-r36.2+svnr170880: task do_compile: 
>Failed
> ERROR: Function 'do_compile' failed (see  
>/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi
>/gcc
>-cross-sdk-4.5-r36.2+svnr170880/temp/log.do_compile.14514 for further
> information) ERROR: Task 594
> (/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb,
> do_compile) failed with exit code '1' ERROR:
> '/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb' 
>failed
> 
>-----------------------------------------------------------------------
>----
>--------------------------
>
> Any idea what it could be?
>
> Cheers,
> bernie
>
>
>
>
> 
>-----------------------------------------------------------------------
>----
>--------------- I want to die peacefully in my sleep, like my 
>grandfather,  not screaming and yelling like the passengers in his car.
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf 
> Of Charles Manning Sent: Thursday, 7 July 2011 1:52 p.m.
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] Debugging u-boot
>
> On Thu, Jul 7, 2011 at 1:13 PM, Bernard Mentink
<Bernard_Mentink@trimble.com> wrote:
> > Hi Charles,
> >
> > Didn't know you were lurking on this list ... ;-)
>
> You can run but you can't hide.
>
> > I have built for the angstom distro (arm-angstrom-linux-gnueabi-*), 
> > but the tools got put in my project path I described in my earlier 
> > email, but There was no GDB included for some reason ..
>
> The regular toolchian than oe builds for its own purposes does not use 
> gdb because gdb is not needed for building. That toolchain is intended 
> for use within OE bitbakery only.
>
> A meta-toolchain is built as a standalone toolchain intended for use 
> outside of OE (eg. if you pull u-boot to a standalone directory for 
> development purposes or want to do your own app development outside of 
> OE.)
>
> > How do you build the meta-toolchain, and how will that help.
>
> bitbake meta-toolchain.
>
> This makes a toolchain which you can unpack thus:
>
> $ cd /
> $ sudo tar xvjf
> 
>${OETOP}/tmp/deploy/glibc/sdk/angstrom-2009.X-test-20110301-armv7a-linu
>x-gn
>ueabi-toolchain.tar.bz2
>
> [NB your toolchain name will be something different]
>
>
> To set up all the paths etc use
>
> . /usr/local/angstrom/arm/environment-setup
>
> Google openembedded metatoolchain will also give some interesting info.
>
> NB If you're building apps and need extra libraries you will need to 
> make your own SDK. That's a bit more effort and you don't need all 
> that just for gdbing u-boot
>
> -- Charles
>
> > Cheers,
> > Bernie
> >
> >
> > --------------------------------------------------------------------
> > --
> > -------------------- I want to die peacefully in my sleep, like my 
> > grandfather, not screaming and yelling like the passengers in his car.
> >
> > -----Original Message-----
> > From: openembedded-devel-bounces@lists.openembedded.org
> > [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf 
> > Of Charles Manning
> > Sent: Thursday, 7 July 2011 12:38 p.m.
> > To: openembedded-devel@lists.openembedded.org
> > Subject: Re: [oe] Debugging u-boot
> >
> > Bernie
> >
> > What toolchain are you building?
> >
> > If you build meta-toolchain that should build all the stuff you can 
> > put into /usr/local/angstrom/arm/... which includes gdb.
> >
> > That should then work with a JTAG debugger etc.
> >
> > -- Charles
> >
> > On Thu, Jul 7, 2011 at 11:25 AM, Bernard Mentink
<Bernard_Mentink@trimble.com> wrote:
> >> Hi All,
> >>
> >> Can some one please tell me how to debug u-boot  on my target. I 
> >> have built u-boot for similar hardware and I want to debug with 
> >> gdb, but cannot even find the cross-compile version of gdb, It does 
> >> not exist in the directory 
> >> "build/tmp/sysroots/i686-linux/usr/armv6/bin/" where the other cross-compile tools live ..
> >>
> >> I want to execute "${CROSS_COMPILE}gdb u-boot"
> >>  .. and breakpoint at some very early symbol ..... Some steps to 
> >> achieving this would be much appreciated ..
> >>
> >> Many Thanks,
> >> Bernie
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-de
> >> ve
> >> l
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > el
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > el
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel