| Age | Commit message (Collapse) | Author |
|---|
|
ok jsg@
|
|
from ISIHARA Takanori
|
|
|
|
from ISIHARA Takanori
|
|
ok jsg@, miod@
|
|
usage in a currently disabled codepath to prevent future surprised.
|
|
|
|
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: msi, MoW2
ok jsg@
|
|
USB host-to-host link cable. This driver is derived from upl(4).
|
|
no functional change.
ok sthen@
|
|
MAC address, continue on, because if_etherattach contains logic for this.
ok mikeb
|
|
This function never fails. So change it's return type to void and
adjust the copy-pasted callers that were checking the return.
"If it compiles, ok" mpi@
|
|
The child should not have to call the parent for deactivation.
The parent should handle it.
So kill the activate routine in ucom(4) and adapt the parents
to no longer call it.
Also remove sc_dying in ucom(4) and use usbd_is_dying() instead.
Okay mpi@.
|
|
This set of drivers were very very dirty.
i/ Clean-up the match/attach multi-casting hackjob
- stop casting aux to every attach arg in existance
- be consistent about casting it only to uhidev_attach_arg
- fetch the usb_attach_arg from above where needed
ii/ Sort out the activate routines
- leave the deactivation to the parent (uhidev(4))
- ditch the sc_dying flag in favour of usbd_is_dying()
iii/ Get closer to keeping all the usb hid information in the uhidev
structure (one uhidev per reportID)
- store the usbd_device in the uhidev
- use it consistently instead of always peaking at the parent's
soft state
Okay mpi@
|
|
fix excessive timeouts and 'Michael mic' errors.
Problem pointed out by vigdis via bugs@
ok dlg@
|
|
still in workqs.
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
The controllers are linked through device->bus so the iface is redundant.
So fixing usbd_dopoll() to take the device as argument and making
usbd_interface2device_handle() private (for now) inside usbdi_util.
Tested and okay mpi@
|
|
|
|
present in this function, but I've been advised to walk away, and it
have been this way forever (and this code is not even enabled in GENERIC
by default anyway)
original bug found by Maxime Villard, thanks.
|
|
%u for u_int32_t d_secsize.
|
|
Okay mpi@
|
|
Okay mpi@
|
|
|
|
Leave the deactivate bits to the parent.
Simplify by making a single dying check in uhidev(4) interrupt routine
instead of having each child doing it.
Okay mpi@
|
|
network to presentation format to inet_ntop().
The few remaining functions will be soon converted.
ok mikeb@, deraadt@ and moral support from henning@
|
|
ok yasuoka@
|
|
"ticks - start > interval" because the latter copes with ticks wrapping.
pointed out by guenther@
|
|
i havent had any tests, so if there's any fallout ill deal with it when
people hit it. i wont feel guilty about it at all though.
|
|
Otherwise using any atomic memory operation will lock up the GPU due
to a Haswell hardware bug.
v2: Use the _MASKED_BIT_ENABLE macro. Drop drm parameter definition.
From Francisco Jerez
018e31d2bd17a8bc95e1d1ca519650f2418b6010 in ubuntu 3.8
f3fc4884ebe6ae649d3723be14b219230d3b7fd2 in mainline linux
|
|
On HSW enabling a plane on a disabled pipe may hang the entire system.
And there's no good reason for doing it ever, so just don't.
v2: Move the crtc active checks to intel_crtc_cursor_{set,move} to
avoid confusing people during modeset
From Ville Syrjala
f6c0873963a9b8ea1d94541e0e219e6ea090012b in ubuntu 3.8
f2f5f771c5fc0fa252cde3d0d0452dcc785cc17a in mainline linux
|
|
The cursor is disabled before crtc mode set in crtc disable (and we
assert this is the case), and enabled afterwards in crtc enable. Do not
update it in crtc mode set.
On HSW enabling a plane on a disabled pipe may hang the entire system.
And there's no good reason for doing it ever, so just don't.
v2: Add note about HSW hangs - vsyrjala
From Jani Nikula
0be01fc195fd4ea1aec1f8be7c03ca8f920a9486 in ubuntu 3.8
cc173961a68034c1171a421f0dbed39edfb60880 in mainline linux
|
|
With updates to the spec, we can actually see the context layout, and
how many dwords are allocated. That table suggests we need 70720 bytes
per HW context. Rounded up, this is 18 pages. Looking at what lives
after the current 4 pages we use, I can't see too much important (mostly
it's d3d related), but there are a couple of things which look scary. I
am hopeful this can explain some of our odd HSW failures.
v2: Make the context only 17 pages. The power context space isn't used
ever, and execlists aren't used in our driver, making the actual total
66944 bytes.
v3: Add a comment to the code. (Jesse & Paulo)
From Ben Widawsky
6bab5ce3f3224d3c1fcc92ed9184392558ae3df4 in ubuntu 3.8
a0de80a0e07032a111230ec92eca563f9d93648d in mainline linux
|
|
Okay mpi@
|
|
coherently through all our controller drivers and kill the mstohz() macro.
ok pirofti@
|
|
the timeout task in the *_timeout() routine. It now becomes obvious
that the allocx/freex hooks can be merged.
ok pirofti@
|
|
|
|
|
|
|
|
|
|
|
