From: Robert Schwebel <r.schwebel@pengutronix.de>
To: IngoM <ingo.maindorfer@ipm.fraunhofer.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [Virtex 4 PPC] Which Linux?
Date: Tue, 5 Feb 2008 15:58:34 +0100 [thread overview]
Message-ID: <20080205145834.GQ13945@pengutronix.de> (raw)
In-Reply-To: <15268468.post@talk.nabble.com>
On Mon, Feb 04, 2008 at 05:54:55AM -0800, IngoM wrote:
> 2) Linux
> I'd like to build my kernel and filesystem myself. But which way to go?
> Using OE, buildroot, ELDK...
> Can you please provide some starting points for me?
ptxdist would be another alternative.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
next prev parent reply other threads:[~2008-02-05 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 13:54 [Virtex 4 PPC] Which Linux? IngoM
2008-02-04 15:32 ` Grant Likely
2008-02-05 14:58 ` Robert Schwebel [this message]
2008-02-06 14:51 ` IngoM
2008-02-06 19:29 ` Stephen Neuendorffer
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=20080205145834.GQ13945@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=ingo.maindorfer@ipm.fraunhofer.de \
--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).