From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Thomas Hood <jdthood@yahoo.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PnPBIOS additional fixes
Date: Wed, 3 Oct 2001 15:32:29 +0200 [thread overview]
Message-ID: <20011003153229.O574@come.alcove-fr> (raw)
In-Reply-To: <20011003124423.78EAB58B@thanatos.toad.net>
In-Reply-To: <20011003124423.78EAB58B@thanatos.toad.net>
On Wed, Oct 03, 2001 at 08:44:23AM -0400, Thomas Hood wrote:
> > # uname -a
> > Linux crusoe.alcove-fr 2.4.10-ac4 #2 Wed Oct 3 11:20:19 CEST 2001 i586 unknown
> > # cd /proc/bus/pnp
> > # ls
> > boot devices
>
> Good ...
Ok.
> Also, "lspnp -bv" should work and "lspnp -v" should fail.
It doesn't:
# lspnp -v
00 PNP0c02 bridge controller: ISA
01 PNP0c01 memory controller: RAM
02 PNP0200 system peripheral: DMA controller
03 PNP0000 system peripheral: programmable interrupt controller
04 PNP0100 system peripheral: system timer
05 PNP0b00 system peripheral: real time clock
06 PNP0303 input device: keyboard
07 PNP0c04 reserved: other
08 PNP0800 multimedia controller: audio
09 PNP0a03 bridge controller: PCI
0b PNP0c02 memory controller: RAM
0c PNP0c02 memory controller: RAM
0d PNP0e03 bridge controller: PCMCIA
0e PNP0f13 input device: mouse
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|
next prev parent reply other threads:[~2001-10-03 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 12:44 [PATCH] PnPBIOS additional fixes Thomas Hood
2001-10-03 13:32 ` Stelian Pop [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-05 19:17 Thomas Hood
2001-10-05 13:41 Thomas Hood
2001-10-03 17:01 Thomas Hood
2001-10-03 15:38 Thomas Hood
2001-10-03 4:39 Thomas Hood
2001-10-03 9:25 ` Stelian Pop
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=20011003153229.O574@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=jdthood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.