Re: PPC tool chain - uClibc

In message <s0c0b448.016@EMAIL> you wrote:

I have taken the ELDK distro and using its tool chain.
I have compiled uClibc also with the cross compiler.(ppc)
After installing uClibc also the ppc cross compiler is refering glibc
library only. How to change wrap ppc with uClibc...

The uCLibc project comes with some descriptions what needs to be done
to build a toolchain. See http://www.uclibc.org/toolchains.html

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"Ada is PL/I trying to be Smalltalk.                 - Codoso diBlini

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

I am participating in a project that has a challenging boot time
requirement. We need a Linux boot solution where we have booted in the
50msec range, talking on a protocol stack, from a COLD Start (power being
applied to the board.) The loading of the drivers and the stack
initialization has to occur within 50msec.

Does anyone have any leads/ideas for being able to meet this deadline?

Thanks,
Kevin Dankwardt


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

There are some simple things you need to do for this.  The first is
abondon the idea that EVERYTHING needs to be done in 50msec!  What you
really want is a base set of functionality that exists in the 50msec
range, then you bring up the rest of the functionality either as
required or in parallel with other system tasks.

What you want to do is have a minimal driver set built into the kernel.
 Also, get your firmware optimized as much as possible.  A lot of the
time, the firmware can eat a large chunk of time.

Basically you will boot the kernel with minimal drivers (perhaps just a
single filesystem driver).  Once the kernel hits userspace, load the
driver modules in an appropriate order.  If that is still not fast
enough, you will have to modify the drivers to allow for parallel system
initialization.

So my point in all of the above is figure out the exact minimum
requirements you have.  Work on getting that up "first".  Then expand to
your full compliment of drivers and userspace applications.

--Mark

Kevin P. Dankwardt wrote:

I am participating in a project that has a challenging boot time
requirement. We need a Linux boot solution where we have booted in the
50msec range, talking on a protocol stack, from a COLD Start (power being
applied to the board.) The loading of the drivers and the stack
initialization has to occur within 50msec.

Does anyone have any leads/ideas for being able to meet this deadline?

Thanks,
Kevin Dankwardt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Kevin,

On Mon, 7 Jun 2004, Kevin P. Dankwardt wrote:

I am participating in a project that has a challenging boot time

...

Does anyone have any leads/ideas for being able to meet this deadline?

I once had the (probably rather weird) idea than one could port the
swsusp.sf.net stuff to PPC to shorten the boot time. Don't know if
it's really saving that much, though, since the driver modules need to
be unloaded/loaded anyway.

Regards,
Marius

--
Marius Groeger [off-list ref]           Project Manager
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

On Tue, 2004-06-08 at 10:35, Marius Groeger wrote:

Kevin,

On Mon, 7 Jun 2004, Kevin P. Dankwardt wrote:

quoted

I am participating in a project that has a challenging boot time

...

quoted

Does anyone have any leads/ideas for being able to meet this deadline?

Btw, does anyone know what has happened to
"Software tweak boots Linux in under 200 ms"?

http://www.linuxdevices.com/news/NS5907201615.html

I guess you can't make such tweaks into a proprietary module...

--
Stefan Nickl
Kontron Modular Computers


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

On Tue, 2004-06-08 at 03:57, Kevin P. Dankwardt wrote:

I am participating in a project that has a challenging boot time
requirement. We need a Linux boot solution where we have booted in the
50msec range, talking on a protocol stack, from a COLD Start (power being
applied to the board.) The loading of the drivers and the stack
initialization has to occur within 50msec.

Does anyone have any leads/ideas for being able to meet this deadline?

You don't say much about the hardware but I would say it's a borderline
case even if you put a lot of work into it.

say you have a 8bit flash 120ns access time that gives
8.3 MB/sec thus you can only copy 400kB data in 50ms so you have barley
enough time getting the data into dram before your time is up.

It's not going to happen just checking a config option that's for sure.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/