From: Dan Malek <dan@embeddededge.com>
To: Brad Bonkoski <bradb59@home.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ADS 8260
Date: Thu, 15 Nov 2001 00:52:05 -0500 [thread overview]
Message-ID: <3BF35805.5000702@embeddededge.com> (raw)
In-Reply-To: 3BF31908.7E591B3B@home.com
Brad Bonkoski wrote:
> I noticed that in the current linuxppc_2_4_devel kernel tree there is no
> longer an option for the ADS8260 platform. Is one of the other 8260
> boards compatible with this one, if so which one?
Sorry, I have some updates that I have yet to pull out of the HHL 2.0
distribution into this kernel. The changes are trivial, I just haven't
done it. Maybe over the weekend..........or you could just download
the HHL 2.0 Journeyman edition for the ADS8260 and send me the patches :-).
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-15 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 1:23 ADS 8260 Brad Bonkoski
2001-11-15 5:52 ` Dan Malek [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=3BF35805.5000702@embeddededge.com \
--to=dan@embeddededge.com \
--cc=bradb59@home.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;
as well as URLs for NNTP newsgroup(s).