ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
sakman has quit [Remote host closed the connection]
headless has joined #armlinux
heat has joined #armlinux
apritzel has joined #armlinux
headless has quit [Quit: Konversation terminated!]
apritzel has quit [Ping timeout: 245 seconds]
rvalue has quit [Ping timeout: 246 seconds]
rvalue has joined #armlinux
<maz>
amstan: holly crap! I remember running KVM on that exact device, and it wasn't pretty (Cortex-A15 r0p4 has so many interesting bugs...). Good thing I killed 32bit support in 5.6 or so!
apritzel has joined #armlinux
Huahua_w has joined #armlinux
Huahua_w has quit [Quit: Leaving]
HappyMaya has joined #armlinux
HappyMaya has quit [Quit: Client closed]
heat has quit [Remote host closed the connection]
heat_ has joined #armlinux
apritzel has quit [Ping timeout: 264 seconds]
rvalue has quit [Ping timeout: 246 seconds]
rvalue has joined #armlinux
heat has joined #armlinux
heat_ has quit [Ping timeout: 245 seconds]
apritzel has joined #armlinux
apritzel has quit [Ping timeout: 245 seconds]
headless has joined #armlinux
elastic_dog has quit [Ping timeout: 245 seconds]
elastic_dog has joined #armlinux
heat_ has joined #armlinux
heat has quit [Read error: Connection reset by peer]
macromorgan has quit [Remote host closed the connection]
macromorgan has joined #armlinux
apritzel has joined #armlinux
Sally1 has quit [Ping timeout: 245 seconds]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
apritzel has quit [Ping timeout: 244 seconds]
heat_ has quit [Remote host closed the connection]
heat_ has joined #armlinux
apritzel has joined #armlinux
Sally1 has joined #armlinux
Sally1 has quit [Ping timeout: 246 seconds]
elastic_dog has quit [Ping timeout: 260 seconds]
<psydroid>
I've got both of my ARM SBCs, an Nvidia Jetson Nano and an Orange Pi Win Plus, up and running again with Debian 12.1 this week
<psydroid>
I was wondering if any effort has been put into mainlining the kernel bits for Jetson Nano, as I just took the kernel from Jetpack (Ubuntu) for that
<psydroid>
I know this should be Nvidia's job, but they don't seem to be very interested, so I wonder if anyone else has been working on it
elastic_dog has joined #armlinux
<Xogium>
in all fairness, there are a good bunch of manufacturers that act the same way. And also given nvidia's track record with their gpu and linux kernel support, I'm not exactly surprised they wouldn't bother
<Xogium>
doesn't seem like people have worked on it. At least I can't see any device tree file for it anywhere
<psydroid>
alright, that's good to know at least
<Xogium>
no mention of it on internet also
<psydroid>
the device has gone end-of-life, so I think this would be a good way to extend its life using mainline software
<psydroid>
yes, I looked a bit on the internet and couldn't find any mention of it anywhere
<Xogium>
yeah thing is porting the SoC and such will be a lot of work
<Xogium>
I've also not a clue if the AI things would even work, not to mention the gpu
<psydroid>
so maybe this would be an ideal device to get my hands dirty with
<Xogium>
cause you won,t just need to port the board, you'll also need to port the SoC and maybe the gpu, and all the AI bit and pieces
<Xogium>
still, if you have the knowledge, I'd say why not ?
<psydroid>
I have graphical output using whatever default driver it loads, which I think is nvgpu
<Xogium>
yeah but my point is, they might have patched it in their kernel
<Xogium>
or maybe this is enough of a common gpu that it would work
<psydroid>
I'm not exactly experienced, but I know C, ARM assembly and Linux (2.6) kernel internals
<psydroid>
yeah, I will look into all of that
<psydroid>
I've got the sources to their kernel too
<Xogium>
oof 2.6, sounds like you will need some up to date knowledge ;) but heh, this is already much better than me