From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40915) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6xW6-0005Ck-Qb for qemu-devel@nongnu.org; Mon, 22 Jun 2015 04:55:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z6xW0-0003IF-33 for qemu-devel@nongnu.org; Mon, 22 Jun 2015 04:55:46 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:63676) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6xVz-0003I5-PX for qemu-devel@nongnu.org; Mon, 22 Jun 2015 04:55:40 -0400 Message-ID: <5587CD82.8010308@vivier.eu> Date: Mon, 22 Jun 2015 10:55:30 +0200 From: Laurent Vivier MIME-Version: 1.0 References: <1434926106-5905-1-git-send-email-laurent@vivier.eu> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 0/2] m68k: 680x0 processors family support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Andreas Schwab , QEMU Developers , Greg Ungerer Le 22/06/2015 10:33, Peter Maydell a écrit : > On 21 June 2015 at 23:35, Laurent Vivier 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