Skip to contentSkip to conversation

Compile Penguin PPC for x386?

DISCUSSION Kent Borg 4 participants 5 messages Dec 12, 2001 – Dec 20, 2001

lore
Share & tools
lore
#1 lore raw
In reply to Kent Borg
Quoted 13 lines · Kent Borg

Is the i386 arch vaguely up to date in the PPC tree? Does it work?

I mean, if I want to debug some driver that doesn't need actual hardware (maybe dummy out actual HW banging), can I swap over to building an i386 kernel? It would be nice to be using the same kernel.

If I can do that, how? In Makefile I changed "ARCH" to i386, changed "CROSS_COMPILE" to be nothing, did a "make mrproper", copied in a .config from my Red Hat install, defaulted everything asked by "make oldconfig", did "make dep", and "make bzImage".

Quoted 4 lines

But then it chokes on some problem in include/linux/highmem.h (48:
parse error before `0').

Should this work?

No, the PPC MM changes in 2_4_devel rely on changes to the generic MM API that aren't yet in the kernel.org release. You could modify the appropriate files in arch/i386/mm/ and include/asm-i386/ to match if you like.

--
Matt Porter
MontaVista Software, Inc.
[email protected]

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Kent Borg

author
#0 lore raw

Is the i386 arch vaguely up to date in the PPC tree? Does it work?

I mean, if I want to debug some driver that doesn't need actual hardware (maybe dummy out actual HW banging), can I swap over to building an i386 kernel? It would be nice to be using the same kernel.

If I can do that, how? In Makefile I changed "ARCH" to i386, changed "CROSS_COMPILE" to be nothing, did a "make mrproper", copied in a .config from my Red Hat install, defaulted everything asked by "make oldconfig", did "make dep", and "make bzImage".

But then it chokes on some problem in include/linux/highmem.h (48:
parse error before `0').

Should this work?

Thanks,

-kb

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#4 lore raw
Quoted 2 lines · Kent Borg

But then it chokes on some problem in include/linux/highmem.h (48:
parse error before `0').

We use to just pull out the section in the ifndef and things would work on the 386, but then at some point the 386 kernel would just hang. I have not been doing any builds recently so I have no idea how things are going now.

#ifndef __HAVE_ARCH_USER_PAGE

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#2 lore raw
In reply to Matt Porter
Quoted 5 lines · Matt Porter

No, the PPC MM changes in 2_4_devel rely on changes to the generic MM API that aren't yet in the kernel.org release. You could modify the appropriate files in arch/i386/mm/ and include/asm-i386/ to match if you like.

Matt, do you know the origin of those changes? Are they an invention of the linuxppc people, or part of the 2.5 tree? I'm asking because I'm afraid that these changes might not make it into kernel.org release for a LONG time...

--

Marius Groeger        SYSGO Real-Time Solutions GmbH    www.sysgo.de
Software Engineering  Embedded and Real-Time Software   www.osek.de
mgroeger @ sysgo de   Germany                           www.elinos.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#3 lore raw
Quoted 11 lines · Marius Groeger
Quoted 5 lines · Matt Porter

No, the PPC MM changes in 2_4_devel rely on changes to the generic MM API that aren't yet in the kernel.org release. You could modify the appropriate files in arch/i386/mm/ and include/asm-i386/ to match if you like.

Matt, do you know the origin of those changes? Are they an invention of the linuxppc people, or part of the 2.5 tree? I'm asking because I'm afraid that these changes might not make it into kernel.org release for a LONG time...

Ask Paulus about the status of them being included. My understanding is that he has been working with the appropriate parties (i.e. Linus and co) on these changes.

If you want something that closely tracks kernel.org then use linuxppc_2_4. A merge of most of the "new" ports from linuxppc_2_4_devel is planned now that organizational changes are settling down.

--
Matt Porter
MontaVista Software, Inc.
[email protected]

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/