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? Maybe it's OK for now to have lots of model specific workarounds regarding whether we throw the Big Binary Switch of OSIL(Linux), but what if in the future that's not enough. It may be hard to make vendors change designs mid-course, yes, but it may be even harder in the future, and even more of a disaster. Maybe the answer is we don't use OSI(Linux) in the future, but we use a series of OS compatibility OSI switches. Even then, we'll need to know when we should use OSI(Linux), and when we don't, which means we'll have to track BIOS versions. I almost wonder if we're better not putting any model-specific versions at all, and then work really hard to influence the vendors, as opposed to a "half-way pregnant" approach where we whitelist individual models, but not BIOS versions.... Tradeoffs either way! > > vendors who care about Linux run this: > > > > http://linuxfirmwarekit.org/ > > > > So I think if shout there, then it we'll be heard. Sure --- do we have the right language in linuxfirmwarekit.org to talk about issues such as Windows- and Linux- specific behaviours and how to handle OSI(<foo>) issues? - Ted - 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
