| Age | Commit message (Collapse) | Author |
|---|
|
this probably means the controller is dead -- as in, a hot plug eject
event. in that case, mark the driver dead and try harder to return -1
in the interrupt handler.
tested by many
ok dlg, miod did not object
|
|
test it now that it's in-tree. ok deraadt ("It causes no harm")
|
|
ok deraadt
|
|
|
|
argument to wdcreset(), to have it skip waiting until active channels see
their BUSY bit clear in the status register.
Use this feature in the resume path, during the first reset operation. The
first reset is supposed to only wake up the controller, and the disks don't
come back until the second reset is issued, therefore waiting for them to
report themselves as ready after the first reset, but before the second, is
moot - and as a matter of fact some controllers, such as the AMD 754 and
clones/offspring (e.g. Geode) keep the BUSY bit asserted after the first
reset.
Last, but not least, make sure wd@ata invokes wd_get_params() again before
returning from the resume code, as we will still be using polled transfers
for a short while.
This causes the Lemote Yeelong to resume within less than one second, instead
of the lousy 30 seconds wait between the two resets; and the wd_get_params()
voodoo prevents it from getting spurious ide interrupts afterwards.
wd_get_params() magic from dlg; rest of the work by yours truly after enough
prodding by dlg@ and pirofti@, among others. ok deraadt@ dlg@
|
|
RTL8103E, from FreeBSD.
ok sthen@
|
|
Discovered, narrowed down, and tested by jmc@.
"definitely commit that" deraadt@, ok miod@
|
|
ok deraadt
|
|
is 0.
ok deraadt.
|
|
|
|
|
|
prompted by deraadt
|
|
prodded and ok deraadt
|
|
ok matthew@ tedu@, also eyeballed by at least krw@ oga@ kettenis@ jsg@
|
|
ar9380_spur_mitigate_ofdm().
|
|
|
|
the siop command buffers and add dmaable buffers for sense data.
matthew@ found that siop used to try to dma to the xs->sense bufer, which
is not guaranteed to be dma safe.
tested by matthew@ kettenis@
|
|
damage kernel memory very much while doing the job. It is not very
pretty yet, but improving it will need some MI work.
ok mlarkin jsg dlg
|
|
"reads OK" claudio@
|
|
ok claudio krw
|
|
is probing, rather than every time it issues an io.
ok krw@
|
|
future) will try to dma the command buffer to the disk in some way. Use
dma_alloc() to get ahead of this potential failure path.
ok dlg krw
|
|
to before scsi_done(). This doesn't mean aac will ever enabled!
ok dlg@
|
|
also cuts the aen drain over to using an iohandler so it can be made
reliable.
this compiles, but i havent got hardware to test with. its going in as a
way to force testing. if there's a problem with the code then let me know
or back it out.
"man up" k2k11
|
|
the backing store. The state of a VT is only coherent if both the active
flag and the backing store are in order, which is not the case during VT
switches.
This fixes display glitches occuring during VT switches if one of the
VT involved is doing a lot of tty updates.
Noticed by deraadt@ on a machine too fast for mere mortals.
|
|
ok dlg@ ("miod will not object" dlg@)
|
|
it will crash with 'External Non-Linefetch Abort (S)'.
similar diff provided by drahn@. tested by jasper@, deraadt@ ok.
|
|
based on discussion with damien; tested by others on the lists
|
|
ok deraadt
|
|
instead of a read barrier only, as it is used in read-modify-write cycles.
ok mjacob
|
|
Fixes DMA errors seen on sparc64.
ok miod@
|
|
queue. In some situations this prevents us from reading a garbled reply.
If this commit breaks your mpi, please report ASAP.
The issue was reported and the fix was verified by Emeric Boit. Thanks!
Ok dlg, kettenis, marco (who warned us and wanted to test more)
|
|
devices.
my theory is that some devices report queue full conditions in ways
the firmware doesnt understand, or some firmwares default to NOT
doing the queue full handling internally. either way it reports
queue full conditions as faulted io which gets passed up to the
block layer as errors.
this makes us conservative again and safe.
this fixes panics from ajacout
ok sthen@ deraadt@
|
|
Might prevent the unrecoverable DMA error mentioned in PR 6557.
ok damien@
|
|
commands on the passthru busses after the kernel becomes !cold. however,
if the enclosure doesnt have any sensors then we dont issue regular
commands to it, so ami cant see what its name is.
this moves the name fetch from the passthru io path to a walk of all the
devices on the bus just after they were attached.
problem reported and fix tested by henning@
ok miod@
|
|
issues. No actual OKs, but general acknowledgement and 'get it in' from several.
|
|
applicable on AR9271.
|
|
do not read back the LED GPIO pin since it is configured in output
only mode.
makes the link LED blink on the WiFiStation EXT when scanning (the
LEDs indicating the signal strength are not working yet).
|
|
do AR9271-specific stuff here.
|
|
this adds preliminary support for the Atheros AR9271 chipset and
probably the AR9280+AR7010 and AR9287+AR7010 too though those were
not tested.
scanning still takes a very long time (~1 sec per channel) but
otherwise, operation in STA mode seems stable.
will implement fast channel change soon.
committed over the Ubiquiti WifiStation EXT (AR9271) on i386 with WPA.
requires firmware (see man page for details)
ok deraadt@ (who checked the .h files)
|
|
|
|
jakemsr@ ok.
|
|
it not NULL before using it.
fixes crash reported by jmc@
|
|
NetBSD
|
|
|
|
add Tx gain initvals for high-power AR9380 solutions.
|
|
pointed out by Benoit Lecocq.
|
|
|
|
|
|
for MCS0~15 to not exceed the PCIe power requirements.
|
