From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: vojtech-AlSwsSmVLrQ@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
seife-l3A5Bk7waGM@public.gmane.org,
rjw-KKrjLPT3xs0@public.gmane.org,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Call for help: list of machines with working S3 (fwd)
Date: Fri, 18 Feb 2005 01:09:11 +0100 [thread overview]
Message-ID: <42153227.9060800@gmx.net> (raw)
In-Reply-To: <20050217232719.GB12638-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
Pavel Machek schrieb:
>
>>>I'm not sure if you can push the whole industry at once.
>>
>>The goal is to know what to tell the system vendors
>>interested in supporting Linux what they should do
>>with their BIOS on future platforms.
>>
>>I believe our message should be:
>>1. BIOS should save/restore video in S3
>
> Actually, that'd expect too much of BIOS writers. I believe right
> solution is "POST video as you do during normal boot in S3 resume".
Why not leave the choice to the BIOS writers? If some are able to
save/restore video state by themselves, we shoudln't stop them.
As long as the state after resume accepts setting the mode without
lockup, we should be fine.
>>2. Use Intel's ACPICA ASL compiler -- if not for production,
>>then at least as a static source code checker for validation.
>
>
> 3. Try to boot linux (here's live cd). If it complains about bios bugs
> (dmesg | grep ...), try to see if it is not indeed your bug.
That could even be automated more. A live cd which boots, performs
a few tests, displays the results on screen and offers an option
to save these results to usbstick/network/disk/whatever.
After saving the boot results, it will perform a S3 suspend and
resume and display/save the results of that, too. If Intel have
enough money, they could provide the functionality on a hard
disk and it would have the benefit that S4 could be tested as well.
If the disk has a FAT32 partition, the results can be saved there.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
-------------------------------------------------------
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
prev parent reply other threads:[~2005-02-18 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 23:27 Call for help: list of machines with working S3 (fwd) Pavel Machek
[not found] ` <20050217232719.GB12638-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-02-18 0:09 ` Carl-Daniel Hailfinger [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=42153227.9060800@gmx.net \
--to=c-d.hailfinger.devel.2005-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-AlSwsSmVLrQ@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
--cc=seife-l3A5Bk7waGM@public.gmane.org \
--cc=vojtech-AlSwsSmVLrQ@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