rellla 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 - *only registered users can talk*
lurchi_ is now known as lurchi__
ElBarto has quit [Read error: Connection reset by peer]
ElBarto has joined #linux-sunxi
ornitorr- has quit [Quit: ZNC 1.7.0 - https://znc.in]
ornitorrincos has joined #linux-sunxi
ornitorrincos has joined #linux-sunxi
ornitorrincos has quit [Changing host]
popolon has quit [Quit: WeeChat 2.2]
Andy-D has quit [Ping timeout: 245 seconds]
mpmc has quit [Ping timeout: 252 seconds]
nuuuciano has joined #linux-sunxi
mpmc has joined #linux-sunxi
DonkeyHotei has quit [Ping timeout: 252 seconds]
random_yanek has joined #linux-sunxi
kaspter has joined #linux-sunxi
DonkeyHotei has joined #linux-sunxi
megi has quit [Quit: WeeChat 2.2]
stellirin has quit [Quit: The Lounge - https://thelounge.github.io]
victhor has quit [Remote host closed the connection]
stellirin has joined #linux-sunxi
indy has quit [Quit: ZNC - http://znc.sourceforge.net]
indy has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 272 seconds]
selfbg has joined #linux-sunxi
t0dd1v has joined #linux-sunxi
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
chewitt has joined #linux-sunxi
leviathan has joined #linux-sunxi
IgorPec has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
diego_ has joined #linux-sunxi
IgorPec has quit [Ping timeout: 252 seconds]
yann has quit [Ping timeout: 240 seconds]
IgorPec has joined #linux-sunxi
tllim has quit [Read error: Connection reset by peer]
afaerber has quit [Quit: Leaving]
t0dd1v has quit [Quit: Connection closed for inactivity]
m4ssi has joined #linux-sunxi
<curlybracket> What seems a bit off is that while there's no HDMI video with neither 2560x1440 nor 1440x2560 screen, it showed up with a 1080x1920 panel. Now I see that both outputs display contents of the same framebuffer
clemens3 has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
f0xx has joined #linux-sunxi
qeed has quit [Quit: Leaving]
nuuuciano has quit [Ping timeout: 252 seconds]
mhlavink_afk has joined #linux-sunxi
hanetzer has quit [Ping timeout: 272 seconds]
mhlavink has quit [Ping timeout: 268 seconds]
nuuuciano has joined #linux-sunxi
yann has joined #linux-sunxi
leviathan has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
tuxillo has joined #linux-sunxi
afaerber has joined #linux-sunxi
nuuuciano has quit [Ping timeout: 252 seconds]
kaspter1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 252 seconds]
kaspter1 is now known as kaspter
elros1 has joined #linux-sunxi
hanetzer has joined #linux-sunxi
afaerber has quit [Quit: Leaving]
tnovotny has joined #linux-sunxi
mavkhimenia has quit [Remote host closed the connection]
mavkhimenia has joined #linux-sunxi
airwind has joined #linux-sunxi
airwind has quit [Quit: airwind]
clemens3 has quit [Remote host closed the connection]
airwind has joined #linux-sunxi
dddddd has joined #linux-sunxi
clemens3 has joined #linux-sunxi
reinforce has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
mavkhimenia has quit [Remote host closed the connection]
mavkhimenia has joined #linux-sunxi
mavkhimenia has quit []
mavkhimenia has joined #linux-sunxi
mavkhime_ has joined #linux-sunxi
mavkhimenia has quit [Ping timeout: 245 seconds]
AneoX has joined #linux-sunxi
AneoX_ has quit [Ping timeout: 245 seconds]
formruga has quit [Quit: Konversation terminated!]
Andy-D has joined #linux-sunxi
megi has joined #linux-sunxi
s_frit has quit [Ping timeout: 252 seconds]
formruga has joined #linux-sunxi
matthias_bgg has quit [Read error: Connection reset by peer]
matthias_bgg has joined #linux-sunxi
leviathan has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
IgorPec has quit [Ping timeout: 260 seconds]
chewitt has joined #linux-sunxi
airwind has quit [Quit: airwind]
diego_ has quit [Ping timeout: 252 seconds]
diego_ has joined #linux-sunxi
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-sunxi
fangesss has joined #linux-sunxi
fangesss has quit [Client Quit]
delarge has quit [Quit: leaving]
f11f13 has joined #linux-sunxi
DonkeyHotei has quit [Read error: Connection reset by peer]
Hao has joined #linux-sunxi
wasutton3_mobile has joined #linux-sunxi
selfbg has quit [Remote host closed the connection]
nuuuciano has joined #linux-sunxi
DonkeyHotei has joined #linux-sunxi
piccolo has joined #linux-sunxi
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 252 seconds]
piccolo has quit [Remote host closed the connection]
DonkeyHotei has quit [Read error: Connection reset by peer]
Hao has quit [Ping timeout: 245 seconds]
Hao has joined #linux-sunxi
alexxy has quit [Ping timeout: 276 seconds]
alexxy has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
Hao has quit [Ping timeout: 268 seconds]
DonkeyHotei has joined #linux-sunxi
elros1 has quit [Remote host closed the connection]
IgorPec has joined #linux-sunxi
piccolo has joined #linux-sunxi
formruga has quit [Quit: Konversation terminated!]
IgorPec has quit [Ping timeout: 268 seconds]
tllim has joined #linux-sunxi
f11f13 has quit [Quit: Leaving]
AneoX has joined #linux-sunxi
AneoX_ has quit [Ping timeout: 252 seconds]
matthias_bgg has quit [Ping timeout: 268 seconds]
tnovotny has quit [Quit: Leaving]
qeed has joined #linux-sunxi
<NiteHawk> anyone using a Linux 4.14 kernel on A20 and seeing this: "unable to initialize libusb: -99"? igraltist were you able to solve that somehow back at the end of last year (https://irclog.whitequark.org/linux-sunxi/2017-11-08#20498531)?
clemens3 has quit [Ping timeout: 244 seconds]
k4be has quit [Quit: nie ma]
k4be has joined #linux-sunxi
m4ssi has quit [Remote host closed the connection]
vagrantc has joined #linux-sunxi
wasutton3_mobile has quit [Ping timeout: 252 seconds]
dev1990 has quit [Ping timeout: 252 seconds]
<lvrp16> does anyone know where the cma is set in the device tree? or what the parameter is called so I can grep for it?
<lvrp16> not referring to the kernel config
afaerber has joined #linux-sunxi
chomwitt has joined #linux-sunxi
<shadeslayer> lvrp16: cma=500M in bootargs?
<lvrp16> hmm maybe i am mixing up another platform
<KotCzarny> rellla was hacking the cma yesterday
anarsoul|2 has joined #linux-sunxi
dev1990 has joined #linux-sunxi
mavkhime_ has quit [Ping timeout: 252 seconds]
yann has quit [Ping timeout: 244 seconds]
<lvrp16> KotCzarny: Thanks! exactly what I was looking for
<KotCzarny> lvrp16: read his whole adventure
<KotCzarny> he succeeds later on
<anarsoul|2> jernej: MoeIcenowy: what's the status of A64 HDMI patches? I see that dts changes have been merged
Mr__Anderson has joined #linux-sunxi
<lvrp16> fun
<jernej> anarsoul|2: 4.20 should have fully working A64 HDMI driver
<anarsoul|2> jernej: nice
<fALSO> FOUR TWENTY :-)
<fALSO> it will be a gooooooooooood kernel
<anarsoul|2> jernej: it's not on http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix for some reason - that's why I'm asking
<jernej> it's best if you check linux-next
<jernej> that's most reliable :)
jaganteki has joined #linux-sunxi
afaerber has quit [Quit: Leaving]
clemens3 has joined #linux-sunxi
Nyuutwo has joined #linux-sunxi
stellirin has quit [Quit: The Lounge - https://thelounge.github.io]
stellirin has joined #linux-sunxi
<fALSO> i saw some patches on the sunxi mailing list about cedros
<fALSO> is that also on linux.next jernej ?
<jernej> no, it's not
<fALSO> ohhh
<jernej> at lest last time I checked
<fALSO> wanted a tree with that already patched, to test it ou :-P
<jernej> but it's in special branch in linux-media
<jaganteki> qt5, EGL Error : Could not create the egl surface: error = 0x3003
<jernej> better use branch prepared by Bootlin
<jaganteki> any idea about this error..it's on arm64
<anarsoul|2> jernej: you mean for a64?
<fALSO> thanks jernej
<jernej> anarsoul|2: what? I was talking about cedrus driver
<jernej> nobody tested it on a64 afaik
<anarsoul|2> OK :)
<shadeslayer> jaganteki: wayland?
<jaganteki> fbdev
<shadeslayer> Qt5 needs GLES
<jaganteki> export QT_QPA_EGLFS_INTEGRATION=eglfs_mali
<jaganteki> export QT_QPA_PLATFORM=eglfs
<jaganteki> these are the settings
<shadeslayer> you need to install the gles libs, not the fbdev ones
<shadeslayer> and configure QtBase to build with GLES
<shadeslayer> that's a known working configuration, I've never used eglfs_mali
<jaganteki> sorry, I didn't get..I'm trying linuxfb
<jaganteki> enabled OpenGL ES2
<shadeslayer> yes, you need X11 armsoc and the DRM setup
<shadeslayer> it doesn't work with fbdev
<shadeslayer> not that I know of
<jaganteki> shadeslayer, fbdev and X11 are two options right. so can't we use fbdev with opengl
<shadeslayer> yes
<shadeslayer> afaik you can't use fbdev and opengl
<shadeslayer> or, again, atleast not to my knowledge
<jaganteki> shadeslayer, so may be I can give a try on X11 test instead of qt5
Nemo_bis has quit [Ping timeout: 272 seconds]
<shadeslayer> jaganteki: you can try it out with X11 + armsoc Xorg driver + Qt5 built with GLES
clemens3 has quit [Ping timeout: 252 seconds]
<jaganteki> shadeslayer, ok thanks. do you have any test procedure
clemens3 has joined #linux-sunxi
Nyuutwo has quit [Read error: Connection reset by peer]
Nyuutwo has joined #linux-sunxi
afaerber has joined #linux-sunxi
Nyuutwo has quit [Remote host closed the connection]
Nyuutwo has joined #linux-sunxi
<shadeslayer> jaganteki: what device are you using?
<jaganteki> BPI-M64
aalm has quit [Ping timeout: 268 seconds]
f0xx has quit [Ping timeout: 246 seconds]
leviathan has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
mavkhimenia has joined #linux-sunxi
jaganteki has quit [Ping timeout: 256 seconds]
mavkhimenia has quit [Ping timeout: 264 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
LargePrime has joined #linux-sunxi
ms71 has joined #linux-sunxi
smaeul has quit [Ping timeout: 252 seconds]
ms71 has quit [Ping timeout: 256 seconds]
<anarsoul|2> MoeIcenowy: do you have any plans to upstream anx6345 driver?
victhor has joined #linux-sunxi
muvlon has joined #linux-sunxi
chomwitt has quit [Quit: WeeChat 1.6]
Andy-D has quit [Ping timeout: 272 seconds]
clemens3 has quit [Ping timeout: 272 seconds]
scelestic has quit [Ping timeout: 272 seconds]
Mr__Anderson has quit [Remote host closed the connection]
quitte has joined #linux-sunxi
<quitte> Hi. What kind of surprises can I expect when I buy a pine a64 but read the cortex a53 reference manuals? Do I get a gic and trustzone?
<quitte> Yes I'm angry at my pi3
<KotCzarny> i think yes, but with gotchas
<quitte> such as?
<KotCzarny> not everything being enforced
<KotCzarny> but i'm only saying from memory of the channel log
<KotCzarny> have you searched irc logs?
<quitte> no.
<KotCzarny> for a quickie
<KotCzarny> look at 2017-01-17
<quitte> If at least it is somewhat there it'll be fine. the dealbreaker with the rpi3 for me is the interrupt controller.
<KotCzarny> basically almost all boards run without secure boot enabled
<quitte> Figured out how to get jtag working so that I could try multicore irq balancig...
<quitte> I don't care about secure boot
<KotCzarny> but without it trustzone isnt doing anything afaiu from those chats
<quitte> it just looks like a quick way to seperate memory access between interrupt service routines and the normal code without mmu reconfiguration, which I assume is slower
<quitte> no trustzone can be used from the interrupt vector tables from how I interpret the parts of the manuals I read
<quitte> by trustzone I mean the 33rd address bit that marks memory as secure
<KotCzarny> but trustzone isnt 64bit specific, then you can get some older board cheaply to play around?
<quitte> I already have a solid-run i.mx6 board. the problem is the jtag connection. It must survive being carried in a backpack
smaeul has joined #linux-sunxi
<KotCzarny> i mean allwinner one (a20/h3)
<quitte> hmm. I have a cubietruck...
<KotCzarny> maybe smaeul will know more
<quitte> burnt the power management chip though. but it still runs. I guess it would do if I figured out a good waz to attach jtag. It's shared with the sdcard so essentially the same problem as with the solid-run board
<KotCzarny> spi boot?
<KotCzarny> or fel-boot (via microusb)
<quitte> booting doesn't matter as long as jtag works
<quitte> oh
<quitte> which it doesn't
<quitte> the problem is attaching the wires such that they will survive being thrown in a backpack
<KotCzarny> get the tv box ?
<quitte> repeatedlz
<quitte> sorry about the y/z mistakes.
<quitte> tv box?
<KotCzarny> you will get something with quite tight box, and you can hotglue the wires/connector
<smaeul> KotCzarny: maybe I will know what?
<KotCzarny> smaeul: trustzone
<smaeul> KotCzarny: hardware or software?
<quitte> smaeul: hardware
<quitte> smaeul: it's about servicing interrupts fast while seperating the interrupted processes memory from the interrupt. My assumption being that doing the MMU thing is slower than switching to secure mode
<quitte> beeble: that looks good if shipping and tax is reasonable
<smaeul> quitte: are you on armv7 or armv8?
<smaeul> on armv8 all secure interrupts go through ATF if received in NS world
<quitte> smaeul: right now rpi3 which turns out doesn't have a usable interrupt controller. So now I need to figure out what kind of hardware I hould use instead
<quitte> ATF? automatic transmission fluid?
<smaeul> ARM trusted firmware
<smaeul> EL3
<smaeul> "secure monitor"
<quitte> that's just code I can write myself?
<beeble> quitte: ebay or search on aliexpress for similar stuff https://www.ebay.com/itm/Micro-SD-MicroSD-Breakout-Board-SPI-For-Arduino-/201781306925
<smaeul> sorry, I sort of turned my computer on in the middle of this discussion... I'm not sure what your goal is
diego_ has quit [Ping timeout: 272 seconds]
<quitte> smaeul: essentially I want to figure out interrupts in a multi core scenario. bare metal. Of course I'd rather not deal with legacy or cost saving measures because why would I.
s_frit has joined #linux-sunxi
<quitte> smaeul: And the RPI3 I have turns out to not have a GIC, which is unacceptable
<KotCzarny> saying the man who bought the rpi :>
<quitte> smaeul: and it needs to be able to be thrown in my backpack ;)
<smaeul> well A64/H5 SoCs have working GICv2, and an OpenRISC coprocessor with its own interrupt controller (including an NMI)
<quitte> KotCzarny: it's armv8 how was I supposed to know they'd recycle even the interrupt controller for a 64bit soc?
<quitte> openrisc? that foss architecture? Time flies.
<smaeul> as for secure mode, you can run A64/H5 with upstream opensource ATF, and I know people have used that with a TrustZone implementation (OPTEE, I believe)
<smaeul> though I'm not sure what the state of TrustZone ports is
<smaeul> yes, that one
matthias_bgg has joined #linux-sunxi
scelestic has joined #linux-sunxi
<quitte> Okay sounds like I won't hit a wall similar to the rpi with a pine 64 before it's obsolete.
<quitte> do you happen to know what it takes to jtag attach to it?
<smaeul> quitte: are you looking for hardware documentation? or software to use/examine?
<quitte> neither: hardware to use/examine
<smaeul> jtag... plug into the appropriate GPIO
<smaeul> beyond that, I don't know for sure
<quitte> so probably needs some pin configuration. It'll be fine
<smaeul> I know MoeIcenowy has used JTAG before, and I'm pretty sure openocd works with the H3 (latest 32-bit SoC), but that's about it
<beeble> iirc on a64 if there is no sd card detected it will mux the pins to jtag. otherwise you have to pinmux these or the alternative pins to jtag
<beeble> works with openocd
<smaeul> quitte: I know the pin configuration is setup by the boot rom if you FEL boot (the boot-over-USB protocol when you don't have a boot device plugged in
<beeble> in swd config
<quitte> beeble: being able to just load code to sram via jtag without any bootloader nonsense would be a dream
<beeble> you will start in 32bit mode on the a64 although
<beeble> but im not 100% sure on the a64 and jtag fallback right now. that was a while back i did it the last time
<quitte> yes I noticed that. no problem. all the peripherals are 32bit anyways so why waste all those bits in interrupt service routines
<quitte> thumb would probably do
<beeble> it is on rk33xx like that (the fallback)
<beeble> just keeping card detect inactive works
<smaeul> quitte: the openrisc coprocessor has direct access to everything (no MMU, can read/write all secure registers, can turn ARM cores on/off)
<smaeul> so you could use it as a custom software jtag or equivalent for some purposes
<beeble> so you might try that if it works the same
<quitte> thanks everybody. Pretty sure I'll buy the thing and then see why I don't like it. (except for the docuentation which I' sure I'd prefer the i.MX8's)
<KotCzarny> ah right, the docs
<KotCzarny> ;)
<smaeul> quitte: yeah, with allwinner documentation, usually it's there somewhere, but you may have to look in an older SoC's manual, or the bsp source code, or...
<KotCzarny> the running joke of allwinner
<beeble> quitte: if you can you might want to use a cmsis-dap adapter instead of ftdi based bitbanger
<quitte> beeble: I have this j-link v8 clone that so far seemed decent.
<beeble> yes, should work similar well
<beeble> quitte: btw, do remeber that gicv2 vs gicv3 has a major difference in interrupt distribution. gicv2 can broadcast interrupts for the sake of latency even though it decreased your performance
<beeble> this got removed from gicv3 and you have to assign a core for an interrupt
<quitte> beeble: 1:N vs. N:N ? and gicv3 dropped N:N?
dddddd has quit [Read error: Connection reset by peer]
<beeble> 1:N was dropped
<quitte> I may have misunderstood which was which. It is now impossible to have an interrupt wake more than one core?
<beeble> was N:N available? not sure right now
<KotCzarny> is that the reason there is no automatic irq scheduling on arm?
<quitte> as far as I understood an interrupt could either be assigned to 1 core or all cores. But not more than one core but less than all
<quitte> A proper service routine should be done fast enough for it not to matter. the peripheral clocks are the bottleneck on cortex-a. At least I hope to find a way to not block the cores waiting for the peripherals
<beeble> The ARM GIC architecture guarantees that a 1 of N interrupt is presented to only one PE
<beeble> listed in the target PE set.
<beeble> and which PE takes it is implementation specific
chewitt has quit [Ping timeout: 252 seconds]
<quitte> PE?
<beeble> processing element. that was a verbatim copy from the gic spec
<beeble> and maybe for some pointers https://patchwork.kernel.org/patch/10409393/
<quitte> I don't think that pdf will load anytime soon on this connection I'm on. But "PE set" sounds like an interrupt can be handled by more thatn one CPU, still. Except now it doesn't have to be either one or all
<quitte> I don't understand how I didn't find out about the existence of GIC3 and 4 days ago when I searched for GIC documentation and the latest I found was V2. Oh well.
IgorPec has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
IgorPec has quit [Ping timeout: 252 seconds]
quitte has quit [Quit: leaving]
matthias_bgg has quit [Ping timeout: 272 seconds]
<anarsoul|2> wens: are you around?
<anarsoul|2> wens: I'm trying to clean up audiocodec patches for A64
<anarsoul|2> and looks like sun8i-codec-analog.c is not trivial - I have to replace has_* quirks with callbacks
<anarsoul|2> and duplicate the code since registers addresses have changed
tllim has quit [Quit: Leaving]
<anarsoul|2> normally I would use regmap to deal with it
<anarsoul|2> but it's not possible in this case since it uses register addresses (and values) in static routes and widgets arrays
<anarsoul|2> wens: so does it justify to move A64 code to another driver instead of extending sun8i-codec-analog.c?
<anarsoul|2> I *can* extend sun8i-codec-analog.c but it becomes messy and hard to read
tl_lim has joined #linux-sunxi
tllim has joined #linux-sunxi