mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Documentation/boards/riscv.rst: can't rebuild image for BeagleV
Date: Fri, 22 Mar 2024 15:29:48 +0100	[thread overview]
Message-ID: <579562bc-72ad-4661-8675-986ccd79126f@pengutronix.de> (raw)
In-Reply-To: <41f4bc52-f619-4a91-a114-5eb2498cc3fc@pengutronix.de>

Hello Antony,

On 11.03.24 12:50, Ahmad Fatoum wrote:
> Hello Antony,
> 
> On 10.03.24 21:33, Antony Pavlov wrote:
>> Hi Ahmad!
>>
>> I have tried to rebuild barebox for BeagleV.
>> Alas I was unable to reproduce the steps from Documentation/boards/riscv.rst
>> because of changes in opensbi repo.

I just Cc'd[1] you on a documentation patch that describes how it needs
to be built now.

>> I have successfully rebuild U-Boot from the https://github.com/andreiw/uboot_jh7100 repo
>> and used it for running sbi-less BeagleV barebox image.
>>
>> I planned to use BeagleV for picotcp demonstration but BeagleV ethernet adapter
>> does not works neither under U-Boot nor under barebox. My dhcp server can't even
>> receive any request from BeagleV.
>>
>> Have we any chance to make BeagleV ethernet adapter works under barebox?
>
> I've been meaning to sync barebox with the kernel, now that there's upstream
> support for the JH7100. Ethernet on this SoC was a bit peculiar, because
> previous RISC-V SoCs were fully cache-coherent, but the MAC on this SoC wasn't.
> 
> I got Ethernet to work though, so if it's broken now, it is a regression.
> 
> I will try building an image when I have time.

Thanks to your report, I found a bug in my DMA coherency patches that made it
into v2024.02.0. I Cc'd[2] you on the fix. Ethernet works again now.

[1]: https://lore.barebox.org/barebox/20240322142441.982089-1-a.fatoum@pengutronix.de/T/#u
[2]: https://lore.barebox.org/barebox/20240322142424.981863-1-a.fatoum@pengutronix.de/T/#u

Cheers,
Ahmad

> 
> Cheers,
> Ahmad
> 
>>
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2024-03-22 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 20:33 Antony Pavlov
2024-03-11 11:50 ` Ahmad Fatoum
2024-03-22 14:29   ` Ahmad Fatoum [this message]
2024-03-24 20:19     ` Antony Pavlov

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=579562bc-72ad-4661-8675-986ccd79126f@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@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