From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Jurgen Botz <jurgen@botz.org>
Cc: Thomas Hood <jdthood@mail.com>,
linux-kernel@vger.kernel.org, ion@cs.columbia.edu,
sduchene@mindspring.com
Subject: Re: [PATCH] PnP BIOS -- bugfix; update devlist on setpnp
Date: Mon, 15 Oct 2001 11:45:56 +0200 [thread overview]
Message-ID: <20011015114556.F4523@come.alcove-fr> (raw)
In-Reply-To: <jdthood@mail.com> <1002987648.764.23.camel@thanatos> <200110150637.f9F6bek14014@nova.botz.org>
In-Reply-To: <200110150637.f9F6bek14014@nova.botz.org>
On Sun, Oct 14, 2001 at 11:37:39PM -0700, Jurgen Botz wrote:
> Thomas Hood wrote:
> > Okay, here's a new major patch to the PnP BIOS driver
> > which needs some testing before it's integrated.
> >[...]
> > Vaio users: Please make sure that this doesn't oops.
>
> Patched against 2.4.12-ac1, it works and doesn't oops my
> VAIO PCG-N505VE.
Same for me (against a 2.4.10-ac12), on a VAIO PCG-C1VE.
Relevant (maybe) output:
...
Sony Vaio laptop detected.
BIOS strings suggest APM reports battery life in minutes and wrong byte order.
PCI: PCI BIOS revision 2.10 entry at 0xfd98e, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
PCI: Found IRQ 9 for device 00:08.0
PCI: Sharing IRQ 9 with 00:07.2
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PnPBIOS: Found PnP BIOS installation structure at 0xc00f8120.
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xb25f, dseg 0x400.
PnPBIOS: 14 nodes reported by PnP BIOS; 14 recorded by driver.
PnPBIOS: PNP0c02: 0xfff80000-0xffffffff was already reserved
PnPBIOS: PNP0c02: 0xfff7f600-0xfff7ffff was already reserved
PnPBIOS: PNP0c02: 0x398-0x399 has been reserved
PnPBIOS: PNP0c02: 0x4d0-0x4d1 has been reserved
PnPBIOS: PNP0c02: 0x8000-0x804f was already reserved
PnPBIOS: PNP0c02: 0x1040-0x104f has been reserved
PnPBIOS: PNP0c01: 0xe8000-0xfffff was already reserved
PnPBIOS: PNP0c01: 0x100000-0x70ffbff was already reserved
PnPBIOS: PNP0c02: 0xdc000-0xdffff was already reserved
PnPBIOS: PNP0c02: 0xd1000-0xd3fff was already reserved
Linux NET4.0 for Linux 2.4
...
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-15 9:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 15:40 Thomas Hood
2001-10-15 6:37 ` Jurgen Botz
2001-10-15 9:45 ` Stelian Pop [this message]
2001-10-15 12:01 ` Andrey Panin
2001-10-15 12:25 ` Alan Cox
2001-10-15 21:49 ` Thomas Hood
2001-10-16 3:27 ` [PATCH] PnP BIOS patch against 2.4.12-ac2 Thomas Hood
2001-10-16 7:58 ` Jörg Ziuber
2001-10-16 21:44 ` Thomas Hood
2001-10-17 6:28 ` Jörg Ziuber
2001-10-17 13:41 ` Thomas Hood
2001-10-17 14:43 ` Jörg Ziuber
2001-10-17 20:43 ` Thomas Hood
2001-10-15 14:15 ` [PATCH] PnP BIOS -- bugfix; update devlist on setpnp Ion Badulescu
2001-10-17 2:48 ` Steven A. DuChene
2001-10-17 3:14 Thomas Hood
2001-10-17 8:10 ` Steven A. DuChene
2001-10-17 16:04 ` Gunther Mayer
2001-10-17 20:58 ` Thomas Hood
2001-10-17 13:35 ` Thomas Hood
2001-10-17 16:08 ` 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=20011015114556.F4523@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=ion@cs.columbia.edu \
--cc=jdthood@mail.com \
--cc=jurgen@botz.org \
--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
all inboxes | Powered by JetHome®