jstein_ has quit [Remote host closed the connection]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
ninolein has quit [Ping timeout: 250 seconds]
ninolein has joined #linux-sunxi
tipo has quit [Remote host closed the connection]
scream has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
LostSoul has quit [Ping timeout: 244 seconds]
LostSoul has joined #linux-sunxi
abruanese has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
oneinsect has joined #linux-sunxi
<oneinsect>
i am trying to change the debug port in fex from uart port 0 to uart port 1 and enable boot params as setenv bootargs vmlinuz-3.4.111-sun8i modules=loop,squashfs,sd-mod,usb-storage modloop=modloop-sunxi hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:800x600p60 initcall_debug=0 console=ttyS1,115200 init=/init rootwait ramdisk_size=50000
<oneinsect>
how it doesnt seem to boot....any ideas on how change the default debug port?
tipo has quit [Remote host closed the connection]
p1u3sch1_ has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 252 seconds]
<wens>
mripard: sun4i-drm is in drm-next, but not in linux-next :/
<wens>
mripard: you could probably include the related dt patches
cnxsoft has quit [Ping timeout: 250 seconds]
cnxsoft has joined #linux-sunxi
<KotCzarny>
oneinsect: boot with default console first and see what is ttyS1/2/3
<oneinsect>
its working
<oneinsect>
i dont need to change anything
<oneinsect>
just enable uart1 in fex file and then boot using ttys1 as bootarg option
<KotCzarny>
so what was the problem?
<oneinsect>
i was trying to change the debug port from port 0 to port 1 which is kinda not required at all
<oneinsect>
in the fex file
prasannatsm has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
oneinsect has quit [Ping timeout: 250 seconds]
lemonzest has joined #linux-sunxi
tipo has joined #linux-sunxi
lemonzest has quit [Ping timeout: 276 seconds]
lemonzest has joined #linux-sunxi
<KotCzarny>
umkay, just got another clue why my opipc doesnt reboot
<prasannatsm>
I am having a InFocus F1 (firefox OS tablet) codenamed flatfish. I don't have serial console access yet. Opening the tablet case is not easy.
apritzel has joined #linux-sunxi
<prasannatsm>
Using Vol+ and power button puts the device in FEL mode but I could not read any data from address 0x42400000 => not able to access boot1.header
<prasannatsm>
Should I use the SD card method? I do not know if the device will directly boot from the SD card.
<prasannatsm>
I compiled u-boot for the device. Running "sunxi-fel uboot u-boot.bin" returns "SPL: eGON header is not found".
<NiteHawk>
it might prefer nand/emmc over sd card - and the sd card method won't initialize boot1 either. you're currently stuck in an awkward situation where it's hard to find a solution
<prasannatsm>
I will try that out. Initialising MMU will be enough to get boot1.header right?
<NiteHawk>
i'm not convinced of that :/ DRAM and MMU inititialization is part of boot0 afaik, i'm unsure it it would always proceed to loading boot1 then
<NiteHawk>
but that device page could give you some ideas, e.g. toying around with the android firmware image (to possibly unpack it) and making creative use of the files contained within
<prasannatsm>
I was able to get script.bin from the bootloader partition. Is boot1.header necessary still for creating device tree for the board?
<NiteHawk>
well, did you verify that it contains usable information - by converting it to human-readable .fex ?
<prasannatsm>
yeah did that already. The result file looks usable. I would prefer someone to look at it and say if that really is.
<NiteHawk>
ah sorry, my bad. the boot1.header is for essential device information like e.g. DRAM timings etc. - so it's definitely helpful to have it. you might possibly get away without it by using some standard/default values for A31-based devices
<prasannatsm>
interesting.
<NiteHawk>
prasannatsm: the preferred way would be to contribute it to https://github.com/linux-sunxi/sunxi-boards - ideally via submitting the .fex as a patch via the mailing list
<prasannatsm>
Is it possible to extract boot1.header from that file?
IgorPec has quit [Ping timeout: 260 seconds]
<NiteHawk>
i'm not experienced with extracting firmware images, only been using a devboard so far (where things are much more accessible and thererfore easier)
<prasannatsm>
NiteHawk Without having boot1.header it should still be possible to create DT for the device and run a mainline kernel. Am I right?
<NiteHawk>
take my answer with a grain of salt (i'm by far not an expert), but afaik, i would say: yes
<prasannatsm>
good to hear. will find a way to convert the fex to dt and see how things move.
<NiteHawk>
but when doing so, you might really look into ways to get a serial console working on that device (either by soldering or by using a microsd-breakout adapter). it helps a lot with debugging
<prasannatsm>
Does all allwinner board has UART output through micro sd adapter? If so I will follow instructions in http://linux-sunxi.org/MicroSD_Breakout
<jelle>
that sounds like magic
<NiteHawk>
prasannatsm: the "trick" with this is redefining the mmc pins as serial (via fex/dts), so the kernel will simply put them to a different use
<NiteHawk>
if you want to be sure, look up the pin numbers from the A31 datasheet / user manual, and check if they are "multiplexed" (i.e. can be used for either SDC0 or UART)
<mripard>
wens: yeah, but i'm still missing the clocks drivers that haven't been acked
<mripard>
there's no next during the weekend
<mripard>
so it will probably be in tomorrow's
jernej has quit [Ping timeout: 276 seconds]
<wens>
which ones are those?
<mripard>
display and tcon0 clocks
<mripard>
stephen did some reviews, i'd like an ack from him
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Equilibrium 4.2.0, revision: 42021, sources date: 20120701, built on: 2013-10-21 12:25:22 UTC 42021 http://www.kvirc.net/]
zuikis has quit [Remote host closed the connection]
zuikis has joined #linux-sunxi
Shirasaka-Hazumi has quit [Ping timeout: 260 seconds]
<prasannatsm>
I extracted script.bin using sunxi-script_extractor (one of the sunxi-tools). But running bin2fex results in the following error "fexc-bin: ../flatfish/script_extracted.bin: version: 0.1.2
<prasannatsm>
Does sunxi-script_extractor and sunxi-meminfo tools really work?
<Tartarus>
NiteHawk: indeed. What to get some stackoverflow points and answer the person? :)
<NiteHawk>
i'm not registered at SO either...
<Tartarus>
ha, ok
jernej has joined #linux-sunxi
<Tartarus>
I'll give it a whirl then, thanks.
<NiteHawk>
prasannatsm: i think those tools have fallen into disuse / weren't update in a while. so it's possible that you're encountering a case where they can't deal properly with your files
<NiteHawk>
s/update/updated/
<prasannatsm>
NiteHawk I am able to extract boot1.header using sunxi-meminfo but could not make sure it is correct. Is there a way to check whether it is correct?
<NiteHawk>
i'm not familiar with that. did you compare it to the (A31) github folder for sunxi-board that i gave earlier? if they look reasonably similar, i'd say give it a go
<prasannatsm>
Compared it, many values are same, around 25+ values differ. The DDR frequency reported is 720MHz for the device I have while other devices have 624MHz.
<prasannatsm>
This could be the reason for difference but I could not confirm it yet.
<NiteHawk>
iirc: some DRAM configurations were lowered in specs to be on the safe side with a variety of devices
<prasannatsm>
lima-memtester does not work in my tablet because it has a powervr sgx GPU and not Mali.
<NiteHawk>
in that case, i'd start with the vendor-provided values - if you suspect those don't work properly / cause memory issues, you can always tweak it later
libv has joined #linux-sunxi
libv has quit [Ping timeout: 240 seconds]
premoboss has quit [Quit: Sto andando via]
libv has joined #linux-sunxi
libv has quit [Ping timeout: 250 seconds]
<prasannatsm>
sure.
<prasannatsm>
I have cloned sunxi-boards, adding the fex file and boot1.header to it. Will submit a patch soon.
<NiteHawk>
great! btw: out of interest, how did you finally manage to get the meminfo?
<prasannatsm>
meminfo tools works without issues, only the script_extractor's output could not be parsed by bin2fex.
<prasannatsm>
I just wanted to cross check the output of meminfo with some test or from specification but could not do that.
<NiteHawk>
ah, i see
libv has joined #linux-sunxi
libv has quit [Ping timeout: 260 seconds]
lemonzest has quit [Quit: Leaving]
zuikis has quit [Remote host closed the connection]
oliv3r has quit [Quit: Lost terminal]
<prasannatsm>
I have sent a patch to linux-sunxi@googlegroups.com but its not reflected in google groups yet.
zuikis has joined #linux-sunxi
abruanese has quit [Max SendQ exceeded]
<NiteHawk>
prasannatsm: give it a few minutes. i should eventually show up
libv has joined #linux-sunxi
jernej has quit [Ping timeout: 252 seconds]
IgorPec has joined #linux-sunxi
<prasannatsm>
sure. will wait.
pmattern has joined #linux-sunxi
libv_ has joined #linux-sunxi
apritzel has joined #linux-sunxi
libv has quit [Ping timeout: 244 seconds]
libv has joined #linux-sunxi
libv_ has quit [Ping timeout: 276 seconds]
libv_ has joined #linux-sunxi
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
libv has quit [Ping timeout: 260 seconds]
libv has joined #linux-sunxi
prasannatsm has left #linux-sunxi ["Part"]
libv_ has quit [Ping timeout: 240 seconds]
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
avph has quit [Ping timeout: 260 seconds]
apritzel has quit [Ping timeout: 244 seconds]
avph has joined #linux-sunxi
kaspter has joined #linux-sunxi
jernej has joined #linux-sunxi
Netlynx has joined #linux-sunxi
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
apritzel has joined #linux-sunxi
Nacho_ has quit [Remote host closed the connection]
tkaiser has joined #linux-sunxi
Nacho has joined #linux-sunxi
avph has quit [Ping timeout: 260 seconds]
avph has joined #linux-sunxi
TheSeven has quit [Ping timeout: 276 seconds]
TheSeven has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
tkaiser has quit [Ping timeout: 276 seconds]
avph has quit [Ping timeout: 260 seconds]
tkaiser has joined #linux-sunxi
avph has joined #linux-sunxi
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
avph has quit [Ping timeout: 260 seconds]
avph has joined #linux-sunxi
<tipo>
is there a place on the armbian site where they sign the images or have checksums?
Netlynx has quit [Quit: Leaving]
<KotCzarny>
tipo: just grab the building script and rebuild it yourself?
<tipo>
could do; could do.
<tipo>
i'm using the orange pi pc (h3) for this test.... of course I wouldn't build it on that, but where might I find an appropriate build script?
vagrantc has quit [Quit: leaving]
<KotCzarny>
click: sources
<KotCzarny>
clone the repo and follow readme
<tipo>
thanks
<tkaiser>
tipo: What's the problem with checksums?
<KotCzarny>
tkaiser: he cant see them
<tkaiser>
KotCzarny: There are archives (zip or .7z) containing the image, the checksum and a readme
<KotCzarny>
tkaiser: so you have put checksums inside archives?
<tkaiser>
Sure
legobane has quit [Quit: Leaving]
<KotCzarny>
offtopic: did you stumble on a patch for 8188 that helps with it being 'forgetfull' ?
<tkaiser>
KotCzarny: I consider RealTek WiFi dongles not worth a look :)
<KotCzarny>
:)
<KotCzarny>
i did a mistake and bought it instead of rl5370
mossroy has quit [Quit: Quitte]
newpine64user has joined #linux-sunxi
tipo has quit [Remote host closed the connection]
tipo has joined #linux-sunxi
<lvrp16>
8188cu and 8188eu series are really popular
<lvrp16>
>75% of the SBC dongles are based on 8188eu and 8188cu
<lvrp16>
at least the ones sold in the USA
<KotCzarny>
yes, but do you know the remedy for the problem i've described? (other than going mainline, which i will do at 4.7)
avph has quit [Ping timeout: 260 seconds]
zuikis has left #linux-sunxi [#linux-sunxi]
avph has joined #linux-sunxi
<lvrp16>
no, i haven't really messed with 8188eu on 3.4 kernels
<lvrp16>
even on the 4.5 kernel, rtl8188 has issues with some chipsets