From: Gunther.Mayer@t-online.de (Gunther Mayer)
To: "Steven A. DuChene" <sduchene@mindspring.com>
Cc: Thomas Hood <jdthood@mail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP BIOS -- bugfix; update devlist on setpnp
Date: Wed, 17 Oct 2001 18:04:32 +0200 [thread overview]
Message-ID: <3BCDAC10.A7F40982@t-online.de> (raw)
In-Reply-To: <1003288485.14282.100.camel@thanatos> <20011017041014.B2015@lapsony.mydomain.here>
"Steven A. DuChene" wrote:
>
> OK, I tried this with the Intel STL2 motherboard I also have and I got
> a similar error when trying to load the correct i2c bus module when the
> PnPBIOS stuff is compiled into the kernel.
>
> modprobe i2c-piix4
> /lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o: init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ >parameters
i2c-piix4 has to be taught to ignore PNP0c0x reservations.
PNP0C02 means "mainboard resource" and obviously i2c-piix4
would like to use it, so it should make use of it's knowledge.
As "mainboard resouce" is very generic we must reserve it
to protect against mapping other addresses over it.
next prev parent reply other threads:[~2001-10-17 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 3:14 [PATCH] PnP BIOS -- bugfix; update devlist on setpnp Thomas Hood
2001-10-17 8:10 ` Steven A. DuChene
2001-10-17 13:35 ` Thomas Hood
2001-10-17 16:08 ` Steven A. DuChene
2001-10-17 16:04 ` Gunther Mayer [this message]
2001-10-17 20:58 ` Thomas Hood
-- strict thread matches above, loose matches on Subject: below --
2001-10-13 15:40 Thomas Hood
2001-10-15 6:37 ` Jurgen Botz
2001-10-15 9:45 ` Stelian Pop
2001-10-15 12:01 ` Andrey Panin
2001-10-15 12:25 ` Alan Cox
2001-10-15 21:49 ` Thomas Hood
2001-10-15 14:15 ` Ion Badulescu
2001-10-17 2:48 ` Steven A. DuChene
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=3BCDAC10.A7F40982@t-online.de \
--to=gunther.mayer@t-online.de \
--cc=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sduchene@mindspring.com \
/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