From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
netdev@vger.kernel.org, Chris Healy <cphealy@gmail.com>,
"John W . Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 0/7] ethtool: add pretty dump for DSA mv88e6xxx drivers
Date: Sun, 16 Dec 2018 21:00:26 +0100 [thread overview]
Message-ID: <20181216200026.GA29825@lunn.ch> (raw)
In-Reply-To: <a2258189-41c4-b0e1-308b-99760143dda7@gmail.com>
> > Hi Florian, Vivien
> >
> > I was wondering about that. Having this all under 'dsa' seems too
> > granular. It would be better if we could have 'mv88e6xxx', 'b53',
> > 'ksz', etc. That might need a new DSA driver op to get the driver name
> > which we then use for the slave?
>
> We could indeed do that, the other option would be return something
> like: "dsa-mv88e6xxx" or "dsa-b53" in ethtool::get_drv_info() but this
> might be breaking ABI since "dsa" has been commonly established for the
> past 10 years or so.
>
> Changing things within ethtool is reasonably easy, but we probably need
> to decide now whether kernel changes are requited to assist with
> companion ethtool changes.
Hi Florian, Vivien
Using reg[3] is not very robust. Some of the other devices could have
a value which happens to be a Marvell ID.
As you said, driver="DSA" is well established, so we probably don't
want to change that.
We could use the version string. We currently don't have a value in
it. It would a bit unusual, but actually kind of fits to have the
mv88ex6xxx version, b53 version, ksz version, of DSA.
Andrew
next prev parent reply other threads:[~2018-12-16 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 2:50 [PATCH 0/7] ethtool: add pretty dump for DSA mv88e6xxx drivers Vivien Didelot
2018-12-15 2:50 ` [PATCH 1/7] ethtool: dsa: add pretty dump Vivien Didelot
2018-12-15 2:50 ` [PATCH 2/7] ethtool: dsa: mv88e6xxx: " Vivien Didelot
2018-12-15 2:50 ` [PATCH 3/7] ethtool: dsa: mv88e6xxx: add pretty dump for 88E6185 Vivien Didelot
2018-12-15 2:50 ` [PATCH 4/7] ethtool: dsa: mv88e6xxx: add pretty dump for 88E6161 Vivien Didelot
2018-12-15 2:50 ` [PATCH 5/7] ethtool: dsa: mv88e6xxx: add pretty dump for 88E6352 Vivien Didelot
2018-12-15 2:50 ` [PATCH 6/7] ethtool: dsa: mv88e6xxx: add pretty dump for 88E6390 Vivien Didelot
2018-12-15 2:50 ` [PATCH 7/7] ethtool: dsa: mv88e6xxx: pretty dump others Vivien Didelot
2018-12-15 17:28 ` [PATCH 0/7] ethtool: add pretty dump for DSA mv88e6xxx drivers Florian Fainelli
2018-12-15 17:48 ` Andrew Lunn
2018-12-16 18:02 ` Florian Fainelli
2018-12-16 20:00 ` Andrew Lunn [this message]
2018-12-16 18:03 ` Vivien Didelot
2018-12-16 17:57 ` Vivien Didelot
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=20181216200026.GA29825@lunn.ch \
--to=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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 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.