From: Thomas Hood <jdthoodREMOVETHIS@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Small change to pnp_bios.c
Date: Tue, 25 Sep 2001 00:03:42 -0400 [thread overview]
Message-ID: <3BB0021E.D1977DBD@yahoo.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
I have been trying to find out why the PnP BIOS driver
causes the disabling of all the PnP-configurable devices
on my ThinkPad 600. (One other user has reported the same
problem.) I've been checking the pnp_bios.c driver against
the spec and I found one little nit.
The spec says that after this call to the BIOS:
Q2_SET_SEL(PNP_TS1, nodenum, sizeof(char));
Q2_SET_SEL(PNP_TS2, data, 64 * 1024);
status = call_pnp_bios(PNP_GET_SYS_DEV_NODE, 0, PNP_TS1, 0, PNP_TS2, boot ? 2 : 1, PNP_DS, 0);
nodenum will be set to the next node number, or to 0xFF
if there are no more nodes. I added a check so that
the build-devlist loop will terminate if nodenum is 0xff.
This didn't solve my problem but it does seem like the
kosher thing to do. The patch also initializes the
variable "num" to zero. I know that static variables
in the kernel are automatically initialized to zero, but
I assume that the same is not true of stack variables.
Am I wrong?
The attached patch is against -ac13. Sorry, but the
-ac15 differential patch hasn't come out yet. :(
Thomas
[-- Attachment #2: pnpbios-patch-20010924-1 --]
[-- Type: text/plain, Size: 546 bytes --]
--- linux-2.4.9-ac13-mwave/drivers/pnp/pnp_bios.c_1 Fri Sep 21 16:15:44 2001
+++ linux-2.4.9-ac13-mwave/drivers/pnp/pnp_bios.c Mon Sep 24 18:32:26 2001
@@ -839,13 +839,13 @@
return;
node = kmalloc(node_info.max_node_size, GFP_KERNEL);
if (!node)
return;
- for(i=0;i<0xff;i++) {
+ for(i=0,num=0;i<0xff,num!=0xff;i++) {
dev = kmalloc(sizeof (struct pci_dev), GFP_KERNEL);
if (!dev)
break;
if (pnp_bios_get_dev_node((u8 *)&num, (char )0 , node))
continue;
next reply other threads:[~2001-09-25 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 4:03 Thomas Hood [this message]
2001-09-25 4:10 ` Ignacio Vazquez-Abrams
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=3BB0021E.D1977DBD@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
all inboxes | Powered by JetHome®