| 1 |
On Aug 18, 2005, at 2:46 AM, Marcel Romijn wrote: |
| 2 |
>> As it is a x86 howto, here are the possible values for UCLIBC_CPU: |
| 3 |
>> |
| 4 |
>> 386, 486, ELAN, 586, 586MMX, 686, PENTIUMII, |
| 5 |
>> PENTIUMIII,PENTIUM4, K6, K7, |
| 6 |
>> CRUSOE, WINCHIPC6, WINCHIP2, CYRIXIII, NEHEMIAH. |
| 7 |
>> |
| 8 |
>> For people with VIA boards, take CYRIXIII or NEHEMIAH. |
| 9 |
>> |
| 10 |
> |
| 11 |
> Is this setting used for both the development and the embedded |
| 12 |
> machine? |
| 13 |
> |
| 14 |
> I'm developing on a Pentium4, but I'm deploying to a VIA board |
| 15 |
> (CytrixIII). |
| 16 |
|
| 17 |
The idea in this Howto is to use filesystems inside filesystems. What |
| 18 |
I mean is this (pardon me if you already know this stuff): |
| 19 |
|
| 20 |
I have a full Gentoo installation with all the optimizations for my |
| 21 |
desktop processor installed. |
| 22 |
|
| 23 |
Then, following the Howto, I create on my harddrive a directory called: |
| 24 |
|
| 25 |
/opt/i586-gentoo-uclibc-linux |
| 26 |
|
| 27 |
And inside that you basically install a SECOND gentoo installation, |
| 28 |
but this time using uclibc and with optimizations for your target |
| 29 |
platform. This is sort of a bridge to the eventual filesystem you'll |
| 30 |
install on your embedded device. X, KDE, Gnome, or whatever will |
| 31 |
still run on your regular installation, but when you build targets |
| 32 |
for the embedded device, you'll change into this new uclib based |
| 33 |
filesystem, which is optimized for the embedded environment. Thats |
| 34 |
what the chroot command does. I |
| 35 |
|
| 36 |
But this development installation, although optimized for your target |
| 37 |
device has too much junk to install onto an embedded device (the |
| 38 |
entire portage tree for example), so that is why you created the / |
| 39 |
embedded_rootfs directory, and emerge binary packages into that |
| 40 |
directory. Emerging just the binaries will ensure you don't get too |
| 41 |
much extra garbage in the final filesystem you'll install to your |
| 42 |
device. |
| 43 |
|
| 44 |
After following this howto, your computer filestructure will look |
| 45 |
like this: |
| 46 |
|
| 47 |
/ <- Your desktop optimized installation. Could be Gentoo, SuSE, |
| 48 |
RedHat, or anything else. |
| 49 |
| - dev/ |
| 50 |
| - home/ |
| 51 |
| - .... (etc) |
| 52 |
| - /opt/i586-gentoo-uclibc/ <- 'full' Gentoo installation optimized |
| 53 |
for your embedded machine |
| 54 |
| |
| 55 |
| - embedded_rootfs <-'minimal' |
| 56 |
install to put onto the embedded device. |
| 57 |
|
| 58 |
|
| 59 |
Maybe putting this explanation in the How-to would be useful? |
| 60 |
|
| 61 |
-Josh |
| 62 |
|
| 63 |
|
| 64 |
-- |
| 65 |
Joshua ChaitinPollak |
| 66 |
Software Engineer |
| 67 |
Kiva Systems |
| 68 |
|
| 69 |
|
| 70 |
-- |
| 71 |
gentoo-embedded@g.o mailing list |
Archives