00:03 <Armbian-Discord> <T​enkawa> linux-5.10-gen-rkr3.4 is a radxa specific repo thing...

00:03 <Armbian-Discord> <T​enkawa> so its their naming conventions

00:04 <Armbian-Discord> <T​enkawa> https://github.com/radxa/kernel/tree/linux-5.10-gen-rkr3.4

00:05 <Armbian-Discord> <T​enkawa> just like they formerly were using stable-5.10-rock5

00:06 <Armbian-Discord> <T​enkawa> however that one has long since stopped being updated

00:08 <Armbian-Discord> <c​0rnelius> really poor naming... they should have just named it radxa-5.10.y or something to that effect.

00:08 <Armbian-Discord> <T​enkawa> Yeah... not sure what their intent was with the naming

00:10 <Armbian-Discord> <T​onymac32> Lolz

00:10 <Armbian-Discord> <c​0rnelius> my guess would be generation rockchip release 3.4

00:10 <Armbian-Discord> <T​onymac32> Lindroidixa

00:36 <Armbian-Discord> <r​pardini> What I meant is... is there a source for original rk tree somewhere? I wanna split off Radxa's patches from rk base

00:42 <Armbian-Discord> <r​pardini> maybe I'm overcomplicating. say, looks like dd57ee4c1f3e4b974fedb5f452f2c618be87ae28 might be a good marker, "Radxa's stuff after this"

00:42 <Armbian-Discord> <c​0rnelius> https://github.com/rockchip-linux/kernel/tree/develop-5.10

00:43 <Armbian-Discord> <c​0rnelius> i think they work off a fork of this original branch, but I can't be 100% sure,

00:45 <Armbian-Discord> <c​0rnelius> much like everyone else and they just give it their own stupid name; https://github.com/friendlyarm/kernel-rockchip/commits/nanopi5-v5.10.y_opt

00:45 <Armbian-Discord> <r​pardini> exactly what I needed. thanks

00:46 <Armbian-Discord> <T​onymac32> Beat me to it

00:52 <Armbian-Discord> <r​pardini> so this is common ancestor between the trees, https://github.com/radxa/kernel/commit/cbf9da816c4a2d062c55272de83936e597df31d2

00:56 <Armbian-Discord> <r​pardini> but really Radxa only begins at https://github.com/radxa/kernel/commit/dd57ee4c1f3e4b974fedb5f452f2c618be87ae28

01:03 <Armbian-Discord> <r​pardini> so radxa tree has 228 patches of which only 108 (!) are Radxa proper, but that's still manageable.

01:03 <Armbian-Discord> <r​pardini> we've the Xunlong opi5 patches in, DT, a few drivers.

01:03 <Armbian-Discord> <r​pardini> I've a try with the Khadas edge2 tree, same stuff except a lot of mcu stuff taking over, of course.

01:07 <Armbian-Discord> <r​pardini> then again, hate wasting time on vendor shit.

01:07 <Armbian-Discord> <r​pardini> how goes with the mainline rk3588 tryouts @c0rnelius ?

01:08 <Armbian-Discord> <c​0rnelius> @rpardini encountered a bug and then squashed it and then encountered another. 🙂 slowly it goes. plus I'm not in a super rush here.

01:10 <Armbian-Discord> <r​pardini> any sign of ethernet working?

01:36 <Armbian-Discord> <c​0rnelius> @rpardini i don't have any 3588 units I was just looking at it on a code level, but there was a ethernet patch submitted and accepted last I saw for the 3588.

01:37 <Armbian-Discord> <r​pardini> we've the same problem, lack of units.

01:37 <Armbian-Discord> <c​0rnelius> yeah... hopefully be able to get one next year.

01:38 <Armbian-Discord> <c​0rnelius> i have no practical reason to own a 3568 but I would eventually like to get one of those.

01:44 <Armbian-Discord> <r​pardini> 66/68 are sweet mainline bliss. ethernet, pcie nvme, stable if cooled, I'm happy.

01:45 <Armbian-Discord> <r​pardini> I dont care about hdmi, gpu, etc.

01:50 <Armbian-Discord> <c​0rnelius> nice. I don't care about hdmi either.

01:50 <Armbian-Discord> <c​0rnelius> only when I'm using the board as a kodi player or something like this.

02:44 <Armbian-Discord> <T​enkawa> ethernet working on which?

03:02 <Armbian-Discord> <c​0rnelius> mainline and 3588 I believe

03:02 <Armbian-Discord> <T​enkawa> As far as I have heard it is still doing nothing but the serial console on mainline

03:03 <Armbian-Discord> <T​enkawa> still no more progress yet

