From: Dan Malek <dan@netx4.com>
To: Stuart <stu@asyn.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Hostname problems
Date: Wed, 09 Feb 2000 01:17:55 -0500 [thread overview]
Message-ID: <38A10693.C75820F4@netx4.com> (raw)
In-Reply-To: 000501bf728d$d717f550$0100000a@asyn.com
Stuart wrote:
>
> 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.
The 2.3.xx tree for the 8xx is pretty bad. There are some updates
I want to incorporate, but I have been tracking down all of the
changes that cause 8xx not to build or boot properly.
For the MBX in particular, the support of the PC-style I/O has
finally been broken. The support of the IDE was always a problem
because of the desire to use PCMCIA flash, the QSpan never seemed
to pass interrupt correctly, and now generic kernel changes finally
broke the indirect access to the 8259 (and I am still puzzled how
it is supported on other PMacs.....).
Anyway, those are some of the things I am working on. There are
many other little things, like building without PCI configured
doesn't work either. The last working 2.3.xx kernel I used and
updated was 2.3.18.
I am actively working on all of these because I want to make
sure we have a solid 8xx configuration when 2.4.x hits.
I will make an announcement when I get something stable again.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-09 6:17 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 ` Hostname problems Stuart
2000-02-09 6:17 ` Dan Malek [this message]
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=38A10693.C75820F4@netx4.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stu@asyn.com \
/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).