From: schwab@suse.de (Andreas Schwab)
To: linux-riscv@lists.infradead.org
Subject: Hifive-U vs 1000baseT
Date: Thu, 18 Oct 2018 11:40:17 +0200 [thread overview]
Message-ID: <mvmftx3twxq.fsf@suse.de> (raw)
Are there any known issues with ethernet on the Hifive-U connecting to a
1Gb port? I see that the port gets a link, but no traffic at all. When
connecting to a 100Mb port it works fine.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Subject: Hifive-U vs 1000baseT
Date: Thu, 18 Oct 2018 11:40:17 +0200 [thread overview]
Message-ID: <mvmftx3twxq.fsf@suse.de> (raw)
Message-ID: <20181018094017.FSu7EuP9V35M_0EWcGwbNwmAGGEYS-wdaxOcSg2iDyo@z> (raw)
Are there any known issues with ethernet on the Hifive-U connecting to a
1Gb port? I see that the port gets a link, but no traffic at all. When
connecting to a 100Mb port it works fine.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-10-18 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 9:40 Andreas Schwab [this message]
2018-10-18 9:40 ` Hifive-U vs 1000baseT Andreas Schwab
2018-10-18 10:21 ` Andreas Schwab
2018-10-18 10:21 ` Andreas Schwab
2018-10-18 17:41 ` Palmer Dabbelt
2018-10-18 17:41 ` Palmer Dabbelt
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=mvmftx3twxq.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-riscv@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