All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org, Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [Buildroot] Interested in board support for BeagleV-Ahead
Date: Thu, 10 Aug 2023 19:03:20 +0200	[thread overview]
Message-ID: <845846062.0ifERbkFSE@kilian-aisec> (raw)
In-Reply-To: <CAOCHtYjiGK+oKiYoPPosM6Ead+kcw1YEN8225FT3n=r=oqJ_Yw@mail.gmail.com>

Hello Robert,

> > I am interested in adding board support for the BeagleV-Ahead.
> > 
> > I already started trying to setup the board support, but at the moment it
> > does not work yet, due to some gcc 12 and zicsr and zifencei RiscV
> > extension issue (see below).
> 
> Awesome work!

Thanks!

> BTW, i've created a special u-boot branch for mainline gcc situations,
> with *-ubuntu extension on the branch..
> 
> https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-u-boot/-/tree/beagle
> v-v2020.01-1.1.2-ubuntu

So should I try using that branch then?

> Using kernel.org's x86_64-gcc-13.2.0-nolibc-riscv64-linux.tar.xz
> 
> I've been mostly working on mainline for the board with @Drew Fustini
> 
> Otherwise on the mainline we've been using main branch of opensbi and
> linu's 6.5.x-rc (only eMMC wip support).. not much else on the
> mainline branch yet..

Do you suggest, that I should then try to use mainline kernel, instead of 
"beaglev-ahead-linux" (https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-linux)?

You seem to also be a maintainer for the "beaglev-ahead-linux" repository? Is 
the light_defconfig the proper one for the beaglev-ahead? What do you think 
about the issues I encountered regarding vector extension v0.7.1 and recent 
gcc apparently not supporting it? What do you think about maybe removing the 
CONFIG_VECTOR flags from the light_defconfig?

https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-linux/-/blob/beaglev-v5.10.113-1.1.2/arch/riscv/configs/light_defconfig#L21-22

And also as mentioned in my other mail, I encountered an enum-int-mismatch 
error when compiling with (buildroot generated) gcc v13.2 between a functions 
an its prototype, see here:

https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-linux/-/blob/beaglev-v5.10.113-1.1.2/drivers/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_linux.h#L338

https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-linux/-/blob/beaglev-v5.10.113-1.1.2/drivers/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c#L6144

And one more question: I was able to generate some binaries, but so far I 
don't have a clue how to assemble them to a proper image and how I would flash 
that image to the BeagleV-Ahead's eMMC. Do you happen to have some hint(s) for 
me, e.g., some link, some documentation, anything?

Best regards,
Kilian



_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-08-10 17:03 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
2023-08-10 16:34 ` Robert Nelson
2023-08-10 17:03   ` Kilian Zinnecker via buildroot [this message]
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=845846062.0ifERbkFSE@kilian-aisec \
    --to=buildroot@buildroot.org \
    --cc=kilian.zinnecker@mail.de \
    --cc=robertcnelson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.