On Sat, 19 Jan 2008, Theodore Tso wrote: > On Sat, Jan 19, 2008 at 10:08:30AM -0200, Henrique de Moraes Holschuh wrote: > > Actually, that only depends on us. If you drop support for people using > > known-bad BIOS versions that give you greif, they have no choice but to go > > away, or to upgrade. And so far, I have never had anyone complain that they > > had to update their thinkpad BIOS and just go away. > > > > Of course, I am terribly nice about it when I ask someone to upgrade their > > BIOS, but still... > > > > On the thinkpad-specific case, I don't actually mind tracking down the > > last-known-sane BIOS version for every thinkpad model and bitching like a > > madman on thinkpad-acpi telling people to update because it is known buggy > > and unsupported if their BIOS is too old. We already sort of track every > > important BIOS version of every model anyway in ThinkWiki... > > More importantly, what worries me is exactly the issue which Len > raised; what if OSI(Linux) enables some things that we desperately > want, and at the same time, enables some things that we don't want? That worries me as well. On the ThinkPad case, that means we need to move *fast* and reach an agreement with Lenovo, while they are still actively developing the current crop of BIOSes. Which means we need to agree among ourselves on a course of action, *document it* properly, check with Lenovo and any other vendor which is reasonably Linux-friendly if it is something they can agree to use, and get it into the firmware kit. > Tradeoffs either way! Yes. This is no easy problem asking for a quick hack as a solution. It is not impossible to solve, but it will definately require more than hacks on our side to get it done properly. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - 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
