| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when workqs were introduced, we provided a second argument so you
could pass a thing and some context to work on it in. there were
very few things that took advantage of the second argument, so when
i introduced pools i suggested removing it. since tasks were meant
to replace workqs, it was requested that we keep the second argument
to make porting from workqs to tasks easier.
now that workqs are gone, i had a look at the use of the second
argument again and found only one good use of it (vdsp(4) on sparc64
if you're interested) and a tiny handful of questionable uses. the
vast majority of tasks only used a single argument. i have since
modified all tasks that used two args to only use one, so now we
can remove the second argument.
so this is a mechanical change. all tasks only passed NULL as their
second argument, so we can just remove it.
ok krw@
|
|
|
|
| |
creating sensors.
|
|
|
|
|
|
| |
conversion to tasks.
tested by chris@
|
|
|
|
| |
ok tedu
|
|
|
|
| |
after discussions with beck deraadt kettenis.
|
|
|
|
|
|
| |
"type D" Marvel 9580. From Ching Huang, Areca.
ok dlg@
|
|
|
|
|
|
|
|
| |
"chip type D" which is Marvell 9580. None of the other types do
this and OpenBSD doesn't interrupt during the interrupt routine
anyways. From Ching Huang, Areca.
ok dlg@
|
|
|
|
|
|
|
| |
the DVA macro should cast, but i am wary of the effects on all uses of it,
so fixing it in the one place that needs it.
fixes compiles on i386
|
|
|
|
|
|
| |
Tested on a variety of Intel-IOP cards
ok dlg@ henning@ "i'll ok to get this unstuck"
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
cleaning up some shutdown-hook related code on the way.
(A few drivers related to sparc are still skipped at kettenis' request)
ok kettenis mlarkin, tested by many others too
|
|
|
|
|
|
| |
is causing problems when trying to boot sparc64 from an isp(4).
Verified to fix the sparc64/isp(4) regression by krw@; ok deraadt@
|
|
|
|
|
|
| |
saa_luns instead of adapter_buswidth and luns in the prototype link.
ok dlg@, miod@
|
|
|
|
|
|
|
|
|
| |
intrstat on arc may have other status bits set which are masked as
interrupt cause and not handled by our driver. So the intrstat ==
0 check does not work reliably. It is better to do use a variable
that is set to 1 when work is done and the cause is cleared.
This makes arc(4) behave on systems where interrupts are shared.
OK deraadt@ dlg@
|
|
|
|
|
| |
traversal code to suspend/resume
ok oga kettenis blambert
|
|
|
|
|
|
|
| |
Bogus chunks pointed out by matthew@ and miod@. No cookies for
marco@ and jasper@.
ok deraadt@ miod@ matthew@ jasper@ macro@
|
|
|
|
|
|
|
| |
Tested by me on an ARC-1210 on both single and multi volume
configurations.
ok dlg
|
|
|
|
| |
ok dlg matthew
|
|
|
|
|
|
| |
Requested by dlg when reviewing a different diff.
ok dlg
|
|
|
|
|
|
| |
sparsely populated buses.
ok dlg@, krw@
|
|
|
|
|
|
|
|
|
| |
matter, an SLIST is smaller, and the first element is more likely to be
in cache. Previously we took from the head and returned to the tail,
which meant that we were using the ccb that was the least recently used
one which also means it has the smallest chance of being in cache.
ok deraadt
|
|
|
|
|
|
|
|
| |
step in elminating 'struct scsi_device' entirely.
Spotted and initial diff from matthew@.
ok matthew@ dlg@ deraadt@ marco@ miod@
|
|
|
|
|
|
|
| |
low-hanging splbio/splx pairs that are no longer needed and see if
this reveals any hidden scsi flaws.
ok dlg@
|
|
|
|
| |
ok krw@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
void. Use XS_NO_CCB error in the scsi command (xs) to report the
NO_CCB condition. Eliminates all SUCCESSFULLY_QUEUED and COMPLETE
confusion and untangles the midlayer from the adapter a bit more.
Eyes and some fixes by miod@
There may be some compile issues on little used (i.e. I don't have
any) drivers but the change is mechanical and thus easy to remedy.
ok dlg@
|
|
|
|
|
|
|
| |
else cares so it's just noise. Drivers that actually look at ITSDONE
are unchanged.
ok marco@ (for his files) dlg@ beck@
|
| |
|
|
|
|
|
|
| |
as additional argument. This will allow intermediate layers between
scsi devices such as sd and scsi host adapters to take appropriate
action if necessary.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4 bytes in the new firmware.
To allow this to work on older firmwares add a "short read allowed"
flag to arc_msgbuf(), which will allow short reads by getting
the read length from the header of the response the firmware sends.
Only set the flag on the arc_msgbuf() call that deals with the diskinfo
struct for now.
Discussed with and ok dlg@
|
|
|
|
|
|
|
| |
Lets cards like the 1261ML with SGPIO sideband on Mini SAS,
control locator LEDs through bioctl.
ok dlg@
|
| |
|
|
|
|
| |
marvell boards.
|
|
|
|
| |
traditional intel iop and the new marvell one used on the ARC-1200 rev B.
|
| |
|
| |
|
|
|
|
|
|
| |
based ones. this renames the register defines for the revision A boards
(the intel ones) to ARC_RA instead of ARC_REG so we can differentiate them
from the ARC_RB registers for revision B that are coming.
|
|
|
|
|
| |
mappings. without this a problem board can cause a panic when the interrupt
handler touches unallocated memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
restrict changes to its configuration. in our case we want to be
able to disable or enable the alarm. if a password is set though,
the firmware will reject that request with a PASSWORD_REQUIRED
response code. this change lets the kernel return EPERM instead of
EIO in that case.
if you dont have a password set on the firmware you can configure
the alarm just fine.
makes sense claudio@
|
|
|
|
|
| |
SATA ports. print "firmware" instead of "FW Version:" cos i think it looks
better. tested on a 1680 which seems to just work so far.
|
|
|
|
| |
obvious.
|
|
|
|
|
| |
the correct size for my 4.TB volume. Original diff from dlg@ with some
tweaks by me; ok dlg@
|
|
|
|
|
|
|
|
|
| |
kernel thread of its own. the api has changed (which will be fixed in the
manpage shortly) so all the users of sensor tasks that i can find have
been fixed too.
noone tested, so its going in to force people to run with it.
"put it in" deraadt@
|
|
|
|
| |
ok marco@ then suggested deraadt@
|
|
|
|
| |
OK tedu@, dlg@.
|
| |
|
| |
|
|
|
|
|
|
| |
of new fields in the future is less disruptive. This is done similar
to how struct proc is handled for ps(1). ok jmc (man page changes)
tested fkr simon, and more suggestions from millert
|
|
|
|
| |
ok dlg@, tested by jolan@
|