From: Dan Malek <dmalek@jlc.net>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: 8xx updates
Date: Tue, 14 Sep 1999 22:13:49 -0400 [thread overview]
Message-ID: <37DF00DD.A0806F12@jlc.net> (raw)
OK. I just posted all of the outstanding 8xx updates to the
CVS tree. Read the web page for more info.
I will probably make mbx_defconfig a generic m8xx_defconfig that will
build on all boards. You can then selectively add features you
know your board supports. I just haven't found the lowest
common denominator yet.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-15 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-15 2:13 Dan Malek [this message]
1999-09-15 3:02 ` 8xx updates Brendan Simon
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=37DF00DD.A0806F12@jlc.net \
--to=dmalek@jlc.net \
--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).