03:20 <Armbian-Discord> <T​enkawa> I'd like to test something more and start working on mainline myself (If its realisticly being developed) too since I have two machines to use.

10:25 <Armbian-Discord> <a​mazingfate> @rpardini radxa's kernel for rock5b is based on this rk official branch: https://gitlab.com/rk3588_linux/rk/kernel/-/tree/linux-5.10-gen-rkr3.4

10:26 <Armbian-Discord> <a​mazingfate> They may update it to rkr3.5 in the future.

13:47 <Armbian-Discord> <T​enkawa> How far off do you think it has "diverted" since it was branched? would it even run on the Rock5 in its current form? The difficulty I have with the way this is being handled is there are "too" many divergant paths being taken with no real plan being communicated to the community om which codebase we should be following

13:50 <Armbian-Discord> <a​mazingfate> This is the original sdk released by rockchip, all the downstream rockchip boards create their own branch based on this official sdk.

13:51 <Armbian-Discord> <T​enkawa> Nod. I agree.. I'm illustrating the need for each vendor to be more clear about what they are using.

13:53 <Armbian-Discord> <a​mazingfate> The branch name of radxa is clear, just the same as the sdk tag. For other boards we have to ask their developer or compare the source code with rockchip's sdk.

13:54 <Armbian-Discord> <T​enkawa> No.. Radxa has already used 2 different git sources and switched midstream

13:54 <Armbian-Discord> <T​enkawa> stable-5.10-rock5 and rkr3.4

13:55 <Armbian-Discord> <a​mazingfate> I mean the new branch rkr3.4.

13:56 <Armbian-Discord> <T​enkawa> But that goes back to my original point... communications

13:56 <Armbian-Discord> <T​enkawa> or lack of

13:57 <Armbian-Discord> <T​enkawa> Having all of these out there without knowing which one is the "right" branch.. its a dice roll

13:58 <Armbian-Discord> <a​mazingfate> @RadxaYuntian is maintaining the source code of radxa. I got these info I know from him.

13:58 <Armbian-Discord> <T​enkawa> I as well.,,

14:00 <Armbian-Discord> <T​enkawa> I'm also very picky on documenting everything because of my past career....

14:05 <Armbian-Discord> <a​mazingfate> This should be a basic knowledge in rockchip legacy world. Rockchip releases new updated version of it's sdk and updates the code tag. If we pay attention to the updates from rockchip, every downstream update will be reasonable.

14:07 <Armbian-Discord> <T​enkawa> Ok.

14:07 <Armbian-Discord> <T​enkawa> Time to get ready to rebuild a RK3399 and 2 BCM2711's... this should be an "interesting" day.

14:27 <Armbian-Discord> <T​onymac32> I can't wait for this nonsense to be done with. Rockchip legacy needs thrown in a dumpster, lit on fire, and sunk into the ocean

14:27 <Armbian-Discord> <T​onymac32> What a joke that entire code base is

15:49 <Armbian-Discord> <a​mazingfate> lol

15:50 <Armbian-Discord> <a​mazingfate> Although it sucks, it is the only kernel that has full multimedia support.

15:59 <Armbian-Discord> <T​onymac32> https://cdn.discordapp.com/attachments/858684284070789130/1054790112535400558/image0.gif

16:00 <Armbian-Discord> <T​onymac32> @TheBug you took over that M4S activity, is it your board now?

16:00 <Armbian-Discord> <T​onymac32> Or R4S

16:00 <Armbian-Discord> <T​onymac32> Whatever alphabet soup it is

16:03 <Armbian-Discord> <T​heBug> Huh?

16:04 <Armbian-Discord> <T​heBug> knows not what you speak of?

16:04 <Armbian-Discord> <T​heBug> @Tonymac32

16:04 <Armbian-Discord> <T​onymac32> Jira

16:04 <Armbian-Discord> <T​onymac32> Patch refactoring ticket

16:05 <Armbian-Discord> <T​heBug> If my name is associated I didnt put it there??

16:06 <Armbian-Discord> <T​onymac32> Lol

16:06 <Armbian-Discord> <T​onymac32> https://cdn.discordapp.com/attachments/858684284070789130/1054791825329770526/Screenshot_20221220-110543.png

16:06 <Armbian-Discord> <T​onymac32> 🤷‍♂️

16:06 <Armbian-Discord> <T​heBug> Interesting that was likely 100% unintentional and happened during review of tickets, please unset/set back if appropriate

16:07 <Armbian-Discord> <T​onymac32> ROFL

16:07 <Armbian-Discord> <T​onymac32> Ok

16:07 <Armbian-Discord> <T​heBug> Sorry about that, if it was me it was a mistake :/

