going to toss the packet anyway?
…s the packet: fix a but introduced in rev 1.20.
…ced in rev 1.54.
Do not use Giant for kbdmux(4) locking. This is wrong and apparently causing more problems than it solves. This will re-open the issue where interrupt handlers may race with kbdmux(4) in polling mode. Typical symptoms include (but not limited to) duplicated and/or missing characters when low level console functions (such as gets) are used while interrupts are enabled (for example geli password prompt, mountroot prompt etc.) MFC after: 3 days
Most compilers nowadays (including GCC) are smart enough to know what's going on and generate more efficient code anyway. Submitted by: Christoph Mallon <firstname.lastname@example.org>
Approved by: julian (mentor)
frames passed down through the transmit path o mark ndis requiring 802.3 encap'd frames Reviewed by: "Paul B. Mahol" <email@example.com>, thompsa
are more commonly known as BSD partition names. Discussed with: ivoras@
It turns out my handling of SIGTTOU and SIGTTIN didn't entirely comply to the standards. It is true that in the SIGTTOU case we should not return EIO when the signal is ignored/blocked, but in the SIGTTIN case we must. See also: POSIX issue 7 section 11.1.4
above to avoid referencing undefined terms (humans are not compilers but still care about these things). Change some .Sh to .Ss to better reflect the structure of the text. No new content.
…rk on ARM. Submitted by: Grzegorz Bernacki gjb ! semihalf dot com
a pointer to the ip header. -style -spacing
machine-specific flags to match but ar5523.bin doesn't have. Pointed by: marcel
(framing, parity, etc), but does not indicate characters being received. Since no chracters have been received, ignore the line errors. PR: 131006 MFC after: 3 days
- 1000BaseSX - 2500BaseSX While I'm there, correct 1000BaseTX as more standard 1000BaseT. MFC after: 3 days