Zhao Yakui <yakui.zhao@xxxxxxxxx> writes: >> Instead of just writing a plain 6. I think at least on some machines >> there is a requirement for a low to hight transition. > Maybe the 0xCF9 port is defined for NVidia, SiS and Several others > vendor. But we can't say that it is appropriate for most boxes. Let me get this straight. We survey all of the major chipsets in existence. We discover a register that is implemented the same way in all of them. You conclude that using that register is not appropriate for most boxes? > Of course IMO it is not a generic solution for reboot. > At the same time the value written to the 0xCF9 I/O port should not be a > fixed value. Maybe it varies on different vendors/chipset. Even the > value will vary on the boxes from different BIOS vendors although the > boxes are based on the same chipset. Reading in between the lines. Did you just say someone implemented a nasty hack on some laptop and attempting to reboot by writing to 0xcf9 will cause nasty problems? If you know of such a case please describe the failure mode. If there is a case where writing to 0xcf9 will makes things worse than we need to tread carefully, and we will happily deal with reality. If you can only tell us that we are being rude and circumventing a vendors vision of the then your input is not especially useful. > And the value should be provided by BIOS. If BIOS doesn't provide > the above info, it is not safe to use them. Balderdash. There are other ways to learn things than by talking to the BIOS. Usually BIOS's are a mediocre information source at best. The job of a BIOS is to boot and if it can do that solidly you can ship it, when the schedule gets tight. Everything else is a nice to have. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
