From: "jeffrey.tseng (曾弘)" <jeffrey.tseng@gigabyte.com>
To: "michael@walle.cc" <michael@walle.cc>
Cc: "pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [Intel-wired-lan] [PATCH v2] PCI: Fix Intel i210 by avoiding overlapping of BARs
Date: Mon, 17 Oct 2022 01:42:01 +0000 [thread overview]
Message-ID: <54ee7db66ef04f11ac74dbb5832a8c12@gigabyte.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 669 bytes --]
Hi
Here is my question.
My platform : imx8mm
Ethernet Control : Intel I210
Linux version 5.10.72-lts-5.10.y+g22ec7e8cbace (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2. UTC 2011
I follow this https://lore.kernel.org/linux-pci/20201230185317.30915-1-michael@walle.cc/
to add the patch in my platform.
The issue and problem is still there. Anyone can give me a hand ?
thank you
jeffrey
Best Regards,
Jeffrey Tseng 曾弘
技嘉科技 GIGABYTE
新北市新店區北新路三段213號11樓
電話: 02-89787668 ext. 556
Mobile : 0952432332
line : 0952432332
E-mail: jeffrey.tseng@gigabyte.com<mailto:jeffrey.tseng@gigabyte.com>
[-- Attachment #1.2: Type: text/html, Size: 4998 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-10-17 13:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 1:42 jeffrey.tseng (曾弘) [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-30 18:53 [Intel-wired-lan] [PATCH v2] PCI: Fix Intel i210 by avoiding overlapping of BARs Michael Walle
2021-01-08 21:20 ` Bjorn Helgaas
2021-01-09 18:31 ` Michael Walle
2021-01-12 22:58 ` Bjorn Helgaas
2021-01-12 23:32 ` Michael Walle
2021-01-15 23:57 ` Bjorn Helgaas
2021-01-17 19:27 ` Michael Walle
2021-02-01 19:49 ` Michael Walle
2021-02-01 22:20 ` Bjorn Helgaas
2021-03-15 21:51 ` Michael Walle
2021-08-20 15:12 ` Michael Walle
2021-12-20 17:43 ` Michael Walle
2021-12-21 17:48 ` Bjorn Helgaas
2021-12-23 9:27 ` Michael Walle
2021-12-23 16:37 ` Bjorn Helgaas
2021-12-23 18:12 ` Michael Walle
2022-01-12 14:50 ` Bjorn Helgaas
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=54ee7db66ef04f11ac74dbb5832a8c12@gigabyte.com \
--to=jeffrey.tseng@gigabyte.com \
--cc=bhelgaas@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael@walle.cc \
--cc=pmenzel@molgen.mpg.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