From: Thomas Hood <jdthood@mail.com>
To: Gunther Mayer <Gunther.Mayer@t-online.de>
Cc: "Steven A. DuChene" <sduchene@mindspring.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP BIOS -- bugfix; update devlist on setpnp
Date: 17 Oct 2001 16:58:33 -0400 [thread overview]
Message-ID: <1003352314.1188.30.camel@thanatos> (raw)
In-Reply-To: <3BCDAC10.A7F40982@t-online.de>
In-Reply-To: <1003288485.14282.100.camel@thanatos> <20011017041014.B2015@lapsony.mydomain.here> <3BCDAC10.A7F40982@t-online.de>
On Wed, 2001-10-17 at 12:04, Gunther Mayer wrote:
> 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.
Your approach would work. But ...
Alan has said that the thing to do is mark these resources
as extant but unused. I presume one does this by calling
request_resource with appropriate flags [un]set.
Thomas
next prev parent reply other threads:[~2001-10-17 20:59 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
2001-10-17 20:58 ` Thomas Hood [this message]
-- 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=1003352314.1188.30.camel@thanatos \
--to=jdthood@mail.com \
--cc=Gunther.Mayer@t-online.de \
--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