<KotCzarny>
dimilar to this one, but with 3 ribs instead of 5
<ssvb>
tkaiser: UART0 pins are duplicated on the Euler and the Exp connectors, but they are located in the damaged area
tgaz has joined #linux-sunxi
<yann|work>
tkaiser: hopefully the next batches will be more properly packaged (at least, so they say in their last update ;)
<ssvb>
tkaiser: there is also the RPi header on the other side with UART2, it should be possible to use it for the serial console too
<ssvb>
yann|work: yes, especially considering that their shipping price is not so cheap
<yann|work>
right, but isn't that just usual for kickstarted project? IIRC C.H.I.P was a bit similar there
<KotCzarny>
how much paper carton one can get for 1usd?
<tkaiser>
ssvb: Connecting to pins 6/8/10 (UART2) on the RPi header didn't work. I tried it again connecting to 29/30 on the Euler connector
<tkaiser>
Spitting out garbage. In both situations powermeter reported consumption of 0.6W-0.7W so it would assume it's really stuck in boot0?
<libv>
tkaiser: wtf...
<ssvb>
tkaiser: you need a different dtb blob for using UART2, and if apritzel pushes complete sources to github (including dts), then we could give it a try ;-)
Ueno_Otoko has joined #linux-sunxi
Worf has joined #linux-sunxi
Worf has quit [Client Quit]
vishnup has quit [Ping timeout: 250 seconds]
vishnup_ is now known as vishnup
vishnu_ has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 276 seconds]
<ssvb>
tkaiser: the current draw of my pine64 board is reported to be around 90-100mA from a 5V PSU after it reaches the command prompt
<KotCzarny>
ssvb: nice
<ssvb>
measured after detaching the UART cable
<KotCzarny>
is it with eth cable connected?
gianMOD has joined #linux-sunxi
<yann|work>
ssvb: btw, I pushed more stuff on my h3 branch, including mali_drm and stuff from the loboris tree
<tkaiser>
ssvb: Thx, good to know
<ssvb>
yann|work: great, feel free to add a link to this branch to the opi pc wiki page with some comments about it
<ssvb>
we will cleanup the wiki later
<apritzel>
ssvb: UART0 seems to be hardwired into boot0 and BL3-1, U-Boot presumably refers to it's own DT, which is embedded in their blob
<apritzel>
once you reach u-boot, you can amend the kernel DT using the u-boot fdt commands and set the alias for serial0 to a different UART
p1u3sch1 has quit [Ping timeout: 250 seconds]
<ssvb>
apritzel: but the kernel can use any UART, right? assuming that the board is able to reach the kernel
<apritzel>
regarding the DT: as you may have noticed, the DT on the image is badly hacked
<apritzel>
I made some progress with a proper DT (based on the H3 .dtsi) yesterday, but it still hangs
<apritzel>
I don't want to publish broken DTs, as they may link and create a support nightmare with people copying crap
<apritzel>
s/link/leak/
<apritzel>
I will push a complete patch set once -rc1 is out
p1u3sch1 has joined #linux-sunxi
<apritzel>
ssvb: if you are desperately interested in a DT, you can use "fdt print /" in U-Boot and copy&paste that
<ssvb>
I have already extracted and decompiled 3 dts files from your sd card image
<apritzel>
please don't look at the altdtb one - this is embarrassingly broken ;-)
<apritzel>
*Jedi handwaving* this isn't the DT you are looking for
<apritzel>
I am sorry for being so reluctant on pushing the patches (and the DTs), but I want to get it right in the first place
<ssvb>
ok, no problems
<ssvb>
just some people may start complaining about providing binary images without the exact sources that had been used to create them
<apritzel>
ssvb: had to smile when I read your Wiki edit on the reset switch ;-)
<apritzel>
ssvb: I see that, please kindly refer to Allwinner for coming up with this practise ;-)
<apritzel>
the reset switch was the first thing I soldered on the board, and I added the power switch one day later
<apritzel>
highly recommended to avoid churn on the connectors
<apritzel>
tkaiser: oh dear, is that a picture of your board in the Wiki?
<apritzel>
mine was also badly packaged, but at least it did survive
<apritzel>
lets hope they use better packaging for the Kickstarter batches
<apritzel>
oh, the campaign seems to be officially finished
<apritzel>
tkaiser: have you tried HDMI?
<tkaiser>
Just downloaded the Android image. This will be last try
<apritzel>
I tried the Android image first, it worked for me, but took quite a while to display something
<apritzel>
so at least you know how broken your board is then
<tkaiser>
I realised that I have one spare 8GB card (playing around with H8 OS images on A83T which worked after exchanging boot0)
p1u3sch1 has quit [Ping timeout: 250 seconds]
<tkaiser>
Yes, will try this out in a few minutes
<apritzel>
TLLim promised to send me two more boards (512MB + 2GB), so I may give you mine next week
cnxsoft has quit [Quit: cnxsoft]
<tkaiser>
He sent out another together with your 2
<tkaiser>
This is then his 3rd try
Ueno_Otoko has joined #linux-sunxi
<apritzel>
yeah, shipping from China seems to be so cheap, but: You get what you pay for ;-)
p1u3sch1 has joined #linux-sunxi
<KotCzarny>
apritzel, but imagine all of those boards went through similar way
<KotCzarny>
it might be damaged somewhere closer to his destination
<apritzel>
sorry, didn't want to blame China post, it's actually a packaging problem
<apritzel>
my wife would be happy to give away some of my cardboard boxes I keep collecting here ;-)
<KotCzarny>
:)
Ueno_Otoko has quit [Ping timeout: 265 seconds]
<tkaiser>
apritzel: Sending from Shenzhen through Hongkong seems to be much faster. I got dev boards from LeMaker and SinoVoip that took less than 72 hours to arrive. And both sent out on friday and Monday at noontime I had the _cardboard boxes_
<wens>
tkaiser: I assume that's because they are proper products, not some pre-prod version
<wens>
the a83 devboard we got from allwinner didn't even have an anti static bag, just bubble wrap
<apritzel>
wens: seriously?
vishnu_ has quit [Ping timeout: 250 seconds]
vishnu_ has joined #linux-sunxi
<wens>
apritzel: yeah, seriously
<wens>
not to mention the sd slot was held on by 2 metal struts
reinforce has quit [Quit: Leaving.]
reinforce has joined #linux-sunxi
<tkaiser>
wens: nope, were final versions of LeMaker's Guitar and 'Banana Pi M3'. But they chose DHL Express
<plaes>
did you read the notice on the first page?
<plaes>
I added few more :)
soderstrom has joined #linux-sunxi
gianMOD has quit []
<KotCzarny>
yeah, the notice got me consufed
<KotCzarny>
*confused
<KotCzarny>
ahm, shucks, no usb and eth?
<plaes>
H3?
<KotCzarny>
yes
<plaes>
yup, WIP
<KotCzarny>
i find it baffling that linux kernel relies on some pre-kernel things to access devices
<KotCzarny>
different uboot, bam, device works?
<plaes>
things would be a lot easier, if soc-maker would cooperate
<KotCzarny>
so its a problem with device driver in kernel itself?
<plaes>
yeah, noone has had time to write the code
<plaes>
well, it's actually motivation ;)
<tkaiser>
KotCzarny: You want to use mainline u-boot combined with kernel 3.4.39, right?
<KotCzarny>
tkaiser, i want to use any u-boot at the moment
<KotCzarny>
but until h3(opipc) gets mainline support, i will probably be stuck with 3.4.39
<KotCzarny>
(as i plan to use it as a pc replacement, so i need eth and display at least)
<KotCzarny>
or usb and display
<tkaiser>
From my understanding you can combine u-boot 2016.01 with kernel 3.4 without problems. USB and Ethernet won't work in u-boot but later when the kernel starts.
<KotCzarny>
ahm, that would be great
<KotCzarny>
as i dont really care what works in uboot as long it works in linux
pekka_10 is now known as pekka_afk
<KotCzarny>
that hint should be added to uboot info on h3/opipc page
interrobangd has joined #linux-sunxi
<ssvb>
KotCzarny: some people want to be able to boot the system over Ethernet or from a USB stick
<ssvb>
and they may (and do) complain, saying something like this: "How dare you claim that the mainline U-Boot now supports Orange Pi PC if these features don't work?"
<KotCzarny>
ssvb: that's reasonable, still, for someone new to uboot saying 'eth is not supported' is ambiguous
<ssvb>
feel free to update the wiki
<KotCzarny>
k
<KotCzarny>
It can boot from the SD card or via [[FEL/USBBoot|FEL]]. Only the initial basic functionality is implemented and there are still no USB host and Ethernet drivers for H3 in U-Boot v2016.01 (it affects only u-boot functionality, device would work in linux as long kernel supports it).
<KotCzarny>
good enough?
reinforce has quit [Quit: Leaving.]
<KotCzarny>
4 cores of opipc are very nice for native compiling
Ueno_Otoko has joined #linux-sunxi
<WarheadsSE>
tkaiser: KotCzarny my board made it here in perfect shape, barely eve a dimply in the static bag
viccuad has quit [Ping timeout: 240 seconds]
reinforce has joined #linux-sunxi
premoboss has quit [Read error: No route to host]
<WarheadsSE>
Looking forward to dicking aroud with the pine64 as soon as uboot is a bit more sane, and I can package it up in ALARM
cptG has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 240 seconds]
<KotCzarny>
hmm, i should get at least red led, right?
<NiteHawk>
mass storage would be http://linux-sunxi.org/USB_Gadget#Kernel_support_2 - or maybe it could be better to reorganize that page to describe kernel versions/configurations apart from actual device classes
<KotCzarny>
hmm, anyone here with opipc and mainline uboot?
<cptG>
NiteHawk: maybe a separate section for kernel 4.4 with configFS, explaining how to configure g_ether- and g_mass_storage-equivalents? Keep the current sections of the page as is with links down to the new section?
<NiteHawk>
cptG: i have no clear idea on how to proceed best with that. it somewhat depends on how much recent kernels will (or have already) diverge from the sunx-3.4 version. might even be preferable to describe mainline primarily, and point out differences for the "legacy"/community kernel (3.4) only where needed
<tkaiser>
NiteHawk: Is there 'the sunxi-3.4' version? I don't think so. At least Alwinner's BSP for A31/A31s was based on 3.3.0 (really) and the new one fow H3/A83T/H8/R58/R16 is based on 3.4.39 containing/missing stuff that is already fixed in the sunxi-3.4 branch for older Allwinner SoCs
<tkaiser>
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 just as a simple example
cptG_ has joined #linux-sunxi
<tkaiser>
Or missing 1-wire. Or no available script.bin (or even worse: vendor OS images containing script.bin that will never be read)
<tkaiser>
In other words: Might be reasonable to differentiate between 3.x kernels or to list them all with a short list what to expect?
apritzel has quit [Ping timeout: 248 seconds]
cptG has quit [Ping timeout: 265 seconds]
<NiteHawk>
i'm a bit worried we'd end up micro-managing a plethora of kernel versions, instead of communicating a "bigger" sunxi vs. mainline picture ("sunxi" referring to 3.4 as described in http://linux-sunxi.org/Linux_Kernel#Kernel_versions). if newer socs are lacking behind that, is it even sure they have gadget support / "musb"?
<KotCzarny>
hrm, anyone with opipc and a few minutes?
fire855 has joined #linux-sunxi
<fire855>
Hi! Have someone already implemented libvdpau-sunxi into android?
soderstrom has joined #linux-sunxi
soderstrom has quit [Client Quit]
<cptG_>
Hm. I only have A20 boards and have only used 3.4.10x and 4.4 so I don't know about how heterogenous the field is. But to me it sounds reasonable to split the page into 3.4 and "mainline" (4.3, 4.4 and above) I think the differences between 3.4 and mainline are big enough to justify putting them in their own sections, whereas I'd expect the differences between 4.3 and 4.4 to be more of a "missing in 4.3
<cptG_>
, implemented in 4.4", allowing for a hand-wavy "Note: NYI in 4.3"?
<cptG_>
NiteHawk: I for myself am stuck on 3.4 for my work project due to the Mali binary blob. I can imagine there'll be more people in my situation for the foreseeable future so keeping legacy seperate does not sound too bad. I'd also expect legacy to remain more stable feature-wise than mainline, meaning there wouldn't many edits needed to that section... Or not?
<wens>
there is no community (sunxi-3.4) kernel for any of the newer SoCs
<wens>
you can use either Allwinner's kernel or the mainline kernel
<wens>
newer SoCs = ! A10/A10s/A13/A20
<NiteHawk>
"Allwinner's kernel" meaning an outdated / forked branch of earlier 3.4 ?
<KotCzarny>
more like allwinner android kernel
<KotCzarny>
:)
cptG_ is now known as cptG
<tkaiser>
wens: Agreed. Then I will start writing a random wiki page listing few issues users might run into when they buy a board with the newer SoCs and run into problems since stuff 'found somewhere in the Internet' seems not apply to their situation.
<tkaiser>
Of course when they try to use OS images from the hardware vendor or 'community provided' that make use of the BSP for the SoC in question
avph has quit [Ping timeout: 245 seconds]
<wens>
weather is all messed up this weekend, dropping close to 0 at sea level, and snowing on all the mountains here
<wens>
i'm so supposed to be near the tropics :|
avph has joined #linux-sunxi
<KotCzarny>
well, it should be -10..-30C here, going to be +4 in a few days
fredy has joined #linux-sunxi
<fire855>
Hello. I switched from 3.0.101 kernel to 3.4.10* and I only see a green picture in camera (android). Maybe someone know why? Is that a driver problem?
paulk-collins has quit [Ping timeout: 250 seconds]
avph has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
apritzel has joined #linux-sunxi
Imminens has joined #linux-sunxi
avph has quit [Ping timeout: 245 seconds]
Imminens has quit [Ping timeout: 256 seconds]
mosterta has quit [Ping timeout: 264 seconds]
avph has joined #linux-sunxi
orly_owl has joined #linux-sunxi
viccuad has quit [Quit: WeeChat 1.3]
apritzel has quit [Ping timeout: 248 seconds]
paulk-collins__ has joined #linux-sunxi
paulk-collins_ has quit [Ping timeout: 260 seconds]
Imminens has joined #linux-sunxi
<cptG>
Does anyone have experience with LCD on Olimex Lime2 with kernel 4.4? I'm not sure how to enable the LCD - I tried variations of console=tty1 video=simplefb:1024x600 to no avail...
<cptG>
KotCzarny: I have but I might just have read it the wrong way. Does simple framebuffer not imply that some sort of video support is present?
Imminens has quit [Quit: Bye]
<cptG>
KotCzarny: nope, 4.4 here. I saw on the page about mainlining effort that the Video Engine is NYI but IIRC video engine is for decoding video formats, no?
SMD1 has quit [Ping timeout: 240 seconds]
Imminens has joined #linux-sunxi
<cptG>
d'oh Video Engine != Display Engine :(
paulk-collins_ has joined #linux-sunxi
<ssvb>
cptG: does your LCD work in U-Boot?
<ssvb>
if yes, then it should also work in the kernel
paulk-collins__ has quit [Ping timeout: 264 seconds]
<ssvb>
the current setup implies that U-boot configures the display hardware, and the kernel just inherits it pre-configured, without touching any display hardware registers (that's why it is called 'simplefb')
<ssvb>
so your first step is to make sure that LCD works fine in U-Boot
<cptG>
ssvb: I see, thanks.
<cptG>
Is enabling the LCD sth I can to from the uboot cmdline or is that compiled in?
<ssvb>
currently LCD settings need to be added to the board defconfig file in U-Boot
<cptG>
ssvb: awesome, thanks!
<cptG>
...I somehow have a talent to ship around the relevant wiki pages :D
<ssvb>
I guess, there is no ready-made LCD enabled defconfig for Lime2 because it does not have LCD out of the box, and also because you can try to use different types of LCD displays with it
<ssvb>
if you have a working FEX file for the 3.4 kernel, then you can automatically convert it with a script to generate the needed U-Boot defconfig lines
<Imminens>
I am looking for someone who knows how to edit a wiki page on linux-sunxi.org or would help in editing, in terms of changes in the http://linux-sunxi.org/Inet_86vs there are a few details that need improvement, and some helpful information for owners of these tablets
MACscr has joined #linux-sunxi
<cptG>
ssvb: well that's handy, I have a working fex :) Found the script. Thanks a bunch!
paulk-collins__ has joined #linux-sunxi
premoboss has quit [Remote host closed the connection]
paulk-collins_ has quit [Ping timeout: 245 seconds]
sabresfan03 has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 248 seconds]
<cptG>
ssvb: recompiled uboot and the LCD does not work but I noticed that there's dts files as well and changed state="enabled" in sun7i-a20.dtsi, recompiling...
<cptG>
anything else to consider / tinker with?
<ssvb>
cptG: can you paste your U-Boot defconfig somewhere?
<cptG>
ssvb: just noticed a typo in my defconfig, should've copy&pasted it from the wiki page. The defconfig that's compiling atm is: http://paste2.org/kh7MJmEg
<cptG>
...I had screwed-up CONFIG_VIDEO_LCD_POWER in my current build *cough*
<cptG>
...aaaand it's working now :)
<cptG>
woohoo! time to throw out that stinky old 3.4 kernel
<ssvb>
congratulations :-)
apritzel has joined #linux-sunxi
<cptG>
I'm so happy, I'm considering naming my firstborn #linux-sunxi ;)
ricardocrudo has quit [Ping timeout: 245 seconds]
ricardocrudo has joined #linux-sunxi
Tytyryty has joined #linux-sunxi
Imminens has quit [Ping timeout: 276 seconds]
Tytyryty has quit [Ping timeout: 250 seconds]
Tytyryty has joined #linux-sunxi
MackBoy has quit [Excess Flood]
MackBoy has joined #linux-sunxi
MackBoy has quit [Excess Flood]
<Turl>
Tytyryty / Imminens, just log in and click the edit button
MackBoy has joined #linux-sunxi
Tytyryty has quit [Ping timeout: 260 seconds]
reinforce has quit [Quit: Leaving.]
reinforce has joined #linux-sunxi
MackBoy has quit [Excess Flood]
MackBoy has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
ricardocrudo has quit [Remote host closed the connection]
akaizen has joined #linux-sunxi
fire855 has quit [Ping timeout: 252 seconds]
leio has quit [Ping timeout: 240 seconds]
akaizen has quit [Remote host closed the connection]