* Building ppc/powerpc kernel to run under QEMU. @ 2007-05-10 2:03 Rob Landley 2007-05-10 17:28 ` Linas Vepstas 0 siblings, 1 reply; 12+ messages in thread From: Rob Landley @ 2007-05-10 2:03 UTC (permalink / raw) To: linuxppc-dev I've been puttering 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. I was told this was the right place to ask: what's the status of the ppc->powerpc migration, and is there any known way to get ARCH=powerpc to build a kernel qemu can boot? Rob ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-10 2:03 Building ppc/powerpc kernel to run under QEMU Rob Landley @ 2007-05-10 17:28 ` Linas Vepstas 2007-05-10 22:07 ` Matt Sealey 2007-05-12 1:14 ` Rob Landley 0 siblings, 2 replies; 12+ messages in thread From: Linas Vepstas @ 2007-05-10 17:28 UTC (permalink / raw) To: Rob Landley; +Cc: linuxppc-dev Hi Rob, On Wed, May 09, 2007 at 10:03:25PM -0400, Rob Landley wrote: > I've been puttering 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. Hmm. I'm not a boot expert, (although many people on this list are). Any hint of where the boot is failing? Maybe qemu is not setting up a device tree? > what's the status of the > ppc->powerpc migration, pretty far along; bits f ppc are getting nuked regularly. > and is there any known way to get ARCH=powerpc to > build a kernel qemu can boot? Dunno... --linas ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-10 17:28 ` Linas Vepstas @ 2007-05-10 22:07 ` Matt Sealey 2007-05-11 1:46 ` David Gibson 2007-05-12 1:46 ` Rob Landley 2007-05-12 1:14 ` Rob Landley 1 sibling, 2 replies; 12+ messages in thread From: Matt Sealey @ 2007-05-10 22:07 UTC (permalink / raw) To: Linas Vepstas; +Cc: linuxppc-dev, Rob Landley QEMU really really wants a PREP kernel, and that stuff's just not in the new arch/powerpc tree anymore is it? I'd love to see the device tree once QEMU's kernel has booted :D I wonder.. would it be useful to have a qemu platform in arch/powerpc and for someone to start hacking in devices from a non-emulated point of view? It seems a bit of a waste in my mind to emulate a network card, serial port IDE interface, ADB (yick!) and a VESA graphics adapter in such 'detail' when it can be passed back to the emulation somehow through some kind of clever call interface (maybe just have the zero page of the emulation contain a bunch of 'ports' which are really function calls pointers..?) -- Matt Sealey <matt@genesi-usa.com> Genesi, Manager, Developer Relations Linas Vepstas wrote: > Hi Rob, > > On Wed, May 09, 2007 at 10:03:25PM -0400, Rob Landley wrote: >> I've been puttering 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. > > Hmm. I'm not a boot expert, (although many people on this list are). > Any hint of where the boot is failing? Maybe qemu is not setting up > a device tree? > >> what's the status of the >> ppc->powerpc migration, > > pretty far along; bits f ppc are getting nuked regularly. > >> and is there any known way to get ARCH=powerpc to >> build a kernel qemu can boot? > > Dunno... > > --linas > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-10 22:07 ` Matt Sealey @ 2007-05-11 1:46 ` David Gibson 2007-05-12 3:30 ` Rob Landley 2007-05-12 1:46 ` Rob Landley 1 sibling, 1 reply; 12+ messages in thread From: David Gibson @ 2007-05-11 1:46 UTC (permalink / raw) To: Matt Sealey; +Cc: linuxppc-dev, Rob Landley On Thu, May 10, 2007 at 11:07:52PM +0100, Matt Sealey wrote: > QEMU really really wants a PREP kernel, and that stuff's just not in the new > arch/powerpc tree anymore is it? qemu is PReP, eh? Well that would explain the not working: PReP hasn't been ported to arch/powerpc yet. The fact that qemu acts like a PReP might make doing so rather easier. > I'd love to see the device tree once QEMU's kernel has booted :D > > I wonder.. would it be useful to have a qemu platform in arch/powerpc and > for someone to start hacking in devices from a non-emulated point of view? > It seems a bit of a waste in my mind to emulate a network card, serial port > IDE interface, ADB (yick!) and a VESA graphics adapter in such 'detail' when > it can be passed back to the emulation somehow through some kind of clever > call interface (maybe just have the zero page of the emulation contain a > bunch of 'ports' which are really function calls pointers..?) Possibly in the long term. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-11 1:46 ` David Gibson @ 2007-05-12 3:30 ` Rob Landley 0 siblings, 0 replies; 12+ messages in thread From: Rob Landley @ 2007-05-12 3:30 UTC (permalink / raw) To: David Gibson; +Cc: linuxppc-dev On Thursday 10 May 2007 9:46 pm, David Gibson wrote: > On Thu, May 10, 2007 at 11:07:52PM +0100, Matt Sealey wrote: > > QEMU really really wants a PREP kernel, and that stuff's just not in the new > > arch/powerpc tree anymore is it? > > qemu is PReP, eh? Well that would explain the not working: PReP > hasn't been ported to arch/powerpc yet. The fact that qemu acts like > a PReP might make doing so rather easier. It's slightly more compliated than that. The CVS version of QEMU says it can emulate the following architectures: qemu-system-ppc -M ? Supported machines are: g3bw Heathrow based PowerMAC (default) mac99 Mac99 based PowerMAC prep PowerPC PREP platform ref405ep ref405ep taihu taihu Unfortunately, the powermac variants want a hard drive image (the open hackware bios won't finish booting without it), and the other two are new enough I haven't had a chance to try 'em yet. The only way I've managed to build a prep kernel is ARCH=ppc. I can build a CHRP kernel with arch=powerpc, but can't figure out how to tell qemu to boot it (and am told formatting a fake partitioned hard drive image is The Way). Rob ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-10 22:07 ` Matt Sealey 2007-05-11 1:46 ` David Gibson @ 2007-05-12 1:46 ` Rob Landley 2007-05-12 3:00 ` Doug Maxey 1 sibling, 1 reply; 12+ messages in thread From: Rob Landley @ 2007-05-12 1:46 UTC (permalink / raw) To: Matt Sealey; +Cc: linuxppc-dev On Thursday 10 May 2007 6:07 pm, Matt Sealey wrote: > QEMU really really wants a PREP kernel, and that stuff's just not in the new > arch/powerpc tree anymore is it? In theory I could feed it a power mac kernel, but I'd have to create a partitioned hard drive image to satisfy open hackware. A prep kernel fakes being a partitioned image sufficiently that I can use -kernel to boot. > I'd love to see the device tree once QEMU's kernel has booted :D So would I. :) I'm told they've got that part working. I once managed to get a powerpc Ubuntu ISO image to boot under qemu, I just can't _build_ a kernel that does. (I have no idea how to create the specially partitioned hard drive image it wants, and since I got 5 other architectures working without needing to do that, I'm looking for a way to make a prep kernel work so I won't have to.) > I wonder.. would it be useful to have a qemu platform in arch/powerpc and > for someone to start hacking in devices from a non-emulated point of view? > It seems a bit of a waste in my mind to emulate a network card, serial port > IDE interface, ADB (yick!) and a VESA graphics adapter in such 'detail' when > it can be passed back to the emulation somehow through some kind of clever > call interface (maybe just have the zero page of the emulation contain a > bunch of 'ports' which are really function calls pointers..?) Yeah, but qemu already _has_ an IDE interface, graphics card (an old western digital something or other), and network card working. Once they got 'em working on one platform, they can plug them into a virtual PCI bus for other platforms. What I wind up fighting with most when trying to get multiple platforms to work is firmware and bootloaders. (All of which are insane, without exception so far.) This is why I like the qemu -kernel thing, which lets me bypass the whole issue... Usually. Rob ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-12 1:46 ` Rob Landley @ 2007-05-12 3:00 ` Doug Maxey 2007-05-12 4:05 ` Rob Landley 0 siblings, 1 reply; 12+ messages in thread From: Doug Maxey @ 2007-05-12 3:00 UTC (permalink / raw) To: Rob Landley; +Cc: linuxppc-dev On Fri, 11 May 2007 21:46:35 EDT, Rob Landley wrote: > On Thursday 10 May 2007 6:07 pm, Matt Sealey wrote: > > QEMU really really wants a PREP kernel, and that stuff's just not in the new > > arch/powerpc tree anymore is it? > > In theory I could feed it a power mac kernel, but I'd have to create a > partitioned hard drive image to satisfy open hackware. A prep kernel fakes > being a partitioned image sufficiently that I can use -kernel to boot. > > > I'd love to see the device tree once QEMU's kernel has booted :D > > So would I. :) > > I'm told they've got that part working. I once managed to get a powerpc > Ubuntu ISO image to boot under qemu, I just can't _build_ a kernel that does. > (I have no idea how to create the specially partitioned hard drive image it > wants, and since I got 5 other architectures working without needing to do > that, I'm looking for a way to make a prep kernel work so I won't have to.) Have you tried to use parted (or fdisk) to set the first partition table entry as type 0x41? I personally have no experience with qemu, but do fiddle with loading images with the real IBM firmware (a lot). What I usually end up doing is dd'ing a bootloader into the appropriate sized 0x41 partition. Am pretty sure no GPL stuff groks PREP partitions per se, other than seeing the part type. AIX stores its kernel in the PREP part, and boots from that partition (no bootloader, loads kernel directly). ++doug ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-12 3:00 ` Doug Maxey @ 2007-05-12 4:05 ` Rob Landley 0 siblings, 0 replies; 12+ messages in thread From: Rob Landley @ 2007-05-12 4:05 UTC (permalink / raw) To: Doug Maxey; +Cc: linuxppc-dev [-- Attachment #1: Type: text/plain, Size: 4597 bytes --] On Friday 11 May 2007 11:00 pm, Doug Maxey wrote: > > I'm told they've got that part working. I once managed to get a powerpc > > Ubuntu ISO image to boot under qemu, I just can't _build_ a kernel that does. > > (I have no idea how to create the specially partitioned hard drive image it > > wants, and since I got 5 other architectures working without needing to do > > that, I'm looking for a way to make a prep kernel work so I won't have to.) > > Have you tried to use parted (or fdisk) to set the first partition table > entry as type 0x41? I personally have no experience with qemu, but do > fiddle with loading images with the real IBM firmware (a lot). Ok, backstory. I have a cross-compile build system called Firmware Linux (http://landley.net/code/firmware). It's a shell script that you run to build a system, entirely from source, for a given target platform. Cross-compile toolchain and all. First it builds a cross compiler from source code (gcc, binutils, uClibc, and make headers_install from Linux), and then it does just enough cross-compiling with that to get you a minimal native build environment (a root filesystem containing uClibc, linux, busybox, gcc, binutils, make, and bash), so you can build natively under emulation from thereon in. (MUCH easier than cross compiling. Slower, but throwing hardware at the problem is easier than throwing engineers at it. I wrote a "why cross-compiling sucks" at http://landley.net/writing/docs/cross-compiling.html not that I have strong opinions on the topic or anything. :) Anyway, I have this thing building a half-dozen archtectures already, and the ones I regularly test under are i686, x86-64, armv4l, and mipsel. (Sparc's uClibc support is broken, and powerpc just DOESN'T LIKE ME. I'm tackling the second first because I don't really care about sparc.) All the other architectures (except sparc and powerpc) run under qemu. I run the appropriate qemu variant with the "-kernel" command line option to use the built-in bootloader, and feed them an unpartitioned ext2 image containing the root filesystem, and all of 'em (except sparc and ppc) boot up to a shell prompt within the emulator and are capable of building and running "hello world". There are idiosyncrasies. (For example I have to feed arm a scsi hard drive instead of IDE, but that's just a different qemu command line. And for some reason 2.6.21 broke arm's scsi support, this but worked in 2.6.20.) But mostly, all the architectures work the same way. Unfortunately, open hackware requires a partitioned hard drive image or it refuses to boot. PREP looks enough like a paritioned image to fool the firmware into letting the built-in "-kernel" bootloader of qemu work. None of the macintosh variants do. > What I usually end up doing is dd'ing a bootloader into the appropriate > sized 0x41 partition. Am pretty sure no GPL stuff groks PREP partitions > per se, other than seeing the part type. With qemu I can go: qemu -kernel vmlinuzfile -hda walrus.img -nographic And it'll load that kernel into memory and boot it, without it actually being anywhere in walrus.img. On most platforms this bypasses the bios/firmware entirely, but apparently powerpc can't do this (due to the need to set up a fake hardware tree and pass it off to the kernel, or some such). And the firmware is chock-full of built-in assumptions, and sits down and throws a tantrum if any of them are violated. It's kind of annoying, really. But if I could build a prep kernel, I could work around this. Unfortunately, ARCH=ppc builds a prep kernel, but won't do a headers_install. With ARCH=powerpc I can do a headers_installbuild a CHRP kernel that won't boot, but not a PREP kernel. I could teach my build script to use one ARCH for headers_install and one for building the kernel, but that's amazingly ugly and I dont have to do it for any of the other architectures. I could also write a wrapper to turn CHRP into a partitioned hard drive image, which looks like what I'm going to have to do. > AIX stores its kernel in the PREP part, and boots from that partition > (no bootloader, loads kernel directly). That's what I'm trying to use, yeah. ARCH=ppc does that, ARCH=powerpc does not. The current mercurial version of Firmware Linux builds a CHRP kernel I can't boot. One of my users donated a config that sort of builds a PREP kernel (attached), but you have to patch the ./cross-compiler.sh and ./mini-native.sh build scripts to feed in "powerpc" instead of $KARCH to headers_install. Rob [-- Attachment #2: powerpc --] [-- Type: text/plain, Size: 3410 bytes --] KARCH=ppc KERNEL_PATH=arch/ppc/boot/images/zImage.prep GCC_FLAGS= BINUTILS_FLAGS= QEMU_TEST= #ppc emulator_command() { echo qemu-system-ppc -M prep -nographic -hda "$1" \ -kernel "$2" } # Write out Linux kernel .config file cat > "${WORK}"/miniconfig-linux << 'EOF' CONFIG_EXPERIMENTAL=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_EMBEDDED=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_ALTIVEC=y CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_BINFMT_ELF=y CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE="rw init=/tools/bin/sh panic=1 PATH=/tools/bin root=/dev/hda console=ttyS0" CONFIG_SECCOMP=y CONFIG_ISA=y CONFIG_ADVANCED_OPTIONS=y CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_INITRD=y CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_TASK_IOCTL=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_SCSI_PROC_FS=y CONFIG_BLK_DEV_SD=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_LOGGING=y CONFIG_ATA=y CONFIG_SATA_AHCI=y CONFIG_MD=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_KEYBOARD=y CONFIG_INPUT_MOUSE=y CONFIG_SERIO=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_PCI=y CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_HWMON=y CONFIG_FB=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TRIDENT=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y CONFIG_EXT2_FS=y CONFIG_EXT3_FS=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_DNOTIFY=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_CONFIGFS_FS=y CONFIG_SQUASHFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_UTF8=y EOF # Write out uClibc .config file. cat > "${WORK}"/miniconfig-uClibc << 'EOF' TARGET_powerpc=y ARCH_USE_MMU=y UCLIBC_HAS_FLOATS=y UCLIBC_HAS_FPU=y DOPIC=y HAVE_SHARED=y LDSO_LDD_SUPPORT=y LDSO_CACHE_SUPPORT=y UCLIBC_STATIC_LDCONFIG=y LDSO_RUNPATH=y UCLIBC_CTOR_DTOR=y UCLIBC_HAS_THREADS=y LINUXTHREADS_OLD=y UCLIBC_HAS_LFS=y MALLOC_GLIBC_COMPAT=y UCLIBC_DYNAMIC_ATEXIT=y UCLIBC_SUSV3_LEGACY=y UCLIBC_HAS_SHADOW=y UCLIBC_HAS___PROGNAME=y UNIX98PTY_ONLY=y ASSUME_DEVPTS=y UCLIBC_HAS_TM_EXTENSIONS=y UCLIBC_HAS_TZ_CACHING=y UCLIBC_HAS_TZ_FILE=y UCLIBC_HAS_TZ_FILE_READ_MANY=y UCLIBC_HAS_RPC=y UCLIBC_HAS_STRING_GENERIC_OPT=y UCLIBC_HAS_STRING_ARCH_OPT=y UCLIBC_HAS_CTYPE_TABLES=y UCLIBC_HAS_CTYPE_SIGNED=y UCLIBC_HAS_STDIO_GETC_MACRO=y UCLIBC_HAS_STDIO_PUTC_MACRO=y UCLIBC_HAS_STDIO_AUTO_RW_TRANSITION=y UCLIBC_HAS_ERRNO_MESSAGES=y UCLIBC_HAS_SIGNUM_MESSAGES=y UCLIBC_HAS_GNU_GETOPT=y UCLIBC_HAS_GNU_GETSUBOPT=y UCLIBC_HAS_REGEX=y UCLIBC_HAS_REGEX_OLD=y UCLIBC_HAS_FNMATCH=y UCLIBC_HAS_FNMATCH_OLD=y UCLIBC_HAS_GLOB=y UCLIBC_HAS_GNU_GLOB=y UCLIBC_BUILD_RELRO=y UCLIBC_BUILD_NOEXECSTACK=y DOSTRIP=y EOF ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-10 17:28 ` Linas Vepstas 2007-05-10 22:07 ` Matt Sealey @ 2007-05-12 1:14 ` Rob Landley 2007-05-14 19:09 ` Hollis Blanchard 1 sibling, 1 reply; 12+ messages in thread From: Rob Landley @ 2007-05-12 1:14 UTC (permalink / raw) To: Linas Vepstas; +Cc: linuxppc-dev On Thursday 10 May 2007 1:28 pm, Linas Vepstas wrote: > Hi Rob, > > On Wed, May 09, 2007 at 10:03:25PM -0400, Rob Landley wrote: > > I've been puttering 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. > > Hmm. I'm not a boot expert, (although many people on this list are). > Any hint of where the boot is failing? Maybe qemu is not setting up > a device tree? How about "not building a prep kernel at all"? The Open Hackware bootloader used by QEMU insists on a boot partition, even when I use "-kernel" to use the built-in bootloader. But the prep kernel is apparently formatted to look like a boot partition, or close enough for the firmware to recognize it. (The macintosh-style kernels require a hard drive image in order for the firmware to like them. So I can't boot one of those with "qemu -kernel filename" even if I build it right.) Rob ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-12 1:14 ` Rob Landley @ 2007-05-14 19:09 ` Hollis Blanchard 0 siblings, 0 replies; 12+ messages in thread From: Hollis Blanchard @ 2007-05-14 19:09 UTC (permalink / raw) To: linuxppc-dev On Fri, 11 May 2007 21:14:57 -0400, Rob Landley wrote: > > The Open Hackware bootloader used by QEMU insists on a boot partition, even > when I use "-kernel" to use the built-in bootloader. But the prep kernel is > apparently formatted to look like a boot partition, or close enough for the > firmware to recognize it. (The macintosh-style kernels require a hard drive > image in order for the firmware to like them. So I can't boot one of those > with "qemu -kernel filename" even if I build it right.) Why don't you try dumping OpenHackware entirely? With small modifications to OpenBIOS's briQ build, I got pretty far under qemu's PReP emulation. The biggest problem was that the briQ 16550 driver was not correct (maybe it worked on hardware, but it didn't follow spec and failed under qemu). I got up to "ok, now how do I boot from the Forth prompt?" before running out of time. -- Hollis Blanchard IBM Linux Technology Center ^ permalink raw reply [flat|nested] 12+ messages in thread
* Building ppc/powerpc kernel to run under QEMU. @ 2007-05-09 22:39 Rob Landley 2007-05-09 23:38 ` Stephen Rothwell 0 siblings, 1 reply; 12+ messages in thread From: Rob Landley @ 2007-05-09 22:39 UTC (permalink / raw) To: linux-kernel 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Building ppc/powerpc kernel to run under QEMU. 2007-05-09 22:39 Rob Landley @ 2007-05-09 23:38 ` Stephen Rothwell 0 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2007-05-09 23:38 UTC (permalink / raw) To: Rob Landley; +Cc: linux-kernel [-- Attachment #1: Type: text/plain, Size: 285 bytes --] On Wed, 9 May 2007 18:39:55 -0400 Rob Landley <rob@landley.net> wrote: > > Who do I ask about the status of the migration from ARCH=ppc to ARCH=powerpc? linuxppc-dev@ozlabs.org ... -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ [-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2007-05-14 19:30 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-05-10 2:03 Building ppc/powerpc kernel to run under QEMU Rob Landley 2007-05-10 17:28 ` Linas Vepstas 2007-05-10 22:07 ` Matt Sealey 2007-05-11 1:46 ` David Gibson 2007-05-12 3:30 ` Rob Landley 2007-05-12 1:46 ` Rob Landley 2007-05-12 3:00 ` Doug Maxey 2007-05-12 4:05 ` Rob Landley 2007-05-12 1:14 ` Rob Landley 2007-05-14 19:09 ` Hollis Blanchard -- strict thread matches above, loose matches on Subject: below -- 2007-05-09 22:39 Rob Landley 2007-05-09 23:38 ` Stephen Rothwell
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.