openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Troy Lee <troy_lee@aspeedtech.com>
To: Graeme Gregory <quic_ggregory@quicinc.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: RE: AST2600 EVB eth0 (MAC1) Issue
Date: Thu, 23 Sep 2021 09:09:02 +0000	[thread overview]
Message-ID: <HK0PR06MB2145678C356EC1ADFB194D1E8AA39@HK0PR06MB2145.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <8f36a6e9-eccf-5d9b-2c29-3546ded6ba5d@quicinc.com>

Hi Gaeme,

Which soc revision and evb board revision are you using? 
Can you try to use phy-mode = "rgmii-rxid" for eth0/1 in your dts? 

Thanks,
Troy Lee

> -----Original Message-----
> From: openbmc <openbmc-
> bounces+troy_lee=aspeedtech.com@lists.ozlabs.org> On Behalf Of Graeme
> Gregory
> Sent: Wednesday, September 22, 2021 11:49 PM
> To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> Subject: AST2600 EVB eth0 (MAC1) Issue
> 
> Hi,
> 
> I know A0 versions of the AST2600 had an issue where eth0 was not working,
> but the errata indicates this is fixed in later revisions.
> 
> I am seeing an issue on the EVB board though where eth0 (MAC1) is not
> functional. The other three ports all function as expected.
> 
> On my DHCP host machine I can see DHCP requests from the AST2600, and
> replies are sent. Looking at /proc/interrupts it looks very much like no IRQs
> are ever generated for incoming packets.
> 
> Thanks
> 
> Graeme
> 


  reply	other threads:[~2021-09-23  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 15:49 AST2600 EVB eth0 (MAC1) Issue Graeme Gregory
2021-09-23  9:09 ` Troy Lee [this message]
2021-09-23 21:22   ` Graeme Gregory
2021-09-24  3:32     ` Troy Lee
2021-09-24 13:12       ` Graeme Gregory

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=HK0PR06MB2145678C356EC1ADFB194D1E8AA39@HK0PR06MB2145.apcprd06.prod.outlook.com \
    --to=troy_lee@aspeedtech.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=quic_ggregory@quicinc.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;
as well as URLs for NNTP newsgroup(s).