From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>, Bob Breuer <breuerr@mc.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] option-rom (was cg14)
Date: Fri, 4 Jun 2010 19:40:37 +0200 [thread overview]
Message-ID: <AANLkTimcFylTXHN_S8RFv0KOAefFcg_rRT-Cq2xkR6d0@mail.gmail.com> (raw)
>>> 2010/5/27 Bob Breuer <breuerr@mc.net>:
>>> + /* DBRI (audio) */
>>> + cpu_register_physical_memory_offset(0xEE0001000ULL, 0x10000, bad_mem, 0xE0001000);
>>
>> Please add a new DBRI device ;-).
>
> Or maybe just a field in hwdef + empty_slot? :-)
Or actually don't bother at all. What is expected at 0xee0001000 is
not the DBRI device, but its FCode driver.
I wrote a stub, but don't see that it helps to boot except one has a
nice device name (
Probing /obio at 2,0 cgfourteen
Probing /iommu@f,e0000000/sbus@f,e0001000 at f,0 espdma esp sd st
ledma le SUNW,bpp
Probing /iommu@f,e0000000/sbus@f,e0001000 at e,0 qemu,device-stub
Probing /iommu@f,e0000000/sbus@f,e0001000 at 0,0 Nothing there
) and switching off slot "e" probing is not necessary.
What would be nice is a generic '-option-rom' switch which would take
a rom address and rom file or contents
as params. Or do we have something like this? I mean for qemu-system-sparc.
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next reply other threads:[~2010-06-04 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 17:40 Artyom Tarasenko [this message]
2010-06-04 19:28 ` [Qemu-devel] Re: option-rom (was cg14) Blue Swirl
2010-06-05 20:25 ` Bob Breuer
2010-06-05 20:35 ` Blue Swirl
2010-06-05 23:10 ` [Qemu-devel] sun framebuffer selection (was option-rom) Bob Breuer
2010-06-06 7:32 ` [Qemu-devel] " Blue Swirl
2010-06-06 16:28 ` Artyom Tarasenko
2010-06-09 19:43 ` Blue Swirl
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=AANLkTimcFylTXHN_S8RFv0KOAefFcg_rRT-Cq2xkR6d0@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=breuerr@mc.net \
--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).