From: Hayes Wang <hayeswang@realtek.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC PATCH 0/4] r8169: support dash
Date: Tue, 7 Dec 2021 07:28:02 +0000 [thread overview]
Message-ID: <e2fd429a489545e7a521283600cb7caa@realtek.com> (raw)
In-Reply-To: <20211203070410.1b4abc4d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Jakub Kicinski <kuba@kernel.org>
> Sent: Friday, December 3, 2021 11:04 PM
[...]
> Ah, I've only spotted the enable/disable knob in the patch.
> If you're exchanging arbitrary binary data with the FW we
> can't help you. It's not going to fly upstream.
How is it that we only provide certain basic settings,
such as IPv4 address, IPv6 address, and so on? Then,
they are not the arbitrary binary data.
Could devlink param be used for more than 4 bytes settings?
At least the IPv6 address is longer.
Besides, we need the information of SMBIOS which could
be 4K ~ 8K bytes data. Is there any way we could transmit
it to firmware?
Best Regards,
Hayes
next prev parent reply other threads:[~2021-12-07 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211129101315.16372-381-nic_swsd@realtek.com>
2021-11-29 17:59 ` [Intel-wired-lan] [RFC PATCH 0/4] r8169: support dash Jakub Kicinski
2021-12-01 2:57 ` Hayes Wang
2021-12-01 3:09 ` Jakub Kicinski
2021-12-03 7:57 ` Hayes Wang
2021-12-03 15:04 ` Jakub Kicinski
2021-12-04 1:08 ` Alexander Lobakin
2021-12-04 1:32 ` Jakub Kicinski
2021-12-07 7:28 ` Hayes Wang [this message]
2021-12-08 4:21 ` Jakub Kicinski
2021-12-08 7:53 ` Hayes Wang
2021-12-08 21:37 ` Jakub Kicinski
2021-12-09 7:14 ` Hayes Wang
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=e2fd429a489545e7a521283600cb7caa@realtek.com \
--to=hayeswang@realtek.com \
--cc=intel-wired-lan@osuosl.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