linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Greg Ungerer <gerg@uclinux.org>,
	Waldemar Brodkorb <wbx@openadk.org>,
	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: Fri, 3 Feb 2017 16:17:44 +0100	[thread overview]
Message-ID: <20170203151744.GY11210@waldemar-brodkorb.de> (raw)
In-Reply-To: <d8ae1bac-90c9-3cb3-b6e0-2b2b09cc3db3@vivier.eu>

Hi,
Laurent Vivier wrote,

> Le 03/02/2017 à 01:35, John Paul Adrian Glaubitz a écrit :
> > On 02/03/2017 01:10 AM, Greg Ungerer wrote:
> >> This is a limitation in the FEC support in QEMU.
> >> This works on real ColdFire hardware (which do support the
> >> FEC MIB stats registers from offset 0x200 - so not 5272).
> >> I sent this patch to the qemu dev list a couple of weeks
> >> back which fixes qemu:
> >>
> >>  http://lists.gnu.org/archive/html/qemu-devel/2017-01/msg01781.html
> >>
> >> I do not believe it has been picked up by QEMU mainline yet
> >> (I will probably have to resend and push a little to get that done).
> > 
> > QEMU upstream can sometimes take a while before they are merging patches,
> > but usually it helps containing the maintainer of this part of the
> > source tree directly.
> > 
> > Unfortunately, mcf5208 is currently unmaintained [1]:
> > 
> > mcf5208
> > S: Orphan
> > F: hw/m68k/mcf5208.c
> > F: hw/m68k/mcf_intc.c
> > F: hw/char/mcf_uart.c
> > F: hw/net/mcf_fec.c
> > 
> > But you can try getting into touch with Laurent Vivier who is the
> > new maintainer of the m68k target. I have CC'ed him.
> > 
> > Adrian
> > 
> >> [1] http://git.qemu.org/?p=qemu.git;a=blob;f=MAINTAINERS
> > 
> 
> Use scripts/get_maintainer.pl on your patch to find the people.
> 
> This patch is on the network part, so you should cc:
> Jason Wang <jasowang@redhat.com> (odd fixer:Network devices)
> 
> If you cc me, you add more chances to have a review ;)

I tried the patch on top of 2.8.0 qemu release and it works for me
with Linux Kernel 4.9.
Thanks for the hint and patch!
I hope Greg's patch get included in the next qemu release.

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.

best regards
 Waldemar

  reply	other threads:[~2017-02-03 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 20:15 regression for m68k/coldfire Waldemar Brodkorb
2017-02-02 20:21 ` Nikita Yushchenko
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 [this message]
2017-02-03 15:22         ` Laurent Vivier
2017-02-04  2:03           ` Greg Ungerer
2017-02-04  9:49             ` Laurent Vivier
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=20170203151744.GY11210@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=laurent@vivier.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=nikita.yoush@cogentembedded.com \
    --cc=uclinux-dev@uclinux.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).