qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PXA27x processor support (XScale)
Date: Wed, 07 Feb 2007 11:34:01 +0100	[thread overview]
Message-ID: <45C9AB19.8030105@aurel32.net> (raw)
In-Reply-To: <fb249edb0702061819u1c94c2abh48c246bb04723eb9@mail.gmail.com>

andrzej zaborowski a écrit :
> Hi,
>   for anybody interested I uploaded a patch containing support for
> Intel's PXA270 processor emulation for qemu. The patch is against
> current CVS (or 0.9.0) and you can find it at
> 
> http://www.zabor.org/balrog/qemu-pxa270-and-more.patch
> 
> (450 kB). PXA is a series of embedded processors used in PDAs, mobile
> phones and other devices. PXA is an ARM based system-on-chip. 27x is
> the newest out of the ones produced by Intel. PXA 25x and 260 devices
> can be emulated using the same code. Main additions are:
> 
>  - On-chip peripherals: DMA, interrupt controller, GPIOs, sysem
> timers, memory manager, clocks manager, power manager, LCD controller,
> PCMCIA cards controller, MMC/SD host controller, I2C device, USB host
> (OHCI), I2S controller, SSP controller, UARTs, an RTC.
> 
>  - NAND memory emulation - should work for all chips supported by
> Linux given the ID of the chip to emulate (small or large page).
>  - PCMCIA bus with hotplugging (added "info pcmcia" command for
> listing sockets and inserted cards).
>  - an IBM/hitachi microdrive, reuses existing IDE code adding the
> CF-ATA command set.
>  - ADS7846 touchscreen controller from Texas Instruments (used in maaany PDAs).
>  - Wolfson WM8750 audio codec chip (I2C slave).
>  - Maxim MAX1111 ADC chip.
>  - Maxim MAX7310 gpio expander chip (I2C slave).
>  - SD card emulator (unchanged from the omap support patch)
>  - iwMMXt coprocessor support (untested).
>  - some bugfixes.
> 
> I'm posting this as is because I won't have time to make a final
> clean-up and I was asked for it by some persons who want to emulate
> pxa270 based devices. I also want to avoid duplicating code. One case
> of duplication is the I2C bus, there was a different I2C bus recently
> merged in qemu. Our implementation is slightly more detailed (as need
> by some I2C hosts) and does some buffering, but is 8-bit only.
> (hw/i2c.h should probably be made into a template that implements 8
> and 16 bit i2c included two time from vl.h).

I have quickly looked at your patch, it seems your implementation of the
I2C bus could be re-used for the Malta board. It uses a bit banging I2C
interface.

Thanks for your patch, I will have a closer look later.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

      parent reply	other threads:[~2007-02-07 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07  2:19 [Qemu-devel] PXA27x processor support (XScale) andrzej zaborowski
2007-02-07  4:49 ` Hetz Ben Hamo
2007-02-07  9:31   ` andrzej zaborowski
2007-02-07 10:34 ` Aurelien Jarno [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=45C9AB19.8030105@aurel32.net \
    --to=aurelien@aurel32.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 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).