From: "Thomas Hood" <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: modular floppy broken in 2.5.3
Date: Mon, 04 Feb 2002 14:26:37 -0500 [thread overview]
Message-ID: <20020204192638.59181.qmail@mail.com> (raw)
Gunther Mayer wrote:
> 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).
> [...]
> The BIOS probably wants to tell you there
> is a superio chip at 0x3f0
The floppy controller commonly uses io ports
0x3f2-0x3f5 and 0x3f7. 0x3f0-0x3f1 were used
by the floppy controller on the PC AT (only).
The latter two ports are now frequently used
for superio chips or other motherboard
devices, as the BIOS will report. PnPBIOS
is acting properly in reserving the ports.
Since the floppy driver does not use ioports
0x3f0-0x3f1 it should not reserve them.
The issue was previously discussed in this
thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=100516032204531&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=100495936122982&w=2
and the conclusion, I believe, was that the
floppy driver should be patched so as not to
reserve 0x3f0 and 0x3f1. Someone even
submitted a patch.
> PNPBIOS should not reserve 3f0/3f1
> as a _workaround_ for this BIOS bug.
The correct solution is to modify the floppy
driver.
Until that happens, use the "pnpbios=no-res"
option, which prevents pnpbios from reserving
any ioports.
--
Thomas Hood
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Win a ski trip!
http://www.nowcode.com/register.asp?affiliate=1net2phone3a
next reply other threads:[~2002-02-04 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 19:26 Thomas Hood [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 1:30 modular floppy broken in 2.5.3 Thomas Hood
2002-02-02 1:38 Alessandro Suardi
2002-02-03 20:48 ` Alessandro Suardi
2002-02-03 21:22 ` Alan Cox
2002-02-04 17:29 ` Gunther Mayer
2002-02-04 23:58 ` Thomas Hood
2002-02-05 10:13 ` Alessandro Suardi
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=20020204192638.59181.qmail@mail.com \
--to=jdthood@mail.com \
--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