| Age | Commit message (Collapse) | Author |
|---|
|
|
|
- support additional volume events;
- track volume rebuild progress;
- support for drive hotplug;
- log when volume state changes and when we start to resync;
- mpii_device handling rewrite (r/b tree is no more);
- improvements in mpii_ioctl_* functions;
- use internal disk_phys_num again as phy port number based
scheme was proven to be unreliable;
- fixup ioc_status check in mpii_scsi_cmd_done;
- change Offline state to Invalid when drive is gone;
- fixup recognition of the rebuilding state;
- don't leak ccb if poll fails;
- make use of the MPII_F_RAID flag and register with bio only
if there are RAID capabilities (idea from mpi);
- EVENT_UNMASK macro improvement from Kai Doernemann;
- use proper endianness when setting ccb_dev_handle;
- lower a polling delay in the mpii_complete;
- improve readability and debugging output in several places;
- change semantics of the SAS discovery event handler;
- start of the event cleanup;
- start of the whitespace cleanup;
- start of the KNF cleanup;
from Mike Belopuhov <mkb@crypt.org.ru>
|
|
now, so it not our job to free it.
|
|
Manager api.
This is currently disabled by default under ifdef INTELDRM_GEM (option
INTELDRM_GEM in a kernel config or a patch to i915_drv.h needed to
enable), mostly because the intel X driver currently in tree does not
always play well with GEM and needs to be switched to UXA accelmethod
(which is the only option on later drivers).
While based on the intel drm code in the linux kernel this has come cleanups and
some obvious behaviour changes:
1) mmap through the GTT is entirely coherent with the gpu cache, removing
mappings whenever the cache dirties so you can not race with userland to write
to memory at the same time as the gpu.
2) pread/pwrite access is tiling-correct, so userland does not need to tile
manually (mesa has already been fixed for this a while ago). The straw that
broke the camels back here was the bit17 swizzling stuff on some mobile gpus
meansing that while userland did the swizzle itself, the kernel had to do
*extra* swizzling, this was frankly retarded so the option was dropped.
3) there is no option to map via the cpu from userland, again due to
coherency issues.
4) additional integer overflow checking in some areas.
5) we only support the newer EXECBUFFER2 command submission ioctl. the
old one is not supported at all (libdrm was fixed WRT over a week ago).
now the TODOs:
1) the locking is funky and is only correct due to biglock. it does
however work due to that. This will be fixed in tree, the design in
formulating in my head as I type.
2) there are currently no memory limits on drm memory, this needs to be
changed.
3) we really need PAT support for the machines where MTRRs are useless, else drm
uses quite a lot of cpu (this is a bug that continues from the older code
though, nothing new).
4) gpu resetting support on other than 965 is not written yet.
5) currently a lot of the code is in inteldrm, when memory management
comes to other chipset common code will be factored out into the drm
midlayer.
Tested on: 855 (x40), GM965 and 915 by me. 945 by armani@ and jkmeuser@,
gm45 by armani@ and marco@. More testing is needed before I enable this
by default though. Others also provided testing by what they tested
escapes me right now.
In order to test this enable INTELDRM_GEM in a kernel and add the following line
to the driver section in xorg.conf (I am working on a patch to autodetect the X
stuff):
Option "AccelMethod" "UXA"
|
|
|
|
if supported.
When we do memory management on intel this would lead to a LOT of
wbinvd() to deal with gpu->cpu incoherency. no one wants that.
Needed for sanity of inteldrm memory management which is coming up next.
|
|
|
|
ok sthen@
|
|
and Belkin F6C120 UPS, both UQ_BAD_HID.
|
|
|
|
and Belkin F6C120 UPS.
|
|
ok deraadt@, earlier version ok jasper@, feedback halex@
|
|
to ease grepping, rewording them slightly to mostly fit onto 1 line
and to clarify UQ_EHCI_NEEDTO_DISOWN. ok deraadt@
|
|
When we move more towards kms we'll need to save/restore what is bound
to the aperture, but right now this is not needed (since we always
unbind everything before we go down anyway).
"can not hurt" deraadt@. tested by halex, deraadt and maybe some others.
|
|
suspend, we must roll back by calling wsdisplay_resume() or the virtual
console switching will be locked forever
ok oga
|
|
Check for emptiness of the TX queue instead of lastds != NULL.
I have a feeling this might fix the "device timeout" issues reported
by Rivo Nurges on his AR5418 unveiled by athn.c r1.28 commit, though
he is not around to confirm.
This is a candidate for -stable.
|
|
check result of carrier leakage calibration and redo calibration if needed
add support for newer AR9285 chips (AR9285 XE 2.0).
tested for non-regression on a DNXA-95
"Still seems to work here" kettenis@
|
|
from mlarkin@ and me, with some amd64 fixes thrown in by deraadt@
ok marco@, deraadt@, pirofti@, mlarkin@
|
|
|
|
is presented for some of the Broadcom bge(4) FastE adapters. From Brad.
|
|
we're using. fixes operation on some 5GHz channels (e.g 153).
great thanks to Yao Zhao (dragonlinux at gmail dot com) for
identifying the issue on run(4).
|
|
that the radio is disabled with the same message as in other drivers.
let initialization continue for the moment until i'm sure it is correct.
|
|
|
|
Found after jbg@ sent me a horrible dmesg.
|
|
that could be PCI-X. This bit is not valid for PCIe controllers.
From Brad
|
|
|
|
|
|
noted by damien@
|
|
ok deraadt@, damien@
|
|
|
|
|
|
|
|
access to its free ccbs.
ok krw@ beck@ marco@
tested by beck@
|
|
to its free ccbs.
this allows the midlayer to schedule access to the bus in a roundrobin
fashion for all consumers on the bus, including io from devices and even
the internal mpi management commands used to poll the state of raid
devices. the result is fairer sharing between disks on the bus and more
reliable sensor updates.
ok krw@ beck@ marco@
tested by beck@
|
|
|
|
|
|
Probably not functionnal yet (but test reports are welcome).
Update microcode for RT2860 while I'm here (remember to run
make && make install under sys/dev/microcode/ral/).
|
|
|
|
|
|
"iff you commit over the Hero" mk@
|
|
indicates the LBA of the first logical block that is located at the
beginning of a physical block
implemented as best as i can by my understanding of the spec. not tested
yet.
|
|
factoring the processing that the limits vpd page does out.
this will be easier when i get hold of a disk that does provide values in
these ata identify fields.
|
|
|
|
ever seen one, but the spec describes how to do it.
|
|
|
|
with codecs like the ALC269 that have pins that need to be configured but
don't have an associated mixer item.
ok jakemsr@
|
|
is not yet available.
The combo WiFi/WiMAX devices need a separate firmware too (that is not
yet available), so do not use the firmware for WiFi-only devices as it
will likely not work.
Change the way active chains (the ones that have an antenna plugged in)
are detected to work around a firmware bug which could make us mark
non-existing chains as active.
|
|
|
|
|
|
|
