From: Vlad Lungu <vlad@comsys.ro>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] U-Boot
Date: Sat, 29 Sep 2007 11:44:42 +0300 [thread overview]
Message-ID: <46FE107A.6090505@comsys.ro> (raw)
In-Reply-To: <46FB7EED.3090205@comsys.ro>
Vlad Lungu wrote:
lol, replying to myself
> Blue Swirl wrote:
>
>>
>> Someone could port OpenBIOS or LinuxBIOS to MIPS.
>>
>
> Well, just FYI:
>
> I sort-of-ported U-Boot to Qemu (-M mips). Network performance sucks for
> some reason (hard enough that tftp-booting a kernel is impossible) and I
> didn't have time to investigate this yet. But I guess that porting to
> (-M malta) should not be that hard, and I think there is some PCI
> support already in U-boot.
>
Reports of poor network performance have been greatly exagerated.
Apparently, what it happens is :
- qemu doesn't respond with a next-server or server-name in DHCP, apparently
- U-Boot uses broadcast in this case as the server address
- things don't quite work
Setting IP by hand or using tap for networking and configuring DHCP on
the host correctly allows loading bt TFTP (or even nfs-booting with
tap). I can boot a vmlinux with embedded ramdisk (a couple of Megs) in
maybe 10 seconds. Still getting RX timeouts, but it's no big deal.
I will polish the thing a little and post an update in 1-2 weeks max.
Maybe we can have a bootrom for MIPS shipping with Qemu, after all. Even
for malta.
Vlad
next prev parent reply other threads:[~2007-09-29 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 12:31 [Qemu-devel] Qemu and Linux 2.4 Vlad Lungu
2007-09-11 12:54 ` Thiemo Seufer
2007-09-11 13:39 ` Vlad Lungu
2007-09-26 16:25 ` Alexander Voropay
2007-09-26 16:59 ` Ralf Baechle
2007-09-27 10:06 ` Vlad Lungu
2007-09-26 17:12 ` Blue Swirl
2007-09-27 9:59 ` Vlad Lungu
2007-09-29 8:44 ` Vlad Lungu [this message]
2007-09-27 9:53 ` Vlad Lungu
2007-09-11 13:31 ` [Qemu-devel] " ralf
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=46FE107A.6090505@comsys.ro \
--to=vlad@comsys.ro \
--cc=qemu-devel@nongnu.org \
/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).