Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Nov 1996 13:24:45 +0900
From:      Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To:        Ron Bolin <rlb@mindspring.com>
Cc:        nate@mt.sri.com, sos@freebsd.org, freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject:   Re: boot: -c does not work for me 
Message-ID:  <199611220424.NAA18594@zodiac.mech.utsunomiya-u.ac.jp>
In-Reply-To: Your message of "Thu, 21 Nov 1996 21:00:49 EST." <32950951.41C67EA6@mindspring.com> 
References:  <9611200134.AA09530@cabri.obs-besancon.fr> <199611200534.WAA04055@rocky.mt.sri.com> <3294540F.41C67EA6@mindspring.com> <199611211820.LAA11348@rocky.mt.sri.com> <32950951.41C67EA6@mindspring.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
Hello. 

I am currently working on the `psm' driver and the `kbdio' module for
the `syscons' and the `psm' drivers.

>> > When I did a cvsup again on the /usr/src/sys tree the other day when I
>> > sent you my results it was 1.189 for sure. Same tbl junk on login at
>> > the keyboard, had to do a hardware reset/reboot.

Have you, by any chance, set the XT_KEYBD flag during UserConfig or 
in your config file?

>I have noticed that with 1.89 syscons.c I can take my P6 200 down
>to 10% idle (top 3.4) by just moving an rxvt term with the PS/2 mouse.
>The older 
>driver did not do that as far as I know. Anyone else with a PS/2 mouse
>or seiral mouse for that mater notice this?

This may have something to do with the report rate of the PS/2 mouse.
The new `psm' driver explicitly sets the report rate to 100
reports/sec.  (This doesn't necessarily mean the mouse will generate
100 interrupts per sec. It is quiet while no movement is detected.)

I thought 100 is acceptable value, because the older driver DID have
code to set the report rate this way.  But the code was commented out. 
I guess that that part of the driver didn't work because it sent a
wrong sequence of command and data to the mouse. I thought "OK, 100
was the value originally intended; I shall make it work..."

If 100 reports/sec is too high, we can try:

1. Lower rate 
But, some PS/2 mouse cannot change the rate to anything less than 100.
Some of my PS/2 mouses certainly cannot.

2. Don't try to set the rate, use the power-up default 
Basically the old driver did this (was it a bug or a feature?).

(I also remember seeing a document stating 100 is the default after
reset, and thinking it wouldn't do any harm explicitly setting the
value. But, I don't remember which doc it was.)

Kazu



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611220424.NAA18594>