From: Stephen Hemminger <stephen@networkplumber.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: "Pali Rohár" <pali@kernel.org>,
"Sean Anderson" <sean.anderson@seco.com>,
"Michal Suchánek" <msuchanek@suse.de>,
netdev <netdev@vger.kernel.org>, u-boot <u-boot@lists.denx.de>,
"Device Tree Mailing List" <devicetree@vger.kernel.org>
Subject: Re: ethernet<n> dt aliases implications in U-Boot and Linux
Date: Tue, 9 Aug 2022 14:58:44 -0700 [thread overview]
Message-ID: <20220809145844.3048fa9c@hermes.local> (raw)
In-Reply-To: <CAJ+vNU3bFNRiyhV_w_YWP+sjMTpU28PsX=BTkT7_Q=79=yR1gg@mail.gmail.com>
On Tue, 9 Aug 2022 14:39:05 -0700
Tim Harvey <tharvey@gateworks.com> wrote:
> > Maybe it would be better first to use "label" and then use ethernet alias?
>
> I've been wondering the same as well which made me wonder what the
> history of the 'aliases' node is and why its not used in most cases in
> Linux. I know for the SOC's I work with we've always defined aliases
> for ethernet<n>, gpio<n>, serial<n>, spi<n>, i2c<n>, mmc<n> etc. Where
> did this practice come from and why are we putting that in Linux dts
> files it if it's not used by Linux?
>
> Best Regards,
>
> Tim
I added ifalias as part of better SNMP support.
In telco and router equipment they report the type/topology information
as ifAlias in MIB.
In Vyatta distribution this was set to information that came from
the pci subsystem for typical network PCI devices.
Recent distributions added altname support to allow for alternative
or longer names.
next prev parent reply other threads:[~2022-08-09 21:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 19:18 ethernet<n> dt aliases implications in U-Boot and Linux Tim Harvey
2022-08-08 19:57 ` Sean Anderson
2022-08-08 21:09 ` Michal Suchánek
2022-08-08 21:38 ` Stephen Hemminger
2022-08-08 21:45 ` Michal Suchánek
2022-08-09 20:48 ` Sean Anderson
2022-08-09 21:31 ` Pali Rohár
2022-08-09 21:36 ` Sean Anderson
2022-08-09 21:42 ` Pali Rohár
2022-08-09 22:41 ` Sean Anderson
2022-08-09 22:42 ` Tim Harvey
2022-08-09 22:45 ` Pali Rohár
2022-08-09 23:17 ` Tim Harvey
2022-08-10 1:11 ` Andrew Lunn
2022-08-10 7:16 ` Michal Suchánek
2022-08-10 15:17 ` Andrew Lunn
2022-08-10 15:35 ` Michal Suchánek
2022-08-11 19:43 ` Sean Anderson
2022-08-20 9:16 ` Pali Rohár
2022-08-20 13:02 ` Sean Anderson
2022-08-09 21:39 ` Tim Harvey
2022-08-09 21:45 ` Pali Rohár
2022-08-09 21:58 ` Stephen Hemminger [this message]
2022-08-10 9:56 ` Francesco Dolcini
2022-08-23 19:21 ` Rob Herring
2022-08-09 21:35 ` Tim Harvey
2022-08-09 21:41 ` Sean Anderson
2022-08-08 21:18 ` Tim Harvey
2022-08-08 21:18 ` Florian Fainelli
2022-08-08 21:28 ` Tim Harvey
2022-08-08 21:34 ` Florian Fainelli
2022-08-08 21:40 ` Tim Harvey
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=20220809145844.3048fa9c@hermes.local \
--to=stephen@networkplumber.org \
--cc=devicetree@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=netdev@vger.kernel.org \
--cc=pali@kernel.org \
--cc=sean.anderson@seco.com \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
/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).