16:08 <Armbian-Discord> <T​onymac32> No worries I wanted to make sure

16:08 <Armbian-Discord> <T​onymac32> It needs refactored before next release, Roman took care of/is taking care of the laughable patch set we got handed for the Rock Pi S

16:08 <Armbian-Discord> <T​heBug> Thanks for doing that as i wouldnt have caught it for a while

16:09 <Armbian-Discord> <T​onymac32> The station RK3328 I think I'll just delete since it lives in Oleg's kernel

16:09 <Armbian-Discord> <T​onymac32> Helios64 should be looked over by the man of the sea

16:10 <Armbian-Discord> <T​onymac32> https://cdn.discordapp.com/attachments/858684284070789130/1054792840384888892/image0.gif

16:10 <Armbian-Discord> <T​heBug> Well isnt 64 the rk3399 and 4 the armada?

16:11 <Armbian-Discord> <T​onymac32> Yeah but I don't think we were miscommunicating. If we were I'll look it over

16:11 <Armbian-Discord> <T​onymac32> Need some beer money soon though if the pileup keeps going 🤣🤣🤣

16:13 <Armbian-Discord> <T​onymac32> https://cdn.discordapp.com/attachments/858684284070789130/1054793587499479090/image0.gif

16:16 <Armbian-Discord> <T​heBug> lol

16:16 <Armbian-Discord> <T​heBug> wait, I know your address I think....

16:16 <Armbian-Discord> <T​heBug> plots to have door dash delivery several cases of beer

16:16 <Armbian-Discord> <T​onymac32> 🤣🤣

17:03 <Armbian-Discord> <M​anoftheSea> I'm working on it.

17:04 <Armbian-Discord> <M​anoftheSea> Looking at u-boot presently, then going to figure out the difference between the old added dts and the now mainline 6.1 dts

17:21 <Armbian-Discord> <M​anoftheSea> okay, I don't know what I'm doing. trying to port the helios64 patch to u-boot master, and getting an error from binman.

17:22 <Armbian-Discord> <M​anoftheSea> binman: Node '/binman/simple-bin/blob': Offset 0x2e000 (188416) overlaps with previous entry '/binman/simple-bin/mkimage' ending at 0x2e800 (190464)

17:51 <Armbian-Discord> <T​onymac32> That shouldn't happen

17:51 <Armbian-Discord> <T​onymac32> Hmmm

17:52 <Armbian-Discord> <M​anoftheSea> I copied over a "PAD_SPL" config option from rockpro64's defconfig, and it got past that point.

18:25 <Armbian-Discord> <T​onymac32> Ahhh ok

21:53 <Armbian-Discord> <M​anoftheSea> what is going on with u-boot patches in armbian/build? There's 3 different versions of u-boot as well as a rockchip64, a rockchip64-2022.04...

21:53 <Armbian-Discord> <M​anoftheSea> And here I'm trying to patch against 2023.01-rc4

22:02 <Armbian-Discord> <M​anoftheSea> looks like I want u-boot-rockchip64, but I don't yet know what version of u-boot that builds against.

22:22 <Armbian-Discord> <M​anoftheSea> ```U-Boot TPL 2023.01-rc4-00001-g7c65d724c5 (Dec 20 2022 - 16:38:35)

22:22 <Armbian-Discord> <M​anoftheSea> lpddr4_set_rate: change freq to 400MHz 0, 1

22:22 <Armbian-Discord> <M​anoftheSea> Channel 0: LPDDR4, 400MHz

22:22 <Armbian-Discord> <M​anoftheSea> BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB

22:22 <Armbian-Discord> <M​anoftheSea> Channel 1: LPDDR4, 400MHz

22:23 <Armbian-Discord> <M​anoftheSea> BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB

22:23 <Armbian-Discord> <M​anoftheSea> 256B stride

22:23 <Armbian-Discord> <M​anoftheSea> lpddr4_set_rate: change freq to 800MHz 1, 0

22:23 <Armbian-Discord> <M​anoftheSea> Trying to boot from BOOTROM

22:23 <Armbian-Discord> <M​anoftheSea> Returning to boot ROM...

22:23 <Armbian-Discord> <M​anoftheSea>

22:23 <Armbian-Discord> <M​anoftheSea> U-Boot SPL 2023.01-rc4-00001-g7c65d724c5 (Dec 20 2022 - 16:38:35 -0500)

23:09 <Armbian-Discord> <T​onymac32> Yeahhhhhhhhhhhhhhh

23:10 <Armbian-Discord> <T​onymac32> https://cdn.discordapp.com/attachments/858684284070789130/1054898541526532136/image0.gif