mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: tomita@users.sourceforge.jp, a13a@users.sourceforge.jp,
	B.Zolnierkiewicz@elka.pw.edu.pl, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove dead PC9800 IDE support
Date: Sat, 15 May 2004 15:09:30 -0700	[thread overview]
Message-ID: <20040515150930.7af6f87e.rddunlap@osdl.org> (raw)
In-Reply-To: <20040515202347.GA22742@fs.tum.de>

On Sat, 15 May 2004 22:23:47 +0200 Adrian Bunk <bunk@fs.tum.de> wrote:

| On Mon, May 03, 2004 at 04:32:20PM -0700, Randy.Dunlap wrote:
| > On Tue, 4 May 2004 01:35:14 +0200 Bartlomiej Zolnierkiewicz wrote:
| > 
| > | 
| > | It was added in 2.5.66 but PC9800 subarch is still non-buildable.
| > | Also this is one big hack and only half-merged.
| > | 
| > 
| > It's fairly simple to make it buildable, but it's still a hack
| > that no one seems to want to support, so I agree, kill it.
| > 
| > Can we kill the rest of it too?
| 
| What's the opinion of the PC-9800 people regarding this issue?
| 
| Is there any work done now or in the near future on the PC-9800 port?

We haven't heard from them.  I have written email to them a few
times (2 or 3), but they haven't replied.

The current PC-9800 implementation is only 1/2 done, and IDE
is very hackish, according to Bart.

And currently X86_PC9800 cannot be selected at all (it's not
there!), so people cannot attempt to build/fix it either
(without fixing that, which I have done, but I don't think it's
worth submitting that patch).

--
~Randy

      reply	other threads:[~2004-05-15 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 23:35 Bartlomiej Zolnierkiewicz
2004-05-03 23:32 ` Randy.Dunlap
2004-05-15 20:23   ` Adrian Bunk
2004-05-15 22:09     ` Randy.Dunlap [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=20040515150930.7af6f87e.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=a13a@users.sourceforge.jp \
    --cc=bunk@fs.tum.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomita@users.sourceforge.jp \
    /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

all inboxes | Powered by JetHome®