>
> I tend to bottom post by default but top post where a thread has
> already been top posted.
Bad habit, IMO. This only encourages the evil practice.
--
Chuck F (cbfalconer@yahoo.com) (cbfalconer@worldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!
Reply by Fred●December 17, 20042004-12-17
"Mark A. Odell" <odellmark@hotmail.com> wrote in message
news:Xns95C18C933DC79CopyrightMarkOdell@130.133.1.4...
>
> Top posting corrected. ACCESS.bus uses the I2C physical layer while the
> PS/2 physical layer look similar, does not adhere to the I2C protocol. A
> discription of PS/2 is available here:
>
> http://tinyurl.com/7xr6m
>
> It looks quite trivial to implement (e.g. you could bit bang it).
>
> --
> - Mark ->
> --
I tend to bottom post by default but top post where a thread has already
been top posted.
I was coming to that conclusion myself. Interesting that the mouse I have
is quiet and doesn't send the self test on power up as suggested in the
article. Holding the data line low does initiate a clocking sequence.
Reply by Mark A. Odell●December 16, 20042004-12-16
"Fred" <Fred@nospam.com> wrote in
news:41c1c05a$0$8338$db0fefd9@news.zen.co.uk:
>> >Whilst I can still get serial mice I feel their days are numbered
>> >moreso than PS/2 mice which presumable will also eventually become
>> >obsolete for
> USB
>> >mice.
>> >
>> >I have trawled for 8051 code for the PS/2 mouse and only found one
> instance
>> >which is in assembler and not for the assembler bundled with the SDCC
>> >compiler. There were some hints that there might be code on the
>> >Philips website but I can't find it or it's gone.
>> >
>> >Can anyone help here?
> Many thanks for that article. PS/2 isn't mentioned anywhere whereas
> "ACCESS.bus" is mentioned quite frequently. I've never heard of this
> standard before and is it the same as PS/2?
Top posting corrected. ACCESS.bus uses the I2C physical layer while the
PS/2 physical layer look similar, does not adhere to the I2C protocol. A
discription of PS/2 is available here:
http://tinyurl.com/7xr6m
It looks quite trivial to implement (e.g. you could bit bang it).
--
- Mark ->
--
Reply by Fred●December 16, 20042004-12-16
Many thanks for that article. PS/2 isn't mentioned anywhere whereas
"ACCESS.bus" is mentioned quite frequently. I've never heard of this
standard before and is it the same as PS/2?
"Bill Knight" <billk@rosw.com> wrote in message
news:uuv2s0l2r98o2vcmd40l0260htaqnettjs@4ax.com...
>
>
> Regards
> -Bill Knight
> R O SoftWare
>
>
>
> On Wed, 15 Dec 2004 12:02:27 -0000, "Fred" <Fred@nospam.com> wrote:
>
> >Whilst I can still get serial mice I feel their days are numbered moreso
> >than PS/2 mice which presumable will also eventually become obsolete for
USB
> >mice.
> >
> >I have trawled for 8051 code for the PS/2 mouse and only found one
instance
> >which is in assembler and not for the assembler bundled with the SDCC
> >compiler. There were some hints that there might be code on the Philips
> >website but I can't find it or it's gone.
> >
> >Can anyone help here?
> >
>
>
>Whilst I can still get serial mice I feel their days are numbered moreso
>than PS/2 mice which presumable will also eventually become obsolete for USB
>mice.
>
>I have trawled for 8051 code for the PS/2 mouse and only found one instance
>which is in assembler and not for the assembler bundled with the SDCC
>compiler. There were some hints that there might be code on the Philips
>website but I can't find it or it's gone.
>
>Can anyone help here?
>
Reply by Fred●December 15, 20042004-12-15
Whilst I can still get serial mice I feel their days are numbered moreso
than PS/2 mice which presumable will also eventually become obsolete for USB
mice.
I have trawled for 8051 code for the PS/2 mouse and only found one instance
which is in assembler and not for the assembler bundled with the SDCC
compiler. There were some hints that there might be code on the Philips
website but I can't find it or it's gone.
Can anyone help here?