From: "Stuart" <stu@asyn.com>
To: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Hostname problems
Date: Tue, 8 Feb 2000 15:40:11 -0800 [thread overview]
Message-ID: <000501bf728d$d717f550$0100000a@asyn.com> (raw)
In-Reply-To: <389EEA75.4982DC88@eng.uct.ac.za>
Hi all.
What's the status on the 860 port in the 2.3.x tree from kernel.org.
Specifically I'm working with an MBX box.
I recall seeing something recently from Dan about collecting many
patches, and hoping to have something together soon. I think it was
for the 860.
The 2.3.42 kernel did not compile out of the box. But I've made
several changes to get it to build. However it still does not run.
I've either messed up on something in my fixes to get it building,
or there are more significant problems with it.
Are there others working with the current versions of the 2.3.x
development? Anyone have it working on an MBX?
Thanks...
-- Stuart --
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-02-08 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <389EEA75.4982DC88@eng.uct.ac.za>
2000-02-08 23:40 ` Stuart [this message]
2000-02-09 6:17 ` Hostname problems Dan Malek
2000-02-11 21:08 ` Cort Dougan
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='000501bf728d$d717f550$0100000a@asyn.com' \
--to=stu@asyn.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).