summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* update remaining usb.org URLssthen2021-01-294-12/+12
|
* update usb.org URLssthen2021-01-293-7/+7
|
* update some usb.org URLs following reorganisation, add a new one for updsthen2021-01-296-13/+15
| | | | partly from Alessandro Ricci
* Adjust for disabling gcc on macppc.kettenis2021-01-292-609/+0
|
* Stop building gcc on macppc.kettenis2021-01-291-3/+2
| | | | ok cwen@, deraadt@
* repair declerations to satisfy -fno-commonderaadt2021-01-293-19/+4
| | | | ok kettenis
* be more forceful about FULLPKGPATHespie2021-01-291-3/+8
|
* Don't rely on USB interfaces being at compliant indices.edd2021-01-291-5/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When obtaining an interface handle, we currently rely on the device being properly USB compliant, and thus the interface being at the correct index in the interfaces array. However, some devices present their indices incorrectly. For example, the following audio device exposes interfaces 0, 1 and 3, in that order (skipping interface 2 entirely): uaudio2 at uhub4 port 4 configuration 1 interface 3 "E+ Corp. DAC Audio" rev 1.10/0.01 addr 2 uaudio2: class v1, full-speed, async, channels: 2 play, 0 rec, 3 ctls This means that that the audio stream interface (number 3) is not found at the expected index of 2, and this causes looking up the handle to fail. This change makes usbd_device2interface_handle() search for the right interface, instead of assuming it will be at the right index. Although this is a little slower, note that this routine not very frequently called and there are typically not hundreds of interfaces on a typical USB device. This fixes the above E+ Corp device, and one other uaudio device reported broken by a user. With input from, tested by, and OK ratchov@, mglocker@ and kettenis@. Many thanks!
* Make audio clients use struct opt to reach the deviceratchov2021-01-293-46/+46
| | | | | No behavior change. This decreases the number of explicit references to the dev structure
* Make control clients use struct opt to reach the deviceratchov2021-01-293-18/+21
| | | | | No behavior change. This decreases the number of explicit references to the dev structure.
* Rename ctlslot->mask to ctlslot->self to match the rest of the coderatchov2021-01-293-10/+10
| | | | No binary change.
* Order opt_list in opt_new() call order, limit items to OPT_NMAXratchov2021-01-292-13/+25
| | | | No behavior change, except for improved debug printfs.
* Move the options list out of the device structureratchov2021-01-295-27/+33
| | | | | No behavior change. Later this will ease applying the configuration of one device to another by "just" swapping pointers.
* Move the control client state out of the device structureratchov2021-01-293-18/+18
| | | | | No behavior change. Later this will ease changing the controlled device by "just" swapping pointers.
* Move the audio clients state out of the device structureratchov2021-01-294-46/+69
| | | | | No behavior change. Later this will ease moving clients from one device to another by "just" swapping pointers.
* Use NULL instead of 0 to clear v_socket pointer (which actually clears allclaudio2021-01-291-2/+2
| | | | | of the v_un pointers). OK jsg@ mvs@
* Adjust regress test, the hash argument to the parse functions was removed.claudio2021-01-292-4/+4
|
* A while ago rpki-client was changed to validate the sha256 hashes ofclaudio2021-01-298-180/+41
| | | | | | | | | | files referenced in MFT files during the validation of the MFT file. An MFT is only valid if all files are present and their hashes are valid. Because of this there is no longer the need to check the hash when these files are parsed later on. Remove these checks for CRT, ROA and CRL files. Use the presence of the pkey when parsing cert files to decide if it is a root cert or not. OK tb@
* Trim output overwritten by later text or clears completely rather thannicm2021-01-294-213/+234
| | | | | only in a few cases. This means we can better track when a line should wrap. GitHub issue 2537.
* recognise Cortex-A78Cjsg2021-01-291-1/+3
|
* fix the values of enum sock_typedjm2021-01-291-4/+4
|
* give typedef'd struct a struct name; makes the fuzzer I'm writing a bitdjm2021-01-291-2/+2
| | | | easier
* Whitespace.rob2021-01-291-3/+2
|
* Remove print_{debug,verbose} since they're currently unused and I see nomartijn2021-01-282-28/+2
| | | | | | reason to start using them in the future. OK tb@
* bridge(4): convert ifunit() to if_unit(9)mvs2021-01-282-16/+38
| | | | ok bluhm@ sashan@
* trunk(4): convert ifunit to if_unit(9)mvs2021-01-281-9/+21
| | | | ok bluhm@
* Add '$' to ober_scanf_elements().martijn2021-01-282-4/+13
| | | | | | | | This allows us to enforce end of sequence/set without having to manually check be_next for NULL. No lib bump needed according to millert@ OK millert@ rob@
* bios_memmap[] should not be a commonderaadt2021-01-282-3/+4
| | | | ok kettenis
* Remove direct assignment of aead_ctx.jsing2021-01-281-13/+7
| | | | | | Now that AEAD is handled internally, we should no longer be assigning aead_ctx directly, as this will result in a leak. Missed during the previous change.
* Add ldap(1) to the SEE ALSO section. OK deraadt@millert2021-01-281-2/+3
|
* Again allow COPTS= to come from the environment again, and don't lose thederaadt2021-01-2814-56/+56
| | | | | SMALL_KERNEL specific variations. ok espie jsg
* tpm(4): fix delay unitscheloha2021-01-281-18/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tpm(4) has timeout constants in milliseconds, e.g. #define TPM_ACCESS_TMO 2000 /* 2sec */ This is fine. The odd thing is that tpm(4) first converts these timeouts to counts of ticks via tpm_tmotohz() before using DELAY() to busy-wait. DELAY() takes a count of microseconds, which are not equivalent to ticks, so the units are all screwed up. Let's correct this: - Remove tpm_tmotohz(). We're not working with ticks so we don't it. - Multiply the timeouts to match the delay interval. tpm_request_locality() and tpm_getburst() use intervals of 10 microseconds, so multiply the millisecond timeouts by 100. In tpm_waitfor() the delay interval is 1 microsecond, so multiply the millisecond timeout by 1000. - Update the parameter name in tpm_waitfor() to note that we expect a count of milliseconds, not "tries". Discussion: https://marc.info/?l=openbsd-tech&m=160995671326406&w=2 Prompted by kettenis@. Suspend/resume tested by florian@ on an X1 Gen 2. For the record, it looks like this: tpm0 at acpi0 TPM_ addr 0xfed40000/0x5000, device 0x0000104a rev 0x4e Earlier versions of this patch were reviewed by kn@, but the patch became more ambitious when kettenis@ got involved so those reviews are no longer applicable. jcs@ notes (https://marc.info/?l=openbsd-tech&m=160834427630142&w=2) in a related discussion that this driver "sucks" and should be replaced with NetBSD's rewrite. This would get us a cleaner driver with TPM 2.0 support. So there is future work to do here. ok kettenis@
* Move AEAD handling into the new TLSv1.2 record layer.jsing2021-01-284-134/+102
| | | | ok tb@
* Show when witness(4) has run out of lock order data entries.visa2021-01-281-2/+14
| | | | | | This makes it clearer why lock order traces are sometimes not displayed. Prompted by a question from, and OK anton@
* Drop tcp_trace() from SMALL_KERNEL builds to make room on amd64 floppyvisa2021-01-282-3/+13
| | | | OK deraadt@
* Be consistent in not using parameter names for function prototypes;mglocker2021-01-281-3/+3
| | | | I've missed two more cases in the previous commit.
* When an audio device is disconnected, drop MIDI clients controlling itratchov2021-01-284-24/+28
|
* Dont attempt to drain disconnected clientsratchov2021-01-283-9/+10
| | | | | | | | | | Clients are always drained before they disconnect, so this change affects programs that die unexpectedly or loose thier network connection. Besides the bad style, this change fixes a theoretical bug when the disconnected client slot could be recycled and given to another client while it's being drained
* In slot_xxx(), store dev pointer in local variableratchov2021-01-281-16/+9
| | | | | | This removes many redundant dereferences to obtain the dev pointer from the slot stucture and makes the source slightly more readable. No behavior change.
* Use everywhere the same pattern to handle fractional clock ticksratchov2021-01-281-3/+9
| | | | | No behavior change; this change is only to make the maths easier to proofread
* Make slot_{attach,detach}() the opposite of each otherratchov2021-01-281-16/+56
| | | | | | | No bahavior change. Now, slot_attach() moves slot's clock forward and puts the slot on device list; slot_detach() does the opposite: remove from device list and move clock backwards. This will allow to detach a client and attach it later in exactly the same state.
* Drop unused dev_nctl() function and few unused prototypesratchov2021-01-282-19/+5
|
* handle "once" rules before letting pfsync defer tx of a packet.dlg2021-01-281-15/+15
| | | | | | | | | | | | | pfsync may want to defer the transmission of a packet. it does this so it can try and get a state over to a peer firewall before a host may send a reply to the peer, which would get dropped cos there's no matching state. i think the once rule processing should happen before that. the state is created from the rule, whether the packet the state is for goes out immediately or not shouldn't matter. ok sashan@
* A new resolver can be created while we currently run a check with theflorian2021-01-281-3/+7
| | | | | | | | | old configuration. We will then request another check that runs in parallel to the old check. If the new check finishes earlier, the current check result will be overwritten by an outdated check result which is likely wrong. While here fix some whitespace. OK phessler
* Rename bNumInterface to bNumInterfaces to fix build on arm64.kurt2021-01-281-2/+2
|
* Extern dwarf2_loc_mark_labels. Fixes compiation with -fno-common.mortimer2021-01-281-1/+1
| | | | ok deraadt@
* Explicitly enable -fcommon, rather than untangle common symbols.mortimer2021-01-281-1/+2
| | | | ok deraadt@
* Extern privsep_process. Fixes compilation with -fno-common.mortimer2021-01-282-3/+5
| | | | ok deraadt@
* Extern transport_list. Fixed compilation with -fno-common.mortimer2021-01-282-3/+6
| | | | ok deraadt@
* if the route resolved in pf_route is invalid, generate an icmp error.dlg2021-01-271-1/+10
| | | | | | of course this is limited to the !dup-to case. ok sashan@ bluhm@