From: Marcel Selhorst <selhorst-Un86pfwebVPMYnii8HsYE0T4CPmD8wNEs0AfqQuZ5sE@public.gmane.org>
To: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Accessing DSDT entries within a kernel device driver
Date: Wed, 03 Aug 2005 00:05:43 +0200 [thread overview]
Message-ID: <42EFEE37.2090500@crypto.rub.de> (raw)
In-Reply-To: <1123019412.5110.52.camel@tdi>
> Heh, I should pay better attention to who I'm talking to ;^)
lol, sounds a little like the godfather:
<italian sound on>
you better pay attention whom you're talking to
<italian sound off>
:-))
> Very cool. While you're at it, I think we're going to end up having
> TPMs that live in MMIO space instead of I/O port space. I assume the
> access semantics are pretty similar, readb/writeb vs inb/outb, but it's
> probably a good time to add that too.
great idea, I will think about that :)
> Completely untested, but based on 8250_pnp, I think you'd need
> something like this: [...]
wow, that was quick, thanks for the fast reply and the detailled examples!
I will try them out now (hmm, hope this is not going to be an insomnian night).
> I probably have some scrap
> code around from when I was trying that approach if you'd like it.
For the moment I should have enough :)
> Cool, sounds like things are on the right track. Let me know if I
> can help further.
Yes, thanks, you can test the new code, when its done :-)
Bye,
Marcel Selhorst
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
prev parent reply other threads:[~2005-08-02 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 19:29 Accessing DSDT entries within a kernel device driver Marcel Selhorst
[not found] ` <42EFC9AD.8060607-yWjUBOtONefk1uMJSBkQmQ@public.gmane.org>
2005-08-02 20:18 ` Bjorn Helgaas
[not found] ` <200508021418.40355.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-02 21:00 ` Marcel Selhorst
2005-08-02 20:38 ` Alex Williamson
2005-08-02 21:33 ` Marcel Selhorst
[not found] ` <42EFE697.8030701-yWjUBOtONefk1uMJSBkQmQ@public.gmane.org>
2005-08-02 21:50 ` Alex Williamson
2005-08-02 22:05 ` Marcel Selhorst [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=42EFEE37.2090500@crypto.rub.de \
--to=selhorst-un86pfwebvpmynii8hsye0t4cpmd8wnes0afqquz5se@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alex.williamson-VXdhtT5mjnY@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