From: Hayes Wang <hayeswang@realtek•com>
To: "Marek Behún" <kabel@kernel•org>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"linux-usb@vger•kernel.org" <linux-usb@vger•kernel.org>,
nic_swsd <nic_swsd@realtek•com>
Subject: RE: [PATCH net-next 1/5] r8152: use generic USB macros to define product table
Date: Wed, 4 Nov 2020 07:14:55 +0000 [thread overview]
Message-ID: <2c5c23b4cbae499e82a307b95685fed1@realtek.com> (raw)
In-Reply-To: <20201104070251.52fe638e@kernel.org>
Marek Behún <kabel@kernel•org>
> Sent: Wednesday, November 4, 2020 2:03 PM
[...]
> BTW Hayes, is it possible for me gaining access to Realtek
> documentation for these chips under NDA? For example via my employer,
> CZ.NIC? I can't find any such information on Realtek website.
I have to ask my boss.
Maybe I reply you in private when I get the answer.
> Also I could not download the driver from Realtek's website, I had to
> find it on github. When clicking the download button on [1], it says:
> Warning
> The form #10 does not exist or it is not published.
I try to download the driver from our website.
And it seem to work fine.
I will send it to you later.
> BTW2 I am interested whether we can make the internal PHY visible to
> the Linux PHY subsystem.
I think it is possible.
I am not familiar with the Linux PHY subsystem, so I have no idea about
how to start.
Best Regards,
Hayes
next prev parent reply other threads:[~2020-11-04 7:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 19:22 [PATCH net-next 0/5] r8152 changes Marek Behún
2020-11-03 19:22 ` [PATCH net-next 1/5] r8152: use generic USB macros to define product table Marek Behún
2020-11-04 1:57 ` Hayes Wang
2020-11-04 6:02 ` Marek Behún
2020-11-04 7:14 ` Hayes Wang [this message]
2020-11-04 8:53 ` Greg KH
2020-11-03 19:22 ` [PATCH net-next 2/5] r8152: cosmetic improvement of product table macro Marek Behún
2020-11-03 19:22 ` [PATCH net-next 3/5] r8152: add MCU typed read/write functions Marek Behún
2020-11-03 21:47 ` Vladimir Oltean
2020-11-04 5:55 ` Marek Behún
2020-11-04 8:47 ` Vladimir Oltean
2020-11-04 10:25 ` Marek Behún
2020-11-04 10:35 ` Marek Behún
2020-11-04 11:00 ` Vladimir Oltean
2020-11-04 11:10 ` Marek Behún
2020-11-04 12:14 ` Vladimir Oltean
2020-11-04 21:07 ` Jakub Kicinski
2020-11-05 9:54 ` Marek Behún
2020-11-05 10:56 ` Vladimir Oltean
2020-11-05 11:30 ` Marek Behún
2020-11-05 12:06 ` Vladimir Oltean
2020-11-06 3:01 ` Hayes Wang
2020-11-06 6:39 ` Marek Behún
2020-11-06 7:39 ` Hayes Wang
2020-11-03 19:22 ` [PATCH net-next 4/5] r8152: rename r8153_phy_status to r8153_phy_status_wait Marek Behún
2020-11-03 19:22 ` [PATCH net-next 5/5] r8152: use *_modify helpers instead of read/write combos Marek Behún
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=2c5c23b4cbae499e82a307b95685fed1@realtek.com \
--to=hayeswang@realtek$(echo .)com \
--cc=kabel@kernel$(echo .)org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nic_swsd@realtek$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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