From: Gunther.Mayer@t-online.de (Gunther Mayer)
To: Maciej Zenczykowski <maze@druid.if.uj.edu.pl>
Cc: Thomas Hood <jdthood@mail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.12-ac3 floppy module requires 0x3f0-0x3f1 ioports
Date: Tue, 06 Nov 2001 21:02:12 +0100 [thread overview]
Message-ID: <3BE841C4.947416CB@t-online.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0111051219080.29021-100000@druid.if.uj.edu.pl>
Maciej Zenczykowski wrote:
>
> On 4 Nov 2001, Thomas Hood wrote:
> >
> > Maciej: perhaps on your machine the motherboard uses 0x3f0-0x3f1
> > for some other (secret, highly classified) purpose. Have you
> > read your hardware reference manual?
> >
> I did that before posting the previous time - beautiful over 100 page
> manual - but no mention of 03xf0-0x3f1 being special and can't find them
> in any bios setup screens either...
Diagnosis:
----------
Your PNPBIOS announces these ports:
0c PNP0c02 Motherboard resources
io 0x03f0-0x03f1
These ports are used by various SuperIO chips, e.g.Winbond W83877ATF:
8.2 Extended Function Index Registers (EFIRs), Extended Function Data Registers(EFDRs)
After the extended function mode is entered, the Extended Function Index Register (EFIR) must be
loaded with an index value (0H, 1H, 2H, ..., or 29H) to access Configuration Register 0 (CR0),
Configuration Register 1 (CR1), Configuration Register 2 (CR2), and so forth through the Extended
Function Data Register (EFDR). The EFIRs are write-only registers with port address 251H or 3F0H
(as described in section 8.0) on PC/AT systems; the EFDRs are read/write registers with port address
252H or 3F1H (as described in section 8.0) on PC/AT systems. The function of each configuration
register is described ...
You have to write various magic vendor defined values to
vendor defined ports to enable "extended function mode" :-)
http://home.t-online.de/home/gunther.mayer/lssuperio-0.63.tar.gz will
identify your chip sitting at 0x3f0/0x3f1 !
Solution:
---------
PnPBIOS in linux should _not_ reserve these 2 ports (this kind of
solution is commonly called a quirks).
next prev parent reply other threads:[~2001-11-06 19:02 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
2001-11-05 12:02 ` Maciej Zenczykowski
2001-11-06 20:02 ` Gunther Mayer [this message]
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=3BE841C4.947416CB@t-online.de \
--to=gunther.mayer@t-online.de \
--cc=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.