> As you see, parport came out with some messages (*), in this
> situation we can show some bad warning and maybe don't
> load parport1....
>
> (*) 0x278: CTR: wrote 0x0c, read 0xff
> 0x278: DATA: wrote 0xaa, read 0xff
We can give a warning if you like, but we have no choice but to believe
the user. When no peripheral is attached, the most reliable register is
CTR, but there's no _need_ for it to be readable and I don't think all
chipsets allow reads from it. On those machines, the automatic probing
will fail.
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/