From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI and the PNP Layer
Date: Mon, 2 Feb 2004 10:31:39 -0800 (PST) [thread overview]
Message-ID: <20040202102827.Y22816@root.org> (raw)
In-Reply-To: <20040201172447.GV18725-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
On Sun, 1 Feb 2004, Matthew Wilcox wrote:
> On Sun, Feb 01, 2004 at 02:41:02AM +0000, Dino Klein wrote:
> > I took a quick look at the two files, and they are quite comparable
> > code-wise; the additional size in 8250_pnp.c is due to the extra comments
> > and EISA IDs defined.
> > Now about the legacy devices - wouldn't you say that the keyboard/PS2
> > driver should be modified to register with the ACPI bus, just in order to
> > have everything nice & neat? or how about the parallel port, or motherboard
> > based IRDA (PNP0510)?
> > Perhaps I'm just exaggerating with this, but I like to have things nice and
> > neat :)
>
> PS/2 is obsoleted by USB, as is parallel. I don't know abut IRDA but I
> would expect it to show up as a PCI device normally. Are manufacturers
> still making machines which have this as a non-PCI device? Remember just
> because it's on the motherboard doesn't mean it's a non-PCI device.
Compare the output of acpidump and the datasheet for a Super I/O chip some
time. Everything on the LPCB is legacy and is thus probed through ACPI,
not PCI. IRDA is almost always on the Super I/O.
http://www.via.com.tw/en/Products/superIO.jsp
-Nate
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-02 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 2:41 ACPI and the PNP Layer Dino Klein
[not found] ` <Law11-F969ScIXWOReP0000022f-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2004-02-01 17:24 ` Matthew Wilcox
[not found] ` <20040201172447.GV18725-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-02-02 18:31 ` Nate Lawson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-01 0:28 Dino Klein
[not found] ` <Law11-F77kuQMAEZyO20001c9f5-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2004-02-01 1:43 ` Matthew Wilcox
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=20040202102827.Y22816@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.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