[coreboot] SimNOW V2 LAB problem
mylesgw at gmail.com
Fri May 9 17:40:57 CEST 2008
> -----Original Message-----
> From: Jordan Crouse [mailto:jordan.crouse at amd.com]
> Sent: Friday, May 09, 2008 9:16 AM
> To: Myles Watson; Marc.Karasek at Sun.COM; coreboot at coreboot.org
> Subject: Re: SimNOW V2 LAB problem
> On 08/05/08 20:32 -0400, Ward Vandewege wrote:
> > On Thu, May 08, 2008 at 03:52:21PM -0600, Myles Watson wrote:
> > > > Disregard my feeble wanderings.. I was thinking about my attempt to
> > > > move busybox to 1.10.1 and the problems I was seeing there.
> > > >
> > > > I think though the two are related. Seems that uClibc 0.9.29 no
> > > > supports the toolchain wrappers for -nostdlib and forcing a linking
> > > > native tools (gcc/binutils) and a compiled uClibc library. This was
> > > > pulled in 0.9.22 according to the uclibc FAQ. Maybe it was just a
> > > > off that FC5 still worked.
> > >
> > > Strange. It worked for 0.9.28 as well. Those are the two versions
> > > used in buildrom.
> > >
> > > Ward: You've used lab haven't you? What toolchain do you use?
> > Yep, I've got LAB systems running. I build on gNewsense deltad
> > which is basically Ubuntu Dapper, 32 bit.
> It might be time for us to ping the uClibc / busybox teams for some
So you think it's a broken uClibc / busybox problem, not a compiler/binutils
I'm inclined to think that it's a toolchain issue since I can't build v2 on
my 32-bit system. I don't know how to tell the difference, though.
Having the serial port continue working through the kernel on SimNow would
More information about the coreboot