Netdev List
 help / color / mirror / Atom feed
From: Philipp Rossak <embed3d@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	netdev@vger.kernel.org, qiangqing.zhang@nxp.com,
	philipp.rossak@formulastudent.de
Subject: Re: Question: Ethernet Phy issues on Colibri IMX8X (imx8qxp) - kernel 5.19
Date: Wed, 10 Aug 2022 09:20:17 +0200	[thread overview]
Message-ID: <48b9ecb8-5685-4ffe-b543-637f711be70e@gmail.com> (raw)
In-Reply-To: <YvMHp0K65a/L0pa4@lunn.ch>



On 10.08.22 03:19, Andrew Lunn wrote:
> On Wed, Aug 10, 2022 at 12:55:58AM +0200, Philipp Rossak wrote:
>> Hi,
>>
>> I currently have a project with a Toradex Colibri IMX8X SOM board whith an
>> onboard Micrel KSZ8041NL Ethernet PHY.
>>
>> The hardware is described in the devictree properly so I expected that the
>> onboard Ethernet with the phy is working.
>>
>> Currently I'm not able to get the link up.
>>
>> I already compared it to the BSP kernel, but I didn't found anything
>> helpful. The BSP kernel is working.
>>
>> Do you know if there is something in the kernel missing and got it running?
> 
> dmesg output might be useful.
> 
> Do you have the micrel driver either built in, or in your initramfs
> image?
> 
> 	Andrew

Hi Andrew,

the driver is built in.

In [1] you find the dmesg log from the 5.19 kernel. I also added the 
DEBUG built flag for the relevant phy and network drivers.

As reference the bsp kernel 5.4.129 kernel [3] works without issues as 
you can see in [2].

Thanks,
Philipp

[1] https://pastebin.com/g4XKw5yY
[2] https://pastebin.com/5t8iAAEu
[3] 
https://git.toradex.com/cgit/linux-toradex.git/tree/?h=toradex_5.4-2.3.x-imx

  reply	other threads:[~2022-08-10  7:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 22:55 Question: Ethernet Phy issues on Colibri IMX8X (imx8qxp) - kernel 5.19 Philipp Rossak
2022-08-10  1:19 ` Andrew Lunn
2022-08-10  7:20   ` Philipp Rossak [this message]
2022-08-10  8:05 ` Marcel Ziswiler
2022-08-10  8:49   ` Aisheng Dong
2022-08-10 18:40   ` Philipp Rossak
2022-08-11  8:07     ` Philippe Schenker
2022-08-31  8:12       ` Marcel Ziswiler

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=48b9ecb8-5685-4ffe-b543-637f711be70e@gmail.com \
    --to=embed3d@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=philipp.rossak@formulastudent.de \
    --cc=qiangqing.zhang@nxp.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