Re: [PATCH v3] crypto: aes - Fix undesired override of some optimized AES modes
From: Stian Halseth
Date: Wed Sep 30 2026 - 10:57:07 EST
Hi Adrian,
On Wed, 2026-09-30 at 11:27 +0200, John Paul Adrian Glaubitz wrote:
>
>
> > The T2 and T3 has a separate crypto unit, but not supported here.
> > Support was removed from the kernel in 6.14. Haven't tested it, as
> > I
> > don't have the hardware.
>
> Why was it removed? I'm not happy about such removals as long as the
> hardware is supported.
Looks like there were issues that prompted the removal:
https://github.com/torvalds/linux/commit/9cda46babdfe
>
> > Also worth noting, it's only used when the firmware lists the
> > machine
> > description's hwcap-list and the CFR has its bit set.
>
> Is that not the case by default?
Yes, on real hardware. Just mentioned to clarify that it doesn't cause
problems on hardware that doesn't support it.
> > I have no idea about Fujitsu's SPARC64 X family.
>
> I think SPARC64 X is not supported by the Linux kernel at all, is it?
>
There some chip detection for it, but I've never tested, or heard about
anyone actually using it.
sparc64: correctly recognize SPARC64-X chips
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76950e6e54ccfc98a25b501dbb1bc879cce1aa29
cpu hw caps support for sparc64x:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e96377983d2e060dd89703f1846ad920af9e17f
Attachment:
signature.asc
Description: This is a digitally signed message part