From: Dan Malek <dmalek@jlc•net>
To: Cort Dougan <cort@persephone•cs.nmt.edu>
Cc: Troy Benjegerdes <hozer@drgw•net>, linuxppc-dev@lists•linuxppc.org
Subject: Re: vger CVS questions
Date: Wed, 23 Dec 1998 01:36:05 -0500 [thread overview]
Message-ID: <36808F55.71DDCA9A@jlc.net> (raw)
In-Reply-To: Pine.LNX.3.96.981222023432.25778A-100000@persephone.cs.nmt.edu
Cort Dougan wrote:
> I think another branch would be a bad idea. Everything in the main tree
> is best for now.
I agree. Once you get comfortable working with the
kernel you will discover the 8xx modifications are minimal.
Trying to track other kernel updates in a unique 8xx tree
would not be spending time wisely :-).
I created an 8xx directory from the beginning to contain
those things unique to the 8xx. Right now, it contains
drivers and functions unique to the CPM or other 8xx I/O.
The only things we really need unique to the embedded
processors are support libraries. They need to be
compiled with software floating point, and minimal.
I was finally successful today building the glibc SRPM
for the 8xx processors. I will drop it on the server and
build a new embedded root file system image with them.
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists•linuxppc.org ]]
prev parent reply other threads:[~1998-12-23 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-22 3:53 vger CVS questions Troy Benjegerdes
1998-12-22 9:36 ` Cort Dougan
1998-12-23 6:36 ` 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=36808F55.71DDCA9A@jlc.net \
--to=dmalek@jlc$(echo .)net \
--cc=cort@persephone$(echo .)cs.nmt.edu \
--cc=hozer@drgw$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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