http://bugzilla.kernel.org/show_bug.cgi?id=13497





--- Comment #13 from Steve Hill <st...@nexusuk.org>  2009-06-17 09:26:00 ---
There is no BIOS more recent than the one I'm using.

I'm not sure what the current kernel policy is on working around broken
hardware/firmware?  Replacing the DSDT for non-debugging purposes has fallen
out of favour these days, and whilst it _is_ a bug which the vendor should be
fixing, the fact remains that the vendor don't seem to care so I don't expect
them to fix it.

So in these cases where there's a hardware or firmware bug that will almost
certainly never be fixed, what is the policy for workarounds?  Either we
implement a work around so that Linux "Just Works" on the device (and put up
with the code bloat that this adds to the kernel), or we accept the fact that
Linux will never work properly on the device without each and every end-user
implementing their own work around (for example, patching the DSDT, which
involves recompiling the kernel after every update on many distros).

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to