ak_hepcat
-
Posts
5 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by ak_hepcat
-
-
1 hour ago, TRS-80 said:
[...]
In my time here, I have gathered that the ARM Linux ecosystem is kind of wild and wooly, with random patches and fixes coming from here and there... Armbian in fact is an effort to try and unify all these things floating around on the Internet into some sort of cohesive whole. Which I guess is why we maintain our own patch sets.
Your efforts toward contribution are appreciated.
welp, I guess that's where i'll head then. Ugly as sin, but... it is what it is.
Heading off to PR... ( https://github.com/armbian/build/pull/3495 )
thanks!
-
Okay, so... again...
Should i perform a PR against the patchfile itself?
Or is there a master repo somewhere else that's it's generated from that would be more appropriate?
specifically for: armbian/patch/kernel/media-edge/general-rockchip-overlays.patch
None of this patch process seems to be documented anywhere, so, I'm struggling with how to get changes made in the correct manner. -
yes, the patches are there in multiple directories from historical use.
But the question that's really being asked is " are those patchfiles the correct place to PR against, or is there someplace upstream where they're managed"
because... patching a diff file seems really incorrect.
-
I was trying to enable i2c on my RockPro64, and when looking at the documentation in the overlay directory, it states this:
rockchip (Rockchip) ### Provided overlays: - i2c7, i2c8, pcie-gen2, spi-spidev, uart4, w1-gpio ### Overlay details: ### i2c7 Activates TWI/I2C bus 7 I2C7 pins (SCL, SDA): GPIO2-B0, GPIO2-A7 GPIO1-C5, GPIO1-C4 ### i2c8 Activates TWI/I2C bus 8 I2C8 pins (SCL, SDA): GPIO1-C5, GPIO1-C4Note that the "GPIO1-C5, GPIO1-C4" from i2c8 is accidentally included on the i2c7 pins line.
I would submit a PR for this change, but ... I'm not sure where this document actually lives, and it's not easy to figure out.
I see that @Igor is listed as the maintainer of the package, but that's not helping me find the source to submit changes.
Also, for clarity, it would be nice to include that i2c8 is the pi-connector, and i2c7 is the Digital Video Port
Happy to submit changes if somebody can point me to the right place.
Thanks
Migration to rk35xx LINUXFAMILY
in Orange Pi 5 / 5B
Posted
Just downloaded Armbian_23.5.5_Orangepi5-plus_jammy_legacy_5.10.160.img.xz and installed it to an sdcard to boot up on my Opi5+ and monitored with serial console, but the system wouldn't boot because of a koops. this happened with every boot.
Using the Orangepi5plus_1.0.6_ubuntu_jammy_server_linux5.10.110.img version, I'm able to boot successfully.
I copied the boot files from the OPi5+ img onto my sdcard with Armbian, and made the requisite changes so that the boot environment was pointing to Opi kernel/initrd/dtb, and as expected, was able to boot into the official armbian environment, so i could validate what kernel was installed on the image i downloaded, and it was "linux-image-legacy-rk35xx":
So there's something broken on that build for Opi5+ - at least it's failing on my board.
Happy to provide more info, run test builds, etc.