From: Gunther Mayer <gunther.mayer@gmx.net>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: Alessandro Suardi <alessandro.suardi@oracle.com>,
linux-kernel@vger.kernel.org, jdthood@yahoo.co.uk
Subject: Re: modular floppy broken in 2.5.3
Date: Mon, 04 Feb 2002 18:29:08 +0100 [thread overview]
Message-ID: <3C5EC4E4.B5A6E84F@gmx.net> (raw)
In-Reply-To: <E16XU69-0005MJ-00@the-village.bc.nu>
Alan Cox wrote:
> > It turns out this is due to the new PnPBIOS kernel config option:
> >
> > [asuardi@dolphin asuardi]$ grep PnPBIOS /proc/ioports
> > 03f0-03f1 : PnPBIOS PNP0c01
> > 0600-067f : PnPBIOS PNP0c01
> > 0680-06ff : PnPBIOS PNP0c01
> > 0800-083f : PnPBIOS PNP0c01
> > 0840-084f : PnPBIOS PNP0c01
> > 0880-088f : PnPBIOS PNP0c01
> > f400-f4fe : PnPBIOS PNP0c01
> >
> > But since modular floppy was working before without setting any
> > ioport parameter I'm not entirely sure this is a "feature".
>
> Its a mix of fp and pnpbios things that need untangling. PnPBIOS should
> register the resource as not in use, floppy should allocate the right
PNPNIOS is right to reserve PNP0C01 as "used". Else there will be hangs
when drivers poke in io space (e.g. laptops tend to have special
hardware which doesn't like to be touched).
PNPBIOS should not reserve 3f0/3f1 as a _workaround_ for this BIOS bug.
The BIOS probably wants to tell you there is a superio chip at 0x3f0
(try http://home.t-online.de/home/gunther.mayer/lssuperio-0.63.tar.gz).
next prev parent reply other threads:[~2002-02-04 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 1:38 modular floppy broken in 2.5.3 Alessandro Suardi
2002-02-03 20:48 ` Alessandro Suardi
2002-02-03 21:22 ` Alan Cox
2002-02-04 17:29 ` Gunther Mayer [this message]
2002-02-04 23:58 ` Thomas Hood
2002-02-05 10:13 ` Alessandro Suardi
-- strict thread matches above, loose matches on Subject: below --
2002-02-04 19:26 Thomas Hood
2002-02-07 1:30 Thomas Hood
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=3C5EC4E4.B5A6E84F@gmx.net \
--to=gunther.mayer@gmx.net \
--cc=alessandro.suardi@oracle.com \
--cc=jdthood@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.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