Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kilian Zinnecker <kilian.zinnecker@mail.de>
Cc: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Interested in board support for BeagleV-Ahead
Date: Fri, 11 Aug 2023 16:40:45 +0200	[thread overview]
Message-ID: <20230811164045.1c5416b4@windsurf> (raw)
In-Reply-To: <13322713.uLZWGnKmhe@kilian-aisec>

Hello Kilian,

On Thu, 10 Aug 2023 11:20:49 +0200
Kilian Zinnecker <kilian.zinnecker@mail.de> wrote:

> > Ah, ah, I was working on this as well!  
> 
> Nice, then let's do it together?

Sure, why not. You seem to be ahead of me already, so let me know when
you have something and I can give it a test. Or if you face some issue,
I can have a look and try to help.

> > Backport commit 1dde977518f13824b847e23275001191139bc384 from upstream
> > U-Boot on top of this vendor branch, it will solve your problem.  
> 
> Great, thanks, that did the trick!

I know, because I already encountered this exactly same problem while
trying to build U-Boot for the BeagleV-Ahead :-)

> I however run into a similar problem with opensbi afterwards. As I use the 
> beaglev_defconfig as basis, I also used the opensbi version defined there:
> 
> https://gitlab.com/buildroot.org/buildroot/-/blob/3a4ce27f/configs/
> beaglev_defconfig#L29

I'm not sure it makes sense to use the same OpenSBI version as the one
that was used for the original BeagleV. You probably want to check the
Yocto layers for the BeagleV-Ahead to see which OpenSBI
version/configuration they are building.

> However, the (2 years old) opensbi version (currently defined in the 
> beaglev_defconfig) does not define the neccessary flags for the zicsr and 
> zifencei extensions, needed by gcc12, as seen here in the newer opensbi 
> release-1.3.x version:
> 
> https://github.com/riscv-software-src/opensbi/blob/release-1.3.x/Makefile#L274
> 
> So my build broke until I changed to release-1.3.x. This makes me wonder about 
> the current beaglev_defconfig: It might be broken since bumbing gcc to v12, but 
> I actually don't know. I could try building an image for the beaglev later 
> today?

The beaglev_defconfig indeed fails to build in U-Boot:
https://gitlab.com/buildroot.org/buildroot/-/jobs/4839059972

However, I think beaglev_defconfig should probably be removed, this
board is not produced.

> Now, regarding the bealgev-ahead, it seems to build opensbi on my machine. But 
> I don't know whether the official opensbi is actually needed, or the custom 
> version, i.e.:
> 
> https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-opensbi

See
https://git.beagleboard.org/beaglev-ahead/xuantie-yocto/-/tree/Linux_SDK_V1.1.2-light-beagle/meta-light/recipes-bsp/opensbi
for how they are building OpenSBI.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-08-11 14:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 13:57 [Buildroot] Interested in board support for BeagleV-Ahead Kilian Zinnecker via buildroot
2023-08-09 17:38 ` Thomas Petazzoni via buildroot
2023-08-10  9:20   ` Kilian Zinnecker via buildroot
2023-08-10 11:02     ` Kilian Zinnecker via buildroot
2023-08-11 14:41       ` Thomas Petazzoni via buildroot
2023-08-11 21:30         ` Robert Nelson
2023-08-11 22:53           ` Robert Nelson
2023-08-12  9:51             ` Kilian Zinnecker via buildroot
2023-08-12  9:56               ` Thomas Petazzoni via buildroot
2023-08-18 17:18             ` Kilian Zinnecker via buildroot
2023-08-18 21:33               ` Robert Nelson
2023-08-18 21:35                 ` Robert Nelson
2023-08-20 12:54                   ` Kilian Zinnecker via buildroot
2023-08-21 21:43               ` Thomas Petazzoni via buildroot
2023-08-10 15:25     ` Kilian Zinnecker via buildroot
2023-08-11 14:48       ` Thomas Petazzoni via buildroot
2023-08-12  9:56         ` Kilian Zinnecker via buildroot
2023-08-12 10:19           ` Thomas Petazzoni via buildroot
2023-08-12 11:06             ` Kilian Zinnecker via buildroot
2023-08-11 14:40     ` Thomas Petazzoni via buildroot [this message]
2023-08-10 16:34 ` Robert Nelson
2023-08-10 17:03   ` Kilian Zinnecker via buildroot
2023-08-10 18:57     ` Robert Nelson
2023-08-10 19:05       ` Robert Nelson
2023-08-10 19:53       ` Kilian Zinnecker via buildroot
2023-08-10 20:45         ` Robert Nelson
2023-08-11  7:11           ` Kilian Zinnecker via buildroot
2023-08-10 20:38       ` Kilian Zinnecker via buildroot
2023-08-10 20:53         ` Robert Nelson
2023-08-11  7:07           ` Kilian Zinnecker via buildroot

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=20230811164045.1c5416b4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=kilian.zinnecker@mail.de \
    --cc=thomas.petazzoni@bootlin.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