Turl changed the topic of #linux-sunxi to: Allwinner/sunxi /development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi
jstein_ has joined #linux-sunxi
jstein_ is now known as jstein
lurchi__ is now known as lurchi_
kaspter has joined #linux-sunxi
tllim has joined #linux-sunxi
popolon has quit [Quit: WeeChat 1.9.1]
rwmjones|KVM2017 has quit [Ping timeout: 246 seconds]
MoeIcenowy has quit [Quit: Leaving.]
jstein has quit [Remote host closed the connection]
<marble_visions> however, now i get a Mali: ERR: /home/user/work/projects/winpos/a_new_hope/sunxi-mali/r6p2/src/devicedrv/mali/common/mali_pp.c mali_pp_reset_wait() 269
<marble_visions> i think i am specifying reset/clocks wrong
<marble_visions> https://pastebin.com/fSgjauM8 this is where I'm at
* marble_visions is using a13-olinuxino
<marble_visions> assigned-clock-rates = <384_000_000>; is actually <384000000> when I compile, the underscores help me track the zeros..
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 260 seconds]
<ullbeking> does anybody know what the difference is between the opi zero and opi r1?
<ullbeking> also, has anybody noticed how usb otg is advertised as a feature but there are these red highlighted notes all over the place saying not to use it for linux? i was hoping to power my
<Guest92134> i think otg is currently broken in mainline, but working in legacy
<Guest92134> at least on other boards
<ullbeking> i'm not sure if saying "don't use usb otg" means that power/booting still works and that the full range of otg functionality is lessened
<ullbeking> or if it shouldn't be used at all
<ullbeking> how am i supposed to power this from linux? http://www.orangepi.org/orangepizero/
<ullbeking> 02:01 <Guest92134> i think otg is currently broken in mainline, but working in legacy
<ullbeking> what do you mean by "legacy"? and it's annoying to have to use "other boards" because all i have opi zeros and r1s, as i'm waiting on the +2e to be re-released (if that ever happens)
<ullbeking> 02:02 <Guest92134> at least on other boards
<Guest92134> legacy = the 3.4-based allwinner kernels from the bsp's
<ullbeking> yike
<ullbeking> s
<ullbeking> and
<ullbeking> ew
<pmpp> no please not the bsp one :p
<pmpp> use armbian's one
<Guest92134> "one" ?
<ullbeking> oh whew
<Guest92134> there are different ones for different chips
<ullbeking> Guest92134: different whats?
<Guest92134> kernels
<ullbeking> i'm so confused by all the opi websites
<Guest92134> i don't see anything in red on that page except ram and ethernet
<ullbeking> Guest92134: let me check that, brb
<ullbeking> Guest92134: go to "Orange Pi Quick Start Guide" (or any other model) under Resources -> Quick Start
<ullbeking> OPi is a cool board but sometimes i feel like a beta tester for the guys who are making money off this
maz has joined #linux-sunxi
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
rwmjones has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
MoeIcenowy has joined #linux-sunxi
lurchi_ has quit [Client Quit]
lurchi_ has joined #linux-sunxi
anarsoul has quit [Ping timeout: 248 seconds]
anarsoul has joined #linux-sunxi
lurchi_ has quit [Quit: Konversation terminated!]
maz has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-sunxi
ninolein has quit [Ping timeout: 248 seconds]
ninolein has joined #linux-sunxi
lurchi_ has quit [Quit: Konversation terminated!]
cnxsoft has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
<MoeIcenowy> anarsoul: do you have simplefb code for DE2 LCD in U-Boot?
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-sunxi
tlwoerner has quit [Changing host]
tlwoerner has joined #linux-sunxi
<smaeul> ullbeking: the people who say "don't use usb otg" are telling you to always power the board with the DC barrel connector if possible
<smaeul> USB OTG works fine in mainline linux in device mode, and similarly badly in host mode
<smaeul> you _can_ power over usb otg, even though it's not recommended. for a board like the opi zero, which doesn't have a barrel plug, you don't have a choice
<[TheBug]> You can power by gpio pins
<[TheBug]> using a dupont connector or similar
<Guest92134> power over gpio is eww
<anarsoul> MoeIcenowy: no
<anarsoul> MoeIcenowy: I've never tried simplefb, since jernej's patches work fine for HDMI and your patches work fine for LCD :)
TheSeven has quit [Ping timeout: 258 seconds]
TheSeven has joined #linux-sunxi
<MoeIcenowy> you mean Linux patches?
<MoeIcenowy> but I think adding SimpleFB can make the display appears more early
<MoeIcenowy> for example, if DRM is built as M, the DRM display will only start when udev is trying to load all devices' modules
<MoeIcenowy> but the SimpleFB display will be started when booting (SimpleFB is set to bool, not tristate, so it's not possible to M it)
JohnDoe_71Rus has joined #linux-sunxi
lurchi__ has joined #linux-sunxi
RichardG867 has quit [Ping timeout: 240 seconds]
lurchi_ has quit [Ping timeout: 248 seconds]
<anarsoul> MoeIcenowy: I see
<anarsoul> MoeIcenowy: OK, will check
RichardG867 has joined #linux-sunxi
RichardG867 has quit [Changing host]
RichardG867 has joined #linux-sunxi
<MoeIcenowy> oh I made the patch
<MoeIcenowy> will soon send it after testing
<anarsoul> cool, thanks
IgorPec has joined #linux-sunxi
TheSeven has quit [Ping timeout: 255 seconds]
SP7RT has quit [Ping timeout: 264 seconds]
TheSeven has joined #linux-sunxi
vagrantc has joined #linux-sunxi
maz has joined #linux-sunxi
gnufan has quit [Quit: Leaving.]
awais has joined #linux-sunxi
MoeIcenowy has quit [Ping timeout: 255 seconds]
MoeIcenowy has joined #linux-sunxi
maz has quit [Ping timeout: 248 seconds]
reinforce has joined #linux-sunxi
reinforce has quit [Remote host closed the connection]
reinforce has joined #linux-sunxi
maz has joined #linux-sunxi
yann|work has quit [Ping timeout: 240 seconds]
<codekipper> anarsoul: Hi,
<codekipper> I've pushed some patches here https://github.com/codekipper/linux-sunxi/commits/upstream
<codekipper> based on your observations but I've not been able to test yet
Putti has joined #linux-sunxi
putti_ has joined #linux-sunxi
Putti has quit [Read error: Connection reset by peer]
tllim has quit [Read error: Connection reset by peer]
putti_ has quit [Ping timeout: 248 seconds]
afaerber has joined #linux-sunxi
MoeIcenowy has quit [Quit: Leaving.]
jogoes has joined #linux-sunxi
jzvhgfmchl has joined #linux-sunxi
jzvhgfmchl has quit [Remote host closed the connection]
kaspter has quit [Quit: kaspter]
afaerber has quit [Ping timeout: 248 seconds]
maz has quit [Ping timeout: 246 seconds]
Gerwin_J has joined #linux-sunxi
sr-digitronic has joined #linux-sunxi
afaerber has joined #linux-sunxi
maz has joined #linux-sunxi
jbrown has quit [Ping timeout: 258 seconds]
matthias_bgg has joined #linux-sunxi
msimpson has joined #linux-sunxi
kaspter has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
IgorPec has quit [Ping timeout: 258 seconds]
yann|work has joined #linux-sunxi
libv has joined #linux-sunxi
libv_ has quit [Ping timeout: 260 seconds]
maz has quit [Ping timeout: 240 seconds]
maz has joined #linux-sunxi
ornitorrincos has quit [Quit: ZNC 1.6.5 - http://znc.in]
ornitorrincos has joined #linux-sunxi
ornitorrincos has quit [Changing host]
ornitorrincos has joined #linux-sunxi
indy has quit [Ping timeout: 240 seconds]
anarsoul has quit [Ping timeout: 248 seconds]
anarsoul has joined #linux-sunxi
<Pe3ucTop> Question: Is it possible simply use allwinner CPU as uC in low power mode (without DDR and other rich peripheral), before Linux and after shutdown ??
<KotCzarny> yes, with arisc
<Pe3ucTop> but is it konwn which Allwinner CPUs have arisc? I\m interested in V3s but don't know doest it have one.
<KotCzarny> seems it doesnt
<KotCzarny> no mention in specs pdf either
<Pe3ucTop> :( sad.
<KotCzarny> but h3 and a33 have it
fkluknav has joined #linux-sunxi
<KotCzarny> and probably h5/h64
<KotCzarny> but probably you can write asm to run arm cores only too
<KotCzarny> there is sram accessible but is tiny
MoeIcenowy has joined #linux-sunxi
maz has quit [Ping timeout: 248 seconds]
Andy-D__ has joined #linux-sunxi
<MoeIcenowy> All sun8i/sun50i except V3s and R40 are currently known to have arisc
<KotCzarny> r40 doesnt have it? o.o
<wens> it's an a20 with updated stuff :p
<KotCzarny> i would count on 'updated' part they have added arisc too
<MoeIcenowy> but the only function they added is 2 ARM cores and MIPI-DSI
<MoeIcenowy> But as it's a 40nm chip it's not pin-to-pin compatible with A10/A20 (55nm)
maz has joined #linux-sunxi
chlorine has joined #linux-sunxi
chlorine_ has joined #linux-sunxi
chlorine has quit [Ping timeout: 252 seconds]
<marble_visions> all, got mainline and mali kernel module working, but i've got a question about qt5 using mali
<marble_visions> libMali.so is compiled in a few variants
<marble_visions> in order for qt5 to link and use correctly libMali.so, i need the fbdev variant, right?
<marble_visions> the alternatives are x11_ump and x11_dma_buf
<marble_visions> i'm not using ump so that's out
<marble_visions> i start to suspect that it is x11_dma_buf, and qt5 xcb platform
Andy-D__ has quit [Quit: Alive/Dead]
maz has quit [Ping timeout: 246 seconds]
putti_ has joined #linux-sunxi
putti_ has quit [Read error: Connection reset by peer]
Gerwin_J has joined #linux-sunxi
IgorPec has joined #linux-sunxi
chlorine has joined #linux-sunxi
chlorine_ has quit [Ping timeout: 252 seconds]
xvnvx has joined #linux-sunxi
xvnvx has quit [Max SendQ exceeded]
xvnvx has joined #linux-sunxi
MoeIcenowy has quit [Remote host closed the connection]
xvnvx has quit [Ping timeout: 258 seconds]
sr-digitronic has quit [Remote host closed the connection]
gumblex_ has joined #linux-sunxi
gumblex has quit [Ping timeout: 246 seconds]
<mripard> marble_visions: use the fbdev variant, with qt's eglfs
matthias_bgg has quit [Ping timeout: 240 seconds]
gumblex has joined #linux-sunxi
<marble_visions> mripard: thanks, will try
gumblex_ has quit [Ping timeout: 240 seconds]
cnxsoft1 has joined #linux-sunxi
chlorine has quit [Remote host closed the connection]
chlorine has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 260 seconds]
cnxsoft1 is now known as cnxsoft
chlorine_ has joined #linux-sunxi
chlorine has quit [Ping timeout: 252 seconds]
afaerber has quit [Quit: Leaving]
paulk-gagarine has quit [Excess Flood]
paulk-gagarine has joined #linux-sunxi
TEKrantz has quit [Quit: Me fail English? That's unpossible.]
TEKrantz has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
Worf has joined #linux-sunxi
awais has quit [Ping timeout: 240 seconds]
Guest92134 has quit [Ping timeout: 260 seconds]
jbrown has joined #linux-sunxi
obbardc has joined #linux-sunxi
<obbardc> hey guys, completely new to allwinner. what's the status of i2s audio going upstream? willing to help work on patches, once the board arrives ;).
cnxsoft has quit [Quit: cnxsoft]
indy has joined #linux-sunxi
phil42 has quit [Read error: Connection reset by peer]
zoobab has joined #linux-sunxi
<mripard> montjoie: can you send a new iteration of your DT patches today?
<mripard> Ideally, I'd like to get it in 4.15, and if we wait too much we're going to miss it
TEKrantz has quit [Quit: Beware of programmers who carry screwdrivers.]
<miasma> hm, some fud about bad support here in the comments https://liliputing.com/2017/10/banana-pi-m2-zero-faster-raspberry-pi-zero-clone-15.html
<obbardc> ha, funny cuz Rpi upstream & binary blobs is pretty much junk right
popolon has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
SP7RT has joined #linux-sunxi
<willmore> obbardc, anarsoul and codekipper were the last ones in here discussing I2S in mainline.
efraim has joined #linux-sunxi
<obbardc> codekipper's repo fork has some interesting i2s stuff in it, thanks.
aalm has quit [Quit: xyz 1.9.1]
<miasma> whats with sinovoip? there are like 7 banana pi m2 boards already?
<miasma> and 6 different SoCs
<willmore> Does anyone pay attention to banana pi?
<KotCzarny> you bet. but if you ask if serious people, that can do their own research before deciding on something do, now, that's another story
<willmore> Yeah, I thought they were in the 'friends don't let friends buy Bpi'.
Putti has joined #linux-sunxi
<obbardc> Just bought an orange pi PC2 with H5
chlorine has joined #linux-sunxi
chlorine_ has quit [Ping timeout: 255 seconds]
Guest54164 has joined #linux-sunxi
<[TheBug]> obbardc: have fun with that
<Guest54164> willmore: oh, like Opi is any better...
chlorine has quit [Remote host closed the connection]
chlorine has joined #linux-sunxi
gzamboni has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
chlorine_ has joined #linux-sunxi
Worf has quit [Quit: Konversation terminated!]
<willmore> obbardc, I have one and it works well. DVFS isn't working on mainline, but it's in the works.
chlorine has quit [Ping timeout: 246 seconds]
<willmore> Yes, actually, they are.
<obbardc> awesome news willmore, I know where to come when I get it from the slow china post.
<Guest54164> in the short time that i have been in this channel, i have already seen a couple of reports of Opi hardware failure after a brief service period
gzamboni has quit [Quit: Ex-Chat]
<obbardc> It's the problem with chinese hardware..!
<KotCzarny> no, it isnt
<KotCzarny> they are selling in tens/hundreds of thousands
<KotCzarny> there will always be failures some in 0.1%
<KotCzarny> especially that they are often not properly secured from bad electricity
<obbardc> bit of both, and user failure
<obbardc> like using dodgy PSUs
<KotCzarny> for example hdmi port is fragile (electrically) on oranges
<KotCzarny> so hot-plug is a bad idea there
<Guest54164> some protections against things like that could go into the design
<KotCzarny> sure, but then they wouldnt sell under 10usd
<KotCzarny> you want good board, go for intel nuc
<KotCzarny> no?
<obbardc> ah right
<KotCzarny> you want cheap, no-support stuff? be prepared for more work
<Guest54164> oh yeah? do a web search for "atom clock errata"
<obbardc> had a rockchip board that had scrambled HDMI output
<obbardc> like old analog TV
<obbardc> putting finger near HDMI chip made it worse
<obbardc> coupling in mains hum
<obbardc> adding better ceramic filtering to power rail fixed ;-)
<KotCzarny> another thing is that most often you see people having problems speaking than joining just to say 'it works'
<Guest54164> gone are the days when putting fingers on 300Ω twin leads made tv _better_
<KotCzarny> Guest54164: still works for wifi ;)
<Guest54164> i'd rather not do that with 2.4G, thanks
<KotCzarny> hehe
<willmore> 100mW isn't going to hurt you.
<Guest54164> an AP is closer to 300mW
<willmore> Meh. I have 2n2222 etched into one of my fingers..
SP7RT has quit [Quit: Lost terminal]
tom_nov has joined #linux-sunxi
<kilobyte> Pine64+, current linus+icenowy/sunxi64-4.14-rc6: 「sunxi-mmc 1c0f000.mmc: could not find pctldev for node /soc/pinctrl@1c20800/mmc0-pins, deferring probe」, same for a bunch of other drivers
<kilobyte> am I holding it wrong (bad config, etc), or is it a known issue?
SP7RT has joined #linux-sunxi
<kilobyte> there's 「sun50i-a64-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver」 later, but whatever got deferred doesn't get undeferred
kaspter has quit [Quit: kaspter]
tllim has joined #linux-sunxi
<montjoie> mripard: sorry I just came back from we
<montjoie> will send next iteration in some hours
<mripard> montjoie: awesome, thanks
tom_nov has quit [Ping timeout: 248 seconds]
tom_nov has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
tl_lim has joined #linux-sunxi
Ntemis has quit [Remote host closed the connection]
tllim has quit [Ping timeout: 255 seconds]
phil42 has joined #linux-sunxi
tl_lim has quit [Ping timeout: 252 seconds]
tl_lim has joined #linux-sunxi
SP7RT has quit [Ping timeout: 240 seconds]
tom_nov has quit [Ping timeout: 252 seconds]
msimpson has quit [Quit: Leaving]
tom_nov has joined #linux-sunxi
reinforce has joined #linux-sunxi
<smaeul> kilobyte: that message means one driver (mmc) required another driver (PIO) to be loaded first, so it says "try loading me again later". The order that drivers are first loaded in is not deterministic
<smaeul> usually you don't see any messages when it tries again later
<smaeul> but it _does_ try again
adj__ has quit [Ping timeout: 248 seconds]
<smaeul> in this case, if you see a "mmcblk0" device, then you know that it did eventually load the driver
SP7RT has joined #linux-sunxi
nvz has joined #linux-sunxi
nvz is now known as rant
<wens> miasma: bpi mX has 2^X cores... seems to make sense :p
<KotCzarny> what about m2m ?
<wens> KotCzarny: r16 = a33 = 4 cores
<wens> :)
<KotCzarny> but 2^2m doesnt make much sense anymore ;)
tom_nov has quit [Ping timeout: 246 seconds]
<wens> ignore the suffix :p
Putti has quit [Ping timeout: 260 seconds]
<wens> only the integer part counts
<KotCzarny> you can't just blindly ignore little letters or dots in math, it makes the answer wrong :P
chlorine has joined #linux-sunxi
tom_nov has joined #linux-sunxi
chlorine_ has quit [Ping timeout: 240 seconds]
tom_nov has quit [Ping timeout: 260 seconds]
tom_nov has joined #linux-sunxi
obbardc has quit [Quit: Page closed]
adj__ has joined #linux-sunxi
<marble_visions> all, what's the preferred way to contribute sunxi-related packages to buildroot (before or even without mainlining)? for example suppose i've got a sunxi-mali and mali-blobs packages based on mripard's work
<marble_visions> should they be a series of patches against buildroot
<marble_visions> or should i fork mainline buildroot and place them there?
adj__ has quit [Ping timeout: 240 seconds]
adj__ has joined #linux-sunxi
anarsoul|2 has joined #linux-sunxi
<miasma> KotCzarny: oh right, didn't realize it's the same of the 'magic' board
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
<wens> marble_visions: no idea
efraim has quit [Remote host closed the connection]
efraim has joined #linux-sunxi
adj__ has quit [Ping timeout: 258 seconds]
adj__ has joined #linux-sunxi
yann|work has quit [Ping timeout: 258 seconds]
paulk-gagarine has quit [Excess Flood]
dev1990 has quit [Ping timeout: 252 seconds]
paulk-gagarine has joined #linux-sunxi
sunxi_fan has quit [Read error: Connection reset by peer]
tl_lim has quit [Ping timeout: 258 seconds]
TEKrantz has joined #linux-sunxi
aalm has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
<Pe3ucTop> Hey friens, question about SPI , is it possible to hold CS (chip select) manualy even when other SPI device do transfer ??
<Pe3ucTop> Curent situation: SPI device do accept only one big data transfer (single burst = single CS activity) and it have nHOLD input, which force ignore clock/data when needed.
jelle has quit [Quit: Ragequittt]
<Pe3ucTop> In this situation - I need control CS manualy and HOLD is controled by other SPI devices nCS signals. How correctly implement this ?
tl_lim has joined #linux-sunxi
<aalm> Pe3ucTop, the IP used for SPI is pretty configurable, and if i understood correctly, what you want is certainly doable..
Mr__Anderson has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc 4.9.2 Aria http://www.kvirc.net/]
netlynx has quit [Quit: Ex-Chat]
<kilobyte> smaeul: it indeed retries serial and dwmac later, but not mmc -- which makes booting from it quite hard
<Guest54164> are you using initramfs?
<kilobyte> nope
<Guest54164> then maybe you should
<Guest54164> it makes debugging problems like this a lot easier
rant has quit [Ping timeout: 258 seconds]
dave0x6d has quit [Quit: Connection closed for inactivity]
tl_lim has quit [Ping timeout: 258 seconds]
rant has joined #linux-sunxi
IgorPec has quit [Ping timeout: 264 seconds]
tom_nov has quit [Ping timeout: 240 seconds]
tom_nov has joined #linux-sunxi
tom_nov has quit [Client Quit]
Putti has joined #linux-sunxi
dave0x6d has joined #linux-sunxi
Putti has quit [Ping timeout: 258 seconds]
tl_lim has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
tl_lim has quit [Ping timeout: 252 seconds]
tl_lim has joined #linux-sunxi
tl_lim has quit [Client Quit]
Ntemis has joined #linux-sunxi
tllim has joined #linux-sunxi
benettig has joined #linux-sunxi
<benettig> Did someone manage to have Mali r6p2 working on A20 or A33?
<benettig> I've tried with fbdev and weston versions. Both says there's no display, but I have fb0 and drm registered
iamfrankenstein has quit [Quit: iamfrankenstein]
fdcx has quit [Ping timeout: 248 seconds]
<Guest54164> benettig: my understanding is a20 yes, a33 no. however, i will try on a33 when i can
<benettig> Guest54164: I think I miss something on DTS,
<benettig> because in both on fbdev and wayland versions it gives me there's no display
<benettig> in particular Mali gives me 0x3003, BAD_ALLOC
fdcx has joined #linux-sunxi
<benettig> but mali-kernel driver side seems to be ok
<benettig> cma connected and big(256M to exagerate)
<benettig> I've tried on A20-OLinuXino with HDMI, A33-OLinuXino, our custom board with A20
<benettig> it always give 0x3003 error
<benettig> maybe you have a working dts and defconfig, if yes can you share it?
<Guest54164> i'm on a tablet, not olinuxino
<benettig> which tablet?
<Guest54164> Naxa NID-7015
<Guest54164> A33 inside
<benettig> and do you use a distribution?
<Guest54164> it's a Q8
<benettig> And did you use the original dts from sunxi-next?
<Guest54164> i'm just trying the kernel for now with different patchsets and constructing a dts
<benettig> are you using the X11 version of Mali?
<Guest54164> there is no existing matching dts but the q8 reference one is the closest
<Guest54164> i have not tried X11 on it yet
<Guest54164> dts not stable enough so far
<benettig> so you've used the fbdev version?
<Guest54164> that's why i said "will try when i can"
<Guest54164> my dts is not ready for mali yet
<Guest54164> unfortunately there are conflicting A33 patchsets for mainline
<benettig> but on A20 you've managed to make it work?
Mr__Anderson has quit [Remote host closed the connection]
<Guest54164> i do not have an A20. my other board is A10, and i have not tried it on that
<benettig> Guest54164: sorry if I ask you again, did you use fbdev Mali version on A33 tablet Q8 based?
<marble_visions> mripard: "QT_QPA_EGLFS_INTEGRATION=eglfs_mali /usr/lib/qt/examples/gui/analogclock/analogclock -platform eglfs" errors out with "EGL Error : Could not create the egl surface: error = 0x3003"
<benettig> marble_visions: have someone found a fix for that? Or maybe with X11 would it work?
fkluknav has quit [Ping timeout: 240 seconds]
<marble_visions> benettig: no idea, i will have a look around. i suspect that maybe it's an incorrectly configured stack.. i still don't fully understand the proper relationship between x, xcb, fb, x drivers, qt opengl support, egl and eglfs to know what's wrong
<marble_visions> i mean, i do understand the surface, but obviously i need to dive in more to get this fixed
<benettig> oh, so stuck at the same point. I had that problem with fbdev and wayland too.
<benettig> mripard told me that it should be because I don't have a display registered. Maybe in DRM, this is why Mali can't find where to write on
<marble_visions> benettig: what does it mean to register a display? have a device section in "/etc/X11/xorg.conf"?
<benettig> never tried with X11
<Guest54164> benettig: as i said, my dts is not ready for mali yet, only the kernel framebuffer
<benettig> Guest54164: ok, now it's clear
<benettig> marble_visions: X11 is different from using EGLFS
<benettig> EGLFS should only use fbdev
<benettig> I've tried to dig into assembly of Mali, but it exits with error con create_surface function
<benettig> and without symbols, and without knowing how it works with linux 4.x it's almost impossible to understand what's going on
<benettig> marble_visions: take a look here to understand differences between all those stuff http://doc.qt.io/qt-5/embedded-linux.html
<benettig> that should clarify those differences
<marble_visions> benettig: thanks
benettig has quit [Read error: Connection reset by peer]
benettig has joined #linux-sunxi
<benettig> marble_visions: you're welcome
<Guest54164> part of the mali confusion overall is that allwinner's mali differs from ARM's reference implementation of mali
<marble_visions> Guest54164: is known in what ways? or are people just reverse engineering? does that reflect on opengles/qt compatibility?
<marble_visions> s/is known/is it known/
TEKrantz has quit [Ping timeout: 248 seconds]
Guest54164 has quit [Ping timeout: 260 seconds]
<benettig> marble_visions: someone tried with lima driver, but that project is dead as I know
<marble_visions> benettig: heard that as well
<benettig> instead everybody uses userspace Mali drivers as binary blobs that Allwinner sometimes give
Guest39250 has joined #linux-sunxi
<benettig> everything was stuck until mripard obtained fbdev and x11 r6p2 blobs with license from Allwinner
gnufan has joined #linux-sunxi
<benettig> but it is very early, and it takes some more time to have a good guide to make it work
<marble_visions> benettig: yeah.. i also think it's an issue with configuration.. not some fundamental issue with the blobs
<benettig> yes, this is why it's so frustrating!
MoeIcenowy has joined #linux-sunxi
* marble_visions suspects that compiling with gcc 6.3 when the libs have been compiled with 4.8 may also contribute to the problem
<marble_visions> benettig: ^ what do you think?
<Guest39250> didn't the arm eabi change in 6.0?