> > I don't like that idea very much as it wouldn't map the hardware to a
> > simple logical model. IMHO that is exactly what a hardware driver should
> > do.
>
> I can see that. But since writing the BIOS is so seldom useful, and
> is almost always dangerous, limiting the device interface to reading
> and requiring an ioctl for writing should be adequate.
>
> If the ioctl _enabled_ writing until the next close, rather than
> performing it, then you could even make a utility that only calls
> ioctl() on stdout, and then you could still use dd:
>
> (enable_bios_write; dd if=bios.image) >/dev/bios
Ok... I think I'll implement it his way.
Stefan.
-- .signature: no such file or directory.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu