From: Brendan Simon <bsimon@ctam.com.au>
To: Dan Malek <dmalek@jlc.net>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx updates
Date: Wed, 15 Sep 1999 13:02:17 +1000 [thread overview]
Message-ID: <37DF0C38.34352830@ctam.com.au> (raw)
In-Reply-To: 37DF00DD.A0806F12@jlc.net
Dan Malek wrote:
> 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.
Sounds ok.
The other thing that needs to be done is the help documentation. I tend to
use "make xconfig" when configuring my kernel. This gives me the ability to
load and store configuration files and then only change the bits I need to
without going through the entire configuration processes. The other reason is
that it has a help button for all the configuration options. I believe "make
menuconfig" also has help features. There are so many options that it is hard
to remember what all of them do (unless you have read the docs a million
times). The 2.2.x and 2.3.x series from kernel mirrors have the help docs but
none of the embedded archives (embedded-2.2.5 and mpc8xx-2.3.10) seem to have
them. I think its just a matter of copying the help files to the
Documentation directory.
Brendan Simon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-09-15 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-15 2:13 8xx updates Dan Malek
1999-09-15 3:02 ` Brendan Simon [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=37DF0C38.34352830@ctam.com.au \
--to=bsimon@ctam.com.au \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.