Messages in this thread | | | Date | Thu, 17 Feb 2005 21:34:22 +0100 | From | Carl-Daniel Hailfinger <> | Subject | Re: [ACPI] Call for help: list of machines with working S3 |
| |
Pavel Machek schrieb: > >>>to reinitialise the graphics hardware, few are going to care about >>>making life easier for Linux. >> > [...] >>3. Get some shiny certification/label going that can be put on >>fully conforming products as a sticker. Something like the old >>"EPA pollution preventer" logo, but with a more appealing design. >>Perhaps a "InstantOn/PowerSave" sticker, you get the idea. > > Like "This machine actually works" sticker? :-)
Yes.
>>4. Include a mandantory description of video bringup after resume > > That sounds overcomplicated. Simply add this to the specs:
You have to start to think like a vendor with a long legacy. Then my spec draft will make more sense. Basically, you can't tell a vendor that his hardware is broken or he will ignore your efforts from that point on. "It's a question of honour." If, on the other hand, a vendor can claim his products are conforming to the spec by issuing a software update for broken hardware, it is much more likely that the spec gets accepted.
> "BIOS must POST video during S3 wakeup. Video must be working > and in 80x25 text mode when it jumps to OS. VESA BIOS calls must be > available to the OS."
That would make some products non-conformant which are working perfectly today. If the video state is preserved over S3, it doesn't make sense to declare that behaviour non-conformant.
> BIOS must do that during normal boot; this should be very little > additional work.
Not necessarily. Some BIOSes stay in graphics mode during the whole bootup (at least it seems so) and would have to include additional code to enter 80x25 text mode.
Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |