From: Emma Jane Hogbin <emmajane-MHIYrZpDPrNWk0Htik3J/w@public.gmane.org>
To: acpi <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI HOWTO
Date: Tue, 18 May 2004 08:37:17 -0400 [thread overview]
Message-ID: <20040518123717.GB1686@smeagol> (raw)
In-Reply-To: <40A95511.3070109-wanGne27zNesTnJN9+BGXg@public.gmane.org>
On Mon, May 17, 2004 at 08:13:05PM -0400, John Belmonte wrote:
> Certainly ACPI is a complex system, and transitioning from APM is
> difficult. These topics are worthy of documentation efforts like yours.
> However, it may be better to start such a document with "Be sure you
> are using the latest 2.4 or 2.6 kernel", provide a reference to
> documents which may assist users in upgrading their kernel, and focus on
> ACPI configuration and troubleshooting itself.
Agreed. At this point I've started introducing the 2.6.x series
information into the document; however, I've actually wrecked my own
laptop to try and get the new information in. I used to have a perfectly
functional laptop, now that I've got the 2.6.5 kernel I'm having problems
with not only ACPI, but also my wireless card and my printers. Even in
2.4.22 ACPI has never worked perfectly for me and it was virtually
impossible for me to extend the documentation past what my laptop was
capable of doing.
Although I'm happy to compile and write documentation on a subject that I
know little about, I am not willing to release documentation that I am not
able to test for myself. I've asked for help from a number of different
places and have gotten no response other than from this email. I recently
received email from one person about a specific bug. When I asked them for
further information about the problem he told me to just put in the documentation
that users should upgrade their BIOS--as if everyone already knew how to
do this. I certainly don't and I can't imagine I'm the only one.
I understand that everyone is busy. I know I certainly am. While I'm happy
to work on bringing the documentation up to date, I cannot do it without
help.
emma
--
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-18 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 19:01 ACPI HOWTO Emma Jane Hogbin
[not found] ` <20040517190137.GD5547-Kz9ENIl45+A@public.gmane.org>
2004-05-18 0:13 ` John Belmonte
[not found] ` <40A95511.3070109-wanGne27zNesTnJN9+BGXg@public.gmane.org>
2004-05-18 12:37 ` Emma Jane Hogbin [this message]
2004-05-21 3:11 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-05-18 14:50 Rockefeller, Harry
[not found] ` <B774920D825C2D4880A3C1B0D6EF94189A5063-YbQoUGCEyAW+LrQOllSzDQC/G2K4zDHf@public.gmane.org>
2004-05-18 15:36 ` Bruno Ducrot
2004-05-21 4:39 ` Len Brown
[not found] ` <1085114355.12354.586.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-21 7:58 ` Michael Frank
2004-05-19 14:47 Rockefeller, Harry
[not found] ` <B774920D825C2D4880A3C1B0D6EF94189E7BE3-YbQoUGCEyAW+LrQOllSzDQC/G2K4zDHf@public.gmane.org>
2004-05-24 14:35 ` Bruno Ducrot
2004-05-26 2:41 Yu, Luming
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=20040518123717.GB1686@smeagol \
--to=emmajane-mhiyrzpdprnwk0htik3j/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox