Changeset View
Changeset View
Standalone View
Standalone View
website/content/en/releases/13.0R/relnotes.adoc
Context not available. | |||||
A new man:usbhid[4] driver has been added, and can be loaded by adding `hw.usb.usbhid.enable=1` to [.filename]#/boot/loader.conf# and adding `usbhid` to `kld_list=""` in [.filename]#/etc/rc.conf#. gitref:b62f6dfaed3d[repository=src] | A new man:usbhid[4] driver has been added, and can be loaded by adding `hw.usb.usbhid.enable=1` to [.filename]#/boot/loader.conf# and adding `usbhid` to `kld_list=""` in [.filename]#/etc/rc.conf#. gitref:b62f6dfaed3d[repository=src] | ||||
=== Cryptography Acceleration | |||||
With man:aesni[4] now included in the GENERIC kernel, users may see their cryptography acceleration reported differently. Until 12.2-RELEASE, loading the man:aesni[4] module and using man:geli[8] registered AES-NI-enabled mainline CPUs as "GEOM_ELI: Crypto: hardware". Many of these CPUs will now show "GEOM_ELI: Crypto: accelerated software". This is simply a change in identification, and does not mean there is reduced support or less efficient encryption. | |||||
[[storage]] | [[storage]] | ||||
== Storage | == Storage | ||||
Context not available. | |||||
jhb: The new comment is related to this commit, not with adding aesni(4) to GENERIC. However, I… | |||||
Not Done Inline ActionsI'd suggest explicitly mentioning that this doesn't imply reduced support. Both on the Forums and on IRC, users have asked whether cryptography will be slower for them with the new identification. I understand it's implied in this minimal phrasing that it won't be, but a little more verbosity couldn't hurt to avoid further questions. freebsd_michael-bueker.de: I'd suggest explicitly mentioning that this doesn't imply reduced support. Both on the Forums… | |||||
Not Done Inline ActionsAgreed, bringing in your last sentence from below would suit that. jhb: Agreed, bringing in your last sentence from below would suit that. |
The new comment is related to this commit, not with adding aesni(4) to GENERIC. However, I would probably instead add an entirely new entry referencing commit a3d565a1188f, something like: