alexxy has quit [Quit: No Ping reply in 180 seconds.]
alexxy has joined #linux-sunxi
lkcl has quit [Ping timeout: 240 seconds]
chewitt has joined #linux-sunxi
lkcl has joined #linux-sunxi
apritzel has quit [Ping timeout: 246 seconds]
Mangy_Dog has quit [Ping timeout: 240 seconds]
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #linux-sunxi
<wens>
apritzel: I'm all for it, but I don't have any ideas # get rid of IPI
cnxsoft has joined #linux-sunxi
cnxsoft1 has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
reinforce has joined #linux-sunxi
tuxd3v has quit [Remote host closed the connection]
tuxd3v has joined #linux-sunxi
shailangsa has quit [Read error: Connection reset by peer]
fl_0 has quit [Ping timeout: 265 seconds]
pmp-p has quit [Read error: Connection reset by peer]
Kooda has quit [Ping timeout: 272 seconds]
fl_0 has joined #linux-sunxi
pmp-p has joined #linux-sunxi
Kooda has joined #linux-sunxi
prefixcactus has joined #linux-sunxi
pCactus has quit [Ping timeout: 264 seconds]
cmeerw has joined #linux-sunxi
asdf28 has joined #linux-sunxi
hlauer has joined #linux-sunxi
shailangsa has joined #linux-sunxi
andy25225 has quit [Ping timeout: 240 seconds]
cmeerw has quit [Ping timeout: 260 seconds]
apritzel has joined #linux-sunxi
andy25225 has joined #linux-sunxi
<hlauer>
whats the syntax for an echo command in uboots bootcmd variable to get ${kernel} resolved?
prefixcactus has quit [Read error: Connection reset by peer]
pCactus has joined #linux-sunxi
prefixcactus has joined #linux-sunxi
apritzel has quit [Ping timeout: 240 seconds]
mmarc__ has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
lurchi_ has quit [Read error: Connection reset by peer]
lurchi__ has joined #linux-sunxi
yann has quit [Ping timeout: 256 seconds]
mmarc__ has quit [Remote host closed the connection]
mmarc__ has joined #linux-sunxi
mmarc___ has joined #linux-sunxi
mmarc__ has quit [Read error: No route to host]
dev1990 has joined #linux-sunxi
mmarc___ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 246 seconds]
mmarc__ has joined #linux-sunxi
yann has joined #linux-sunxi
mmarc__ has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
warpme_ has joined #linux-sunxi
mmarc__ has joined #linux-sunxi
ldevulder has joined #linux-sunxi
ldevulder_ has quit [Ping timeout: 272 seconds]
Mangy_Dog has joined #linux-sunxi
iyzsong has quit [Ping timeout: 240 seconds]
elros1 has joined #linux-sunxi
mmarc__ has quit [Remote host closed the connection]
iyzsong has joined #linux-sunxi
yann has quit [Ping timeout: 240 seconds]
mmarc__ has joined #linux-sunxi
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-sunxi
<plaes>
echo "variable 'kernel': ${kernel}"
<plaes>
but I'm not 100% sure whether I understood the question
lerc_ has quit [Ping timeout: 240 seconds]
<apritzel>
yeah, was trying to understand that question as well the whole morning ;-)
lerc has joined #linux-sunxi
mmarc__ has quit [Remote host closed the connection]
mmarc__ has joined #linux-sunxi
<prefixcactus>
apritzel: I've loaded/started a kernel (supposedly together with an initrd and rest of distro) via U-Boot on my board. Only problem is I don't get any feedback from it besides "Uncompressing Linux... done, booting the kernel."
<plaes>
ah.. you need to enable early console in kernel configuration
<prefixcactus>
I dunno if it has to do with u-boot or the kernel itself (or both), and how I should determine the culprit
<prefixcactus>
plaes: already did that
<plaes>
CONFIG_EARLY_PRINTK ?
<prefixcactus>
yes, that
<prefixcactus>
(via menuconfig)
<apritzel>
prefixcactus: what is your commandline?
smaeul has quit [Ping timeout: 264 seconds]
<prefixcactus>
It does print what I posted earlier now, before that the last message was from U-Boot
<apritzel>
"done, booting the kernel" is a message from the kernel, more precisely the ARM kernel decompressor
<apritzel>
prefixcactus: do you have "console=ttyS0,115200n8" on your command line?
<prefixcactus>
Don't think so. I'll check
<apritzel>
prefixcactus: also, be careful with your DTB: Linux will mercilessly setup the voltages on the PMIC according to what it finds in the DT, so there is some chance that you could fry your board if that is wrong
<prefixcactus>
Yeah, I've already run over the whole thing fixing the voltages
<apritzel>
good!
<prefixcactus>
I'm recompiling the kernel now with the console string appended via config to make sure it's there
<prefixcactus>
oh, by the way
<prefixcactus>
is there a way to make u-boot print the boot script as it sees it?
<apritzel>
prefixcactus: hardcoding the command line into the kernel build? that's nasty, don't do this
<prefixcactus>
not a best practice, but seems like a bulletproof debugging strategy
<prefixcactus>
at least I can be sure it's there now
<apritzel>
that should be all you need to get some early kernel output: setenv bootargs "console=ttyS0,115200n8"; bootz $kernel_addr_r - $fdt_addr_r
<apritzel>
that relies on the DT being accessible, and doesn't include earlyprintk, but should work out of the box
chewitt_ is now known as chewitt
<prefixcactus>
apritzel: the commandline you posted seems to do nothing...
<prefixcactus>
more specifically, executing bootz yields a debug print of where the current stack ends and a new command prompt
yann has joined #linux-sunxi
<apritzel>
prefixcactus: so you are using some image wrapped kernel, not the zImage file directly?
<prefixcactus>
yes
<prefixcactus>
or no, I'm not sure
<prefixcactus>
the kernel is compiled within an image-building script, but there is a zImage in /boot
<prefixcactus>
apritzel: (also, boot.cmd _does_ add "console=ttyS0,115200" to the kernel command line)
<apritzel>
yeah, it's just hard to reason what exactly goes wrong if everything is wrapped up several times (bootz into a U-Boot image, the whole boot commands into some U-Boot script)
<prefixcactus>
Yeah, understandable
<prefixcactus>
I could try to set up a minimal environment, but then in addition to U-Boot or the kernel effing up there will be a probable factor of me having set the whole thing up wrong somehow
netlynx has joined #linux-sunxi
<prefixcactus>
I enabled the earlycon cmdline flag, now it gets to "[ 0.000000] printk: bootconsole [uart0] enabled" and then stops
<prefixcactus>
So I suspect the uart params might be borked somehow..
<apritzel>
prefixcactus: have you tried "earlyprintk" on the command line? In addition to the console=... ?
<apritzel>
(was a while ago that I debugged some ARM32 kernel boot ...)
<prefixcactus>
I added it now (as well as increasing verbosity) and on second 2 it started spewing strcktraces at me
<prefixcactus>
dunno what it did in between, but that's definitely something
reinforce has quit [Quit: Leaving.]
andy25225 has quit [Ping timeout: 256 seconds]
JohnDoe_71Rus has joined #linux-sunxi
chewitt has left #linux-sunxi ["Adios!"]
chewitt has joined #linux-sunxi
mmarc__ has quit [Remote host closed the connection]
andy25225 has joined #linux-sunxi
pCactus has quit [Read error: Connection reset by peer]