mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: alan@lxorguk.ukuu.org.uk, vojtech@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: [no problem] PC110 broke 2.6.9
Date: Sat, 6 Nov 2004 15:37:03 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0411061529200.2223@ppc970.osdl.org> (raw)
In-Reply-To: <20041106232228.GA9446@apps.cwi.nl>



On Sun, 7 Nov 2004, Andries Brouwer wrote:
>
> Yesterday I muttered that 2.6.9 had a mouse problem, and soon
> afterwards I also noticed that my ADSL didnt work.
> 
> I just looked at what was wrong, and the reason turns out to be
> a correct fix in the pc110pad_init() call of request_region().
> 
> Before 2.6.9 the test there was wrong, so that the region was
> seen as unavailable and pc110pad.c did not do anything.
> 
> In 2.6.9 the test is correct, the region and irq are reserved and my
> ethernet card can no longer reserve its irq and ADSL fails.
> Moreover, now pc110pad.c does I/O causing my mouse problems.
> 
> Easy solution: CONFIG_MOUSE_PC110PAD=n
> 
> I write this in some detail in the hope that this inspires somebody
> to figure out whether it is possible to probe & detect this PC110.

Ahh.. Interesting. One improvement might be to make sure that this driver 
links in very late in the game, so that if any other drivers have 
allocated the IO, at least it won't override that. Also, it might make 
sense to say that the dang thing can share interrupts.

But yes, we should probably make sure to make it harder to enable the
driver by mistake, and try to do minimal probing of it. I have no idea how
to probe for the thing, though.

Alan, Vojtech, do you have any register information on this thing? Some 
docs to try to realize when it's not there? Or some other way to detect 
the IBM PC110 hardware (BIOS strings, something?)

		Linus

  reply	other threads:[~2004-11-06 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 23:22 Andries Brouwer
2004-11-06 23:37 ` Linus Torvalds [this message]
2004-11-07  1:42   ` Alan Cox
2004-11-07  2:57     ` Linus Torvalds
2004-11-07 16:34       ` Alan Cox
2004-11-07 18:38         ` Linus Torvalds
2004-11-07 19:13           ` Andries Brouwer
2004-11-08 11:07           ` Alan Cox
2004-11-10 23:44     ` Pavel Machek

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.58.0411061529200.2223@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@ucw.cz \
    /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®