From: "Félix Piédallu" <felix@piedallu.me>
To: andrew@lunn.ch
Cc: davem@davemloft.net, edumazet@google.com, hkallweit1@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk, netdev@vger.kernel.org, pabeni@redhat.com,
ramon.nordin.rodriguez@ferroamp.se
Subject:
Date: Tue, 5 Dec 2023 11:20:39 +0100 [thread overview]
Message-ID: <20231205102039.2917039-1-felix@piedallu.me> (raw)
In-Reply-To: <f25ed798-e116-4f6f-ad3c-5060c7d540d0@lunn.ch>
Subject: Re: [PATCH 2/3] net: microchip_t1s: add support for LAN867x Rev.C1
Hi,
> So there is a gap in the revisions. Maybe a B2 exists?
Actually, probably not. Some search gives this datasheet:
https://ww1.microchip.com/downloads/aemDocuments/documents/AIS/ProductDocuments/DataSheets/LAN8670-1-2-Data-Sheet-60001573.pdf
And page 2 (table 1) shows only revisions A0 (rev0), B1, (rev2), C1 (rev4).
Not sure about why only even revision numbers are released ?
Page 193 (table 10-1) also shows only B1 and C1. So you can be confident that only those exist.
@Ramón, thank you for your work on this driver!
Félix Piédallu
next prev parent reply other threads:[~2023-12-05 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 10:40 [PATCH 0/3] net: microchip_t1s: additional phy support and collision detect handling Ramón N.Rodriguez
2023-11-27 10:40 ` [PATCH 1/3] net: microchip_t1s: refactor reset functionality Ramón N.Rodriguez
2023-11-27 13:27 ` Andrew Lunn
2023-11-27 10:40 ` [PATCH 2/3] net: microchip_t1s: add support for LAN867x Rev.C1 Ramón N.Rodriguez
2023-11-27 13:37 ` Andrew Lunn
2023-11-27 14:02 ` Ramón Nordin Rodriguez
2023-12-05 10:20 ` Félix Piédallu [this message]
2023-12-06 20:58 ` Ramón Nordin Rodriguez
2023-11-27 10:40 ` [PATCH 3/3] net: microchip_t1s: conditional collision detection Ramón N.Rodriguez
2023-11-27 16:00 ` Parthiban.Veerasooran
2023-11-27 16:32 ` Ramón Nordin Rodriguez
2023-11-28 6:52 ` Parthiban.Veerasooran
2023-11-28 9:18 ` Ramón Nordin Rodriguez
2023-11-27 13:58 ` [PATCH 0/3] net: microchip_t1s: additional phy support and collision detect handling Andrew Lunn
2023-11-27 15:30 ` Ramón Nordin Rodriguez
2023-11-27 16:03 ` Andrew Lunn
2023-11-28 8:57 ` Ramón Nordin Rodriguez
2023-12-10 12:10 ` Ramón Nordin Rodriguez
2023-12-11 13:54 ` 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=20231205102039.2917039-1-felix@piedallu.me \
--to=felix@piedallu.me \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ramon.nordin.rodriguez@ferroamp.se \
/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).