From: achraf boussetta <boussettaachraf26@gmail.com>
To: Patryk <pbiel7@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: PHY drivers
Date: Thu, 29 Feb 2024 08:02:38 +0100 [thread overview]
Message-ID: <CAA22Xg7+a9Cu2=YQ_Sz3EyOztZpBuZv_HDwW2qFSMSzw8OYAAA@mail.gmail.com> (raw)
In-Reply-To: <CA+DkFDaP5vagpB0k91Y6yGD_OAnQsKOkWd0msrY+=PUNny4DjA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
Yes, a generic software reads at first the ID of the Phy using MDIO and
then if an ID has matched specific functions will be called.
Take a look at the realtek file for your reference:
https://elixir.bootlin.com/linux/latest/source/drivers/net/phy/realtek.c#L882
On Wed, 28 Feb 2024 at 15:49, Patryk <pbiel7@gmail.com> wrote:
> Hi, I've got a question regarding phy drivers. Supposed that I want to use
> an ethernet phy device - in general - do I need a specific driver to
> handle this, or is it handled by some generic eth phy layer that can
> configure (through MDIO) and exchange data (through XMII) in a generic,
> vendor-agnostic way?
>
> Best regards
> Patryk
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 1497 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-02-29 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:48 PHY drivers Patryk
2024-02-29 7:02 ` achraf boussetta [this message]
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='CAA22Xg7+a9Cu2=YQ_Sz3EyOztZpBuZv_HDwW2qFSMSzw8OYAAA@mail.gmail.com' \
--to=boussettaachraf26@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=pbiel7@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).