lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC> <viraniac> Hi Oskar. I have been working with Armbian for past few months and here are my understanding for kernel branches used by us. Current and edge kernels that we release are generally based on kernels released on kernel.org. If there is a need to release thirdparty kernel, that is usually named - legacy when it comes from board manufacturer, or is given a name identifying the 3rd-Pa <clipped message>
<DC-IRC> <viraniac> rty that the kernel is based on.
<DC-IRC> <viraniac> The edge kernel is supposed to be bleeding edge and is not required to be based on a stable kernel version. If the maintainers feel that the RC kernels are bringing in some core features for a board, they can choose to ship the same.
<DC-IRC> <stonededge> Does anyone know the best way to write to a display frame buffer on the RK3588? Usually I used dispmanx on the rasp pi but Iā€™d like to display a battery indicator over the top of emulationstation. Weston/Wayland and Armbian is my setup currently šŸ™‚
<DC-IRC> <stonededge> Does anyone know the best way to write to a display frame buffer on the RK3588? Usually I used dispmanx on the rasp pi but Iā€™d like to display a battery indicator over the top of emulationstation and maybe some other graphics. Weston/Wayland and Armbian is my setup currently šŸ™‚
<DC-IRC> <stonededge> Does anyone know the best way to write to a display frame buffer on the RK3588? Usually I used dispmanx on the rasp pi which I know is a Broadcom specific API, but Iā€™d like to display a battery indicator over the top of emulationstation and maybe some other graphics. Weston/Wayland and Armbian is my setup currently šŸ™‚
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> <enok71> Thanks for answering Gunjan. This board rock-5a doesn't have a "current" kernel defined. Only legacy, edge and collabora. But perhaps that is related to being a "wip" board.
<DC-IRC> <enok71> Thanks for answering Gunjan. This board rock-5a doesn't have a "current" kernel defined. Only legacy, edge and collabora. But perhaps that is related to being a "wip" board.
<DC-IRC> <enok71> Is anybody testing the rock-5a with latest mainline kernels (collabora, edge)? If not I could contribute with that.
<DC-IRC> <tenkawa42> @enok71 I can only speak for the 5B... I am using it on 2 of those with the 6.7-rc one and its working fairly good however I do use mine headless as servers though
<DC-IRC> <tenkawa42> I think I burned up my oldest board though last week (really put it through a lot)
<DC-IRC> <tenkawa42> I build my own images with a different builder so its a bit different load than Armbian but it still uses Debian as its root/userland base
<DC-IRC> <enok71> @tenkawa42 Yes the 5B has been on the market much longer and is far more popular, and is also a supported board. The 5A is a "wip" board. They have lots in common so I imagine people develop the 5B and then move selected functionality to the 5A. Perhaps with little or no testing? Just my speculations.
<DC-IRC> <tenkawa42> Let me look at the 5A page on Radxa's sit
<DC-IRC> <tenkawa42> Let me look at the 5A page on Radxa's site
<DC-IRC> <enok71> 5A is based on RK3588S, in contrast to the 5B RK3588. Fewer display outputs, fewer PCIE lanes. Smaller physical board format.
<DC-IRC> <tenkawa42> Well if it is a 3588S that's problematic
<DC-IRC> <tenkawa42> The 3588 S vs the full 3588 are still not up to par I think in their enablement
<DC-IRC> <tenkawa42> I would need to look at the dts routing
<DC-IRC> <tenkawa42> unfortunately the one 3588s I have (Khadas) they are way behinnd getting things up to date
<DC-IRC> <tenkawa42> unfortunately the one 3588s I have (Khadas) they are way behind getting things up to date
<DC-IRC> <enok71> There is a 5a dts file at least. And a maintainer @amazingfate . Most things should be very similar, I expected, just removing what's not there? Should be fairly easy to ride on the 5B work, I thought.
<DC-IRC> <spooky8086> I think the 5A should be up to par, but pcie is missing in the dts for mainline?
<DC-IRC> <tenkawa42> (Anyone in here from Khadas yes that is a plea to work with Linus/et all....
<DC-IRC> <tenkawa42> (Anyone in here from Khadas yes that is a plea to work with Linus/et all....)
<DC-IRC> <tenkawa42> @spooky8086 not for the 3588... I'm using pci-e on mine in mainline
<DC-IRC> <enok71> Looks like pcie will be added for both 5a and 5b in 6.7 according to https://www.collabora.com/news-and-blog/news-and-events/kernel-6.6-long-awaited-features-and-enhanced-hardware-support.html
<DC-IRC> <zoro_king503> hi
<DC-IRC> <zoro_king503> woh arabi
<DC-IRC> <tenkawa42> @enok71 which pci-e? for the mini connector?
juri_ has quit [Ping timeout: 252 seconds]
<DC-IRC> <enok71> @tenkawa42 looks like it's only 5B that's got pci-e imlemented in the devicetree so far. It's 4-lane pcie3 in the m.2 m-key and 1-lane pcie2 in the m.2 e-key, and the pcie lane to the ethernet port.
<DC-IRC> <enok71> I can't see any of it in the 5A dts.
<DC-IRC> <tenkawa42> Yeah not surprised
<DC-IRC> <tenkawa42> 3588s are not getting a lot of "attention"
<DC-IRC> <tenkawa42> It took long enough just to get 3588 support at all
<DC-IRC> <enok71> If I get a little time I could try to implement something. It really shouldn't be hard, given that the 5b implementation works.
<DC-IRC> <tenkawa42> heh..... were you around for the 3588 implementation though?
<DC-IRC> <tenkawa42> It was a royal mess
<DC-IRC> <enok71> No? What happened šŸ™‚
<DC-IRC> <tenkawa42> There are still some outlying things that aren't 100% great
<DC-IRC> <tenkawa42> PD power was extremely flaky in most implementations
<DC-IRC> <enok71> Oh I read something about that.
<DC-IRC> <tenkawa42> There were some IO hiccups with certain media but that usually always happens
<DC-IRC> <enok71> That was on Rock 5A. I experienced it myself.
<DC-IRC> <tenkawa42> I've moved on to RISC-V... whole new set of challenges
<DC-IRC> <enok71> Some emmc brands simply don't work.
<DC-IRC> <tenkawa42> the 5B had it too.. not just the 5A
<DC-IRC> <enok71> Some emmc brands simply don't work with the 5A.
<DC-IRC> <tenkawa42> the 5B has been around for a while... keep that in mind
<DC-IRC> <enok71> The documentation from Rockship seems to lack lots of details. Is that the root cause?
<DC-IRC> <tenkawa42> oh most definitely hurts
<DC-IRC> <tenkawa42> That caused a lot of pain over the years in Broadcom debugging too for RPI
<DC-IRC> <tenkawa42> Lot of people use them but Broadcom holds on to their docs tight
<DC-IRC> <enok71> Strange choice. Will hurt the manufacturer when people can't use their products.
<DC-IRC> <tenkawa42> I have a RPI5 just delivered today waiting at home heh
<DC-IRC> <enok71> I was in luch and got two RPI5 8GB very very early šŸ™‚ Used them a lot and watched the price sky-rocket.
<DC-IRC> <tenkawa42> The computer industry "is" strange... I learned that in my career lol
<DC-IRC> <enok71> I was in luck and got two RPI5 8GB very very early šŸ™‚ Used them a lot and watched the price sky-rocket.
<DC-IRC> <enok71> Eventually sold them for double price I bought them. Now price has dropped again. Perhaps time to buy šŸ™‚
<DC-IRC> <tenkawa42> Yeah I got 3 coming ... 1 here, 1 acknowledge (waiting to ship this week), and 1 still on backorder
<DC-IRC> <tenkawa42> Yeah I got 3 coming ... 1 here, 1 acknowledged (waiting to ship this week), and 1 still on backorder
<DC-IRC> <tenkawa42> This is all hobby for me now...
<DC-IRC> <enok71> It's a bit of mix work and pleasure for me. But my rockchip interest is my own, i.e. no paying client.
<DC-IRC> <tenkawa42> nod.. yeah I hear ya
<DC-IRC> <enok71> I think the 5A is nice. I measure 1.8W idle, and that's before spending any effort on e.g. shutting down stuff. The RPI5 consumes a lot more.
<DC-IRC> <enok71> And that's with 8 cores and 16GB, and emmc.
<DC-IRC> <tenkawa42> I have been burned by "every" Rockchip board engineering quality so far... Broadcom builds much better design/quality
<DC-IRC> <enok71> Ok! Yeah, could be a difference in quality/robustness.
<DC-IRC> <tenkawa42> Amlogic and Allwinnner are no friends of mine either
<DC-IRC> <tenkawa42> I "do" like Rockchip's raw performance on some units
<DC-IRC> <enok71> I do have a Rock 4B that's worked flawlessly day and night for years now, as a webserver.
<DC-IRC> <tenkawa42> Yeah that one is is a RK3399... those tend to either be sturdy forever or fall apart instantly
<DC-IRC> <tenkawa42> (I have 2 RK3399's... one is unstoppable... one wouldn't power up one day for no apparent reason... never could get any power to the board
<DC-IRC> <tenkawa42> (I have 2 RK3399's... one is unstoppable... one wouldn't power up one day for no apparent reason... never could get any power to the board)
<DC-IRC> <enok71> Interesting.
<DC-IRC> <tenkawa42> yeah
<DC-IRC> <enok71> I suppose the rational thing is to go with the flow, and use RPI5. Best chance to avoid bad surprises is to do as everyone else.
<DC-IRC> <tenkawa42> Haahaa I have so many random boxes lol
<DC-IRC> <enok71> (Unless experimenting is the goal)'
<DC-IRC> <tenkawa42> it is... that's my forte/kinda what I did for a living
<DC-IRC> <enok71> šŸ™‚ I guess I'm also in for the challenge rather than the final result mostly
<DC-IRC> <tenkawa42> heheh indeed
<DC-IRC> <tenkawa42> good chat.. I gotta shutdown and get ready to leave.. .be back online later
<DC-IRC> <enok71> Me too. Time for sleep here. See ya.
<DC-IRC> <k.s.bedford.jr> Any One know whats going on with armbian and teh rk3588 . our class has 4 Nanopct6 boards but no armbian img for them
<DC-IRC> <k.s.bedford.jr> as we now have armbian on the VisionFive boards we want the same on the t6 boards