The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 19:15:56 -0500	[thread overview]
Message-ID: <1004919359.1318.63.camel@thanatos> (raw)
In-Reply-To: <Pine.LNX.4.33.0111050050160.27009-200000@druid.if.uj.edu.pl>
In-Reply-To: <Pine.LNX.4.33.0111050050160.27009-200000@druid.if.uj.edu.pl>

On Sun, 2001-11-04 at 19:00, Maciej Zenczykowski wrote:
> > A fix for this problem went in to 2.4.13-ac2.  Please
> > try that kernel (or a later -ac kernel) and report back.
> 
> Well just tried kernel 2.4.13-ac6 and there is absolutely no difference.
> 
> After applying the attached patch all works OK...
> 
> Maciej Zenczykowski
> 
> nb. modprobe rivafb leaves the kernel's idea of whats on screen out of
> sync with the truth.  i.e. modprobe rivafb on tty2 and you end up with
> tty1 on the screen, but keypresses going to tty2...

What I would like to know is: What is at 0x3f0-0x3f1 on
your machine, and why does your PnP BIOS list these
two ioports as used by "system peripheral: other"?

On my ThinkPad 600, the BIOS lists 0x3f0-0x3f5 as owned
by the floppy device:
jdthood@thanatos:~$ sudo lspnp -v 08
08 PNP0700 mass storage device: floppy
	irq 6
	io 0x03f0-0x03f5
	dma 2

It looks like there's a bug in your BIOS.  What we could do is
patch the PnP BIOS driver so that it refrains from reserving 
0x3f0-0x3f1.

I'll let others comment on the appropriateness of your patch
to floppy.c .  I don't know whether it's the right thing to
do or not.

--
Thomas Hood



  reply	other threads:[~2001-11-05  0:17 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 [this message]
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
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=1004919359.1318.63.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox