qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ARM XScale core features and PXA270 and PXA255 emulation.
Date: Tue, 17 Apr 2007 19:52:39 +0200	[thread overview]
Message-ID: <fb249edb0704171052k3aa6df66rd0e3f0cd82102b24@mail.gmail.com> (raw)
In-Reply-To: <46d6db660704161510j287af0f8m6192b15674c15804@mail.gmail.com>

Hi,

On 17/04/07, Christian MICHON <christian.michon@gmail.com> wrote:
> On 3/16/07, andrzej zaborowski <balrog@zabor.org> wrote:
> > Implements basic differences between XScale and plain ARM. The patch
> > also adds the main on-chip peripherals of PXA2xx: interrupt
> > controller, DMA, GPIO controller, SSP, I2C, I2S busses, UARTs, FIR
> > port, RTC, Clock/Power/Memory managers.
> >
> > Cheers,
> > Andrew
> >
> >
>
> interesting (I haven't tested it yet)...
>
> how to use this patch ? beside the "-portrait" extra switch, applying
> this patch would make arm-softmmu a pxa2xx by default ?

No, default is whatever the machine uses (-M). Use this patch together
with the rest of the series.

>
> if so, it's very interesting: I've an ipaq (H2210) and I was taking part of
> a port of linux on it. One big drawback then is that I burned a few SD
> cards to get a kernel working, but this patch could be a good fix
> to my problems...
>
> Do I just need the 2 emails with pxa2xx patches ? or is there more
> needed ?

For PXA you need only the two patches. But PXA is only a processor and
the processor alone is useless.

>
> Last, but not least: do you think we could emulate a windows CE
> pocketpc in this way ?

See http://lists.gnu.org/archive/html/qemu-devel/2007-02/msg00109.html

Regards,
Andrew

      reply	other threads:[~2007-04-17 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 20:54 [Qemu-devel] [PATCH] ARM XScale core features and PXA270 and PXA255 emulation andrzej zaborowski
2007-04-16 22:10 ` Christian MICHON
2007-04-17 17:52   ` andrzej zaborowski [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=fb249edb0704171052k3aa6df66rd0e3f0cd82102b24@mail.gmail.com \
    --to=balrog@zabor.org \
    --cc=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).