From: Thiemo Seufer <ths@networkno.de>
To: Vlad Lungu <vlad@comsys.ro>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] U-Boot patch for qemu -M mips
Date: Wed, 3 Oct 2007 20:47:44 +0100 [thread overview]
Message-ID: <20071003194744.GO16772@networkno.de> (raw)
In-Reply-To: <47039DDF.7050004@comsys.ro>
Vlad Lungu wrote:
> Thiemo Seufer wrote:
>> Vlad Lungu wrote:
>> [snip]
>>
>>>>> +long int initdram(int board_type)
>>>>> +{
>>>>> + /* Sdram is setup by assembler code */
>>>>> + /* If memory could be changed, we should return the true value
>>>>> here */
>>>>> + return MEM_SIZE*1024*1024;
>>>>>
>>>> Qemu gets the amount of RAM passed via a command line switch, the
>>>> qemu-mips emulation sets up a Linux kernel like "command line" in
>>>> memory where u-boot could parse it from.
>>>>
>>>>
>>> Does it, or just when you pass -kernel to it? I'll check.
>>>
>>
>> Hm, you are right, it does that only for -kernel. Would it make sense
>> to change that in Qemu?
>>
> IDK. Maybe I can probe the RAM size in U-Boot , or if this does not work,
mips_r4k implements no probable memory controller, so this won't work.
> put some info somewhere (RAM, register,
> emulated DIP-dwitch), like RAM size, endianness of the CPU.
Endianness is rather pointless. If your U-Boot binary doesn't explode
immediately you got the right endianness. :-)
Thiemo
next prev parent reply other threads:[~2007-10-03 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 10:07 [Qemu-devel] U-Boot patch for qemu -M mips Vlad Lungu
2007-10-02 16:40 ` Thiemo Seufer
2007-10-03 8:29 ` Vlad Lungu
2007-10-03 13:37 ` Thiemo Seufer
2007-10-03 13:49 ` Vlad Lungu
2007-10-03 19:47 ` Thiemo Seufer [this message]
2007-10-04 10:52 ` Vlad Lungu
2007-10-04 11:43 ` Thiemo Seufer
2007-10-04 10:58 ` vlad
2007-10-04 13:26 ` [Qemu-devel] U-Boot patch for qemu -M mips TAKE 2 Vlad Lungu
2007-10-04 13:55 ` Wolfgang Denk
2007-10-04 16:33 ` Vlad Lungu
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=20071003194744.GO16772@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.org \
--cc=vlad@comsys.ro \
/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).