> Confirmed. What is the non-bus-walk name of these devices (just curious)?
What do you mean? Devices don't have flat names. The names like "eth0" and so forth are compatibility hacks in bus_walk_from_compat_string. > Ah, which reminds me that I still use device_read and not > device_read_inband, in my kbd driver. Well that's just silly. But they should both work. > Writing of the bytes doesn't seem to work properly, I set up streamio > (cat'ing from that works fine), and then I tried > > echo $'\xED\x07' > kbd The examples/x86/i8042 test program does just that, and it works (lights go on). So this must be a problem interacting with oskit-mach. > It doesn't seem to be the mapping I am using currently. For example, escape > is 0x76, but in GNU Mach 1 it is 0x01, F1 is 0x05, formerly 0x3b. I am not > sure where the difference comes from, I will try to find it out. That is the i8042 translating AT codes to XT codes. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
