From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc64: Add mecanism to check existence of legacy ISA devices
Date: Sat, 23 Oct 2004 10:58:50 +1000 [thread overview]
Message-ID: <1098493130.6008.122.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0410221730560.2101@ppc970.osdl.org>
On Sat, 2004-10-23 at 10:32, Linus Torvalds wrote:
> On Sat, 23 Oct 2004, Benjamin Herrenschmidt wrote:
> >
> > This patch adds an arch function that can be overriden by the various
> > platforms at runtime, to query if a given legacy IO device actually
> > exist on the platform (based on the standard base port).
>
> Ehh..
>
> Why don't you use the "isapnp" or "acpi" interfaces?
>
> Yeah yeah, you don't actually have isapnp on your system. But like it or
> not, when we talk ISA enumeration, there is an existing standard for doing
> it. And since the drivers involved don't actually do BIOS calls or
> anything like that, they don't need to know that your "acpi" or "isapnp"
> enumeration comes from ppc64 firmware..
Hrm... currently, those drivers just blindly go tap IO ports and ...
- the isapnp stuff is _huge_, it's quite difficult to figure out what
to bring in and what not, and how to adapt it, especially since my
knowledge of the ISA stuff isn't that big
- It's only about 2 or 3 drivers and none of theem uses isapnp at this
point anyway
It's really only about keyboard, floppy, and _maybe_ parport, I'm not
sure bringing in the whole isapnp stuff is worth it, but I'll have a
look. I'd appreciate if the workaround I posted could get in for now
though.
Ben.
next prev parent reply other threads:[~2004-10-23 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 0:23 [PATCH] ppc64: Add mecanism to check existence of legacy ISA devices Benjamin Herrenschmidt
2004-10-23 0:32 ` Linus Torvalds
2004-10-23 0:58 ` Benjamin Herrenschmidt [this message]
2004-10-23 8:05 ` Benjamin Herrenschmidt
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=1098493130.6008.122.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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