premoboss has quit [Remote host closed the connection]
vishnup has joined #linux-sunxi
KotCzarny has quit [Ping timeout: 248 seconds]
cosm has quit [Ping timeout: 276 seconds]
huawei has quit [Ping timeout: 276 seconds]
tomboy64 has quit [Ping timeout: 248 seconds]
Shirasaka-Hazumi has joined #linux-sunxi
vishnup has quit [Ping timeout: 276 seconds]
iamfrankenstein1 has joined #linux-sunxi
cosm has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 276 seconds]
iamfrankenstein1 is now known as iamfrankenstein
vishnup has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
shooter_ has quit [Quit: Leaving]
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 240 seconds]
iamfrankenstein1 is now known as iamfrankenstein
JohnDoe7 has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 240 seconds]
cosm has quit [Ping timeout: 246 seconds]
dev1990 has quit [Quit: Konversation terminated!]
cosm has joined #linux-sunxi
vagrantc has joined #linux-sunxi
MrApplecraft has joined #linux-sunxi
<jelle>
silly question here, when I insmod the hdmi driver is there supposed to show a tty on the hdmi output?
<jelle>
testing the h3 driver, Jean-Francois made
iamfrankenstein has quit [Ping timeout: 240 seconds]
<anonkun[lt]>
usually that is the case, but sometimes in kernel boot parameters there is only serial console set. Im not sure if framebuffer is still created in that case
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 240 seconds]
tomboy64 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 244 seconds]
MY123 has joined #linux-sunxi
tomboy66 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 248 seconds]
iamfrankenstein has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
tomboy66 has quit [Ping timeout: 268 seconds]
<ssvb>
jelle: just try some simple framebuffer application or even "dd if=/dev/urandom of=/dev/fb0"
<ssvb>
as for the framebuffer console, some things may be missing in the kernel configuration
vagrantc has quit [Quit: leaving]
vickycq has quit [Ping timeout: 260 seconds]
Shirasaka-Hazumi has quit [Ping timeout: 244 seconds]
vickycq has joined #linux-sunxi
Shirasaka-Hazumi has joined #linux-sunxi
giomba has joined #linux-sunxi
marble_visions has joined #linux-sunxi
<marble_visions>
hi all, i am wondering how does the A13 SoC read the data from script.bin
<marble_visions>
does it read it itself or does the linux kernel + drivers help?
<marble_visions>
u-boot loads the file at 0x43000000, which isn't anything special when I look at the memory map, it is just RAM
domidumont has joined #linux-sunxi
<ssvb>
marble_visions: the allwinner's 3.4 kernel just finds this data at the magic address 0x43000000
<ssvb>
marble_visions: and the bootloader is responsible for putting the script.bin data there (as you can see in boot.cmd)
<ssvb>
marble_visions: btw, what was the outcome of your overclocking adventure?
tomboy64 has quit [Ping timeout: 250 seconds]
tomboy64 has joined #linux-sunxi
FDCX has quit [Remote host closed the connection]
cptG_ is now known as cptG
MrApplecraft has quit [Quit: Page closed]
tomboy64 has quit [Ping timeout: 248 seconds]
Gerwin_J has quit [Quit: Gerwin_J]
<giomba>
Hello. I'm trying to use hardware acceleration on Olimex A20. I compiled libump, libdri2, linux-sunxi and xf86-video-fbturbo as explained in the wiki, and every output looks ok (Xorg logs and the test triangle) but, if I run es2gears or glmark, they have poor performances (20fps and 3-5fps respectively) and say “Failed to create a pipe screen for lima” “failed to open lima”.
<giomba>
How can I tell them to use the Mali proprietary binaries instead of Lima? I think recompiling Mesa OpenGLES could be a good idea, but I haven't found any flag to tell it to force using Mali. What else can I do? I can't figure out. Thanks.
<ssvb>
giomba: what does glmark2-es2 say?
pietre has joined #linux-sunxi
<ssvb>
giomba: and possibly es2_info
Netlynx has quit [Quit: Leaving]
<giomba>
"failed to create a pipe screen for lima"
<giomba>
"DRI2: failed to open lima (search path: /usr/lib/arm-linux-gnueabi/dri${ORIGIN}/dri:/usr/lib/dri" but of course I don't have any lima_*.dri or lima.so in my fs
<giomba>
OpenGL Vendor: Mesa Project
<giomba>
GL RENDERER: Software rasterizer
<giomba>
GL_VERSION: OpenGL ES 2.0 Mesa 8.0.5 (yes, that's not very recent but I couldn't make other things work on more recent versions)
<ssvb>
then it looks like your program is using mesa shared libraries instead mali
<marble_visions>
ssvb: thanks, so the kernel actually uses the script.bin, not the SoC itself
<marble_visions>
the OC was a fail, since not all PLLs can be multiplied by 3
<marble_visions>
(pll3 and pll7)
<marble_visions>
so the PIOs on the chip can actually be driven from two sources if in script.bin you've got two things running on the same pins?
<marble_visions>
at what level does the PIO function muxing work?
<ssvb>
marble_visions: for the pin muxing config you can check the A13 manual
<giomba>
ssvb: ok, there is the symlink but it has "wrong" name... trying an older commit of sunxi-mali
<marble_visions>
ssvb: yeah, i can probably recite that by heart now.. i was wondering if you've got a kernel module loaded (mmc, that operated the mmc2 pins) then change the PIOs to another mux function, why does a signal from the mmc driver still pass through the pins
<ssvb>
marble_visions: hmm, does it?
<marble_visions>
oscilloscope-checked
<marble_visions>
i force a "card inserted" signal to the driver and i see the initial clock pulse for some time before the driver realizes there's nothing there
<marble_visions>
even though the PIOs are not set to <4> (for example)
<marble_visions>
and that's another thing there: what happens if you've got PE4 for example mapped to two different functions in script.bin? does the kernel set the last one seen in the file or something more complicated?
<ssvb>
is the mux function correctly changed though?
<marble_visions>
i use sunxi-tools' pio, i think i devmemed the contents to see if they match
<marble_visions>
I don't know how to verify deeper than that
edolnx has joined #linux-sunxi
<marble_visions>
(i checked 0x01c20800 0x01c20bff here)
<marble_visions>
so you think doing a simple pio pin<func>blah,blah should do it?
<marble_visions>
at runtime, no restart?
mpmc_ is now known as mpmc1
mpmc is now known as mpmctoo
mpmc1 is now known as mpmc
p1u3sch1 has quit [Ping timeout: 248 seconds]
orly_owl has quit [Ping timeout: 240 seconds]
p1u3sch1 has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 244 seconds]
p1u3sch1 has joined #linux-sunxi
<giomba>
ssvb: finally solved! Thank you very much for your help!
<giomba>
Two latest questions:
<giomba>
1) Only for curiosity (and only if you know): I also tried to use the Lima driver, but it looks a real pain to compile. On the official website, they always talk about the Android SDK, is it really necessary? Then, there also seem to be a dead repository on gitorius. Are they still active?
<giomba>
2) Is there a way to donate something to this project? Website doesn't say anything.
<buZz>
giomba: ask libv
<buZz>
giomba: about 1)
<buZz>
and 2)
<buZz>
its his project
<ssvb>
giomba: you are welcome
<ssvb>
feel free to update the wiki page (the troubleshooting section)
buZz has quit [Ping timeout: 260 seconds]
buZz has joined #linux-sunxi
buZz is now known as Guest56642
Guest56642 is now known as buZz
jstein has joined #linux-sunxi
jstein has quit [Remote host closed the connection]