From: Andrew Lunn <andrew@lunn.ch>
To: Dan Murphy <dmurphy@ti.com>
Cc: davem@davemloft.net, f.fainelli@gmail.com, hkallweit1@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: phy: dp83td510: Add support for the DP83TD510 Ethernet PHY
Date: Mon, 19 Oct 2020 23:55:06 +0200 [thread overview]
Message-ID: <20201019215506.GY139700@lunn.ch> (raw)
In-Reply-To: <31cbfec4-3f1c-d760-3035-2ff9ec43e4b7@ti.com>
On Mon, Oct 19, 2020 at 04:33:18PM -0500, Dan Murphy wrote:
> Andrew
>
> On 10/16/20 5:02 PM, Andrew Lunn wrote:
> > On Thu, Oct 08, 2020 at 11:23:47AM -0500, Dan Murphy wrote:
> > > The DP83TD510E is an ultra-low power Ethernet physical layer transceiver
> > > that supports 10M single pair cable.
> > Hi Dan
> >
> > I think you are going to have to add
> > ETHTOOL_LINK_MODE_10baseT1_Full_BIT? We already have 100T1 and 1000T1,
> > but not 10T1 :-(
>
> The data sheet says 10baseT1L. Which is not there either and seems to be
> the latest 802.3cg spec and has a greater max distance and used for IoT and
> Automotive.
Hi Dan
Do you know anything about interropibility? Can a T1 and a T1L talk to
each other, if suitably close? I'm wondering if this device should say
it is both T1 and T1L? Or just T1L?
Andrew
next prev parent reply other threads:[~2020-10-19 21:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:23 [PATCH net-next 0/2] DP83TD510 Single Pair 10Mbps Ethernet PHY Dan Murphy
2020-10-08 16:23 ` [PATCH net-next 1/2] dt-bindings: dp83td510: Add binding for DP83TD510 " Dan Murphy
2020-10-08 17:11 ` Florian Fainelli
2020-10-08 18:18 ` Dan Murphy
2020-10-08 16:23 ` [PATCH net-next 2/2] net: phy: dp83td510: Add support for the " Dan Murphy
2020-10-08 16:51 ` Heiner Kallweit
2020-10-08 17:00 ` Dan Murphy
2020-10-16 22:02 ` Andrew Lunn
2020-10-19 21:33 ` Dan Murphy
2020-10-19 21:55 ` Andrew Lunn [this message]
2020-10-19 22:04 ` Dan Murphy
2020-10-20 12:00 ` Dan Murphy
2020-10-20 13:46 ` Andrew Lunn
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=20201019215506.GY139700@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).