From: "Köry Maincent" <kory.maincent@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: PoE support
Date: Tue, 12 Sep 2023 15:25:13 +0200 [thread overview]
Message-ID: <20230912152513.6dba998a@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20230912110637.GI780075@pengutronix.de>
On Tue, 12 Sep 2023 13:06:37 +0200
Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> > What do you think? Do you think of a better way?
>
> By defining UAPI for PoDL/PoE I decided to follow IEEE 802.3
> specification as close as possible for following reasons:
> - we should be backwards and forwards compatible. IEEE 802.3 is always
> extended, some existing objects and name spaces can be extended
> withing the specification. If we will merge some of them, it may get
> challenging to make it properly again.
> - PoDL and PoE have separate attributes and actions withing the
> specification.
> - If we follow the spec, it is easier to understand for all who need to
> implement or extend related software
> - I can imagine some industrial device implementing PoDL/PoE on same
> port. We should be able to see what is actually active.
>
> IMO, it is better not to mix PoDL and PoE name spaces and keep it as
> close as possible to the IEEE 802.3.
> Same is about ethtool interface.
Ok, it will add more code duplication but indeed, it will be more flexible
for future standard evolution. I will go for this solution then.
prev parent reply other threads:[~2023-09-12 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:26 PoE support Köry Maincent
2023-09-12 11:06 ` Oleksij Rempel
2023-09-12 13:25 ` Köry Maincent [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=20230912152513.6dba998a@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=thomas.petazzoni@bootlin.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