Re: [5.16.0] build error on unrecognized opcode: ptesync

2022-01-17 Thread Mike
It booted at least. I'll try your suggestions as soon as I can, I'm progressing slower than ever, concentration is somewhat lapse still Thanks. Best regards Michael On Tue, Jan 11, 2022, 10:51 Christophe Leroy wrote: > > > Le 11/01/2022 à 10:32, Mike a écrit : > > I managed to fix it in

Re: [5.16.0] build error on unrecognized opcode: ptesync

2022-01-12 Thread Mike
Hmm, why on earth did it historically compile though, from what I gathered before my hand fell off, -maltivec was removed from arch/powerpc/mm, I ran out of hard drive compiling ofc. but it seems happy, >Also please prefer CONFIG_PPC64 to __powerpc64__ Copy pasted the style in of the file... I

Re: [5.16.0] build error on unrecognized opcode: ptesync

2022-01-11 Thread Christophe Leroy
Le 11/01/2022 à 10:32, Mike a écrit : > I managed to fix it in the end, patch attached, though i should have > done a $(call cc-option-, -maltivec, -mabi=altivec) in the > arch/powerpc/mm/Makefile > I wrongly assumed that the manual i had downloaded at 4.44am was for > 32bit ppc only and found

Re: [5.16.0] build error on unrecognized opcode: ptesync

2022-01-10 Thread Christophe Leroy
Le 10/01/2022 à 13:32, Mike a écrit : > Hey, so I originally sat down to compile the fast headers V2 patch, but > quickly discovered other things at play, and grabbed 5.16.0 a few hours > after it lifted off,  arch/powerpc/mm/mmu_context.c I had to > specifically say had to include -maltivec

[5.16.0] build error on unrecognized opcode: ptesync

2022-01-10 Thread Mike
Hey, so I originally sat down to compile the fast headers V2 patch, but quickly discovered other things at play, and grabbed 5.16.0 a few hours after it lifted off, arch/powerpc/mm/mmu_context.c I had to specifically say had to include -maltivec or it barfed on a 'dssall', I'm fine with that,