narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
Elpaulo has quit [Quit: Elpaulo]
angelsl has quit [Read error: Connection reset by peer]
angelsl_ has joined #linux-amlogic
angelsl_ is now known as angelsl
vagrantc has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
Tonymac32 has quit [Ping timeout: 256 seconds]
<Necrosporus> chewitt, but mine is 8726M not MX, is it important?
<chewitt> same thing
<chewitt> unless it's even older
<chewitt> you called it Meson 3 .. I understand 8726MX as Meson 6
<chewitt> either way, this is 10+ years old and comprehensively outperformed by a Raspberry Pi 2 :)
Tonymac32 has joined #linux-amlogic
Tony_mac32 has joined #linux-amlogic
Tonymac32 has quit [Ping timeout: 256 seconds]
<chewitt> only 9 years old
<chewitt> and the MX variant comes later, only 8 years old
Tonymac_32 has joined #linux-amlogic
<chewitt> (but both still outperformed by a Raspberry Pi Zero)
<Tonymac_32> chewitt which is? I missed it
<chewitt> 8726M
<Tonymac_32> it's a dual core though isn't it?
Tony_mac32 has quit [Ping timeout: 256 seconds]
<chewitt> nope, looks like 8726MX is the dual version
<Tonymac_32> ah ok
<chewitt> 8726M is single
<chewitt> M and M3 are single
<chewitt> 1GHz
<Tonymac_32> but a cortex-anything vs an arm11 shouldn't be a competition
<chewitt> Mali 400
<chewitt> A9 chip
<chewitt> the convo originally started at software
<chewitt> so pi wins hands down
<Tonymac_32> ah well in that case. ;)
<Necrosporus> AMLOGIC MESON3 8726M SKT SH
<Necrosporus> Whatever it means
<Necrosporus> So I should look for 8726MX kernel since it's the same thing but dual core
<Necrosporus> chewitt, maybe it is, but there is an important point. The Amlogic thing I do already have but I do not have RPi0 or whatever
<chewitt> If you are retired or unemployed or just really determined (aka bloody minded) .. it's a nice project to get it working
<chewitt> If "my time is money" or anything vaguely like that factors into your life, bin it and get a Pi0
<chewitt> or a similarly cheap (but much newer) ARM thing
* Tonymac_32 has a Mini2440, will stay quiet
<chewitt> Necrosporus what do you want to do with it?
<Necrosporus> I want to turn it into a simple game console so it can run stuff like SuperTux on TV
<Necrosporus> or other native open source GNU/Linux games
<Tonymac_32> my much bigger boards don't hold up well against games, I don't think that one will pull it off
<chewitt> mainline Linux support for Meson 9 is good, Meson 8 is increasingly good - via @xdarklight sources
<Necrosporus> Tonymac_32, even if that's 2D games?
<Necrosporus> Like logic puzzle
<chewitt> Meson 6 is bare-bones, not usable for anything beyond basic board boot
<chewitt> Meson 3 .. non existent
<chewitt> so you'd be dependent on BSP kernels
<Necrosporus> Another idea, maybe it can be used to watch youtube?
<Tonymac_32> ok 2D sure, I misread and thought you put tuxcart ;)
<chewitt> (and u-boot)
<Necrosporus> Well, I can use u-boot burned onto the chip
<chewitt> https://github.com/LibreELEC/linux-amlogic/tree/amlogic-3.10.y <= this is a now-abandoned kernel for 8726MX
<Necrosporus> But default android distro is terrible
<Necrosporus> chewitt, alright, would Orange Pi 4 be a good investment? Or RPi 4b 8G?
<chewitt> these days I'm not aware of anyone anywhere working on anything below Meson 8
<Necrosporus> Or which is the strongest ARM board in existance with good mainline support?
<chewitt> for the gaming use-case Pi hardware is a no brainer because it's so well supported by all the gaming distos
<Tonymac_32> I use an XU4
<chewitt> pi hardware is never the best for raw performance, but the software life is simple
<Tonymac_32> but for native games, an S912 has a Midgard GPU correct?
<chewitt> XU4 is old hardware these days
<Tonymac_32> lol and yet, software ;)
<Necrosporus> Well, I guess I can try to compile something old for this board real quick and see if it works like the link to 3.10.y tree
<chewitt> Linux XU4 5.10.0-rc4 #1 SMP PREEMPT Sat Nov 21 08:57:09 UTC 2020 armv7l GNU/Linux
<chewitt> still can't get panfrost to run tho :(
<chewitt> kmscube works, but not Kodi
<Tonymac_32> ah ok
<Tonymac_32> my retro gaming setup is perfect, can't remember the kernel though
<Tonymac_32> the rest are headless
<Tonymac_32> my RK hardware panfrost is no problem on
<chewitt> 4.14 or 5.4 prob.
<chewitt> most of memeka's hacks aren't valid in the kernel these days either
<Tonymac_32> yeah
<chewitt> so media support is rather regressed, while lots of other bugs are resolved
<chewitt> (sounds a bit like amlogic)
<Tonymac_32> have you had luck on the S912? I never got my hands on one of those.
<chewitt> I have a few of them
<Tonymac_32> I only have a Vim1
<chewitt> panfrost runs well enough that some of the gaming distros are now taking interest
<chewitt> (also because they track my kernels a bit)
<Tonymac_32> haha
<chewitt> but I suspect the issue will be mali blobs (as always)
<chewitt> I think they're still using the libhybris workaround
<chewitt> and Android blobs
<Tonymac_32> dirty
<Tonymac_32> lol
<Necrosporus> Are there good boards which work with no blobs?
<Necrosporus> At least no blobs in kernel space
<Necrosporus> Like wi-fi firmware doesn't count
<chewitt> mali hardware is now very well supported by mesa (lima/panfrost)
<chewitt> but retro games push the boundaries a litttle
<Tonymac_32> just a wee
<Tonymac_32> native games though shouldn'
<Tonymac_32> t be too bad
<chewitt> I suspect half the issue with retro games is the code quality of the emulators
<Tonymac_32> I played some minetest on my Tinker board actually just to see if it would work
<Tonymac_32> that's definitely it, especially since the hardware being emulated often had some wonky ways of doing graphics
<chewitt> the fragmentation in the retro-gaming ecosystem makes Android look amazingly conformant
<Tonymac_32> XD
<chewitt> the wheel is frequently reinvented .. it's a PITA from a maintainer perspective
<chewitt> for retro gaming i'd get a pi simply because i'd rather play games than trace driver weirdness to make things work
<chewitt> pi3/pi4 will be great for that use-case
<Tonymac_32> performance wise I'd say Pi 3 < XU4 < Pi 4
<Tonymac_32> I was horribly disappointed in the Pi3
<Tonymac_32> and can only hope the Pi4 was worth the e-waste
<chewitt> it's a compromise like all pi designs
<chewitt> but it moves the needle in a forwards direction
<Tonymac_32> I use a Pi for my music player with DAC and one for a LOAR gateway
<Tonymac_32> LORA
<chewitt> and since it's a very different SoC to the previous ones, they're taking upstreaming seriously this time
<Tonymac_32> Is it still like a goofy fiddler crab with a GPU leading the ARM Cores around?
<Tonymac_32> The engineering catastrophe of the 3 kind of poisoned my opinion forever I'm afraid
<chewitt> it evolved
<chewitt> but still a compromise
<chewitt> at the end of the day its primary purpose is teaching kids to code, not be the best device in every category
<Tonymac_32> well, maybe tell the foundation that, they seem confused
<Tonymac_32> :D
<Tonymac_32> It is good for that purpose
<chewitt> they can be a bit schizophrenic sometimes
<chewitt> I do enjoy chats with them from time to time :)
<Tonymac_32> I bet
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
angelsl has quit [Read error: Connection reset by peer]
angelsl_ has joined #linux-amlogic
angelsl_ is now known as angelsl
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
cmeerw has joined #linux-amlogic
asdf28 has joined #linux-amlogic
nexysno has joined #linux-amlogic
<asdf28> i have compiled the kernel and loaded the meson drm driver, but there is no /dev/dri/card0, also nothing in dmesg
<asdf28> has anyone made this work?
asdf28 has quit [Ping timeout: 260 seconds]
asdf28 has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 265 seconds]
<narmstrong> asdf28: why would you use this version ? It’s the mainline 4.10 kernel driver I wrote back ported to their 3.14 tree
_whitelogger has joined #linux-amlogic
nexysno has quit [Remote host closed the connection]
nexysno has joined #linux-amlogic
<asdf28> i just found it interesting and wanted to see if it works
<asdf28> by the way, i finally got the mali framebuffer driver to work! but not on an amlogic box, it was on an allwinner board
<asdf28> i used the same kernel and mali driver version on both devices
<asdf28> without leak_smem, both boards showed a black screen when running a graphical app
<asdf28> then i enabled it and the allwinner board worked, but the amlogic box had a segmentation fault
<asdf28> so at least this seems to be the way to go, even if it didn't work out yet
<asdf28> is the DRM driver supposed to create a /dev/dri device? or was that functionality not implemented yet?
<asdf28> there were some lines commented out, but when i enabled them, i realized that they were probably meant for a newer kernel version
<chewitt_> ^ was working on 5.6/5.7 afaik .. not sure it's been tested since as LE switched to mesa/lima
chewitt_ is now known as chewitt
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
<asdf28> chewitt thank you. do you mean it works with the mali fbdev blob? because i thought libreelec used the wayland/kms one
<chewitt> not tested with fbdev
<chewitt> but afaik we didn't disable anything in the driver to make it not-work with others
<chewitt> but mali is all black magic so who knows :)
<asdf28> thank you, will try that. i think i haven't tried that version yet
<chewitt> what board are you trying to use? .. and for which use-case?
<asdf28> an s905x box
<asdf28> the use case is, i wanted to help to update the box to a newer kernel in lakka
<asdf28> but i cannot find a working graphics driver
<asdf28> i mean, they all work but not smoothly
nexysno has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
<chewitt> how far off is mesa/lima?
<chewitt> I ask because, at least with lima there are developers you can report issues to
<chewitt> with blobs it's all on you
<chewitt> and is it "everything" slow or just specific emulators?
<asdf28> well the biggest issue right now is some kind of memory leak
<asdf28> that's probably not even related to the graphics driver
<asdf28> lima does not work smoothly on my allwinner device, it has a little hiccup every second, no matter what's running, it's jerky
<asdf28> it works better on the amlogic box but it crashes from time to time and 3d games will mostly not work
<asdf28> i'm trying to find out if any of that is even related to the graphics driver, i couldn't find out yet
<asdf28> but none of this did happen with the legacy allwinner/amlogic kernels
<asdf28> the mali wayland blob worked best so far but i get memory leak errors and i can see the memory filling up in task manager
nexysno has joined #linux-amlogic
<asdf28> but that's probably something else as it happens with both mesa and mali blobs
<asdf28> i'll try to install glmark to see if it happens there too
asdf28 has quit [Ping timeout: 240 seconds]
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
angelsl has quit [Read error: Connection reset by peer]
angelsl_ has joined #linux-amlogic
angelsl_ is now known as angelsl
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
asdf28 has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
nexysno has quit [Quit: Textual IRC Client: www.textualapp.com]
ldevulder__ has quit [Ping timeout: 264 seconds]
angelsl has quit [Read error: Connection reset by peer]
angelsl_ has joined #linux-amlogic
angelsl_ is now known as angelsl
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
angelsl has quit [*.net *.split]
chewitt has quit [*.net *.split]
AUser has quit [*.net *.split]
ndufresne has quit [*.net *.split]
angelsl has joined #linux-amlogic
chewitt has joined #linux-amlogic
AUser has joined #linux-amlogic
ndufresne has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
<xdarklight> khilman: Hi Kevin, can you please do me a favor and include https://patchwork.kernel.org/project/linux-amlogic/list/?series=384491 in your testing branch so Kernel CI can play with it on the boards in the farm? I'm not expecting any breakage but since I only have one G12A (X96 Max) and one SM1 (X96 Air) board I cannot cover many board-variants myself
yann has joined #linux-amlogic
vagrantc has joined #linux-amlogic
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic
angelsl has quit [Read error: Connection reset by peer]
angelsl_ has joined #linux-amlogic
angelsl_ is now known as angelsl
asdf28 has quit [Ping timeout: 240 seconds]
angelsl has quit [Read error: Connection reset by peer]
angelsl has joined #linux-amlogic