| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
them going negative - this consists of identifying a number of cases of
IO not going through the buffer cache and marking those buffers with
B_RAW - as well as fixing nfs_bio to show pending writes and reads through
the buffer cache via NFS
still has a problem with mishandling the counters I believe in the
async/sync fallback case where counters stay positive which will be
addressed seperately.
ok tedu@ deraadt@
|
|
uvideo_vs_parse_desc_frame_uncompressed().
- If a VS alternate interface isn't valid (e.g. doesn't contain a
UE_ISOCHRONOUS endpoint), abort attachment with a corresponding error
message instead crashing the kernel.
Tested and OK maja@
|
|
|
|
|
|
|
|
|
|
marco@ ok.
|
|
up as this (we love standards). To make those devices attach anyway
we add an explicit quirk device list. Of course this list still needs
to be extended.
Thanks to Jerome Pinot for reporting about this issue and testing this
diff with his cam, which is such a device.
OK yuo@
|
|
|
|
|
|
users.
Thanks to mpf@ for his help to debug this bug down.
|
|
|
|
import some fixes for 1T2R adapters from the linux vendor driver.
|
|
pass a pointer to an ieee80211_rxinfo structure containing those two
fields plus an extra flags field that indicates whether the frame was
decrypted by hardware or not.
required for a future fix.
|
|
Noticed by todd, proded by miod.
|
|
ok jsg@
|
|
pretty-print the UUID in RFC4122 form
|
|
been initialized by the firmware. This was probably the intention of the
origional code, however, it used the wrong default value for the register
in question.
Add TI PCI1510 to the list of 12XX-compatible bridges.
"be brave" deraadt@
|
|
This patch moves these device to umsm(4).
reported by Aleksander Piotrowski, ok jsg@
|
|
|
|
that caused illegal checksums. The new metadata code is more or less ready
to deal with other vendor's metadata formats.
While here clean up the name space.
Fix thib's pool mess by adding removing bad flags in interrupt context.
tested on macppc, amd64, i386, sparc64 & hppa
sparc64 has issues with crypto however those do not seem to be softraid
specific.
help from okan@ ckuethe@ Will Backman and others
|
|
VIDEO_S_FMT doesn't exactly match the devices available resolutions,
return the next best matching resolution which we have.
Makes some V4L2 apps happy when running them with the default resolution
(no options).
|
|
|
|
asking for (GET_CUR) directly. This gets us better negotation values.
|
|
set their desired image size, and therefore users can manipulate the
image size, too via the application.
Also tested by brad@
|
|
o On non-strict alignment archs, dont copy the mbuf, every time, unload it, and send
it up the stack and just get a new one for the rx ring. We still do the copy on
strict alignment archs though...
o create a function to handle mbuf allocation for the rx ring, vr_mbuf_alloc(),
use it to allocate the mbufs and shuffle the bus dma setup around.
ideas/code from vic(4) and sis(4);
ok reyk@, brad@, dlg@
tested by many, been in snapshots for a while.
|
|
chipset revision is not supported yet, so add it commented out.
|
|
|
|
|
|
until I have time to implement proper fix.
Noted by several folks.
|
|
halfway through. Makes the ISP12160 correctly load its firmware again on
sparc64.
ok krw@
|
|
slightly different from the other chipsets using the BCM5705 ASIC.
ok jsg@
|
|
ok deraadt@
|
|
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@
|
|
For now, only one such flag is defined, PCKBC_CANT_TRANSLATE. It hints
pckbc that the device does not behave correctly to the ``set translation''
commands.
Set this flag if we are running on a Tadpole Ultrabook machine, which needs it.
This makes the built-in keyboard work correctly on this laptop (with the
help of the software translation pckbd diff).
tested & ok kettenis@
|
|
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).
If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.
ok kettenis@
|
|
|
|
mode (4KB) for PCIe chips. This resolves the poor TX performance for
the PCIe chips. The result being a bit under double the TX performance
on a Gig connection (roughly 495 Mb/s -> 940 Mb/s).
Tested by reyk@, sthen@, brad@ and a few end users.
|
|
address 0x1a and 0x1e, and that's not where the PCIe capability stuff
lives. Potentially it was mucking with an IO BAR (super dangerous).
But probably it was achieving nothing at all.
ok dlg@, marco@, brad@
|
|
Pointed out by Chris Cappuccio, thanks!
|
|
newer PCI Express adapters (ie 8168C*/8102*) work.
V2 Checksum offload format in RTL8102 devices not yet supported.
No objections from brad@. Thanks to everyone who tested.
|
|
sis_newbuf(), so remove the call.
ok and lots of prodding dlg@, brad@
|
|
|
|
|
|
|
|
can use them later for stuff like VIDIOC_S_FMT (e.g. set custom
resolution).
|
|
upcoming changes and sort list.
|
|
ok dlg
|
