jwillikers has quit [Remote host closed the connection]
mripard has joined #u-boot
mmu_man has quit [Ping timeout: 245 seconds]
LeSpocky has quit [Ping timeout: 240 seconds]
LeSpocky has joined #u-boot
vagrantc has quit [Quit: leaving]
monstr has joined #u-boot
stefanro has quit [Quit: Leaving.]
milkylainen has quit [Quit: Ping timeout (120 seconds)]
stefanro has joined #u-boot
j0hnny has quit [Ping timeout: 252 seconds]
agust has joined #u-boot
j0hnny has joined #u-boot
astroid has quit [Ping timeout: 250 seconds]
astroid has joined #u-boot
guillaume_g has joined #u-boot
fdanis_away is now known as fdanis
frieder has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
milkylainen has joined #u-boot
sbach has joined #u-boot
Peng_Fan has joined #u-boot
guillaume has joined #u-boot
guillaume_g has quit [Ping timeout: 244 seconds]
eduardas has joined #u-boot
alpernebbi has joined #u-boot
matthias_bgg has joined #u-boot
Zapy has quit [Read error: Connection reset by peer]
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
Zapy has joined #u-boot
guillaume is now known as guillaume_g
mmu_man has joined #u-boot
Peng_Fan has quit [Quit: Connection closed for inactivity]
jwillikers has joined #u-boot
jwillikers has quit [Remote host closed the connection]
jwillikers has joined #u-boot
jordemort has quit [Quit: Bridge terminating on SIGTERM]
samueldr has quit [Quit: Bridge terminating on SIGTERM]
[0x4A6F][m] has quit [Quit: Bridge terminating on SIGTERM]
kaji has quit [Quit: Bridge terminating on SIGTERM]
mvaittin has quit [Quit: Bridge terminating on SIGTERM]
cpackham[m] has quit [Quit: Bridge terminating on SIGTERM]
kallisti5[m] has quit [Quit: Bridge terminating on SIGTERM]
cpackham[m] has joined #u-boot
mvaittin has joined #u-boot
samueldr has joined #u-boot
kallisti5[m] has joined #u-boot
jordemort has joined #u-boot
kaji has joined #u-boot
[0x4A6F][m] has joined #u-boot
tnovotny has joined #u-boot
Guest8928 has joined #u-boot
dvorkindmitry has joined #u-boot
<dvorkindmitry>
I have ARM with several A7 cores and one a926. Is there any example how to write standalone application with u-boot API that can run on a926 cpu and can use u-boot api after Linux is loaded on a7 CPU?
Guest8928 has quit [Ping timeout: 256 seconds]
matthias_bgg has quit [Ping timeout: 245 seconds]
eduardas has quit [Quit: Konversation terminated!]
<dvorkindmitry>
is it possible to run u-boot on secondary arm926 cpu while linux is started on first (a7) cpu?
tnovotny has quit [Quit: Leaving]
mmu_man has quit [Ping timeout: 250 seconds]
eduardas has joined #u-boot
<marex>
dvorkindmitry: you can probably try remoteproc/rpmsg for that
<marex>
if the CA7 can control the armv5 core that is
<dvorkindmitry>
marex, yes. from the Linux side to comunicate with my second arm926 core. My qustion is... is it possible to write an application with u-boot api that starts as standalone app on arm926?
<mrnuke>
marex: hi
guillaume_g has quit [Quit: Konversation terminated!]
<marex>
dvorkindmitry: uh, probably yes
<apalos>
sjg1: contributors call ?
<marex>
dvorkindmitry: wouldn't it be better to use some rtos for that ?
<marex>
mrnuke: hi ?
<marex>
dvorkindmitry: ie. run u-boot on the main core, rtos on the companion core ?
<apalos>
sjg1: ah you declined this one, missed it
<mrnuke>
marex: Had a chance to look at Patrick's latest email?
<marex>
mrnuke: it's 46 emails down the stack, no
monstr has quit [Remote host closed the connection]
redbrain has joined #u-boot
eduardas has quit [Quit: Konversation terminated!]
frieder has quit [Remote host closed the connection]
jwillikers has quit [Remote host closed the connection]
<marex>
Tartarus: I will CC you on discussion with ST that mrnuke is fighting
jwillikers has joined #u-boot
vagrantc has joined #u-boot
jwillikers has quit [Quit: jwillikers]
jwillikers has joined #u-boot
fdanis is now known as fdanis_away
Guest89 has joined #u-boot
mmu_man has joined #u-boot
fsvend has joined #u-boot
fsvend has left #u-boot [ERC (IRC client for Emacs 26.3)]
elvishjerricco has quit [Ping timeout: 250 seconds]
redbrain has quit [Ping timeout: 252 seconds]
elvishjerricco has joined #u-boot
redbrain has joined #u-boot
redbrain has quit [Ping timeout: 244 seconds]
redbrain has joined #u-boot
<Guest89>
Where is the extlinux.conf syntax documented? I notice in Bootlin's tutorial they use the parameter 'devicetree' but when I look at, say, https://github.com/u-boot/u-boot/blob/master/doc/README.distro, there's no mention of such a parameter.
<Guest89>
Specifically, I'm looking for how to tell it to load the rootfs.cpio.uboot file (the examples I've seen always point to a partition on flash for the rootfs, which is not what I want to do).
<Guest89>
Is using extlinux.conf preferable over uEnv.txt? If so, why?
<kallisti5[m]>
UEFI > extlinux.conf > uEnv.txt
<kallisti5[m]>
recent u-boot binaries support EFI bootloaders, it's super easy
<kallisti5[m]>
but yeah... u-boot will also detect a extlinux.conf
<Guest89>
kallisti5[m] thanks. I'm using a beaglebone black so I don't think UEFI is involved.
<kallisti5[m]>
that's the point. it can be. Just setup a standard EFI/BOOTARM/BOOTARM.efi EFI/BOOTAARCH64/BOOTAARCH64.efi loader
<kallisti5[m]>
however, yes. extlinux.conf is the more common method used today
<kallisti5[m]>
uEnv.txt is just setting environment variables for u-boot. I'd avoid it unless you need to tune something
<Guest89>
I notice in the last line of the uEnv.txt generated by buildroot the uenvcmd variable is set with the addresses for the kernel, etc., and then the last thing is the bootz command is called. Is uenvcmd a key word in u-boot?
<dvorkindmitry>
marex, no. u-boot starts on a7. it loads a926 u-boot stand-alone app for secondary CPU and starts Linux on main a7 cpu.
<marex>
dvorkindmitry: is there some shared memory and mailbox between the two ?
<marex>
btw is this some nvidia tegra 2 / 3 ?
<dvorkindmitry>
marex, yes. there are shared memory and mailbox. it is custom SoC, sp7021
<marex>
uh
<marex>
then, well, look at linux remoteproc and rpmsg ; and for u-boot, rproc too
<marex>
but about writing custom application for the armv5 using u-boot api, hum
<marex>
you would have to run u-boot on it, do you ?
<dvorkindmitry>
marex, we already made remoteproc driver work with a926 cpu. My idea is to have all u-boot calls and abstractions available on secondary CPU to make standalone application easer to write
<dvorkindmitry>
to run standalone app made on u-boot basis for easer standalone app writing. Make life easer for programmers. U-Boot supports DTS, etc... and it has rich set of abstractions. If programmer will be able to run u-boot standalone code on secondary cpu, it will make they life easer. RTos or something that is made from scratch is probably not better then u-boot (imho)
alpernebbi has quit [Quit: alpernebbi]
<marex>
dvorkindmitry: well, cant you boot u-boot on the secondary CPU via remoteproc then ?
Guest89 has quit [Ping timeout: 256 seconds]
<dvorkindmitry>
marex, I think so. Never try it yet.
<dvorkindmitry>
what do you think about my idea in general?
<dvorkindmitry>
looks reasonable or not?
redbrain has quit [Ping timeout: 252 seconds]
<marex>
dvorkindmitry: it depends on what you hope to achieve in the end
<dvorkindmitry>
marex, I hope to have u-boot api, stable ethernet, dts support and simplicity of writing new app. Instead of using custom API, that was manually developed from scratch
<marex>
dvorkindmitry: well, then sure :)
<dvorkindmitry>
marex, did somebody make something like this?
<marex>
boot u-boot on a CPU and run u-boot application from that ?