Attachment 53456 Details for Bug 80843 – file.diff

[patch] file.diff

file.diff (text/plain), 1.74 KB, created by Harry Coin on 2005-05-10 03:20:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Harry Coin

Created: 2005-05-10 03:20:02 UTC

Size: 1.74 KB

patch

obsolete

>--- psm.4	Mon May  9 21:03:15 2005
>+++ psm.4.new	Mon May  9 20:57:40 2005
>@@ -207,7 +207,14 @@
> .Nm
> driver will attempt to reset the pointing device during the boot process.
> It sometimes takes a long while before the device will respond after
>-reset.
>+reset.  The driver will wait KBD_RESETDELAY msec for the aux device attached to the keyboard controller hosting the PS/2 port to respond per reset attempt. It will make KDB_MAXWAIT reset attempts before failing.  
>+The default for KBD_RESETDELAY of about 200 is enough for most direcly connected pointing devices.  If you are using a device such as a KVM
>+to share a mouse and perhaps keyboard and montior among more than one system box, or if your pointing
>+device takes longer than the default to reset, then the driver will not load even though bootup indications indicate the ps/2 pointing device is present.  In these cases putting 
>+.Pp
>+.Cd "options KBD_RESETDELAY=401"
>+.Pp
>+in a custom kernel configuration has been helpful.  Later versions may make this a tunable system setting to avoid the need to compile a custom kernel.  
> These options control how long the driver should wait before
> it eventually gives up waiting.
> The driver will wait
>@@ -740,7 +747,8 @@
> The second line shows the result of the keyboard controller's
> test on the auxiliary port interface, with zero indicating
> no error; note that some controllers report no error even if
>-the port does not exist in the system, however.
>+the port does not exist in the system, however.  If the driver doesn't load but you think the hardware
>+is working, read the information about the KBD_RESETDELAY option above.
> .Pp
> The third through fifth lines show the reset status of the pointing device.
> The functioning device should return the sequence of FA AA <ID>.

Actions: View | Diff

Attachments on bug 80843: 53456