diff options
Diffstat (limited to 'sys/dev/advansys')
| -rw-r--r-- | sys/dev/advansys/advansys.c | 4 | ||||
| -rw-r--r-- | sys/dev/advansys/advlib.c | 2 | ||||
| -rw-r--r-- | sys/dev/advansys/advlib.h | 6 | ||||
| -rw-r--r-- | sys/dev/advansys/adwlib.h | 4 |
4 files changed, 8 insertions, 8 deletions
diff --git a/sys/dev/advansys/advansys.c b/sys/dev/advansys/advansys.c index 1eaa9a49956c..12ffd81f884e 100644 --- a/sys/dev/advansys/advansys.c +++ b/sys/dev/advansys/advansys.c @@ -633,7 +633,7 @@ adv_timeout(void *arg) * means that the driver attempts to clear only one error * condition at a time. In general, timeouts that occur * close together are related anyway, so there is no benefit - * in attempting to handle errors in parrallel. Timeouts will + * in attempting to handle errors in parallel. Timeouts will * be reinstated when the recovery process ends. */ adv_set_state(adv, ADV_IN_TIMEOUT); @@ -1123,7 +1123,7 @@ adv_done(struct adv_softc *adv, union ccb *ccb, u_int done_stat, * from this initiator are in effect, but this * ignores multi-initiator setups and there is * evidence that the firmware gets its per-device - * transaction counts screwed up occassionally. + * transaction counts screwed up occasionally. */ ccb->ccb_h.status |= CAM_SCSI_STATUS_ERROR; if ((ccb->ccb_h.flags & CAM_TAG_ACTION_VALID) != 0 diff --git a/sys/dev/advansys/advlib.c b/sys/dev/advansys/advlib.c index 9080876c5f98..75d6884b9131 100644 --- a/sys/dev/advansys/advlib.c +++ b/sys/dev/advansys/advlib.c @@ -2060,7 +2060,7 @@ adv_reset_bus(struct adv_softc *adv, int initiate_bus_reset) /*offset*/0, ADV_TRANS_CUR); ADV_OUTW(adv, ADV_REG_PROG_COUNTER, ADV_MCODE_START_ADDR); - /* Tell the XPT layer that a bus reset occured */ + /* Tell the XPT layer that a bus reset occurred */ if (adv->path != NULL) xpt_async(AC_BUS_RESET, adv->path, NULL); diff --git a/sys/dev/advansys/advlib.h b/sys/dev/advansys/advlib.h index 00573ac25576..6952ca960c92 100644 --- a/sys/dev/advansys/advlib.h +++ b/sys/dev/advansys/advlib.h @@ -228,7 +228,7 @@ struct adv_ccb_info { #define ADV_CSW_SCSI_RESET_LATCH 0x0002 #define ADV_CSW_INT_PENDING 0x0001 /* - * XXX I don't understand the relevence of the naming + * XXX I don't understand the relevance of the naming * convention change here. What does CIW stand for? * Perhaps this is to differentiate read and write * values? @@ -590,7 +590,7 @@ struct adv_scsiq_1 { u_int8_t target_lun; /* LUN - taken from our xs */ u_int32_t data_addr; /* - * physical addres of first + * physical address of first * (possibly only) segment * to transfer. */ @@ -793,7 +793,7 @@ u_int16_t adv_read_lram_16(struct adv_softc *adv, u_int16_t addr); void adv_write_lram_16(struct adv_softc *adv, u_int16_t addr, u_int16_t value); -/* Intialization */ +/* Initialization */ int adv_find_signature(struct resource *res); void adv_lib_init(struct adv_softc *adv); diff --git a/sys/dev/advansys/adwlib.h b/sys/dev/advansys/adwlib.h index 09a015538706..a73098539f2f 100644 --- a/sys/dev/advansys/adwlib.h +++ b/sys/dev/advansys/adwlib.h @@ -563,7 +563,7 @@ typedef enum { ADW_FENONE = 0x0000, ADW_ULTRA = 0x0001, /* Supports 20MHz Transfers */ ADW_ULTRA2 = 0x0002, /* Supports 40MHz Transfers */ - ADW_DT = 0x0004, /* Supports Double Transistion REQ/ACK*/ + ADW_DT = 0x0004, /* Supports Double Transition REQ/ACK */ ADW_WIDE = 0x0008, /* Wide Channel */ ADW_ASC3550_FE = ADW_ULTRA, ADW_ASC38C0800_FE = ADW_ULTRA2, @@ -801,7 +801,7 @@ carrierbtov(struct adw_softc *adw, u_int32_t baddr) return (carrierbotov(adw, baddr - adw->carrier_busbase)); } -/* Intialization */ +/* Initialization */ int adw_find_signature(struct adw_softc *adw); void adw_reset_chip(struct adw_softc *adw); int adw_reset_bus(struct adw_softc *adw); |