linux-kernel - Building ppc/powerpc kernel to run under QEMU.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 May 2007 18:39:55 -0400
From:	Rob Landley <rob@...dley.net>
To:	linux-kernel@...r.kernel.org
Subject: Building ppc/powerpc kernel to run under QEMU.

Who do I ask about the status of the migration from ARCH=ppc to ARCH=powerpc?

I've been putting around with my Firmware Linux project trying to add powerpc 
as a supported platform.  I can build kernels that qemu can boot (such as 
a "prep" kernel) using ARCH=ppc, but that one doesn't support make 
headers_install.

Using ARCH=powerpc makes headers_install work, but there's no kernel .config 
I've been able to come up with that generates a kernel I can boot under qemu.

I could add a special case to my build script, but so far I've got it building 
eight targets (x86, x86-64, mips, mipsel, armv4l, armv5l, and sparc) with the 
same ARCH= for headers_install and the actual kernel compile.  It seems there 
_should_ be a way to do this for as prominent an architecture as PowerPC.

Who should I ask about this?

Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/