linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stuart Hughes <stuarth@freescale.com>
To: tmorrison@empirix.com
Cc: linuxppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: options for root file system for MPC8548
Date: Wed, 31 Jan 2007 09:11:37 +0000	[thread overview]
Message-ID: <1170234697.25841.90.camel@m20> (raw)

> On Jan 30, 2007, at 4:19 PM, Morrison, Tom wrote:
> <snip intro>
> > We do NOT want to use LTIB (supplied by Freescale) to create one
> > (for multiple reasons - including the same as ELDK).
> 
> Can you elaborate on what issues you have with ELDK/LTIB, is it just  
> package support?  If so it might be useful for the developers to know  
> what packages you're interested in.  Or if there are other issues  
> with them.
> 
> LTIB uses busybox and in general seems very limited in its support
> (as well as currently backdated in terms of kernel support). 
> ELDK has an incredible set of packages that it supports, but 
> things like many of the scripting languages support (e.g.: PERL),
> additional security libraries(e.g.: ipsec), general network 
> libraries (e.g.: libpcap), and some network utilities (e.g.: wget).
> 
> Individually, none of these are serious, but altogether it's a lot
> to manage - if I had 1 stop shopping, I might go there instead of 
> with the ever incredible ELDK!
> 

Hi Tom,

I just wanted to clear up some points about LTIB:

* If you want support for LTIB go here: http://www.bitshrine.org/ and
there is a mailing list here:
http://lists.nongnu.org/mailman/listinfo/ltib

* Busybox is the default for most platforms, but you don't have to use
it.  Also note that as you scale up the size of the root filesystem it
will replace the busybox utilities with the full ones (and manage
dependencies).

* The kernels as supplied for BSPs represent things that are tested and
are known to work.  If you're a kernel developer, or just want to use a
later kernel, simply choose the 'Local Linux directory build' option.
This will build any kernel (with KBUILD_OUTPUT support).  So you can use
git/cvs/tarballs whatever.  All you need is the unpacked source
somewhere on your local machine.

* LTIB does have all the packages you mention.  Any that are not there
are easy to add.

* LTIB should not be used if: you want a full desktop root filesystem
(e.g. graphics, multi-media, office apps).  Instead I'd recommend using
Debian or some other destktop distro.  However for something like the
8548, you'd need to re-built it with the appropriate DPFP aware
toolchain.

Regards Stuart

             reply	other threads:[~2007-01-31  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31  9:11 Stuart Hughes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-30 22:19 options for root file system for MPC8548 Morrison, Tom
2007-01-30 22:31 ` Kumar Gala
2007-01-30 22:42   ` Morrison, Tom
2007-01-30 22:50     ` Kumar Gala
2007-01-30 23:14       ` Morrison, Tom
2007-01-31 20:52         ` Andy Fleming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1170234697.25841.90.camel@m20 \
    --to=stuarth@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tmorrison@empirix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).