Age | Commit message (Collapse) | Author |
|
Part of the work to remove -Wno-uninitialized.
ok blambert jsg
|
|
Tested by Nathanael Rensen.
|
|
Found by haesbaert@.
ok haesbaert@ deraadt@
|
|
Part of the work to remove -Wno-uninitialized.
ok kettenis@
|
|
1. vmware advertises more scsi targets than command slots, so the maths
we did for openings gave each target 0 openings. always advertise at least
16 openings.
2. if we cant configure the ATA queue depth, dont fail to attach the
controller whole.
finally, improve the error reporting during attach so its more obvious
where things fail.
mostly figured out by jmatthew@
|
|
ok dlg
|
|
ok mikeb
|
|
values and even if this would make more sense. Found by brad some time ago.
|
|
rest of the code expects.
from brad
|
|
|
|
false positives like the DUART on the MPC8347 as found on socppc.
ok deraadt@
|
|
with sleep mode. So skip the wakeup code as well if we are a serial console.
The port on the v445 almost certainly isn't a real st16650 and probably
doesn't implement sleep mode (perhaps someone cut the soft core down a bit
too much?). But it is indistinguishable from it, so we have to deal with it.
ok deraadt@
|
|
ok stsp@, deraadt@
|
|
to get stuck with OACTIVE set, requiring 'ifconfig ral0 down up' to unwedge.
Make space in the Tx queue from the rt2661_tx_dma_intr() handler,
rather than waiting until rt2661_tx_intr() is run. The latter function
now collects AMRR statistics only. AMRR node allocation is now separated
from ieee80211_node allocation to make this possible.
This commit also brings back the separation of OACTIVE flags for management
and data Tx queues which I reverted in the previous commit.
Inspired by ral commits by sephe@dragonflybsd and patch submission to
misc@ by Roland Dreier http://marc.info/?l=openbsd-misc&m=125895269930106&w=2
Tested by myself, edd, jsg, Tobias Ulmer, Pieter Verberne, Tim van der Molen.
|
|
case the kernel will still be using the port even after the last process closes
it. And on machines like the v445 the firmware won't be happy if the console
port is in sleep mode when the kernel reboots or halts.
ok miod@
|
|
these controllers let you specify disks that should be accessed directly
rather than be part of logical volumes. apparently you can plug in things
like tape drives too.
anyway, physical devices are exposed via a separate scsibus attached to
mfi.
ok mikeb@
|
|
timeouts. how embarrassment.
implement mfi_exec for doing sync executions of commands in process
contexts and cut mfi_mgmt over to it.
|
|
calling the done handler.
this makes it consistently complete scsi io with all the proper error
checking.
|
|
as the first argument to functions. like mfii.
|
|
on the free list. ccbs can be reused, so we dont want old state screwing up
new commands.
|
|
rather than put the code everywhere.
|
|
|
|
six years (since bioctl support was added).
ok krw@ dlg@
|
|
than snoop scsi commands and copy it in an io path.
no functional change, but the code has one less XXX now.
|
|
of its scsibus. only advertise 1 lun on logical volumes instead of letting
the midlayer fix it up to 8.
give every target on the bus max_cmds openings. iopools means they will
properly share access to them.
this in particular is useful on skinny controllers which only advertise 31
command slots. if you have 16 volumes, theyll only get 1 opening each with
the old maths. this way round the ones that are busy will share the slots.
tested on a perc5 with two volumes and hard workloads.
|
|
ok deraadt@
|
|
are.
noted by haesbaert@
|
|
|
|
transition_firmware into a member of the iop structures.
ok mikeb@ haesbaert@
|
|
structures and use htole64 instead of htole32(addr >> 32); htole32(addr);
gets rid of "handy" stack variables to get the dva to 64bits.
sprinkle some more byte swaps for things that should have it.
tested on a perc5 (xscale)
|
|
tested on a perc5 (xscale)
|
|
descriptors with single uint64_ts. theyre not some weird middle
endian thing. this makes the code more readable.
add some missing htole32s to the code while here.
tested on a perc5 (xscale).
|
|
endian. do appropriate byteswapping for when the host cpu uses them.
tested on a perc5 (xscale) in an amd64.
|
|
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success
ok miod@
|
|
timeout" messages on my soekris and doesn't fix the real problem.
|
|
and set the interface's IFF_OACTIVE flag if either queue is full and
clear it only if both queues have free slots. Before this change both
queues were setting/clearing the same flag with no regard for the
other queue's state.
Also, don't reset the tx watchdog counter if either queue still has frames
queued when we exit the frame-processing loop in the per-queue interrupt
handlers.
Both changes originally from sephe@dragonfly.
Tested by myself and edd on a slow busy soekris which before this
change required occasional 'ifconfig ral0 down up' to recover.
|
|
involves tweaking of BBP registers. Wait for BBP to stop being busy before
reading from it.
Originally from sephe@dragonfly. ok kettenis sthen
|
|
tested to boot multiuser.
|
|
timeout', instead of being stuck with a non-progressing request. This lets
the nonexistent LUNs of the Insite Floptical probe (as non-existing)
correctly.
Step two of Floptical support, now if only the loading mechanism would unjam
I could try some real I/O with it...
|
|
_4ltol() and _lto4l() to bha, the only place they were used.
ok dlg@
|
|
Probably not enought to make the AR9380 chips to work, but at least the kernel
shouldn't crash anymore when we see one.
ok stsp@
|
|
none of the ahc@pci are twin-channel. Broken since 3.6 as well.
|
|
ok mpi@, miod@
|
|
from Brad
|
|
the PHY is woken up upon attachment. From FreeBSD via Brad.
|
|
makes programs like less and mg look a wee bit prettier
ok miod
|
|
``boots being interrupted while the prom is loading the kernel and then
restarted no longer seem to end up with a hosed chip with this diff'' on
sgi.
|
|
if their size is not exactly six bytes, as the chip can't cope with this
situation.
Another situation all 33C93 do not cope with very well, is sending stop
commands to targets (such as all sd(4) devices when halting with poweroff) -
it takes a very long time to recover once all targets on the bus have been
powered down, so we need to raise timeouts to unholy values (one test case has
required more than 20 seconds to recover). Not surprising, as this command
is not documented as supported in the chip documentation.
|
|
ep@eisa on sgi.
|
|
|