netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Daniel Golle <daniel@makrotopia.org>
Cc: netdev@vger.kernel.org, "René van Dorst" <opensource@vdorst.com>,
	"Felix Fietkau" <nbd@openwrt.org>,
	"Sean Wang" <sean.wang@mediatek.com>,
	linux-mediatek@lists.infradead.org,
	"John Crispin" <john@phrozen.org>
Subject: Re: [PATCH] net: ethernet: mediatek: Add MT7628/88 SoC support
Date: Tue, 13 Aug 2019 15:09:23 +0200	[thread overview]
Message-ID: <b2258258-af40-3e0d-f771-a70428ec798f@denx.de> (raw)
In-Reply-To: <20190717121506.GD18996@makrotopia.org>

On 17.07.19 14:15, Daniel Golle wrote:
> On Wed, Jul 17, 2019 at 01:02:43PM +0200, Stefan Roese wrote:
>> This patch adds support for the MediaTek MT7628/88 SoCs to the common
>> MediaTek ethernet driver. Some minor changes are needed for this and
>> a bigger change, as the MT7628 does not support QDMA (only PDMA).
> 
> The Ethernet core found in MT7628/88 is identical to that found in
> Ralink Rt5350F SoC. Wouldn't it hence make sense to indicate that
> in the compatible string of this driver as well? In OpenWrt we are
> using "ralink,rt5350-eth".

Okay. I'll use this ralink compatible instead in the next version.

Thanks,
Stefan

  parent reply	other threads:[~2019-08-13 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 11:02 [PATCH] net: ethernet: mediatek: Add MT7628/88 SoC support Stefan Roese
2019-07-17 12:15 ` Daniel Golle
2019-07-19  4:06   ` Stefan Roese
2019-08-13 13:09   ` Stefan Roese [this message]
2019-07-17 12:53 ` René van Dorst
2019-08-14  8:26   ` Stefan Roese
2019-08-14  9:26     ` René van Dorst
2019-08-14 10:48       ` Stefan Roese
2019-08-14 13:08         ` René van Dorst
2019-08-15  9:08           ` Stefan Roese
2019-07-18 23:36 ` David Miller
2019-07-19  5:52 ` kbuild test robot

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=b2258258-af40-3e0d-f771-a70428ec798f@denx.de \
    --to=sr@denx.de \
    --cc=daniel@makrotopia.org \
    --cc=john@phrozen.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=nbd@openwrt.org \
    --cc=netdev@vger.kernel.org \
    --cc=opensource@vdorst.com \
    --cc=sean.wang@mediatek.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).