On Fri, Jan 29, 2021 at 02:11:00PM +0200, Adrian Bunk wrote: > > But this a bug in the CPU, right? Do I understand correctly that the > > package can fail depending on what CPU it is run on regardless of how > > it was built? > > > > I'm trying to understand what we can do in WebKit in order to fix or > > work around this. > > It is a bug in WebKit that a kernel configuration is assumed that is > not even permitted on Loongson: > https://sources.debian.org/src/webkit2gtk/2.31.1-1/Source/WTF/wtf/PageBlock.h/#L54 > https://sources.debian.org/src/linux/5.10.9-1/arch/mips/Kconfig/#L2213-L2215
My question is: I cannot choose a page size depending on the particular MIPS CPU model because once the package is built it could be run on a CPU with a different page size, is that right? If that's the case then I should use a conservative value that is guaranteed to work on all models (64KB, or is 16KB safe?). > BTW: The 4kB setting for arm64 is also questionable, Ubuntu releases > now additionally ship kernels with 64 kB page size: > > https://launchpad.net/ubuntu/groovy/+package/linux-image-unsigned-5.8.0-41-generic-64k Ok, I'll use 64KB then. Berto
