[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211208133754.3809bb5e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 8 Dec 2021 13:37:54 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Hayes Wang <hayeswang@...ltek.com>
Cc: "hkallweit1@...il.com" <hkallweit1@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
nic_swsd <nic_swsd@...ltek.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [RFC PATCH 0/4] r8169: support dash
On Wed, 8 Dec 2021 07:53:28 +0000 Hayes Wang wrote:
> Jakub Kicinski <kuba@...nel.org>
> > Sent: Wednesday, December 8, 2021 12:21 PM
> > > Could devlink param be used for more than 4 bytes settings?
> > > At least the IPv6 address is longer.
> >
> > We can add a new devlink sub-command and driver callback in that case.
>
> Excuse me. Do you mean someone will add it? Then, I could use it.
> Or, I have to add it.
You'd need to write all the code.
> > > Besides, we need the information of SMBIOS which could
> > > be 4K ~ 8K bytes data. Is there any way we could transmit
> > > it to firmware?
> >
> > Is structure of that data defined by some DMTF standard?
> Yes.
That's good, as long as the kernel parses and validates the messages
the exact interface to user space does not matter that much.
Powered by blists - more mailing lists