Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@wolfvision.net>
To: Doug Brewer <brewer.doug@gmail.com>
Cc: linux-rockchip@lists.infradead.org
Subject: Re: Problems about NIC, PCIe and usb on RK3568 EVB
Date: Wed, 19 Apr 2023 12:18:05 +0200	[thread overview]
Message-ID: <460114da-d864-0cdb-e482-560f57bf7781@wolfvision.net> (raw)
In-Reply-To: <CAG0V13S4EdYmx-hkpsq-iexwXMOa6e4qcV5_E7XjwYdFYO+CnA@mail.gmail.com>

Hi Doug,

On 4/19/23 07:47, Doug Brewer wrote:
> [...]
>>>>>>> On 4/13/23 07:55, Doug Brewer wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I tested Linux kernel 6.3-rc6 on my rk3568 evaluation board, it seems there
>>>>>>>> are problems with Ethernet, PCIe and usb devices.

PCIe is addressed in a separate thread. As to USB, everything in the log
seems to be normal -- at least the root hubs should show up in lsusb.
Please add the output of lsusb for the sake of completeness.
>>>>>>>> First, NICs doesn't work.
> [...]
>>>>>>>> mdio_bus stmmac-1: MDIO device at address 0 is missing.
Can you try setting CONFIG_REALTEK_PHY=m to CONFIG_REALTEK_PHY=y in your
config?

> [...]
Best regards,
Michael

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2023-04-19 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13  5:55 Problems about NIC, PCIe and usb on RK3568 EVB Doug Brewer
2023-04-13  6:28 ` Johannes Zink
2023-04-13  8:02   ` Aw: " Frank Wunderlich
2023-04-13  9:21     ` Doug Brewer
2023-04-13  9:37       ` Aw: " Frank Wunderlich
2023-04-14  2:39         ` Doug Brewer
2023-04-18  9:26           ` Michael Riesch
2023-04-19  5:47             ` Doug Brewer
2023-04-19 10:18               ` Michael Riesch [this message]
2023-04-20  0:50                 ` Doug Brewer

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=460114da-d864-0cdb-e482-560f57bf7781@wolfvision.net \
    --to=michael.riesch@wolfvision.net \
    --cc=brewer.doug@gmail.com \
    --cc=linux-rockchip@lists.infradead.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