diff options
| author | Murray Stokely <murray@FreeBSD.org> | 2002-03-31 11:02:02 +0000 |
|---|---|---|
| committer | Murray Stokely <murray@FreeBSD.org> | 2002-03-31 11:02:02 +0000 |
| commit | 48e8756011f92b41664b8f1d06840f47d631e759 (patch) | |
| tree | c4cb770e62c1f49229b60c91ea0a2a4d55158a0f /sys/dev/kbd | |
| parent | 737f3cbd3c60544a6be2b9cbc58705b7cb6a63fd (diff) | |
Notes
Diffstat (limited to 'sys/dev/kbd')
| -rw-r--r-- | sys/dev/kbd/atkbdc.c | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/sys/dev/kbd/atkbdc.c b/sys/dev/kbd/atkbdc.c index 176ca666bc66..2f1ca03ad137 100644 --- a/sys/dev/kbd/atkbdc.c +++ b/sys/dev/kbd/atkbdc.c @@ -217,10 +217,10 @@ atkbdc_open(int unit) * I/O access to the controller/keyboard/mouse. The convention requires * close cooperation of the calling device driver. * - * The device driver which utilizes the `kbdio' module are assumed to + * The device drivers which utilize the `kbdio' module are assumed to * have the following set of routines. * a. An interrupt handler (the bottom half of the driver). - * b. Timeout routines which may briefly polls the keyboard controller. + * b. Timeout routines which may briefly poll the keyboard controller. * c. Routines outside interrupt context (the top half of the driver). * They should follow the rules below: * 1. The interrupt handler may assume that it always has full access @@ -239,12 +239,12 @@ atkbdc_open(int unit) * Therefore, `spltty()' must be strategically placed in the device * driver code. Also note that the timeout routine may interrupt * `kbdc_lock()' called by the top half of the driver, but this - * interruption is OK so long as the timeout routine observes the - * the rule 4 below. + * interruption is OK so long as the timeout routine observes + * rule 4 below. * 4. The interrupt and timeout routines should not extend I/O operation - * across more than one interrupt or timeout; they must complete - * necessary I/O operation within one invokation of the routine. - * This measns that if the timeout routine acquires the lock flag, + * across more than one interrupt or timeout; they must complete any + * necessary I/O operation within one invocation of the routine. + * This means that if the timeout routine acquires the lock flag, * it must reset the flag to FALSE before it returns. */ |
