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 - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
anessen97 has quit [Remote host closed the connection]
anessen97 has joined #linux-amlogic
sputnik_ has quit [Read error: No route to host]
sputnik_ has joined #linux-amlogic
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
camus1 has joined #linux-amlogic
chewitt_ has quit [Quit: Zzz..]
camus has quit [Read error: Connection reset by peer]
camus1 is now known as camus
chewitt has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
Terry1373 has quit [Quit: Bye Bye]
Terry1373 has joined #linux-amlogic
camus has quit [Read error: Connection reset by peer]
camus has joined #linux-amlogic
Tartarus has quit [Ping timeout: 264 seconds]
arnd has quit [Ping timeout: 264 seconds]
Tartarus has joined #linux-amlogic
arnd has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
Darkmatt- has quit [Ping timeout: 245 seconds]
alpha_one_x86 has quit [Remote host closed the connection]
camus has quit [Ping timeout: 264 seconds]
camus has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-amlogic
camus has quit [Ping timeout: 245 seconds]
camus has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 245 seconds]
camus1 is now known as camus
<mcirsta> hi chewitt. I managed to get your kernel from github and I am compiling it as a Manjaro package
<mcirsta> they have their own config file which I'm now using, any idea if there's something specific in the config file to build the Amlogic vdec
<mcirsta> btw how chewitt, narmstrong what do you use to build for aarch64 and how long does it take to build the kernel ? ( just curious )
<chewitt> it might be a bit minimal for a desktop OS like Manjaro
<chewitt> but @spikerguy who preps the Manjaro images should have everything needed, if not we can get him/them to add things
<chewitt> I'm cross compiling on a 32x core AMD TR2 box with 128GB ram and 4TB of nvme SSD
<chewitt> although work VMs occupy most space .. my LE build VM is 16GB RAM I think
<chewitt> although work VMs occupy most space .. my LE build VM is 16GB RAM I think
<chewitt> build time for a complete LibreELEC distro image is about 35-40 mins depending on what else is consuming cpu
Darkmatter66 has quit [Ping timeout: 256 seconds]
<chewitt> if I shut everything else down it's about 26 mins, but there are things I host for work that can't be stopped
<chewitt> the kernel building part on it's own takes about 2-3 mins
<chewitt> but the way the build-system works, if it's just a respin with an extra patch or config change is closer to 30s
Darkmatter66 has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
<mcirsta> OK, thanks for that. I'll just use the Manjaro config for now and I'll check if the vdec is in there , hopefully it is
<mcirsta> for some reason I though compiling on a aarch64 distro is better and managed to secure some Oracle cloud with 12 virtual Amprere I think cores
<mcirsta> it's decent
<mcirsta> 9 min to compile the Manjaro ARM kernel which is probably bigger than the LE one
khilman has quit [Ping timeout: 264 seconds]
khilman has joined #linux-amlogic
jernej has joined #linux-amlogic
dagmcr has quit [Ping timeout: 264 seconds]
khilman has quit [Ping timeout: 265 seconds]
jbrunet has quit [Ping timeout: 264 seconds]
dagmcr has joined #linux-amlogic
khilman has joined #linux-amlogic
jbrunet has joined #linux-amlogic
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-amlogic
chewitt has quit [Quit: Zzz..]
jernej has quit [Ping timeout: 245 seconds]
jernej has joined #linux-amlogic
jernej has quit [Ping timeout: 260 seconds]
lvrp16 has quit [Ping timeout: 264 seconds]
lvrp16 has joined #linux-amlogic
rockosov has joined #linux-amlogic
tdebrouw has joined #linux-amlogic
<rockosov> Hi all! Let me introduce myself. I’m kernel developer from SberDevices. We are creating consumer devices based on Amlogic SoC, and started our internal work on the Amlogic upstream kernel support a few months ago. We already sent meson-ir-tx driver to upstream, and it was accepted. I hope we can help the community with Amlogic happy upstreaming.
anessen97 has quit [Remote host closed the connection]
<mcirsta> hi rockosov, if you can say , what kind of consumer devices
<mcirsta> more specifically will you be using the hardware vdec
<rockosov> Yes, sure, I can provide the links to our already released devices. Here you are https://sberdevices.ru/sberportal/, https://sberdevices.ru/sberboxtop/, https://sberdevices.ru/sberbox/
<mcirsta> yes, I saw now
<mcirsta> I actually think it's a great idea so use mainline for Amlogic, I've just tested on an old S912 TV box I had and most things work great
<mcirsta> except for one thing the HW vdec
<mcirsta> I was actually talking with the guys here about how I could help with the hardware vdec for Amlogic
<rockosov> We are using hardware vdec, but still based on Amlogic internal driver
<mcirsta> unfortunately I'm a c++ dev , not a kernel or embedded one
<mcirsta> vdec seems to be one of the last if not the last piece for proper mainline support
<rockosov> I’m in kernel developers teams around 7 engineers. We are maintain all low level things in the our devices. Our goal is transition to upstream code and valuable contribution to it of course
<mcirsta> that would indeed be great
<rockosov> I’m not currently understand a status for other video pipeline support
<rockosov> Amlogic has many things inside like GDC, ge2d etc
<mcirsta> and it would even make the news , as the first Amlogic hardware to use mainline
<mcirsta> I don't know much about the current vdec status either
<mcirsta> just that there was work done but now it needs to be brought up to date and finalized
tdebrouw has quit [Quit: Leaving.]
<rockosov> I thought VIM3 and some Odroid devices already use mainline, haven’t?
<mcirsta> I just started looking into it and setting up my development environment today
<mcirsta> I don't think so, maybe there are some mainline images
<mcirsta> but you cannot really use mainline if you want vdec
<mcirsta> as far I know at least
<mcirsta> besides I don't count those as they're not consumer devices
<mcirsta> I think when you deliver stuff to consumers then you're shipping a product
<mcirsta> dev boards are nice of course but they're for geeks :)
<mcirsta> even as a geek I wouldn't really take a VIM3 and connect it to my TV
<mcirsta> it would care my wife :D
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
warpme__ has quit [Quit: Connection closed for inactivity]
<rockosov> You are right! :-) but dev boards are good choice to debug reference flows for comparing with production device situation
anessen97 has joined #linux-amlogic
tafa has joined #linux-amlogic
anessen97 has quit [Remote host closed the connection]
anessen97 has joined #linux-amlogic