From: Thomas Hood <jdthood@mail.com>
To: Maciej Zenczykowski <maze@druid.if.uj.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.12-ac3 floppy module requires 0x3f0-0x3f1 ioports
Date: 04 Nov 2001 22:37:19 -0500 [thread overview]
Message-ID: <1004931442.1319.123.camel@thanatos> (raw)
In-Reply-To: <Pine.LNX.4.33.0111050149580.27009-700000@druid.if.uj.edu.pl>
In-Reply-To: <Pine.LNX.4.33.0111050149580.27009-700000@druid.if.uj.edu.pl>
On Sun, 2001-11-04 at 20:18, Maciej Zenczykowski wrote:
> W98SE reports the FDC at 0x3f0..0x3f5 and 0x3f7
In hw reference manuals I have looked at, the floppy
ioport range is listed as either 0x3f0-0x3f5 or
0x3f0-0x3f5,0x3f7 or 0x3f0-0x3f7.
0x3f6 is used by some IDE controllers, so it should
not be included in the range. Floppy controller
chips don't use this ioport.
Now I'm looking at the refence for the National Semi
87338 Super I/O chip which among other things emulates
a standard IBM-style floppy controller. It says:
0x3f0,0x3f1 are status registers that were added
to the PS/2. They do not exist on the PC-AT.
The 87338 uses these addresses only in "PS/2 mode",
not in "PC-AT" mode.
0x3f2 (*) is a digital output register
0x3f3 is a "tape drive register". Bring this one into
the Antiques Roadshow!
0x3f4 (*) is the main status register (r)
and data rate select register (w)
0x3f5 (*) is the data register FIFO
0x3f7 (*) is the digital input register (r)
and configuration control register (w)
When I look at the floppy driver itself, it reserves
0x3f0-0x3f5,0x3f7 but only uses 0x3f2, 0x3f4, 0x3f5, 0x3f7
(indicated above with an asterisk). See include/linux/fdreg.h.
I would suggest that the driver refrain from reserving
0x3f0-0x3f1 since not all floppy driver chips take up these
ioports and the Linux driver doesn't use them either.
Maciej: perhaps on your machine the motherboard uses 0x3f0-0x3f1
for some other (secret, highly classified) purpose. Have you
read your hardware reference manual?
--
Thomas
next prev parent reply other threads:[~2001-11-05 3:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 2:02 2.4.12-ac3 floppy module requires 0x3f0-0x3f1 ioports Thomas Hood
2001-11-05 0:00 ` Maciej Zenczykowski
2001-11-05 0:15 ` Thomas Hood
2001-11-05 1:18 ` Maciej Zenczykowski
2001-11-05 2:40 ` Thomas Hood
2001-11-05 3:37 ` Thomas Hood [this message]
2001-11-05 12:02 ` Maciej Zenczykowski
2001-11-06 20:02 ` Gunther Mayer
2001-11-07 11:53 ` Maciej Zenczykowski
2001-11-07 19:09 ` Thomas Hood
2001-11-05 8:45 ` Alan Cox
2001-11-05 11:18 ` Maciej Zenczykowski
-- strict thread matches above, loose matches on Subject: below --
2001-11-03 0:00 Maciej Zenczykowski
2001-11-03 0:21 ` Alan Cox
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=1004931442.1319.123.camel@thanatos \
--to=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@druid.if.uj.edu.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.