From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Laurikainen, Tuukka" <t.laurikainen@ibermatica.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu 0.12.5 sparc64 debian 505
Date: Thu, 19 Aug 2010 22:44:46 +0200 [thread overview]
Message-ID: <AANLkTiko-0Gm=7J+pXpf=Pe+QAAKBNwcwChsj2EWN2aa@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimG+nt4j+doKQADLbqXLco+aq2nxr5puN1THPxE@mail.gmail.com>
2010/8/19 Blue Swirl <blauwirbel@gmail.com>:
> On Thu, Aug 19, 2010 at 10:15 AM, Laurikainen, Tuukka
> <t.laurikainen@ibermatica.com> wrote:
>> Hi,
>>
>> As the Sparc64 support is not complete, I thought I'd ask here before
>> reporting a bug.
>>
>> Trying to boot a Debian netboot cd image for Sparc with Qemu 0.12.5:
>>
>> # qemu-system-sparc64 -boot d -cdrom debian-505-sparc-businesscard.iso
>> -nographic -hda sparc.img
>> OpenBIOS for Sparc64
>> Configuration device id QEMU version 1 machine id 0
>> CPUs: 1 x SUNW,UltraSPARC-II
>> UUID: 00000000-0000-0000-0000-000000000000
>> Welcome to OpenBIOS v1.0 built on Dec 6 2009 11:16
>> Type 'help' for detailed information
>>
>> [sparc64] Booting file 'cdrom' with parameters ''
>> Not a bootable ELF image
>> Not a Linux kernel image
>> Loading a.out image...
>> Loaded 7680 bytes
>> entry point is 0x4000
>> Jumping to entry point...
>> switching to new context: entry point 0x4000 stack 0x00000000ffe02a71
>> SILO Version 1.4.13
>> \
>>
>> Welcome to Debian GNU/Linux lenny!
>>
>> This is a Debian installation CDROM, built on 20100627-10:50.
>> Keep it once you have installed your system, as you can boot from it
>> to repair the system on your hard disk if that ever becomes necessary.
>>
>> WARNING: You should completely back up all of your hard disks before
>> proceeding. The installation procedure can completely and irreversibly
>> erase them! If you haven't made backups yet, remove the rescue CD from
>> the drive and press L1-A to get back to the OpenBoot prompt.
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>> permitted
>> by applicable law.
>>
>> [ ENTER - Boot install ] [ Type "expert" - Boot into expert mode ]
>> [ Type "rescue" - Boot into rescue mode ]
>> boot:
>> Allocated 8 Megs of memory at 0x40000000 for kernel
>> Loaded kernel version 2.6.26
>> Loading initial ramdisk (4310561 bytes at 0xC00000 phys, 0x40C00000
>> virt)...
>> qemu: unsupported keyboard cmd=0x02
>> FLOPPY ERROR: fdctrl_unimplemented: unimplemented command 0xfe
>> Pqemu: unsupported keyboard cmd=0xb1
>> FLOPPY ERROR: fdctrl_unimplemented: unimplemented command 0xc4
>
> This is about how far Sparc64 boot gets now. With a custom kernel I
> get much further (IDE probe) but there are still a few unimplemented
> features.
Is there a list of what is missing? You mentioned the pci bridges
before. What else?
Shall we maintain the TODO file for everything we find? Including
things we may fix within a few days after finding?
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-08-19 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 10:15 [Qemu-devel] qemu 0.12.5 sparc64 debian 505 Laurikainen, Tuukka
2010-08-19 18:20 ` Blue Swirl
2010-08-19 20:44 ` Artyom Tarasenko [this message]
2010-08-19 20:50 ` Blue Swirl
2010-08-20 11:45 ` Laurikainen, Tuukka
2010-08-20 8:21 ` Laurikainen, Tuukka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTiko-0Gm=7J+pXpf=Pe+QAAKBNwcwChsj2EWN2aa@mail.gmail.com' \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=t.laurikainen@ibermatica.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).