* Compile Penguin PPC for x386?
@ 2001-12-12 21:58 Kent Borg
2001-12-12 19:21 ` Matt Porter
2001-12-13 0:13 ` andrew may
0 siblings, 2 replies; 5+ messages in thread
From: Kent Borg @ 2001-12-12 21:58 UTC (permalink / raw)
To: Embedded Linux PPC List
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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compile Penguin PPC for x386?
2001-12-12 21:58 Compile Penguin PPC for x386? Kent Borg
@ 2001-12-12 19:21 ` Matt Porter
2001-12-20 10:57 ` Marius Groeger
2001-12-13 0:13 ` andrew may
1 sibling, 1 reply; 5+ messages in thread
From: Matt Porter @ 2001-12-12 19:21 UTC (permalink / raw)
To: Kent Borg; +Cc: Embedded Linux PPC List
On Wed, Dec 12, 2001 at 04:58:19PM -0500, Kent Borg wrote:
>
> 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?
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.
mporter@mvista•com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compile Penguin PPC for x386?
2001-12-12 19:21 ` Matt Porter
@ 2001-12-20 10:57 ` Marius Groeger
2001-12-20 11:12 ` Matt Porter
0 siblings, 1 reply; 5+ messages in thread
From: Marius Groeger @ 2001-12-20 10:57 UTC (permalink / raw)
To: linuxppc-embedded
In linux.ppc.embedded, Matt Porter wrote:
>
> 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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compile Penguin PPC for x386?
2001-12-20 10:57 ` Marius Groeger
@ 2001-12-20 11:12 ` Matt Porter
0 siblings, 0 replies; 5+ messages in thread
From: Matt Porter @ 2001-12-20 11:12 UTC (permalink / raw)
To: Marius Groeger; +Cc: linuxppc-embedded
On Thu, Dec 20, 2001 at 11:57:16AM +0100, Marius Groeger wrote:
>
> In linux.ppc.embedded, Matt Porter wrote:
> >
> > 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.
mporter@mvista•com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Compile Penguin PPC for x386?
2001-12-12 21:58 Compile Penguin PPC for x386? Kent Borg
2001-12-12 19:21 ` Matt Porter
@ 2001-12-13 0:13 ` andrew may
1 sibling, 0 replies; 5+ messages in thread
From: andrew may @ 2001-12-13 0:13 UTC (permalink / raw)
To: Kent Borg; +Cc: Embedded Linux PPC List
On Wed, Dec 12, 2001 at 04:58:19PM -0500, Kent Borg wrote:
> 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/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-12-20 11:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-12-12 21:58 Compile Penguin PPC for x386? Kent Borg
2001-12-12 19:21 ` Matt Porter
2001-12-20 10:57 ` Marius Groeger
2001-12-20 11:12 ` Matt Porter
2001-12-13 0:13 ` andrew may
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox