| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
the FreeBSD driver, and some linux code. Probably some tweaks to
reach out for more pci cards (some models are currently commented out,
and we have yet to find a card where stereo output gets de-synchronized,
as the FreeBSD driver claims happens).
Suspends/resume works, recording and keyboard volume control on the way.
This is not derived from the NetBSD driver in any way. Just happens
that both works reached completion at the same time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the async code event changes. Note (for __GNUC__) that isp_prt has
__attributes__'s of __format__/__printf__....
|
|
entries). Add some defines for the SNS "Register FC4 Type" subcommand.
|
|
|
|
|
|
wwn handling. Do a Register FC4 Type (so that we can work with McData
switches). Allow F-port topologies to use the target range 0..125 for
logging in fabric devices. We changed ISPASYNC_PDB_CHANGED to
ISPASYNC_LOGGED_INOUT and now use ISPASYNC_CHANGE_NOTIFY for both
loop && fabric events.
|
|
syscall with non-zero priority). This doesn't seem to fix connecting
to a switch problems (which *used* to work... sigh...)...
|
|
from openbsd@zenbu.com
|
|
|
|
|
|
Partial sync w/NetBSD
-Support Ultra/100 on Intel ICH2 (Tomokazu HARADA)
-Support Ultra/66 on VIA Apollo (Manuel Bouyer)
-Disable 16bit io-space limitation on Promise (Charles Hannum)
|
|
simplify locking a bit.
disable write cache if said so in the scsi_xfer.
a few more commands, from freebsd.
|
|
The whole issue of processes and threads need looking at, as NetBSD
and OpenBSD do things slightly differently - think extra arg to
VOP_XXX calls for one.
|
|
|
|
|
|
caused by another device on the PCI bus. So we won't print them. Just ACK them and go.
|
|
|
|
an exact model number for it though...
|
|
<il11@mail.csuchico.edu>
|
|
on a combination of VIA South Bridge and old Toshiba drive.
DMA transfers of 4 bytes work for my old Mitsumi FX600 drive.
Assume Toshiba drive is in error.
Avoid situation by only invoking DMA transfers on transfers over 100 bytes.
Thanks to Tim Howe for the hardware for testing
|
|
|
|
based on netbsd driver.
testing helps from brad@
eisa untested, but should work (;
|
|
panics
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It is done inline for the CY82C693U since it only has one channel.
|
|
- actually check the returned scsi_status value and act accordingly
instead of ALWAYS returning XS_NOERROR
- always return the scsi status value in xs->status for completed
requests
- no longer reference ccb->xs and ccb->dmamap_xfer if an 'unallocated'
ccb is encountered
- immediately remove the ccb adw_isr_callback is working on from the
pending list, leaving it in limbo until it is put on the free list
just before any return
- 'freeze' a target only when a scsi_status indicating it is busy is
encountered, and 'thaw' a target whenever a bus reset is done or a
request completes
- check done_status, host_status and scsi_status in that order as is
done in the linux driver and was done here until very recently, which
seems cleaner to me. But opinions may vary. The only behaviour change
that should result is that done_status of QD_NO_STATUS no longer
causes a check of host_status values, but is an error causing a
XS_DRIVER_STUFFUP
- produce a more general error message with actual values for
host_status, scsi_status and done_status values, with references to
adw(4) for more details on the error where appropriate (man page
update coming)
- take what seems like appropriate action for all known host_status,
scsi_status and done_status values with more use of XS_RESET where
appropriate
- use adw_reset_bus() instead of AdwResetSCSIBus() in
adw_async_callback() so pending requests are requeued and devices left
unfrozen when this happens
- print an error message with the code # when adw_async_callback is
called with an unknown code.
|
|
|
|
|
