Re: Unable to build generic kernel on earmv6hf
Brad Spencer <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.arm |
|---|---|
| Message-ID | <[email protected]> |
Martin Husemann <[email protected]> writes: > On Thu, Nov 28, 2024 at 10:50:19AM -0500, Paul Walker wrote: >> There is a movw instruction in sys/crypto/aes/arch/arm/aes_neon_32.S that is >> preventing a build of the generic kernel for armv6. >> >> Is there any reason to use the movw instruction over mov considering it is >> being used to zero r3? > > That question is actually good and I'll leave the answer to others - but > what use is GENERIC for evbearmv6? It is not usually build, only the > RPI and RPI2 kernels. You can use it in qemu and have a system that advertises itself as a v6 system for pkgsrc builds. My qemu v6 system is much faster than any real v6 hardware would be. > I thought everything supporting GENERIC was evbearmv7* ? > > This is no objection to changing the aes_neon_32.S code. I think that there will be other problems... the last time I tried to use arm GENERIC directly as a v6 build target it blew up in linking the kernel.. I have since forgotten why (maybe something in power management??). Lately I just build my GENERIC v6 kernels using the same method RPI2 does.. that is, as a v7 kernel advertising itself as a v6. > Martin -- Brad Spencer - [email protected]