Age | Commit message (Collapse) | Author |
|
fixed values for the divisors, but the imxesdhc(4) nodes for
SD Cards usually have an assigned clock rate of 200 MHz instead of
400 MHz. So instead of just clearing the divisor, we should set it
according to what is asked. This also allows us to add the clock
for the second imxesdhc(4) node to the list, which I have previously
skipped, since otherwise the controller would have been clocked too
high.
ok kettenis@
|
|
'key->pol_proposals' should be the peer proposal as it is derived from
a received SA payload, 'p->p_proposal' comes from a locally configured
policy.
ok patrick@
|
|
those are already on, since on those machines we mostly boot from SD/MMC
and U-Boot prepares them for us. On machines with a WiFi on imxesdhc(4),
U-Boot isn't necessarily configured to do so. Enabling the clocks is the
right thing to do anyway.
ok kettenis@
|
|
imxesdhc(4) device tree nodes.
|
|
issue a usage message. This matches both historical behaviour, and
the operation upon other keywords.
ok florian
|
|
groups are not recommended to use and are only supported for backwards
compatibility.
Feedback from sthen@
ok kn@
|
|
more readable.
|
|
|
|
comments.
ok claudio job
|
|
feedback and okay schwarze@
|
|
of boot floppies from the INSTALL.alpha notes.
ok deraadt@
|
|
and move it to the end of machdep.c. Rework the actual implementation
for te MC14818 compatible RTC into something that can be used as a todr_handle.
ok mpi@
|
|
and move it to the end of machdep.o.
ok mpi@
|
|
|
|
From Vitaliy Makkoveev, ok visa@
|
|
ok kevlo@ mpi@
|
|
|
|
|
|
middleware layer rather than in ssh code. This allows middlewares that
call APIs that perform the hashing implicitly (including Microsoft's
AFAIK). ok markus@
|
|
|
|
Because for now, the maximum raw value of such controls is either
127 or 255, that assures that whenever the raw value changes, the
displayed value changes, too. At the same time, it preserves the
property that control values are not shown with excessive, misleading
precision.
If controls will ever be introduced that will have maximum raw
values of less than 100 or of more than 999, the number of decimal
places should then be reduced or increased for such controls as
appropriate.
With important help and an OK from ratchov@.
|
|
|
|
|
|
A Type-C controller has multiple tasks. Even though the orientation
of the plug doesn't matter for the user, it matters for the hardware.
To be able to know how to route the SuperSpeed pins you need to know
which way the plug is connected. Also you need to know if you're a
sink/source or device/host. To get the first connection, you toggle
between the modes until you find a connection. In case you see that
a sink is connected, you can turn on USB Vbus to power the sink.
This driver explicitly does not implement USB's Type-C state machine,
but if we get more and more of these controllers it might be worth
doing. Also there's no support for Power Delivery messages yet.
"go for it" kettenis@
|
|
can't be enabled.
|
|
to i.MX27, they actually need different bits to be set than the i.MX27.
The i.MX8MM's node instead rightfully only claims to be compatible to
i.MX7D, since it's the same implementation. Thus change imxehci(4) to
also match the i.MX7D compatible.
ok kettenis@
|
|
Move functions so that they are in the order that the TLSv1.3 messages are
processed. While here, also move tls13_client_end_of_early_data_send() from
tls13_client.c to tls13_server.c.
No functional change.
ok beck@ tb@
|
|
perfectly happy without it.
ok patrick@
|
|
instead of hardcoding the values.
Tested on a Cubox-i by kettenis@
ok kettenis@
|
|
controller and its nop-PHYs. This is needed on the i.MX8MM.
ok kettenis@
|
|
1. Use the correct slice for comparing the cipher output
2. Fix logic error similar to the one in AES-GCM in the previous commit
|
|
This issue was fixed in lib/libcrypto/evp/e_aes.c r1.40.
|
|
EVP_AEAD_CTX_{open,seal}, as this leaks the authentication key.
Issue reported and fix tested by Guido Vranken.
ok beck, jsing
This commit adds a constant to a public header despite library lock,
as discussed with deraadt and sthen.
|
|
|
|
not USB_CORE_REF.
|
|
stop trying to get an ACK from that server after 'timeout'
seconds. Give up and try to get another lease.
Possible infinite loop pointed out by Alexander Markert on tech@.
|
|
|
|
arrm32_machdep.c.
ok mpi@
|
|
implementation.
ok mpi@
|
|
binding uses. Remove warning about overwriting todr_handle since that is
normal behaviour on arm64 systems.
ok sthen@
|
|
time if the flag is set. Instead clear the flag when we set the time.
This way we don't use the clock time if the oscillator has been interrupted.
This happens for example when the battery is dead.
ok sthen@
|
|
come up. This apparently happens when there's no card in the PCIe slot.
Thus improve the error handling in all cases where we wait for a link to
come up, return and don't proceed any further.
ok kettenis@
|
|
that aren't claimed by kernel drivers can be used from userland.
ok sthen@
|
|
ok kettenis@
|
|
ok kettenis@
|
|
Input from sthen@, ok claudio@
|
|
packet headers, rather than the headers inside any of the tunnel protocols
the nic firmware understands. This allows us to receive gre, ipip, mpls,
etc. packets without putting the interface in promisc mode.
ok dlg@
|
|
needed for printing the exit messages. Fixes a bug when detaching with
iTerm2.
|
|
This reduces CPU load during traffic bursts, which is especially noticeable
on boards with relatively slow CPUs such as Alix and APU. For reference,
my rcc-ve boards (Intel Atom C2558) now forward ~2000pps between Ethernet
and wifi with <= 1% CPU interrupt time according to systat. Beforehand, these
boards became noticeably less responsive with fairly high interrupt and spin %.
CCMP offload is used on both PCI and USB devices (thanks kevlo@ for catching
my omission of USB devices in the first iteration of this change!)
Tested by (at least) Kevin Chadwick, tracey@, kevlo@, kili@, Ted Patterson,
David Dahlberg, and Scott Bennett.
ok tracey@ kevlo@
|
|
Fix wrong assumptions about what the data in these notifications is supposed
to represent, and actually piece information about individual subframes of
aggregated frames (A-MPDUs) back together when reporting to MiRA, rather than
reporting unrelated subframes to MiRA individually.
Testing by cwen@, Josh Grosse, f.holop, benno@
ok jmatthew@
|