From: Thomas Hood <jdthoodREMOVETHIS@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Should isa-pnp utilize the PnP BIOS?
Date: Fri, 02 Mar 2001 19:33:43 -0500 [thread overview]
Message-ID: <3AA03BE7.9057EDFC@mail.com> (raw)
In-Reply-To: <20010214092251.D1144@e-trend.de> <3A8AA725.7446DEA0@ubishops.ca> <20010214165758.L28359@e-trend.de> <20010214122244.H7859@conectiva.com.br>
Okay, a couple of people have responded positively to this
suggestion. The next question is, how should it be implemented?
How 'bout:
$ cd pcmcia-cs/modules
$ cp pnp_bios.c pnp_proc.c pnp_rsrc.c /usr/src/linux/2.4.2a/drivers/pnp
$ cd ../include/linux
$ cp pnp_bios.h pnp_resource.h /usr/src/linux/2.4.2a/include/linux
Edit makefiles
Edit isapnp.c to include new global flag "isapnp_usepnpbios",
a MODULE_PARM, which each isapnp function checks at entry.
If the flag is set then: in the case of "low-level" functions,
return immediately; in the case of "high-level" functions, call
appropriate pnp_bios functions to perform the task; in the case
of isapnp_init(), just check isapnp_disabled and exit. isapnp's
/proc interface would not be supported. Presumably
inter_module_get_request() would be used to call the isapnp-bios
routines.
Comments? (Go easy on me; I'm a newbie at kernel hacking.)
Thomas
> Hello, l-k.
>
> On my ThinkPad 600, The ThinkPad PnP BIOS configures
> all PnP devices at boot time.
>
> If I load the isa-pnp.o driver it never detects any ISA PnP
> devices: it says "isapnp: No Plug & Play device found". This
> is unfortunate, because it means that device drivers can't
> find out from isa-pnp where the devices are.
>
> David Hinds's pcmcia-cs package contains driver code that
> interfaces with the PnP BIOS. With it, one can list the resource
> usage of ISA PnP devices (serial and parallel ports, sound chip,
> etc.) and set them, using the "lspnp" and "setpnp" commands.
>
> Would it not be useful if the isa-pnp driver would fall back
> to utilizing the PnP BIOS (if possible) in order to read and
> change ISA PnP device configurations when it can't do this
> itself? If so, could this perhaps be done by bringing the Hinds
> PnP BIOS driver into the kernel and interfacing isa-pnp to it?
>
> Thomas Hood
> jdthood_AT_yahoo.co.uk <- Change '_AT_' to '@'
next prev parent reply other threads:[~2001-03-03 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010214092251.D1144@e-trend.de>
[not found] ` <3A8AA725.7446DEA0@ubishops.ca>
[not found] ` <20010214165758.L28359@e-trend.de>
[not found] ` <20010214122244.H7859@conectiva.com.br>
2001-02-15 21:13 ` [PATCH] to deal with bad dev->refcnt in unregister_netdevice() Thomas Hood
2001-02-19 15:27 ` [PATCH] fix bad dev->refcnt in unregister_netdevice was " Arnaldo Carvalho de Melo
2001-02-21 16:22 ` Thomas Hood
2001-02-25 23:42 ` Should isa-pnp utilize the PnP BIOS? Thomas Hood
2001-02-25 23:49 ` Jeremy Jackson
2001-02-26 0:24 ` Jonathan Morton
2001-03-03 0:33 ` Thomas Hood [this message]
2001-07-20 2:48 ` [BUG] "unregister_netdevice: waiting for eth0 to become free. Usage count = 2" Thomas Hood
2001-07-28 5:44 ` Multiple apm resume events Thomas Hood
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=3AA03BE7.9057EDFC@mail.com \
--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