From: "Kyungmin Park" <kmpark@infradead.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add Apollon (OMAP24xx) board support
Date: Mon, 28 Jul 2008 16:09:26 +0900 [thread overview]
Message-ID: <9c9fda240807280009o1d78afe8ma932ae6b4f6044a8@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0807250115r1a468d17v87c3b8c926e0b1da@mail.gmail.com>
Hi,
>>
>>>
>>> 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)
Okay I will separate apolloc.c
>
>>
>>>
>>> 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.
How about to add prefix 'TODO'?
I'll send new patch again.
Thank you,
Kyungmin Park
next prev parent reply other threads:[~2008-07-28 7:09 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
2008-07-25 9:13 ` andrzej zaborowski
2008-07-28 7:09 ` Kyungmin Park [this message]
-- 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=9c9fda240807280009o1d78afe8ma932ae6b4f6044a8@mail.gmail.com \
--to=kmpark@infradead.org \
--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).