* Looking for the correct way to retrieve ACPI table info
@ 2005-03-02 15:08 Kylene Hall
0 siblings, 0 replies; only message in thread
From: Kylene Hall @ 2005-03-02 15:08 UTC (permalink / raw)
To: acpi-devel; +Cc: Seiji Munetoh, Tom Lendacky, Emily Ratliff, Kent E Yoder
Hello-
We are working on a device driver for the Trusted Computing Group TPM.
BIOS has been augmented to created a log of TCG boot events and
userspace needs to read these events. We plan for the driver to export
them via sysfs, therefore we need to call acpi_os_map_memory and the
corresponding acpi_os_unmap memory. Would it be ok to export these
functions? Would you recommend some other interface which is already
exported or would be better to export. Currently we call
acpi_get_firmware_table with a signature of "TCPA" and a pointer to a
structure like:
struct acpi_tcpa {
struct acpi_table_header hdr;
u16 reserved;
u32 log_max_len PACK;
u32 log_start_addr PACK;
};
The log_man_len and log_start_addr fields are then passed to the
acpi_os_map_memory function and we retrieve the data.
Please let me know your feelings on this approach and the wording of
this note. Sorry for note circulating this conversation wider earlier
and saving you the work you have already done on these patches.
Thanks,
Kylie Hall
--
Kylene Hall
IBM Linux Technology Center
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-03-02 15:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-02 15:08 Looking for the correct way to retrieve ACPI table info Kylene Hall
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox