From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Patrick Mochel <mochel@osdl.org>,
Andre Hedrick <andre@linuxdiskcert.org>,
Russell King <rmk@arm.linux.org.uk>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: driverfs support for motherboard devices
Date: Fri, 8 Feb 2002 00:03:16 +0100 [thread overview]
Message-ID: <20020207230315.GA762@elf.ucw.cz> (raw)
In-Reply-To: <20020206122253.GB446@elf.ucw.cz> <E16YcaF-0006z9-00@the-village.bc.nu> <20020207123125.GF5247@atrey.karlin.mff.cuni.cz> <20020207142333.A22451@suse.de>
In-Reply-To: <20020207142333.A22451@suse.de>
Hi!
> > > I suspect PnPBIOS knows for the 486. There is PnPbios code in 2.4-ac
> > > perfectly ready for a 2.5 merger
> > PnPBIOS is nasty, and I suspect it is not present/working on all
> > models, right?
>
> For the most part it's fine, it just needs the floppy driver / ps2
> driver (and maybe some others) fixed up to not allocate regions
> that pnpbios already reserved. Other than these issues, it seems
> to be working well. It's certainly handled itself ok on all my
> test boxes (Even the weird compaq with the fscked up pnpbios --
> it claims to have pnpbios, yet when you call it, you get feature
> not supported return codes. cute.)
It is *BIOS*, and that makes me nervous.
Anyway, I guess that for old boxen, it is okay to just put ide onto
/driver/legacy/XXX (and for new boxen probably too, we do not want
special code calling PnPbios/PCI just to put drivers to the right
place in the tree, right?)
Pavel
PS: I suspect that those southbridge-integrated IDE controllers are
not *really* on PCI... They certainly do not use PCI IRQ A..D.
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-02-08 21:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 17:39 driverfs support for motherboard devices Pavel Machek
2002-02-05 18:11 ` Xavier Bestel
2002-02-06 7:28 ` Zwane Mwaikambo
2002-02-05 18:36 ` Jeff Garzik
2002-02-05 18:43 ` Patrick Mochel
2002-02-05 20:47 ` Russell King
2002-02-05 22:46 ` Andre Hedrick
2002-02-05 23:06 ` Joel Jaeggli
2002-02-05 23:30 ` Alan Cox
2002-02-05 23:25 ` Patrick Mochel
2002-02-05 23:08 ` Patrick Mochel
2002-02-05 23:17 ` Joel Jaeggli
2002-02-06 12:22 ` Pavel Machek
2002-02-06 23:34 ` Patrick Mochel
2002-02-07 13:03 ` Pavel Machek
2002-02-07 0:38 ` Alan Cox
2002-02-07 12:31 ` Pavel Machek
2002-02-07 13:23 ` Dave Jones
2002-02-07 17:26 ` Patrick Mochel
2002-02-07 17:28 ` Dave Jones
2002-02-07 18:32 ` Gunther Mayer
2002-02-07 23:03 ` Pavel Machek [this message]
2002-02-06 7:33 ` Zwane Mwaikambo
2002-02-06 7:24 ` Zwane Mwaikambo
2002-02-06 12:16 ` Pavel Machek
2002-02-06 20:54 ` Patrick Mochel
2002-02-07 20:21 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 18:18 Thomas Hood
2002-02-07 18:28 ` Patrick Mochel
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=20020207230315.GA762@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linuxdiskcert.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rmk@arm.linux.org.uk \
/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