From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 217922] New: FEC driver not working for imx7dea-com board from kernel 6.1 or later
Date: Mon, 18 Sep 2023 08:06:33 -0700 [thread overview]
Message-ID: <20230918080633.02d5ed06@hermes.local> (raw)
Begin forwarded message:
Date: Mon, 18 Sep 2023 11:51:45 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 217922] New: FEC driver not working for imx7dea-com board from kernel 6.1 or later
https://bugzilla.kernel.org/show_bug.cgi?id=217922
Bug ID: 217922
Summary: FEC driver not working for imx7dea-com board from
kernel 6.1 or later
Product: Networking
Version: 2.5
Hardware: ARM
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: stephen@networkplumber.org
Reporter: m-seo@ukr.net
Regression: No
Fast ethernet controller driver (fec) for imx7d cpu not working in kernel 6.1
or later.
Boot kernel error is:
[ 1.860925] fec: probe of 30be0000.ethernet failed with error -12.
Kernel version from github:
https://github.com/embeddedartists/linux-imx/tree/ea_6.1.y
start driver succsessfully:
[ 1.401249] fec 30be0000.ethernet eth0: registered PHC device 0
but have other problems to boot system.
Driver sources from embeddedartists repository compiled succsessfully with
small adjust of header files on kernel version 6.5.3. But fec driver failed
with error -12 too.
DTB file working successfully on kernel 5.15 and not changed now for kernel 6.1
- 6.5.
Where is mistake, who is use imx7d cpu with 6.1-6.5 kernel sucsessfully?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2023-09-18 15:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230918080633.02d5ed06@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.