qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Serge Vakulenko <serge.vakulenko@gmail.com>
Cc: Leon Alrae <leon.alrae@imgtec.com>,
	qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH pic32 v2 0/5] Support for Microchip pic32mx7 and pic32mz microcontrollers
Date: Thu, 2 Jul 2015 08:31:34 +0300	[thread overview]
Message-ID: <20150702083134.6ee193b130cc4e1922a6e74d@gmail.com> (raw)
In-Reply-To: <cover.1435722961.git.serge.vakulenko@gmail.com>

On Tue, 30 Jun 2015 21:12:29 -0700
Serge Vakulenko <serge.vakulenko@gmail.com> wrote:

> Please find below a set of patches, which allow to simulate Microchip PIC32
> microcontrollers on QEMU. For examples of real PIC32 applications running
> on QEMU, see page: https://github.com/sergev/qemu/wiki
> 
> (1) Make the CPU clock frequency configurable per platform.
>     Currently the clock rate for all MIPS platforms is fixed at 100MHz.
>     Need to make it 40MHz for pic32mx7.
> 
> (2) For TLBWR instruction, the generated random index value has been not
>     quite random and did not take into account the Wired register value. Fixed.
> 
> (3) Added support for external interrupt controller mode (EIC).
>     Required for pic32.
> 
> (4) Added two processor variants: M4K and microAptivUP.
>     Needed for pic32mx and pic32mz simulation.
> 
> (5) Added two machine platforms: Microchip pic32mx7 and pic32mz
>     microcontrollers. Several board types supported for each platform:
> 
>     pic32mx7-explorer16  PIC32MX7 microcontroller on Microchip Explorer-16 board
>     pic32mx7-max32       PIC32MX7 microcontroller on chipKIT Max32 board
>     pic32mx7-maximite    PIC32MX7 microcontroller on Geoff's Maximite computer
>     pic32mz-explorer16   PIC32MZ microcontroller on Microchip Explorer-16 board
>     pic32mz-meb2         PIC32MZ microcontroller on Microchip MEB-II board
>     pic32mz-wifire       PIC32MZ microcontroller on chipKIT WiFire board
> 
> 
> Serge Vakulenko (5):
>   Speed of MIPS CPU timer made configurable per platform.
>   Fixed random index generation for TLBWR instruction. It was not quite
>     random and did not skip Wired entries.
>   Added support for external interrupt controller (EIC) mode.
>   Two new processor variants: M4K and microAptivP.
>   Two new machine platforms: pic32mz7 and pic32mz.

Please fix your subject lines according to "Write a good commit message" section
of http://wiki.qemu.org/Contribute/SubmitAPatch.

Also please use the imperative mood in the subject line.

-- 
Best regards,
  Antony Pavlov

  parent reply	other threads:[~2015-07-02  5:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01  4:12 [Qemu-devel] [PATCH pic32 v2 0/5] Support for Microchip pic32mx7 and pic32mz microcontrollers Serge Vakulenko
     [not found] ` <cover.1435723168.git.serge.vakulenko@gmail.com>
2015-07-01  4:12   ` [Qemu-devel] [PATCH pic32 v2 1/5] Speed of MIPS CPU timer made configurable per platform Serge Vakulenko
2015-07-01 10:02     ` Aurelien Jarno
2015-07-05 23:25       ` Serge Vakulenko
2015-07-06  8:31         ` Aurelien Jarno
2015-07-01  4:12   ` [Qemu-devel] [PATCH pic32 v2 2/5] Fixed random index generation for TLBWR instruction. It was not quite random and did not skip Wired entries Serge Vakulenko
2015-07-01 10:11     ` Aurelien Jarno
2015-07-03 21:39       ` Maciej W. Rozycki
2015-07-06  0:16         ` Serge Vakulenko
2015-07-06  0:03       ` Serge Vakulenko
2015-07-06  8:32         ` Aurelien Jarno
2015-07-02  7:52     ` Antony Pavlov
2015-07-06  0:06       ` Serge Vakulenko
2015-07-01  4:12   ` [Qemu-devel] [PATCH pic32 v2 3/5] Added support for external interrupt controller (EIC) mode Serge Vakulenko
2015-07-01 11:07     ` Aurelien Jarno
2015-07-06  3:05       ` Serge Vakulenko
2015-07-06  3:31         ` Serge Vakulenko
2015-07-06  9:31           ` Aurelien Jarno
2015-07-06  9:28         ` Aurelien Jarno
2015-07-01  4:12   ` [Qemu-devel] [PATCH pic32 v2 4/5] Two new processor variants: M4K and microAptivP Serge Vakulenko
2015-07-01 13:37     ` Aurelien Jarno
2015-07-03 22:04       ` Maciej W. Rozycki
2015-07-06  4:15         ` Serge Vakulenko
2015-07-06  3:48       ` Serge Vakulenko
2015-07-06  8:40         ` Aurelien Jarno
2015-07-01  4:12   ` [Qemu-devel] [PATCH pic32 v2 5/5] Two new machine platforms: pic32mz7 and pic32mz Serge Vakulenko
2015-07-01 13:41     ` Aurelien Jarno
2015-07-06  4:18       ` Serge Vakulenko
2015-07-06  7:33         ` Antony Pavlov
2015-07-06 18:58           ` Serge Vakulenko
2015-07-06 21:43             ` Peter Crosthwaite
2015-07-07  7:30             ` Antony Pavlov
2015-07-07 14:08               ` Aurelien Jarno
2015-07-02  5:56     ` Antony Pavlov
2015-07-06  4:27       ` Serge Vakulenko
2015-07-06  7:55         ` Antony Pavlov
2015-07-02  5:31 ` Antony Pavlov [this message]
2015-07-06  0:39   ` [Qemu-devel] [PATCH pic32 v2 0/5] Support for Microchip pic32mx7 and pic32mz microcontrollers Serge Vakulenko

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=20150702083134.6ee193b130cc4e1922a6e74d@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=aurelien@aurel32.net \
    --cc=leon.alrae@imgtec.com \
    --cc=qemu-devel@nongnu.org \
    --cc=serge.vakulenko@gmail.com \
    /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).