qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add Apollon (OMAP24xx) board support
Date: Fri, 25 Jul 2008 10:15:34 +0200	[thread overview]
Message-ID: <fb249edb0807250115r1a468d17v87c3b8c926e0b1da@mail.gmail.com> (raw)
In-Reply-To: <9c9fda240807250054o7db36912u3f3d11d0a580a91c@mail.gmail.com>

2008/7/25 Kyungmin Park <kmpark@infradead.org>:
>>> @@ -3875,7 +3926,11 @@ static uint32_t omap_sdrc_read(void *opaque, target_phys_addr_t addr)
>>>     case 0x68: /* SDRC_DLLB_CTRL */
>>>     case 0x6c: /* SDRC_DLLB_STATUS */
>>>     case 0x70: /* SDRC_POWER */
>>> +         return 0x00;
>>> +
>>>     case 0x80: /* SDRC_MCFG_0 */
>>> +         return 0x4000;
>>> +
>>
>> This should be made writable (default value is 0) and the bootloader
>> or the board file (hw/nseries.c) needs to write the correct value
>> there.
>
> Agreed, apollon and omap2420h4 read this value at bootloader, Yes it's
> meanless in qemu.
> it's seted at initial bootloader, but it's not in qemu. If sdrc has
> array value, we can read it

I mean something like

    uint32_t mcfg0 = (boot_info.ram_size / 0x200000) << 8;        /* RAMSIZE */

    cpu_physical_memory_write(0x68009080,     /* SDRC_MCFG_0 */
                    (void *) &mcfg0, sizeof(mcfg0));

>
>>
>> Would there be much redundancy if apollon setup was in a separate file?
>
> Yes, as you see almost same as n800.

It seems apollon only uses n8x0_init, n8x0_nand_setup and
n8x0_usb_setup, everything else is nseries-specific. (plus maybe the
menelaus chip on i2c)

>
>>
>> The latter two don't seem to be supported in this patch. OMAP2 on-chip
>> lcdc will require a bit of work to be usable.
>
> It's initial support we need to work more to support full peripherals.
>>
>>> +@item
>>> +Secure Digital card connected to OMAP MMC/SD host
>>> +@item
>>> +One OMAP on-chip UARTs
>>> +@item
>>> +External USB transceiver chip connected to USB controller embedded in a TI
>>
>> (TUSB6010 chip?)
>
> actually ISP1105W.
>
>>
>>> +@item
>>> +Three GPIO switches and GPIO indicate LEDs
>>
>> This isn't in the patch either.
>>
>> I'll commit the omap GPMC improvements for the moment.
>>
>
> same as above.
>
> If you don't mind I want to add mentioned devices later

You don't have to add them, but they shouldn't be listed in
qemu-doc.texi before they are supported.

Cheers,
Andrzej

  reply	other threads:[~2008-07-25  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 23:00 [Qemu-devel] [PATCH] Add Apollon (OMAP24xx) board support Kyungmin Park
2008-07-25  7:18 ` andrzej zaborowski
2008-07-25  7:54   ` Kyungmin Park
2008-07-25  8:15     ` andrzej zaborowski [this message]
2008-07-25  9:13       ` andrzej zaborowski
2008-07-28  7:09       ` Kyungmin Park
  -- strict thread matches above, loose matches on Subject: below --
2008-07-23 23:34 Kyungmin Park
2008-07-24  8:45 ` Andreas Färber

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=fb249edb0807250115r1a468d17v87c3b8c926e0b1da@mail.gmail.com \
    --to=balrogg@gmail.com \
    --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).