From: David Woodhouse <dwmw2@infradead.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Bastos Fernandez Alexandre <ALEBAS@televes.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: ELDK & MPC8272ADS. Machine check
Date: Fri, 02 Jul 2004 11:39:50 +0100 [thread overview]
Message-ID: <1088764790.14216.4230.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20040702101005.8790FC109F@atlas.denx.de>
On Fri, 2004-07-02 at 12:10 +0200, Wolfgang Denk wrote:
> You will need a version of the Linux kernel tree which includes
> support for the MPC8272ADS board. The kernel tree inlucded with the
> ELDK does not contain such support. You will probably be able to use
> the "ads8260" configuration to some extend, though.
The 2.6.7 kernel got support for the MPC8272ADS quite recently.
--
dwmw2
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-07-02 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 9:28 ELDK & MPC8272ADS. Machine check Bastos Fernandez Alexandre
2004-07-02 10:10 ` Wolfgang Denk
2004-07-02 10:39 ` David Woodhouse [this message]
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=1088764790.14216.4230.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=ALEBAS@televes.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).