From: Wolfgang Denk <wd@denx.de>
To: Jeff Stevens <jsteve17@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ELDK based on YDL 3.0?
Date: Wed, 12 Nov 2003 20:41:28 +0100 [thread overview]
Message-ID: <20031112194133.8AED5C5F59@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 12 Nov 2003 10:32:24 PST." <20031112183224.7655.qmail@web41401.mail.yahoo.com>
Dear Jeff,
in message <20031112183224.7655.qmail@web41401.mail.yahoo.com> you wrote:
>
> I am getting ready to build a filesystem based on the
> YellowDog Linux 3.0 release. However, when I
> downloaded the build environment from www.denx.de, I
> notice that the ELDK_BUILD script already points to
> the 3.0 SRPMS. Does that mean that there will be an
> ELDK release based on YDL 3.0 soon? If so, what
This is correct. We are working on it. It should have been ready at
least 3 weeks ago, but we're still fixing problems. If you want to
use the stable version 2.1.1 instead you can find in on the CVS
server tagged as ELDK_2_1_1
> kernel version will it use?
2.4.20 probably. Maybe something later - since we are so late anyway
we might as well wait and use a kernel that supports the MPC5200,
too.
Why are you asking? Do you need some special version?
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
All he had was nothing, but that was something, and now it had been
taken away. - Terry Pratchett, _Sourcery_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-12 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 18:32 ELDK based on YDL 3.0? Jeff Stevens
2003-11-12 19:41 ` Wolfgang Denk [this message]
[not found] <D13FBFDEA70AD111A44900A0C92316930350B757@postoffice.systran.com>
2003-11-13 16:46 ` Wolfgang Denk
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=20031112194133.8AED5C5F59@atlas.denx.de \
--to=wd@denx.de \
--cc=jsteve17@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.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