qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dbaryshkov@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/2] Factor out common SharpSL PDA code
Date: Fri, 30 May 2008 11:33:27 +0000 (UTC)	[thread overview]
Message-ID: <g1oom7$eqf$1@ger.gmane.org> (raw)
In-Reply-To: fb249edb0805300255l70532326m387dda6b6132e50a@mail.gmail.com

Hi,

andrzej zaborowski wrote:

> Hi,
> 
> On 27/05/2008, Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
>> Factor out to sharpsl code to support devices that are present not only
>>  in spitz-family PDAs but also in outher Sharp Zaurus PDAs
> 
> I think of the Tosa as part of spitz family, but we can split the file
> if you think it's advantageous.  hw/spitz.c file would be named
> hw/zaurus.c but I had to be paranoid about trademarked names at that
> time, and afaik the SCOOP chip is only used on the Zaurus.

SCOOP is a custom ASiC used only on zaurus. However not all zaurii are 
spitz'. I moved all common functionality to separate file (should be 
named hw/zaurus.c :)) to make things more clear. And separated 

> 
> BTW, are you planning to add the other Tosa peripherals?

Yes. I'm looking at it now. The main problem probably will be TC6393XB 
which is a SiC containing NAND controller, FB/LCD, OHCI and (unused in 
tosa) MMC controller.  The current code ("return 3") is just a 
placeholder to make machine type detector work. wm9712 (audio codec + ts 
interface) and kbd seem to be simpler to implement.

BTW: I wasn't able to get PXA MMC emulation working neither with my code,
nor with spitz emulation. Does it work for you?

-- 
With best wishes
Dmitry

  reply	other threads:[~2008-05-30 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 21:35 [Qemu-devel] [PATCH 1/2] Factor out common SharpSL PDA code Dmitry Baryshkov
2008-05-30  9:55 ` andrzej zaborowski
2008-05-30 11:33   ` Dmitry Baryshkov [this message]
2008-05-30 12:47     ` [Qemu-devel] " andrzej zaborowski
2008-05-31 16:40       ` Dmitry Baryshkov

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='g1oom7$eqf$1@ger.gmane.org' \
    --to=dbaryshkov@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).