From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
vojtech@ucw.cz,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [no problem] PC110 broke 2.6.9
Date: Sun, 07 Nov 2004 01:42:51 +0000 [thread overview]
Message-ID: <1099791769.5564.118.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0411061529200.2223@ppc970.osdl.org>
On Sad, 2004-11-06 at 23:37, Linus Torvalds wrote:
> 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.
It can't 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.
I never found anything.
> 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?)
I have some register info, the driver is done by disassembly of the
PC-DOS
driver IBM shipped with the PC110. It's a pre pci, pre dmi machine so
there aren't any obvious sane ways to probe. Its not something you'd
want to build
in as opposed to modular on any other system but the PC110
next prev parent reply other threads:[~2004-11-07 2:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 23:22 [no problem] PC110 broke 2.6.9 Andries Brouwer
2004-11-06 23:37 ` Linus Torvalds
2004-11-07 1:42 ` Alan Cox [this message]
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=1099791769.5564.118.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.