From: Laurent Vivier <laurent@vivier.eu>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] m68k: 680x0 processors family support
Date: Mon, 22 Jun 2015 10:55:30 +0200 [thread overview]
Message-ID: <5587CD82.8010308@vivier.eu> (raw)
In-Reply-To: <CAFEAcA98u-=3PeOhtnPx1oLmeqo8=sKLae7XGrsDqb7grK3GRA@mail.gmail.com>
Le 22/06/2015 10:33, Peter Maydell a écrit :
> On 21 June 2015 at 23:35, Laurent Vivier <laurent@vivier.eu> wrote:
>> I carry this series for several years now.
>>
>> I was reluctant to merge it with the mainstream because
>> I was sure it was breaking Coldfire support.
>>
>> But with the kernel provided by Greg Ungerer I was able
>> to check and correct the support of ColdFire family
>> in my tree.
>>
>> This series allows:
>> - to start a ColdFire semi-hosted kernel (m68k-softmmu)
>> - chroot or start a container of debian etch-m68k (m68k-linux-user)
>>
>> I have another series providing privileged instructions and
>> allowing to boot a 680x0 debian kernel (Macintosh Quadra 800),
>> but this one needs more work (and love). Based on this work,
>> we will also be able to boot a NextStation (Bryce Lanham, GSoC)
>>
>> This work is based on the work of Andreas Schwab.
>>
>> Laurent Vivier (2):
>> m68k: Add compatibility with 680x0 processors family
>> m68k: Implement 680x0 processors family 96 bit FPU
>>
>> configure | 2 +-
>> cpu-exec.c | 6 -
>> disas.c | 4 +
>> fpu/softfloat-specialize.h | 48 +-
>> fpu/softfloat.c | 38 +-
>> gdb-xml/m68k-fp.xml | 21 +
>> include/fpu/softfloat.h | 11 +-
>> target-m68k/cpu.c | 67 +-
>> target-m68k/cpu.h | 76 +-
>> target-m68k/helper.c | 1691 ++++++++++++++++++--
>> target-m68k/helper.h | 100 +-
>> target-m68k/m68k-qreg.h | 11 -
>> target-m68k/op_helper.c | 182 ++-
>> target-m68k/qregs.def | 6 +-
>> target-m68k/translate.c | 3682 +++++++++++++++++++++++++++++++++++---------
>> 15 files changed, 5013 insertions(+), 932 deletions(-)
>> create mode 100644 gdb-xml/m68k-fp.xml
>> delete mode 100644 target-m68k/m68k-qreg.h
>
> Thanks for sending this. My initial feeling is that this would
> really benefit from being split up into more patches to make
> it easier to review.
Thank you Peter, I understand.
In fact, in my tree, I have 160 commits I have merged in two big ones
;-) (some are new features, other bug fixes).
So, no problem, just define the granularity, I will create the patches
accordingly.
Is it possible to integrate them little by little ?
I really want to see my patches stack to decrease.
Laurent
next prev parent reply other threads:[~2015-06-22 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 22:35 [Qemu-devel] [PATCH 0/2] m68k: 680x0 processors family support Laurent Vivier
2015-06-21 22:35 ` [Qemu-devel] [PATCH 1/2] m68k: Add compatibility with 680x0 processors family Laurent Vivier
2015-06-21 22:35 ` [Qemu-devel] [PATCH 2/2] m68k: Implement 680x0 processors family 96 bit FPU Laurent Vivier
2015-06-22 8:00 ` Andreas Schwab
2015-06-22 8:33 ` [Qemu-devel] [PATCH 0/2] m68k: 680x0 processors family support Peter Maydell
2015-06-22 8:55 ` Laurent Vivier [this message]
2015-06-22 10:05 ` Peter Maydell
2015-06-22 12:06 ` Greg Ungerer
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=5587CD82.8010308@vivier.eu \
--to=laurent@vivier.eu \
--cc=gerg@uclinux.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=schwab@linux-m68k.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).