From: Aaron Gaudio <prothonotar-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
To: Louis Garcia <louisg00-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org>
Cc: Linux ACPI Devel Mailing List
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: newest ACPI
Date: Fri, 2 Aug 2002 02:29:49 -0400 [thread overview]
Message-ID: <20020802022949.B10668@tarnation.dyndns.org> (raw)
In-Reply-To: <1028256386.18719.10.camel-GyQFOxEsmOM@public.gmane.org>; from louisg00-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org on Thu, Aug 01, 2002 at 10:46:25PM -0400
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
And lo, upon Thu, Aug 01, 2002 at 10:46:25PM -0400, Louis Garcia spaketh thusly:
> Just wondering what the latest patch for kernel-2.4 has that the stock
> 2.4.18 kernel doesn't? To my understanding ACPI is useless without the
> new driver model.
>
> --Lou
>
Aside from the new model (and different layout in /proc/acpi), one
critical thing it has for me is (seemingly) correct PCI IRQ routing..
with the stock 2.4.18 version, several devices on my sony R505E would
not get IRQs assigned and would thus be unusable. With the latest
ACPI patch, they get the IRQs they need.
--
Aaron Gaudio prothontar @ tarnation.dyndns.org
http://tarnation.dyndns.org/~aaron
----------------
"From fullness, aspect. From aspect, being. From being, emptiness."
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2002-08-02 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 2:46 newest ACPI Louis Garcia
[not found] ` <1028256386.18719.10.camel-GyQFOxEsmOM@public.gmane.org>
2002-08-02 6:29 ` Aaron Gaudio [this message]
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=20020802022949.B10668@tarnation.dyndns.org \
--to=prothonotar-2ledzmxkczjeelb3ft/vumd2fqjk+8+b@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=louisg00-Bdlq13kUjeyLZ21kGMrzwg@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