From: Thomas Hood <jdthoodREMOVETHIS@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Problem: PnP BIOS driver reports outdated information
Date: Thu, 20 Sep 2001 19:25:48 -0400 [thread overview]
Message-ID: <3BAA7AFC.49CEFB5D@yahoo.co.uk> (raw)
The PnP BIOS interface driver builds a device list, including
resource information for each device, at init time. Other
drivers search this list using pnpbios_find_device().
The problem is that the information in the device list may
be out of date if setpnp has been used.
Perhaps it will be said that setpnp is a "debugging tool" and
ordinarily one shouldn't change resource assignments, but
setpnp is useful for more than debugging. E.g., with current
kernels it is necessary for me to run setpnp during the boot
sequence in order to set up certain devices properly.
Sometimes, also, there aren't enough IRQs to go around, and
one may use setpnp to disable and enable different devices.
Thus I think that the PnP BIOS driver needs to be fixed so
that it will use and report the correct (current) resource
values. Looking at the code, I see no reason why there
needs to be a device list at all. Functions such as
pnpbios_find_device() could just as well scan through
device info returned (fresh) by the PnP BIOS. I don't
think speed is a big issue here. Are there other reasons
for maintaining a device list in the driver?
--
Thomas Hood
jdthood_AT_yahoo.co.uk
next reply other threads:[~2001-09-20 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 23:25 Thomas Hood [this message]
2001-09-21 0:09 ` Problem: PnP BIOS driver reports outdated information Alan Cox
2001-09-21 1:14 ` Thomas Hood
2001-09-21 1:31 ` 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=3BAA7AFC.49CEFB5D@yahoo.co.uk \
--to=jdthoodremovethis@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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