linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Brian Silverman" <bsilverman@conceptxdesign.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Full Linux distributions
Date: Thu, 3 Jul 2008 22:03:33 +0200	[thread overview]
Message-ID: <c384c5ea0807031303i1ddf7663na80928fd77d40be5@mail.gmail.com> (raw)
In-Reply-To: <486D27B9.8090308@conceptxdesign.com>

Hello Brian,

On Thu, Jul 3, 2008 at 9:25 PM, Brian Silverman
<bsilverman@conceptxdesign.com> wrote:
> I'm looking for advice into what Linux distributions (rootfs) people are
> using for the PowerPC.
>
> Specifically, I'm currently using busybox for my core rootfs, but I'm
>
buildroot I guess, not busybox (alone).

> looking for an alternative that will allow me to:
>   - easily add new packages

>   - is binary compatible with the PPC405. 440, and Freescale 85xx cores.
>
binary compatible? You mean it can build binaries for those cores?

>   - can be large (compared to the usual embedded devices), say in the 100MB
> to 1GB range.  It will sit on an SD card.
>   - Can be built/maintained under cygwin, and can generate a ext2 image
> (e.g. with gen2extfs)
>
>   3) OpenEmbedded (doesn't seem to currently support cygwin)
>
My preference is to use OpenEmbedded and do so under a Linux host
system (any will do).
As I don't want to be tied to a certain host OS, Emdebian or
Gentoo-Embedded are no-go for me.

I have used tools and rootfs systems like crosstool, buildroot, LFS before.

There is also LTIB by Freescale, tried that?

Regards,
-- 
Leon

  reply	other threads:[~2008-07-03 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 19:25 Full Linux distributions Brian Silverman
2008-07-03 20:03 ` Leon Woestenberg [this message]
2008-07-03 20:12   ` Brian Silverman
2008-07-03 23:59     ` Daniel Stonier
2008-07-04 11:48       ` Detlev Zundel

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=c384c5ea0807031303i1ddf7663na80928fd77d40be5@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=bsilverman@conceptxdesign.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).