Messages in this thread | | | Subject | Re: Linux in a binary world... a doomsday scenario | From | David Woodhouse <> | Date | Tue, 06 Dec 2005 22:25:22 +0000 |
| |
On Tue, 2005-12-06 at 19:23 +0000, Alan Cox wrote: > On Maw, 2005-12-06 at 18:42 +0000, David Woodhouse wrote: > > There's some work on reverse-engineering the BIOS so that you can > > hackishly poke 'new' modes into its tables, but it's still not a very > > good option. > > Especially as the BIOS interface at the low level for the analogue end > and the logic driving it is board specific. Intel have been fairly clear > why they use the BIOS interface.
Have they? I haven't seen the excuse.
I assume it's similar to the excuse for ACPI -- "although we _could_ document the chips and allow board manufacturers to include simple tables which describe the way they're wired together (in which they have relatively little leeway), we'd rather hide it all behind some opaque blob and have you trust HardwareVendorCode to drive it instead of being able to write your own and debug it as you can with Free Software"?
Trusting the BIOS for this kind of thing isn't really much better than trusting any other binary-only piece of code, from a technical point of view. (Ignoring the licensing issues; we have indeed digressed). In fact, given the traditional quality of BIOS implementations, trusting the BIOS is far _worse_ than trusting any other piece of binary code.
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |