| Age | Commit message (Collapse) | Author |
|---|
|
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@
|
|
|
|
|
|
ok miod@ marco@ deraadt@
|
|
to get the right names for sensor creation.
|
|
attach it.
|
|
|
|
help from & ok dlg@
|
|
it turns out a drivers detach code isnt called when the machine is shutting
down, which meant my bits to stop bgrb and sync the cache werent being
run. without those bits being run the filesystems on these controllers
were never clean on reboot, so we'd always get an fsck.
so now we provide a shutdown hook which does get run on shutdown to sync
the cache properly.
found by claudio@
|
|
only ack the interrupts we deal with in the interrupt handler.
use the correct macros when setting the interrupt mask.
|
|
|
|
i can just check if this is non zero to see if a volume is degraded. this
means i dont have to pull the raid info page to find failed disks in the
volume inquiry.
|
|
volume is degraded, just if it is working or not. if a volume is degraded,
its still online, so we have to go look for missing disks. if a disk has
been replaced, but it is yet to be rebuilt, the firmware kindly tells us
that it needs rebuilding. we can figure out if a volume is degraded using
these two facts.
|
|
bioctl output. this is actually a bit of a struggle since the firmware
doesnt represent these states well at all. im only showing the obvious
ones: online, init, rebuild, and offline. i have no idea how they tell if
a volume is degraded.
|
|
as 0xff, and the command to query that phys disk will fail and cause the
ioctl to get stuck. so if the disk id is 0xff, fake an offline disk on
another bus since bioctl doesnt know how to show that properly.
|
|
|
|
|
|
|
|
|
|
|
|
they are.
|
|
|
|
|
|
about the disks that are configured on the controller. so far this fetches
the right volumes and disks in each volume, but doesnt properly fill in the
status, the size of both the volumes and disks, the type of raid, or the
firmware version of the physical disks.
|
|
find the names of our volumes.
|
|
|
|
|
|
|
|
|
|
be unaligned we basically need to bounce the contents of the message in and
out of what is submitted to the hardware. rather than have the callers of
arc_msgbuf do that, make arc_msgbuf do it for them. while we're here, make
arc_msgbuf do the checksumming and length checks so the callers dont have
to do that either.
this adds an alternative to arc_msgbuf that does the new functionality and
cuts arc_bio_alarm_state over to using it. i'll cut the other users of
arc_msgbuf over shortly and remove the old implementation.
|
