Re: LOR on Star64 + network problem (eqos TX not working)

> Sent: Sunday, June 08, 2025 at 12:36 PM
> From: "Milan Obuch" <freebsd-riscv@dino.sk>
> To: riscv@freebsd.org
> Subject: Re: LOR on Star64 + network problem (eqos TX not working)
>
> On Sat, 7 Jun 2025 23:37:54 +0200
> JMT Sihvola <jsihv@gmx.com> wrote:
> 
> > > Sent: Saturday, June 07, 2025 at 10:17 AM
> > > From: "Milan Obuch" <freebsd-riscv@dino.sk>
> > > To: riscv@freebsd.org
> > > Subject: Re: LOR on Star64 + network problem (eqos TX not working)
> > >
> > > On Thu, 29 May 2025 12:43:25 +0200
> > > Milan Obuch <freebsd-riscv@dino.sk> wrote:
> 
> [ snip ]
> 
> > > > I am going to prepare a test with Linux based OS, which I used to
> > > > basic functionality check. Stay tuned.
> > > >   
> > > 
> > > As expected, Linux based DietPi just works (I could ssh into the
> > > box, so the network works).
> > > 
> > > I noticed there are two different DTBs for Vision Five boards, so
> > > there should be two different versions. There are somewhat different
> > > definitions for eqos interfaces in those DTBs. So it would be
> > > interesting to know which board version (or maybe there are more
> > > revisions, I did not look for this) those trying FreeBSD on it have.
> > > And how it goes with network - does it work at all? Are there any
> > > troubles?
> > > 
> > > Anybody else with Star64 board?
> > > 
> > > Regards,
> > > Milan
> > >   
> > 
> > I noticed that Linux (mainline) has a later addition in their
> > dwmac-starfive.c driver code which sets a different TX clock rate if
> > the device tree has a property "starfive,tx-use-rgmii-clk". This
> > might be the reason for the problem. I could try to implement this
> > feature within a week (tell me if you're trying to implement it by
> > yourself).
> > 
> 
> That's could be it, sounds reasonable. At the moment, I am not in
> position to implement anything like this myself, I have some problems
> with my workplace setup I need to recover from.
> 
> In the meantime, I plan to prepare some test build, so I should be able
> to do my own build and can incorporate some patches.


It seems now the Ethernet phy driver was possibly written without all the
current device tree files available which led to some bad choices.
It's a bit more complicated than what I wrote in a previous message.

But I prioritize this issue now to provide a patch for it soon.

If you are impatient, you may ask me some quick fixes for Star64 privately.

-jari