On Thursday 23 August 2007 23:42, Alexey Starikovskiy wrote: > Len Brown wrote: > > On Tuesday 21 August 2007 09:22, Alexey Starikovskiy wrote: > > > >> + printk(KERN_ERR PREFIX "ECDT is broken\n"); > >> > > > > I think this is > > 1. guaranteed to happen > > > No, it does not happen on machine with correct ECDT, e.g. my TP is ok. Let me clarify... It is guaranteed to happen on _some_ system out in the field that belongs to somebody who doesn't know what an ECDT is, yes? > > 2. guaranteed to alarm users and be viewed as a regression. > > > There is a message, that we are trying to get boot EC from just found > ECDT. If it fails, we tell why. It tells _you_ why, but the user hasn't a clue. If it said something like ACPI: ec: BIOS bug: mumble mumble abc is corrupt, ignoring it then you'd learn what you want, the the user would know what they need to know -- that Linux thinks their BIOS has a bug, but is continuing on. The user then can check for a new BIOS if they like, but will not send their distro mail about the "broken ECDT" which they think might be related to the Extra Critical Data Transfer feature that if broken is surely important and worth reporting... does this make sense? thanks, -Len > > They have no clue what an ECDT is, and this warning > > doesn't tell them what to do about it, if anything. > > > > -Len > > > - 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
