iamfrankenstein has quit [Ping timeout: 255 seconds]
faisal has quit [Remote host closed the connection]
kaspter has joined #linux-sunxi
naobsd has quit [Quit: naobsd]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
Renard has quit [Remote host closed the connection]
atsampson has quit [Ping timeout: 252 seconds]
FreezingCold has quit [Ping timeout: 264 seconds]
p1u3sch1 has joined #linux-sunxi
p1u3sch1_ has quit [Ping timeout: 256 seconds]
[7] has quit [Disconnected by services]
TheSeven has joined #linux-sunxi
setkeh has joined #linux-sunxi
setkeh has quit [Ping timeout: 245 seconds]
book` has quit [Ping timeout: 245 seconds]
setkeh has joined #linux-sunxi
book` has joined #linux-sunxi
nicksydney has quit [Ping timeout: 244 seconds]
nicksydney has joined #linux-sunxi
nicksydney_ has joined #linux-sunxi
nicksydney has quit [Ping timeout: 245 seconds]
cnxsoft has joined #linux-sunxi
mrnuke has quit [Ping timeout: 265 seconds]
cnxsoft has quit [Ping timeout: 256 seconds]
whitesn has quit [Ping timeout: 245 seconds]
nicksydney has joined #linux-sunxi
mrnuke has joined #linux-sunxi
nicksydney_ has quit [*.net *.split]
setkeh has quit [*.net *.split]
whitesn has joined #linux-sunxi
whitesn has quit [Changing host]
whitesn has joined #linux-sunxi
setkeh has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
ssvb has quit [Ping timeout: 265 seconds]
ssvb has joined #linux-sunxi
whitesn has quit [Ping timeout: 252 seconds]
whitesn has joined #linux-sunxi
<plaes>
jero: which tutorial did you follow?
<plaes>
from wiki or from somewhere else?
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 272 seconds]
whitesn has quit [Ping timeout: 255 seconds]
whitesn has joined #linux-sunxi
naobsd has joined #linux-sunxi
deffrag has joined #linux-sunxi
foudubassan has joined #linux-sunxi
montjoie[home] has quit [Quit: Changing server]
montjoie[home] has joined #linux-sunxi
dev1990 has joined #linux-sunxi
Netlynx has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
montjoie[home] has quit [Quit: leaving]
montjoie[home] has joined #linux-sunxi
<foudubassan>
Hi. I got a A20 with the boot taken from a OS image. It uses uEnv.txt and the uImage. I thought that compiling the kernel and replacing the uImage by the new generated one would work, but it doesn't. Do I miss some step(s)?
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 255 seconds]
whitesn has quit [Ping timeout: 252 seconds]
quitte has joined #linux-sunxi
whitesn has joined #linux-sunxi
<foudubassan>
Of course, switching back to the original kernel makes everything booting and working fine.
<ssvb>
foudubassan: please define "it doesn't"
<ssvb>
also what was the original kernel version and which new kernel have you tried to compile?
<foudubassan>
Original kernel is the 3.4 branch. Got it already compiled of course, and SDCard was formatted at that time. It doesn't work means the board doesn't boot. The monitor keeps switching from Digital to Analogic.
<foudubassan>
I compiled the mainline Linux kernel, taken from git, i.e., Image Name: Linux-4.0.0-rc4
<ssvb>
it needs a little bit more work than just replacing the uImage file
<ssvb>
do you have the serial console?
<ssvb>
if watching whether "The monitor keeps switching from Digital to Analogic" is the only method to see the feedback from the system, then getting it up and running is going to be really tough for you
<foudubassan>
And compiled as it said, both on the A20 board and with a cross-compile too. As for the boot.cmd and such, I saw other things with different addresse when doing fatload. I tried the linux-sunxi one and others, but couldn't make it work.
<foudubassan>
Ok, I checked if I could use the serial console. I don't have the cable, but it can just be a question of 1 day for me to get one...
<ssvb>
that's good, it should really help when troubleshooting
<ssvb>
btw, the http://linux-sunxi.org/Mainline_Kernel_Howto page says "While the mainline kernel should work on any bootloader (with the major exception being the A20), you'll need a recent sunxi U-boot, or even better a Mainline_U-boot"
<ssvb>
*with the major exception being the A20*
paulk-aldrin has joined #linux-sunxi
<foudubassan>
I looked a bit on u-boot page, read, and read again the linux-sunxi ones.. It really puzzles me. Yes, but:
<plaes>
ssvb: maybe the "needs mainline u-boot" warning should be there too..
<ssvb>
plaes: yes, the page tries to present the users with multiple possible options, but in fact it would be much easier to add the mainline u-boot as a requirement
jinzo has joined #linux-sunxi
<plaes>
jero (the user with booting problem) was probably following this page too..
reinforce has joined #linux-sunxi
<foudubassan>
... hm.. I'll installed u-boot-tools-2015.01 from Gentoo and try with that. I used everything as said on the sunxi pages, getting the git of sunxi-boards, sunxi-tools and u-boot-sunxi... But now, I'm not sure if mkimage called during kernel generation is the one of the system (2014.01 on Gentoo by default) or the one compiled from git.. That may explain..
<ssvb>
the version of the mkimage tool should not make any difference
<ssvb>
anyway, without the serial console you are going to be shooting in the dark, so it's best to get the cable first
<foudubassan>
Then I don't get: since the SDCard can boot on the default kernel, that means the boot of the SDCard is good. Is it similar to Lilo and you have to execute something each time you change the kernel?
<ssvb>
you don't have just the kernel alone
<ssvb>
you also have the script.bin file for the 3.4 kernel and dtb file for the mainline kernel (the description of hardware resources)
<foudubassan>
>l /boot/
<foudubassan>
total 4600
<foudubassan>
-rwxr-xr-x 1 root root 50908 mars 21 21:47 script.bin
<foudubassan>
-rwxr-xr-x 1 root root 50908 mars 21 19:27 script.bin.otg-on
<foudubassan>
-rwxr-xr-x 1 root root 50936 mars 21 19:27 script.bin.otg-off
<foudubassan>
-rwxr-xr-x 1 root root 26 mars 21 17:44 .#uEnv.txt
<foudubassan>
-rwxr-xr-x 1 root root 378 mars 21 19:27 uEnv.txt
<foudubassan>
-rwxr-xr-x 1 root root 378 mars 21 19:27 uEnv.txt.video-acc-off
<foudubassan>
-rwxr-xr-x 1 root root 331 mars 21 19:27 uEnv.txt.video-acc-on
<foudubassan>
-rwxr-xr-x 1 root root 4547280 mars 21 21:47 uImage
<ssvb>
foudubassan: the mainline kernel will not work without a correct dtb file, which replaces script.bin
<foudubassan>
Ok, good to know. Well I generated it as well doing "make LOADADDR=0x40008000 uImage dtbs"
<foudubassan>
and got it copied on the SDCard.
<foudubassan>
Question: what is mainline u-boot for? Only format the SDCard at first and never used then? (I can only find u-boot, u-boot-sunxi-with-spl.bin in the directory... but no mkimage. And I had the impression that only mkimage was necessary when using a new kernel. Am I wrong?
<ssvb>
u-boot is the bootloader, it's a piece of code which is loaded by the boot rom and does the initial hardware initialization (for example, the dram controller) and then loads the linux kernel
<foudubassan>
Yes. Just like lilo is.
<foudubassan>
Or Grub.
<ssvb>
just install the mainline u-boot as instructed in the wiki, and you will even get the diagnostic messages from it on the hdmi console
<ssvb>
foudubassan: you current situation is kind of like having an old lilo bootloader on your hard drive, but trying to use grub instructions to configure it
interrobangd has joined #linux-sunxi
<ssvb>
the old versions of u-boot are significantly different from the newer ones in some aspects
<foudubassan>
I did. And got things like u-boot and u-boot-sunxi-with-spl.bin generated. But since it's not uImage dependent, I thought that the ones already installed on my SDCard would be sufficient
<foudubassan>
Ok!
<NiteHawk>
foudubassan: as u-boot is the bootloader it is involved with every startup / boot process, so you can't say it's "never used". replacing the kernel can be done independently from the bootloader, but your new kernel would have no way of loading without a functional u-boot
<foudubassan>
The installed bootlaoder is dependent on the kernel version then?
<ssvb>
it's the other way around
<foudubassan>
NiteHawk, the SDCard is booting, so the embedded u-boot is functional
<ssvb>
for example, the mainline kernel on A20 needs PSCI, which is provided only by the new versions of u-boot
<foudubassan>
ssvb, that's interesting (and very new for me). Where can I find some documentation on that kind of things? (u-boot manual?)
<ssvb>
linux-sunxi wiki has a lot of information, and the rest is in google
<foudubassan>
Last question before I proceed: the SDCard has a 2 partition running system. I just want to make sure that doing what's said here http://linux-sunxi.org/Bootable_SD_card#Bootloader won't impact on the second partition and that I would be able to put things back...
<foudubassan>
ssvb, believe me, I digged quiet a bit already, and when you don't know from where to start, searching is not that trivial
bonbons has joined #linux-sunxi
<ssvb>
foudubassan: one of the problems is that you are trying to improvise instead of following the installation instructions literally
<foudubassan>
Thus, doing dd if=u-boot-sunxi-with-spl.bin of=/dev//dev/mmcblk0 bs=1024 seek=8 is fine with the partitions of the SDCard?
<foudubassan>
ssvb, I maybe look so because I tried it a couple of time, following links here and there, and since nothing worked, I tried things before coming here asking question actually.
p1u3sch1 has quit [Ping timeout: 246 seconds]
p1u3sch1 has joined #linux-sunxi
<ssvb>
foudubassan: your first partition typically starts at the sector 2048, so there is space there for the bootloader
<ssvb>
but be always sure to backup the important information
<ssvb>
foudubassan: if the instructions at some links are not clear enough, then they should be improved
<ssvb>
and the feedback from the people like you is welcome
<foudubassan>
In the layout of the SDCard described higher on the page, it was said that there were informations on partition table from 0 (with 8KB), thus my question to no have the actual partition table erased or modified...
<ssvb>
the "seek=8" part of the dd command ensures that the first 8K of the SD card (with the partition table) are kept intact
<foudubassan>
ssvb, I understand. It's just that I find annoying someone asking questions without even tried to see if he could figure it out. But I'll be glad to give some feedback when I achieved to get my board up.
<foudubassan>
ssvb, thanks. I misinterpreted this indeed...
<ssvb>
you can even fix up the instructions in the wiki yourself, based on your fresh experience
<ssvb>
it's difficult for the long timers to see if anything is wrong or confusing there :-)
<foudubassan>
ssvb, honnestly, I would be rather for on total rewriting to avoid a lot of 3.4 and mainline mixes, based on what is already written of course. True :) I understand that people knowing what's behing the instruction find it clear enough ;)
<foudubassan>
-- One example here http://linux-sunxi.org/Manual_build_howto#boot.scr which talks about uImage when in compiling mainline kernel, it talks about generating and using zImage.. and the addresses in the corresponding boot.cmd are different, and talks about script.bin on one side (still asked to be generated but never used on Mainline_Kernel, etc.
cubeast has joined #linux-sunxi
<foudubassan>
ssvb, btw, do I have to generate uImage of zImage as said in Mainline-Kernel_Howto?
<ssvb>
these are two possible alternatives, but zImage does not need a hardcoded address
<foudubassan>
But that doesn't affect the address used in boot.cmd?
<ssvb>
this is only the LOADADDR=0x40008000 thing
<ssvb>
and is not related to the other addresses
<foudubassan>
Tkx.
<foudubassan>
Is it normal that when I make the "mkimage -C none -A arm -T script -d boot.cmd boot.scr
<foudubassan>
", "Image Name:" is followed by blank, Load Adress is 0, and so is Entry Point?
<foudubassan>
-- it has always been, but since my new first attempt didn't work...
<foudubassan>
I'm of course in the mounted boot/ dir of the SDCard, with the right .dtb, the uImage and boot.cmd present
sehraf has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc Insomnia 4.0.2, revision: 402, sources date: 20100627, built on: 2010-08-02 17:44:33 UTC 402 http://www.kvirc.net/]
interrobangd_ has joined #linux-sunxi
interrobangd has quit [Ping timeout: 252 seconds]
atsampson has joined #linux-sunxi
leio has quit [Remote host closed the connection]
<foudubassan>
Output is the same, using u-boot-sunxi/tools/mkimage and Gentoo mkimage from 2014.01 package...
kaspter has quit [Ping timeout: 245 seconds]
Renard has joined #linux-sunxi
Renard has quit [Remote host closed the connection]
gzamboni has quit [Ping timeout: 265 seconds]
wickwire has joined #linux-sunxi
ssvb has quit [Ping timeout: 272 seconds]
gzamboni has joined #linux-sunxi
gzamboni has quit [Ping timeout: 252 seconds]
<diego71>
ssvb: where can I find your generic u-boot?
froolap has quit [Read error: Connection timed out]
konradoo77 has quit [Ping timeout: 256 seconds]
froolap has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
froolap has quit [Ping timeout: 244 seconds]
gzamboni has joined #linux-sunxi
Black_Horseman has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
ricardocrudo has quit [Ping timeout: 246 seconds]
rz2k has quit [Remote host closed the connection]
jinzo has quit [Quit: Leaving]
whitesn has quit [Ping timeout: 246 seconds]
Vanfanel has joined #linux-sunxi
whitesn has joined #linux-sunxi
<Vanfanel>
ssvb: would it be possible to have an standalone version of pixman_composite_src_0565_8888_asm_neon() so I don't have to include all these pixman files in RetroArch to build my sunxi driver, please?
konradoo77 has quit [Ping timeout: 264 seconds]
<ssvb>
Vanfanel: is this too bad?
froolap has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
<Vanfanel>
ssvb: well, the idea behind retroarch is to keep a light codebase, and it's just two functions anyway. It's a bit of a bloat...
<ssvb>
you can do the source code chopping work yourself, it is MIT X11 licensed
<ssvb>
just be sure that you don't strip the copyright header and you should be fine
<Vanfanel>
ssvb: I see it's named in pixman-arm-neon-asm.S, line 489
<Vanfanel>
but there's no implementation really. It seems to be somehow generated "on the fly"
<Vanfanel>
but I don't get how it's done so I can get the actual function code
<ssvb>
yes, it is expanded from macros
<Vanfanel>
I take generate_composite_function is a macro that generates the fn?