From: "Василий Ковалев" <kovalevvv@basealt.ru>
To: "Neftin, Sasha" <sasha.neftin@intel.com>,
kovalev@altlinux.org, nickel@altlinux.org,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, kuba@kernel.org,
jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, "Ruinskiy,
Dima" <dima.ruinskiy@intel.com>,
"Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>,
"naamax.meir" <naamax.meir@linux.intel.com>
Subject: Re: [PATCH] e1000e: Fix bind network card with ID = 0x0D4F
Date: Sun, 14 May 2023 10:59:44 +0300 [thread overview]
Message-ID: <6894e9f7-7100-255b-b026-5ccf485a7e31@basealt.ru> (raw)
In-Reply-To: <c9ef1c57-3ec5-5cf8-c025-63527280f2fa@intel.com>
14.05.2023 09:00, Neftin, Sasha пишет:
>> Fixes: 914ee9c436cbe9 ("e1000e: Add support for Comet Lake")
>> Signed-off-by: Vasiliy Kovalev <kovalev@altlinux.org>
>> ---
>> drivers/net/ethernet/intel/e1000e/netdev.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c
>> b/drivers/net/ethernet/intel/e1000e/netdev.c
>> index db8e06157da29..8b13f19309c39 100644
>> --- a/drivers/net/ethernet/intel/e1000e/netdev.c
>> +++ b/drivers/net/ethernet/intel/e1000e/netdev.c
>> @@ -7887,7 +7887,7 @@ static const struct pci_device_id
>> e1000_pci_tbl[] = {
>> { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_ICP_I219_LM9),
>> board_pch_cnp },
>> { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_ICP_I219_V9),
>> board_pch_cnp },
>> { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_CMP_I219_LM10),
>> board_pch_cnp },
>> - { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_CMP_I219_V10),
>> board_pch_cnp },
>> + { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_CMP_I219_V10),
>> board_pch_adp },
> This is wrong approach. (we can not process old board similar as new)
>> { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_CMP_I219_LM11),
>> board_pch_cnp },
>> { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_CMP_I219_V11),
>> board_pch_cnp },
>> { PCI_VDEVICE(INTEL, E1000_DEV_ID_PCH_CMP_I219_LM12),
>> board_pch_spt },
> Looking in commit 639e298f432fb0 (e1000e: Fix packet loss on Tiger
> Lake and later) I would suggest to replace the mac->type as follow:
> "if (mac->type >= e1000_pch_tgp)" with "if (mac->type >=
> e1000_pch_cnp)" (more correct) - try it on your side.
I checked this variant first of all - the behavior is correct, network
packets are not lost. Can I prepare a new patch or will this change be
made by you?
--
Best regards,
Vasiliy Kovalev
prev parent reply other threads:[~2023-05-14 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 23:19 kovalev
[not found] ` <c9ef1c57-3ec5-5cf8-c025-63527280f2fa@intel.com>
2023-05-14 7:59 ` Василий Ковалев [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=6894e9f7-7100-255b-b026-5ccf485a7e31@basealt.ru \
--to=kovalevvv@basealt.ru \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=devora.fuxbrumer@intel.com \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kovalev@altlinux.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=nickel@altlinux.org \
--cc=pabeni@redhat.com \
--cc=sasha.neftin@intel.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
all inboxes | Powered by JetHome®