[openbeos] Re: is system_time(); an expensive call?
- From: "Bruno van Dooren" <bruno_van_dooren@xxxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Sat, 17 May 2003 17:55:49 +0200
to implement actual PS2 communication in my driver i have to read and write
to different io addresses.
the keyboard addresses for input and output are 0x60 and 0x64.
i suspect that i have to call map_physical_memory.
this means that i have 4 memory area each 1 byte long? (kb in, kb out, mouse
in, mouse out)
is this correct?
kind regards,
Bruno.
- Follow-Ups:
- [openbeos] Re: is system_time(); an expensive call?
- From: François Revol
- References:
- [openbeos] Re: is system_time(); an expensive call?
- From: Axel Dörfler
Other related posts:
- » [openbeos] is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- » [openbeos] Re: is system_time(); an expensive call?
- [openbeos] Re: is system_time(); an expensive call?
- From: François Revol
- [openbeos] Re: is system_time(); an expensive call?
- From: Axel Dörfler