Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Announcements: #armbian-announcements | Developer talk: #armbian-devel | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
TheCoffeMaker has quit [Ping timeout: 268 seconds]
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian
TheCoffeMaker has joined #armbian
buzzmarshall has quit [Quit: Konversation terminated!]
chewitt has joined #armbian
gabes22 has quit [Quit: The Lounge - https://thelounge.chat]
gabes22 has joined #armbian
coldfeet has joined #armbian
laz0r has quit [Read error: Connection reset by peer]
laz0r has joined #armbian
<DC-IRC> [Discord] <awugong_28971> Apologies for disturbing everyone. I would like to inquire about how to carry out U-boot and kernel adaptation work on Armbian. I’ve noticed that most board modifications only alter the config in the config/boards directory and modify the kernel’s DTS and config files. I believe this is insufficient. Many of the drivers for my board are not built into the mainline Linux, such <clipped message>
<DC-IRC> [Discord] <awugong_28971> as my touch driver. I want to debug the kernel driver, but I can’t find a way to compile the kernel separately in Armbian, make modifications to it, and then verify my driver. I’ve also noticed that Orange Pi has patch operations for U-boot. How are these patches created? Are they generated by pulling the mainline U-boot and Linux, compiling and testing, and then putting the <clipped message>
<DC-IRC> [Discord] <awugong_28971> patches into Armbian?
<DC-IRC> [Discord] <Werner> orangepi build repo is actually a fork of an old version of Armbian. So you may notice similarities. However our framework got a major rewrite in the meantime.
<DC-IRC> [Discord] <Werner> Board which share similarities, like the same SoC, don't need a full fledged board configuration since this would create lots of duplicate code and is handled in family configs in `config/sources/families`. And even higher up the ladder there is _common_ which further combines code which is shared across families.
<DC-IRC> [Discord] <Werner> If your hw is built around a soc which is already introduced in the framework you will find the code you are looking for somewhere within.
<DC-IRC> [Discord] <Werner> Patches are created via `kernel-patch` or `uboot-patch`.
wootehfoot has joined #armbian
<DC-IRC> [Discord] <awugong_28971> Thank you very much for your help. I will give it a try as per your instructions.
<DC-IRC> [Discord] <Werner> Let us know if you have further or more specific questions
zeemate has joined #armbian
zeemate has quit [Remote host closed the connection]
zeemate has joined #armbian
zeemate has quit [Remote host closed the connection]
zeemate has joined #armbian
coldfeet has quit [Quit: Lost terminal]
Toasty has joined #armbian
archetech has joined #armbian
wootehfoot has quit [Ping timeout: 252 seconds]
Toasty has quit [Read error: Connection reset by peer]
Toasty has joined #armbian
jason123onirc has quit [Remote host closed the connection]
jason123onirc has joined #armbian
<DC-IRC> [Discord] <Github> ✅ **Merged** into [armbian/build](<https://github.com/armbian/build>) by [pyavitz](<https://github.com/pyavitz>) - [Link](<https://github.com/armbian/build/commit/cdf8eb8a579ea057705d36432a48a881ba4a8f1b>): *BananaPi SM1: `Fixup patch name association`*
coldfeet has joined #armbian
wootehfoot has joined #armbian
coldfeet has quit [Quit: Lost terminal]
wootehfoot has quit [Read error: Connection reset by peer]
chewitt has quit [Quit: Zzz..]
archetech has quit [Quit: Konversation terminated!]
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #armbian
CrashTestDummy has joined #armbian
CrashTestDummy has quit [Quit: Leaving]
buzzmarshall has joined #armbian