Section 2.4.3 of the UVC 1.5 class specification states that the bulk
endpoint only supports the alternative setting of zero, which is the
default stream, and which is switched at uvideo_attach_hook.
Inside uvideo_vs_close, the code uses the same switch to the alternative
setting of zero to turn off the cam LED.
The additional uvideo_vs_set_alt inside uvideo_vs_open turns off the cam
LED in the case of the bulk endpoint cam. I see this behavior on both
available bulk endpoint cams: it flashes the LED flashes after ffplay
starts, and looks like it was turned off.
OK mglocker@ kn@
This extends the maximum message size of BGP from 4096 to 65535.
This mostly follows rfc8654 with the following differences:
- NOTIFICATIONS are always truncated to fit in 4096 bytes.
- There is no message reduction using "attribute discard" in case of overflow.
- Large messages are only sent if both sides announced extended message support.
OK tb@
removal of shadow timer, cookie configuration, updates to WMI and
start of updates for buffer handling. This brings us forward:
qwz0: wcn7850 hw2.0 fw 0x100301e1 address xx:xx:xx:xx:xx:xx
qwz_dp_htt_htc_t2h_msg_handler: htt event 48 not handled
regdb, which the firmware did not like. This adjusts the way we load
and cache FW, and places the right data for the chip. This allows the
WLAN FW to boot up properly.
and document them properly in their own manual page, including the control
commands EVP_CTRL_SET_RC2_KEY_BITS and EVP_CTRL_GET_RC2_KEY_BITS that were
so far undocumented.
Arguably, the main benefit is another small step making the important,
but still obese EVP_EncryptInit(3) manual page more palatable.
range of DeviceIDs we can set up for translation.
Peripherals capable of doing DMA/MSIs are supposed to show up with
unique DeviceIDs. The Device Table maps the DeviceID to a Interrupt
Translation Table. So far we only used a single contiguous block for
the Device Table, but on some machines this does not cover the whole
range of physical devices. Using the GIC's indirect mode allows to
move to a two-level setup to increase the range.
ok kettenis@
agintcmsi(4) from attaching in this case such that an upcoming change
to make it work (with DTB) on this hardware doesn't break the initial
install.
ok patrick@
Without usbd_get_xfer_status the code is built on the assumption that
usbd_transfer always reads dwMaxPayloadTransferSize bytes from a device.
If this assumption doesn't hold, it produces broken frames which has
unexpected zeros.
OK mglocker@ kn@
This refactors the wNAF multiplication further and introduces a small API
that manages the wNAF digits for bn and the multiples of digit * point in
a single struct that is initialized and freed in two API calls in the main
function, ec_wNAF_mul(). This way the main algorithm is no longer cluttered
with logic to keep various arrays in sync, helper functions calculating the
wNAF splitting of bn and multiples of the point do not need to deal with
memory management, and a pair of accessors obviates previously missing
bounds checking.
At this point we have reached a relatively clean and straightforward wNAF
implementation that fits precisely the purpose needed in libcrypto, i.e.,
ECDSA verification instead of being generalized and optimized to the max
for no good reason apart from endowing the author with an academic degree.
Popper's famous maxim "if you can't say it clearly, keep quiet, and keep
working until you can" very much applies to code as well. In other words,
shut up and hack (and don't pour too much energy into commit messages, tb).
ok jsing
because tb@ deleted almost all functions documented there from the API
in evp.h 1.127 on March 2 this year, but move the functions
EVP_PKEY_CTX_set_data(3) and EVP_PKEY_CTX_get_data(3) that we still
support to EVP_PKEY_keygen(3), because that page already documents
EVP_PKEY_CTX_set_app_data(3) and EVP_PKEY_CTX_get_app_data(3).
This provides a SHA-1 assembly implementation for amd64, which uses
the Intel SHA Extensions (aka SHA New Instructions or SHA-NI). This
provides a 2-2.5x performance gain on some Intel CPUs and many AMD CPUs.
ok tb@
It's so non-obvious that even i had to do some research to find out.
Source: The file "doc/ssleay.doc" from SSLeay 0.8.1b,
see for example OpenSSL commit d02b48c6 on Dec 21, 1998.