mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: John Bradford <john@grabjohn.com>,
	Mikael Pettersson <mikpe@csd.uu.se>,
	Dave Jones <davej@redhat.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: FDC motor left on
Date: Mon, 6 Oct 2003 12:17:16 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0310061157090.9590@chaos> (raw)
In-Reply-To: <Pine.GSO.3.96.1031006174121.18687C-100000@delta.ds2.pg.gda.pl>

On Mon, 6 Oct 2003, Maciej W. Rozycki wrote:

> On Mon, 6 Oct 2003, Richard B. Johnson wrote:
>
> > > This is not a problem to deal with in the kernel - what if there is
> > > hardware other than a floppy controller at that address?
> >
> > In the ix86 architecture (and it is in arch-specific code), there
> > cannot be anything at this address except a floppy or nothing.
> > In both cases, you are covered.
>
>  Huh?  The floppies use ordinary I/O ports at the ISA bus, not the range
> reserved for motherboard devices as, until quite recently, FDCs used to
> exist solely as add-on cards (I still have one).  Any other ISA device is
> free to use the port range if it's unused by anything else (e.g. no FDC
> there).  Ditto for IRQ6 -- older cards used to have an option to use this
> line, only newer ones often do not have it anymore, for unknown reason
> (i.e. the cost is probably one).

No. The range of addresses for floppy disk controllers is
"reserved" for floppy disk controllers. That's the rule for
IBM/PC/AT/Intel compatible devices. This is specified in
the literature like that written by Phoenix, IBM, etc.
(Phoenix Technical Reference Series, System BIOS for
IBM PC/XT/AT and Compatible Computers.  ISBN 0-201-51806-6

We have rules. That's what "Compatible" means. If you break
the compatibility by putting something else at that address,
you take your chances.

When the Super I/O chips are programmed, the floppy device,
(usually logical device 0) is (must) be put at the base
address reserved for floppy disks in compatible machines.
It's the rule. If you are using the same chip in some non-
compatible machine (like a power-PC), they have rules where
the floppy must be addressed, too. These addresses are
different for different architectures and, some machines
don't have I/O ports, they are memory mapped. In those
cases, the floppy is put at some memory-mapped address.

For the architecture in the linux i386 subdirectory, which
is what I was talking about, there will either be a FDC
controller output register at 0x372, with the bits previously
taught, or there will be nothing. It's that simple. If
you make it more complicated, then you don't understand
what compatibility means.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-10-06 16:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 17:25 Richard B. Johnson
2003-10-03 23:58 ` Dave Jones
2003-10-06 12:42   ` Richard B. Johnson
2003-10-06 12:50     ` Maciej W. Rozycki
2003-10-06 12:59     ` Mikael Pettersson
2003-10-06 13:58       ` Richard B. Johnson
2003-10-06 14:25         ` John Bradford
2003-10-06 15:09           ` Richard B. Johnson
2003-10-06 15:49             ` Maciej W. Rozycki
2003-10-06 16:17               ` Richard B. Johnson [this message]
2003-10-06 16:46                 ` Maciej W. Rozycki
2003-10-06 16:06             ` John Bradford
2003-10-06 16:22               ` Richard B. Johnson
2003-10-06 16:41                 ` John Bradford
2003-10-04 13:56 Mikael Pettersson

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=Pine.LNX.4.53.0310061157090.9590@chaos \
    --to=root@chaos.analogic.com \
    --cc=davej@redhat.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=mikpe@csd.uu.se \
    /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

all inboxes | Powered by JetHome®