From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Josua Mayer <josua@solid-run.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH RFC] net: sfp: support assigning status LEDs to SFP connectors
Date: Wed, 11 May 2022 11:26:12 +0100 [thread overview]
Message-ID: <YnuPRKRBj/5YbAUQ@shell.armlinux.org.uk> (raw)
In-Reply-To: <YnpW9nSZ2zMAmmq0@lunn.ch>
On Tue, May 10, 2022 at 02:13:42PM +0200, Andrew Lunn wrote:
> > > As far as i'm aware, the in kernel code always has a netdev for each
> > > MAC. Are you talking about the vendor stack?
> > The coprocessor can be configured both at boot-time and runtime.
> > During runtime there is a vendor tool "restool" which can create and destroy
> > network interfaces, which the dpaa2 driver knows to discover and bind to.
>
> There should not be any need to use a vendor tool for mainline. In
> fact, that is strongly discouraged, since it leads to fragmentation,
> each device doing its own thing, the user needing to read each vendors
> user manual, rather than it just being a standard Unix box with
> interfaces.
You're missing the bigger picture.
There are two ways to setup the networking on LX2160A - one is via
DT-like files that are processed by the network firmware, which tells
it what you want to do with each individual network connection.
Then there is a userspace tool that talks to the LX2160A network
firmware and requests it to configure the network layer - e.g. create
a network interface to connect to a network connection, or whatever.
I believe that when using DPDK, one does not want the network
connections to be associated with Linux network interfaces - but
don't quote me on that.
The tool has nothing to do with LEDs. It's all about talking to the
networking firmware on the chip.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-05-11 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:29 [PATCH RFC] net: sfp: support assigning status LEDs to SFP connectors Josua Mayer
2022-05-09 12:49 ` Andrew Lunn
2022-05-10 8:56 ` Josua Mayer
2022-05-10 12:13 ` Andrew Lunn
2022-05-11 10:26 ` Russell King (Oracle) [this message]
2022-05-11 14:48 ` Ioana Ciornei
2022-05-11 10:12 ` Russell King (Oracle)
2022-05-11 15:48 ` Ioana Ciornei
2022-05-18 7:42 ` Josua Mayer
2022-05-09 15:54 ` Russell King (Oracle)
2022-05-10 9:44 ` Josua Mayer
2022-05-11 10:21 ` Russell King (Oracle)
2022-05-11 13:22 ` Ioana Ciornei
2022-05-11 13:39 ` Russell King (Oracle)
2022-06-01 10:18 ` Josua Mayer
2022-06-01 10:52 ` Russell King (Oracle)
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=YnuPRKRBj/5YbAUQ@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=josua@solid-run.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).