Age | Commit message (Collapse) | Author |
|
the fc4 types for fabric ports we find
|
|
one copy when both isp(4) and qla(4) are enabled. This is a temporary
measure until qla(4) takes over completely.
looked at by miod@ and kettenis@
|
|
|
|
now. The one 2100 card I have doesn't work at all with isp(4). I can get
it to see devices on the fabric, but it can't log in to them, and it can't
see loop devices at all.
|
|
ok jmatthew@
|
|
Otherwise a spurious interrupt might make us dereference a null-pointer.
This is especially important for ISP2200 cards with Open Firmware, where the
card is running a full firmware and the response queue "in" pointer is
non-zero when we take over.
ok jmatthew@
|
|
stub out the firmware loading code and don't include the firmware files
when ISP_NOFIRMWARE is defined.
|
|
later on.
|
|
seems to be disconnected from the interrupt status register, so we shouldn't
wait until the interrupt status is nonzero to check it. This makes onboard
FC controllers in Sun systems work better.
tested on a blade1k (by kettenis@) and a v880.
|
|
be found on some Sun hardware doesn't have an NVRAM.
ok jmatthew@
|
|
icb_xfwoptions. one of my qla2200 cards seems to have this enabled
in its nvram, so it wasn't getting io completions.
|
|
kettenis@ found that this causes problems on sparc64 machines that boot off
isp2200s.
|
|
target.
ok jmatthew@, dlg@
|
|
``Callers of scsi_iopool_init() ought to set up the pool member in struct
scsi_link accordingly, for bad things will happen without (and this was a
real pita to debug).''
|
|
fixes cd panics where the free_xfer path is called after scsi_done calls
xfer_put.
|
|
|
|
because im using it while the system is up and running i need the
xfer free path to take the right locks, which PRIVATEXFER doesnt.
invent a new C_SCSIXFER flag that provides the safety needed.
this fixes issues people have had installing from atapiscsi(4) cdrom
devices.
bug spelunking and tailq corruption identified by jsing@
ok jsing@
|
|
ok jmatthew@
|
|
This involves a bit of a hack in the interrupt processing path, where we
ignore the interrupt status if we're expecting a mailbox command to complete,
but we don't have the mailbox semaphore and the response ring hasn't moved.
Typically next time through, the interrupt status is the same and we have the
semaphore so we can read the results.
|
|
but only for interrupts that return information through mailbox registers.
|
|
into one of 4 types in qla_read_isr.
|
|
These need to be explicitly set to 0, otherwise the firmware might not do
the process login and so leave us unable to talk to the device.
|
|
|
|
|
|
interrupt, 0 if it didn't.
"makes sense" dlg@
|
|
so far). Works reasonably well now, so it's going in the tree so others can
try it out.
with some help and fixes from dlg@, general encouragement from basically
everyone
|
|
place that uses it.
|
|
take advantage of pool_setipl while here.
|
|
thing that stores state for luns.
instead of checking and allocating it in the scsi_cmd path, and
doing weird things all over the place to free it (eg, there's a
timeout that ran every 10m to gc luns), use the scsi_probe and
scsi_free things the midlayer calls.
|
|
scsi_adapter struct, just do it once in the chip code.
ok krw@
|
|
this would have been difficult before because the ata completion
paths try to be helfpul by freeing xfers on the adapters behalf,
whch doesn't work in the new world scsi model where the layer that
allocated the thing is responsible for freeing it, and expects to
get it back and maybe use it again. however, deraadt@ added magic
flags for hibernate that im now using to keep ata xfers for the
scsi layers.
committing this now so itll be tested. i cant think of a better time
to handle fallout from diffs like this than hackathons.
discussed with deraadt@
|
|
single pool, which we now layer iopools on top of and share in the same
way.
tweaks and testing by miod@
|
|
compiled and tweaked by martin@
|
|
subsystem provides for us now when dealing with the xfer pool.
ok krw@
|
|
not XS_NO_CCB.
discussed with krw@ who agrees
|
|
not XS_NO_CCB.
discussed with krw@ who agrees
|
|
a driver stuffup.
aac is XS_NO_CCB clean now.
|
|
eyes and ok by krw@ jmatthew@
|
|
minphys.
|
|
"private" so i dont feel bad about changing it.
|
|
This is so I can use the machine to figure out the others things on it,
the quirk will go away when interrupt routing gets fixed.
ok dlg@, jmatthew@
|
|
32-bit PCI NIC in a 64-bit PCI slot. The code has never been enabled, never will
be and is unused / unmaintained. Update the man page to not indicate there is a
possibility of the driver detecting this hardware issue.
Input about the man page and Ok chris@
|
|
drivers) activate functions at DVACT_RESUME time do not need to do
so, since their PHYs are repaired by IFF_UP.
|
|
mouse port, depending upon the system time, match what the prom is doing and
actually probe for a keyboard on both ports, and decide the first port with a
keyboard is the keyboard port.
If no keyboard is found, but a mouse is found, decide the keyboard port is the
empty one.
If no device is found, then we can try and pick the defaults, depending upon
the system we are running on, as this used to be the case (i.e. coping with
Fuel having keyboard on port 1 and mouse on port 0 when connecting devices
according to the chassis' markings).
This is necessary because different IO9 board revisions on Tezro come with
different wirings, and we can not tell these boards apart.
Discussed with "nullnilaki" (nullnilaki on gmail) who is the lucky owner of an
Onyx 350 with correct wiring and a Tezro with inverted wiring. Tested on Octane
and Fuel with all combinations of devices connected (mouse only, keyboard only,
keyboard and mouse) in both ports, glass and serial console.
XXX We probably want to allow for more pckbd attachment flexibility on non-x86
XXX platforms eventually (at least where the PS/2 slots are really independent,
XXX so that we can attach pckbd to any port and better cope with human error
XXX when connecting devices.
|
|
be any characters. If the chip is not actually there for some reason, we'd
be spinning so early in the resume sequence, we'd probably go mad trying to
find the reason..
ok kettenis
request: people with serial ports on their laptops, try to run a "cu" over
a suspend/resume cycle, and see if you see "input noise"
|
|
bus-independent fashion.
ok kettenis
|
|
|
|
Bug didn't have any bad effects since rtsx doesn't support SDIO at present.
|
|
kernel resumes normal (non-cold, able to run processes, etc) operation.
Previously we were relying on specific DVACT_RESUME op's in drivers
creating callback/threads themselves, but that has become too common,
indicating the need for a built-in mechanism.
ok dlg kettenis, tested by a sufficient amount of people
|
|
replaces pointers in the softc and all sorts of fun stuff. this protects
the call to bio_getitall with the sc_lock the ioctl path uses, so we dont
get panics like those reported on bugs@ recently.
ok deraadt@
|