Age | Commit message (Collapse) | Author |
|
Sean Levy, aka attila, <attila + stalphonsos ! com>, thanks!
ok deraadt@
|
|
negative errno values.
ok jsg@
|
|
fails it's impossible to debug and you cannot use your device.
So instead of calling usbd_set_config_index(), match the right interface.
This is trivial with this device because it has only one configuration
and interface.
|
|
because it submits synchronous transfers, so schedule a task when
necessary.
|
|
Bug reported and fix tested by Thomas Pfaff, thanks!
|
|
don't setup DMA correctly until more configuration has been done -
enabling RX too soon causes DMA to bad places. KVM corruption problems
reported by Adam Wolk on Lenovo G50-70 (RTL8111GU).
Diff derived by Brad from FreeBSD commit; see bz# 197535 and 193743, inspired by
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d6e572911a4cb2b9fcd1c26a38d5317a3971f2fd
Tested on the following by Brad, Adam Wolk, box963 at gmail, Jim Smith
re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x03: RTL8168D/8111D (0x2800), apic 2 int 16, address 00:0a:cd:1a:86:04
re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address 80:ee:73:76:8e:8a
re0 at pci0 dev 3 function 0 "Realtek 8169" rev 0x10: RTL8110S (0x0400), ivec 0x78c, address 00:22:3f:ee:fa:25
re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:31:2e:88
re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x10: RTL8168GU/8111GU (0x5080), msi, address 68:f7:28:18:35:8e
ok mpi@ dlg@
|
|
|
|
there's no need to do it in m_devget(9).
Stop passing an ``ifp'' will help for upcoming interface pointer -> index
conversion.
While here remove unused ``ifp'' argument from m_clget(9) and kill two
birds^W layer violations in one commit.
ok henning@
|
|
code (that isn't actually compiled in). Use dev_priv->dev in one more place
now that we have it, and add set_normalized_timespec() and use it.
|
|
|
|
|
|
used instead of bus_space_read/bus_space_write.
|
|
better matches linux behaviour
|
|
volume, ignoring any device name specified in the bio(4) ioctl struct.
One of bio(4)'s design flaws is that the device name is hardcoded in many
of the ioctl structs, making it basically unusable with DUIDs. In the case
of `bioctl -d' the bioctl(8) code actually uses opendev(3) on the given
name, then issues the ioctl directly to the resulting device. As such, we
already know which device (or in this case, softraid volume) the ioctl was
intended for, however the current softraid(4) code ignores this and instead
attempts to perform a lookup using the name in the bio(4) ioctl struct.
This diff splits the sr_bio_ioctl() code into two parts - one that implements
the API required by bio(4) and the other that contains the ioctl handling
code, which now takes an optional pointer to the softraid discipline. If an
ioctl is issued to a SCSI device associated with a softraid volume, pass
the corresponding softraid discipline struct through and to the bio ioctl
handler and use it in preference to performing a device name lookup.
Amongst other things, this makes bioctl -d now work with DUIDs.
ok krw@
|
|
ok krw@
|
|
ok mpi@
|
|
|
|
|
|
|
|
|
|
so we can use the inline definition of i915_gem_chipset_flush()
that avoids the flush entirely on gen >= 6.
|
|
A leftover from netbsd
|
|
|
|
Tested by Daniel Jakots, thanks!
|
|
|
|
scheduling.
More work is required to properly budget and schedule micro-frames, most
of it at the HUB level. But this let people use USB1.1 uaudio(4) devices
on ehci(4)-only systems.
Thanks to all the testers!
ok ratchov@, sthen@, naddy@
|
|
and change drm_can_sleep() to only use in_atomic() on i386/amd64 as
it isn't defined for other archs currently. Unbreaks the sparc64 build.
Found the hard way by benoit@
|
|
Patch by Fasse <fasse.f2@gmail.com>
ok mpi@
|
|
ok dlg@
|
|
deal with long delays.
|
|
only ever used to decide between mdelay and drm_msleep and our
drm_msleep delays instead of sleeping.
|
|
|
|
|
|
> fix a regression on re chips which have
> 7k jumbo support (RL_JUMBO_MTU_7K) as reported by daniel jakots
> and emilio perea. the regression was caused because RL_JUMBO_FRAMELEN
> was changed to 9k and i missed fixing up the RL_JUMBO_MTU_7K macro.
nice of him to fix the thing he broke ;)
ok sthen@
|
|
This should help dlg's dell 2950 that gets stuck during boot with vmap
in the trace.
ok kettenis@
|
|
ok dlg@
|
|
ok dlg@
|
|
is set by the user.
previously the address read from the eeprom would also be used in discovery
frames, even if later data frames would contain the spoofed address.
ok stsp@
|
|
|
|
|
|
|
|
kernel_map/uvm_km_valloc and i915 has a version that uses
phys_map/uvm_km_valloc_wait as calling code assumes kmap would
sleep if no memory is available.
Move these and ttm's vmap/vunmap into the linux compat files
and make them all use phys_map/uvm_km_valloc_wait.
looks good kettenis@
|
|
Patch by Kimberley Manning <kmanning at gmx ! com> with some
additional tweaks.
|
|
|
|
The exception being the barrier defines that are implemented in terms of
DRM_* defines.
ok kettenis@
|
|
|
|
|
|
|
|
|
|
|