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>
[Discord] <microlinux> I can confirm that. I am surprised about the fixes and overall work made by armbian and @amazingfate on opi3b. Someone even pushed the dtb patch for UHS sd speeds
<DC-IRC>
[Discord] <microlinux> I've told them to copy paste the amrbian/contributors work on their own iamges... just a few lines of code. They didn't care.
<DC-IRC>
[Discord] <microlinux> I could claim from an user experience that opi 3b is a decent.. well, great hw. Their sw department does nothing at all.
<DC-IRC>
[Discord] <microlinux> Without armbian and amazingfate.. it would be a nice piece of paperweight
<DC-IRC>
[Discord] <Werner> Like most of their products lol
<DC-IRC>
[Discord] <microlinux> Many thanks everyone there. Hopefully you would extend my salutations to everyone there at armbian. Also, the x86_64 uefi releases are awesome piece of software. The best way to ubuntu/debian on x86_64
<DC-IRC>
[Discord] <alexl83> Guys, if I may interject, this is the greates, firendlies, most effective and nice to people sw/hw community I've ever experienced
<DC-IRC>
[Discord] <alexl83> and I work in IT for a multinational, within a lot of hw/sw communities
<DC-IRC>
[Discord] <Werner> It is often hard to keep it that way since frustration level is high but overall the only thing left we can do/be to attract more people into the world of (cheap) SBCs combined into one single project.
<DC-IRC>
[Discord] <alexl83> @werner may I ask you for and advice related to my KASLR PRs that got merged lately, please?
<DC-IRC>
[Discord] <Werner> Not sure if I am the correct person to answer but since I don't know the question yet go ahead 😄
<DC-IRC>
[Discord] <alexl83> the patchset allowing KASLR support to be enabled in u-boot are compatible starting u-boot 2024-07, so I bumped nanopi-r5c to that version and detached board uboot patchdir (and I left out general patches for 2024.07 - which are included in my latest PR ~5 mins ago)
<DC-IRC>
[Discord] <alexl83> I was thinking that kaslr-enabling patchset could be moved to general v2024.07 dir in order to:
<DC-IRC>
[Discord] <alexl83> - benefit all boards that use that u-boot version
<DC-IRC>
[Discord] <alexl83> - avoid the chore of replicating general patches to detached nanopi-r5c patchdir everytime a new one gets released
<DC-IRC>
[Discord] <alexl83> Does it make sense? Does it bear any risk? I think no - but I'd prefer an experienced opinion
<DC-IRC>
[Discord] <alexl83> perhaps we can jump to lounge and talk about it - my writing might be unclear
<DC-IRC>
[Discord] <Werner> Sense? Yes, I think so. Risk? Maybe, however if they build I assume they boot as well in most cases. Might wise to defer that after release to reduce risk of breakage. I'd open a PR with these changes, label and label with 11. Also gives enough time to test and collect feedback.
<DC-IRC>
[Discord] <Werner> Sense? Yes, I think so. Risk? Maybe, however if they build I assume they boot as well in most cases. Might wise to defer that after release to reduce risk of breakage. I'd open a PR with these changes, and label with 11. Also gives enough time to test and collect feedback.
<DC-IRC>
[Discord] <Werner> Once uboot mainline is bumped to 2024.10 these patches are dropped again anyways.
<DC-IRC>
[Discord] <Werner> Once uboot mainline gets bumped to 2024.10 these patches are dropped again anyways.
<DC-IRC>
[Discord] <alexl83> great approach - I'll have a draft/wip request tagged 11 and move kaslr to "general public" se feedback can be collected
<DC-IRC>
[Discord] <alexl83> that's also something I didn't think about - my limited feeling is that boards bumping u-boot is a slower process than kernel bumps though
<DC-IRC>
[Discord] <alexl83> because my detached approach is valid for nanopi-r5c and opi5-plus
<DC-IRC>
[Discord] <Werner> It is. While I don't know the technical reasons behind this (I am not a developer) my guess is that for once bumping uboot always comes with the risk of random breakage and for the other most people don't care about uboot version nor does it com with a major risk having one that is a bit outdated, besides making maintenance more difficult.
<DC-IRC>
[Discord] <alexl83> makes sense, I'll keep both boards uboot patchdirs detached and make sure to include general patches in each case - then wip PR for generalizing kaslr to main patchdir and collect feedback for 11 milestone
<DC-IRC>
[Discord] <alexl83> if 2024.10 gets released I'll bump directly to that and patches won't be needed anymore
<DC-IRC>
[Discord] <alexl83> thanks Werner! I'm a very sloppy non-developer
<DC-IRC>
[Discord] <Werner> Not sure about level of sloppiness but certainly more developer than myself 😄
<DC-IRC>
[Discord] <Werner> Also I don't do that stuff for a living
<DC-IRC>
[Discord] <alexl83> same for me, I just manage IT overall - development is done by people who are the real deal 😅
<DC-IRC>
[Discord] <alexl83> If anything I just have a bit of knowledge in infrastructure
<DC-IRC>
[Discord] <Werner> We need infra people as well 😉
<DC-IRC>
[Discord] <alexl83> fortunately in my career I made many jumps, so apart of my overarching accountability, I now focus a bit more on application layer and processes for my stakeholders
<DC-IRC>
[Discord] <alexl83> but still infra, analysys, workplace, vendors,etc needs to be managed
<DC-IRC>
[Discord] <alexl83> and headcount discussions are always short and funny 😄
<DC-IRC>
[Discord] <johnthecoolingfan> Well, I finally got a ft232 usb to uart adapter to try and debug a BigTreeTech Pi 2. But it doesn't seem to work, found in datasheet what uart0 pins are and connected them (tx one side to rx of the other), selected 3.3v, correct speed (1.5M baud), connected ground but not vcc (boardf is powered by type-c externally) yet I don't get any output from the board...
<DC-IRC>
[Discord] <johnthecoolingfan> Turns out I didn't have to trace down gpio pins from datasheet, the tx/rx pins are the same as on the BTT Pi
<DC-IRC>
[Discord] <johnthecoolingfan> And that finally works both sides
<DC-IRC>
[Discord] <johnthecoolingfan> FINALLY
<DC-IRC>
[Discord] <johnthecoolingfan> So it uses uart2 by default, huh
<DC-IRC>
[Discord] <johnthecoolingfan> According to teh rk3566, `GPIO0_D0` and `GPIO0_D1` are used for uart2