From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Pierre Ossman <drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
Cc: ACPI devel list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI to driver connection
Date: Tue, 14 Sep 2004 00:39:52 +0200 [thread overview]
Message-ID: <20040913223952.GB28524@elf.ucw.cz> (raw)
In-Reply-To: <413CD636.6090409-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
Hi!
> I'm currently writing a driver for a sd card reader. This reader is
> present in the ACPI DSDT tree and can be identified there using the EISA
> PNP id. I'm not all too familiar with exactly how ACPI works and even
> less how ACPI works on linux so my question is this. Is there anything
> my driver should do to associate the entries in the DSDT with the
> device? Perhaps there are methods that should be called or similar? I do
> not have the time to study ACPI in detail so I'd appreciate any help.
See for example battery.c driver -- it detects battery based on PNP
id.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
next prev parent reply other threads:[~2004-09-13 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 21:27 ACPI to driver connection Pierre Ossman
[not found] ` <413CD636.6090409-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-09-13 22:39 ` Pavel Machek [this message]
[not found] ` <20040913223952.GB28524-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-09-17 7:06 ` Pierre Ossman
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=20040913223952.GB28524@elf.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=drzeus-list-p3sGCRWkH8CeZLLa646FqQ@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