All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Greg Ungerer <gerg@uclinux.org>
Cc: Waldemar Brodkorb <wbx@openadk.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
	linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
	uclinux-dev@uclinux.org, geert@linux-m68k.org
Subject: Re: regression for m68k/coldfire
Date: Sat, 4 Feb 2017 10:49:54 +0100	[thread overview]
Message-ID: <0ae968cb-9870-0247-fd16-78e113256bfc@vivier.eu> (raw)
In-Reply-To: <9e1036e6-5e75-6b7b-4387-9360826e2620@uclinux.org>

Le 04/02/2017 à 03:03, Greg Ungerer a écrit :
> Hi Laurent,
> 
> On 04/02/17 01:22, Laurent Vivier wrote:
>> Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
> [snip]
>>> Btw: Laurent, are you m68k with mmu support are going to be included
>>> upstream? I always carry an old binary for any m68k with mmu testing.
>>
>> I'm working to have the FPU included for now, that will allow to have
>> the linux-user qemu enabled for 680x0 upstream.
>>
>> I have a 68040 MMU implementation that I will send after this step.
>> I didn't have a look to the ColdFire MMU (is there one?), but as 68040
>> is not the same as the 68030 one, I don't expect it works with coldfire.
> 
> There is a ColdFire MMU in some v4 ColdFire parts, for example
> the 547x, 548x, 5441x and 5445x families. It is not compatible with
> the older 68020/86030/68040 MMU. It is supported in mainline Linux -
> at least for the 547x and 548x parts.
> 
> It would be really nice to have support for ColdFire MMU in QEMU :-)

I can work on this. Do you have a Coldfire distro I can install?

Thanks,
Laurent

  reply	other threads:[~2017-02-04  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 20:15 regression for m68k/coldfire Waldemar Brodkorb
2017-02-02 20:15 ` Waldemar Brodkorb
2017-02-02 20:21 ` Nikita Yushchenko
2017-02-03  0:10 ` Greg Ungerer
2017-02-03  0:10   ` Greg Ungerer
2017-02-03  0:35   ` John Paul Adrian Glaubitz
2017-02-03  8:18     ` Laurent Vivier
2017-02-03 15:17       ` Waldemar Brodkorb
2017-02-03 15:22         ` Laurent Vivier
2017-02-04  2:03           ` Greg Ungerer
2017-02-04  2:03             ` Greg Ungerer
2017-02-04  9:49             ` Laurent Vivier [this message]
2017-02-06 11:40               ` 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=0ae968cb-9870-0247-fd16-78e113256bfc@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=nikita.yoush@cogentembedded.com \
    --cc=uclinux-dev@uclinux.org \
    --cc=wbx@openadk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.