From: ebiederman@uswest.net (Eric W. Biederman)
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Thomas Hood" <jdthood@mail.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux should not set the "PnP OS" boot flag
Date: 06 Oct 2001 19:08:21 -0600 [thread overview]
Message-ID: <m13d4wxnne.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E15pyjj-0002Kn-00@the-village.bc.nu>
In-Reply-To: <E15pyjj-0002Kn-00@the-village.bc.nu>
"Alan Cox" <alan@lxorguk.ukuu.org.uk> writes:
> > Do you have any insite into what needs to be done so that the kernel
> > will automatically configure isa pnp devices?
>
> We already configure isapnp devices. We don't yet configure all the PnPbios
> devices
O.k. I'm getting more interested as I read this. So we have things like
superio chips and the like with configureable resources, (and possibly some
pci<->isa bridge resources that need to bec onfigured.)
Coming from the linuxBIOS side I'm interested as that will allow me to
rip out more code, from linuxBIOS. And I think it is only sane to report
such devices.
I don't know about the stock BIOS interfaces to those devices though. I'll
keep an eye on them and see what I can do. Hopefully within the next couple
of mounths I can start attacking this problem.
Eric
next prev parent reply other threads:[~2001-10-07 1:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 3:35 Linux should not set the "PnP OS" boot flag Thomas Hood
2001-10-06 19:24 ` Eric W. Biederman
2001-10-06 21:11 ` Alan Cox
2001-10-07 1:08 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-07 2:54 Thomas Hood
2001-10-07 10:02 ` Alan Cox
2001-10-07 13:50 ` Thomas Hood
2001-10-07 14:07 ` Dave Jones
2001-10-07 14:18 ` Alan Cox
2001-10-07 17:10 ` Thomas Hood
2001-10-07 21:59 ` Alan Cox
2001-10-07 17:54 ` Thomas Hood
2001-10-08 12:40 Thomas Hood
2001-10-08 13:25 ` Stelian Pop
2001-10-08 22:12 ` J.D. 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=m13d4wxnne.fsf@frodo.biederman.org \
--to=ebiederman@uswest.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=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