From: Damien Challet <challet-dK2jV70R1GDQzY9nttDBhA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Incomplete list of pnp entries/resources with pnpacpi
Date: Mon, 24 Jan 2005 17:04:45 +0000 [thread overview]
Message-ID: <200501241704.46239.challet@maths.ox.ac.uk> (raw)
Dear All,
On my thinkpad 600e,
1) pnpacpi does not seem to be as accurate as pnpbios. First of all the number
of entry points is quite smaller: lspnp stops at 1b, while pnpacpi stops at
10
2) There is no strict correspondance between the entries:
lspnp gives
0e CSC0100 multimedia controller: audio
0f CSC0110 multimedia controller: audio
10 CSC0101 multimedia controller: audio
11 CSC0103 multimedia controller: audio
whereas pnpacpi gives
00:05 CSC0110
00:06 CSC0100
00:07 CSC0101
3) The resources allocated to each entry are not complete:
for instance, pnpbios gives
0e CSC0100 multimedia controller: audio
io 0x0530-0x0537
io 0x0388-0x038b
io 0x0220-0x0233
irq 5
dma 0
dma 1
and pnpacpi
00:06 state = active
io 0x530-0x537
This might be the cause of my sound card not working.
Thanks for any help
Damien
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-01-24 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 17:04 Damien Challet [this message]
[not found] ` <200501241704.46239.challet-dK2jV70R1GDQzY9nttDBhA@public.gmane.org>
2005-01-24 19:25 ` Incomplete list of pnp entries/resources with pnpacpi Ville Syrjälä
[not found] ` <20050124192529.GA9740-ORSVBvAovxo@public.gmane.org>
2005-01-25 18:56 ` Damien Challet
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=200501241704.46239.challet@maths.ox.ac.uk \
--to=challet-dk2jv70r1gdqzy9nttdbha@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.