From: Thomas Hood <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PnP BIOS + 2.4.9-ac16 = no boot
Date: Fri, 28 Sep 2001 11:20:35 -0400 [thread overview]
Message-ID: <3BB49543.6A915332@mail.com> (raw)
In-Reply-To: <3BB48A34.E392B7BC@mail.com> <20010928165122.L21524@come.alcove-fr>
Stelian Pop wrote:
> It works, kind of.
>
> The only remaining problem is that the DMI scan routines are
> called _after_ the PnP BIOS scan, so the is_sony_vaio_laptop
> variable will be always evaluated to 0 in your patch (causing
> the same hang again).
This is unfortunate. :(
Alan: Does this mean that we will have to use a new CONFIG_
macro instead of testing is_sony_vaio_laptop? If so then
I will submit a new patch with "#ifdef CONFIG_SONY_PNPBIOS"s
in it and I'll let you futz with the kernel configuration
files required to set this up.
> After manually changing is_sony_vaio_laptop to 1 the
> patched kernel boots ok, entries in /proc/bus/pnp are present
> (not sure how to test if their contents are corect though).
There should be no numerically named entries in /proc/bus/pnp;
you should see only the "devices" file and the "boot" directory.
You should see numerically named entries in /proc/bus/pnp/boot
for each device.
--
Thomas
next prev parent reply other threads:[~2001-09-28 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 14:33 PnP BIOS + 2.4.9-ac16 = no boot Thomas Hood
2001-09-28 14:51 ` Stelian Pop
2001-09-28 15:20 ` Thomas Hood [this message]
2001-09-28 15:28 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 23:29 Thomas Hood
2001-10-03 14:06 ` Ion Badulescu
2001-10-02 23:17 Thomas Hood
2001-09-28 13:47 Thomas Hood
2001-09-28 14:02 ` Stelian Pop
2001-09-28 14:41 ` Thomas Hood
2001-09-28 14:54 ` Stelian Pop
2001-09-28 14:58 ` Alan Cox
2001-09-28 14:58 ` Thomas Hood
2001-10-02 22:11 ` Ion Badulescu
2001-10-03 9:28 ` Stelian Pop
[not found] <3BB46DCD.91576F70@mail.com>
2001-09-28 13:12 ` Stelian Pop
2001-09-28 12:29 Thomas Hood
2001-09-28 10:46 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=3BB49543.6A915332@mail.com \
--to=jdthood@mail.com \
--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