From: Armin <akuster@kama-aina.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch][update] Mainstone re-org plus flash
Date: Sun, 09 Dec 2007 16:08:50 -1000 [thread overview]
Message-ID: <475C9FB2.8010601@kama-aina.net> (raw)
In-Reply-To: <fb249edb0712091803h7fcf44a5n3c090eb88c3d7cc4@mail.gmail.com>
andrzej zaborowski wrote:
> On 10/12/2007, andrzej zaborowski <balrogg@gmail.com> wrote:
>
>> On 02/12/2007, Armin <akuster@kama-aina.net> wrote:
>>
>>> Thiemo,
>>>
>>> Thiemo Seufer wrote:
>>>
>>>> Armin wrote:
>>>>
>>>>
>>>>> Hello,
>>>>>
>>>>> This includes the previous Mainstone re-org patch I sent earlier plus flash
>>>>> support.
>>>>> This adds two 32MiB flash devices. Mounts from mtdblock2 on flash device 0
>>>>> fine at boot.
>>>>>
>>>>>
>>>> I did some guesswork on the flash initialization to make it build with
>>>> Laurent's -disk patch. Please check if it is still correct.
>>>>
>>>>
>>> works fine.
>>>
>> Note that both chips get mapped at the same offset in phys_ram_base,
>> I'm quite sure this is a bug and not intentional? It may corrupt data
>> if the OS reads from both chips. I wanted to convert mainstone.c to
>> use qemu_ram_alloc like other pxa boards but I want to make sure this
>> is not intentional.
>>
>> The value of mainstone_rom indicates this too.
>>
>
> Sorry, mainstone_rom is not related to this issue, but that means that
> the ram_size check allows too low values and qemu may crash. It also
> means that the two flash chips *and* the ROM all overlap. I think
> gumstix.c registers the flash correctly, you may wnat to look in it.
> Regards
>
will do.
I seem to remember that the two mappings are mutually exclusive and
possible controlled by an external switch.. I will need to double check
that.
sorry for the trouble.
-Armin
prev parent reply other threads:[~2007-12-10 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 3:06 [Qemu-devel] [Patch][update] Mainstone re-org plus flash Armin
2007-12-02 4:55 ` Thiemo Seufer
2007-12-02 22:44 ` Armin
2007-12-10 0:26 ` andrzej zaborowski
2007-12-10 2:03 ` andrzej zaborowski
2007-12-10 2:08 ` Armin [this message]
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=475C9FB2.8010601@kama-aina.net \
--to=akuster@kama-aina.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 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.