linux
linux copied to clipboard
esmil
config: Enable jh7100 SoC
I rebased the patch on top of starlight branch after contents have changed from 5.12.y to 5.13.y. This patch is to be meant for upstream by adding minimum changes to riscv/defconfig which only with enabling jh71x0 soc.
I will rebase it every time when the contents of the starlight branch rebases to new the kernel version. The original PR was https://github.com/esmil/linux/pull/2
Main reason I started to make the minimum changes on defconfig was for adding jh7100 enablement for the upstream defconfig. I remember the upstream maintainer hated to have different defconfig file for each different board when new products show up in the market and end up having huge number of files under arch/arm/configs, so having arch/riscv/configs/defconfig only touching hw enablement.
Hi @mcd500 -san, Can you use starlight_defconfig? As mentioned in the readme? https://github.com/esmil/linux/blob/starlight/README.md
Hi @mcd500 -san, Can you use
starlight_defconfig? As mentioned in the readme? https://github.com/esmil/linux/blob/starlight/README.md
Nevermind, I see you said the upstream maintainer just wants one defconfig. I don't agree with that so much, but ok.
@stffrdhrn This is the discussion in the past.
Akira Tsukamoto: 10 days ago
@Esmil I tried both your starlight_defconfig and my additions on the original defconfig on the fedora rootfs and perfectly working fine. No Ethernet link down, hartbeat LED is blinking, reboot is working fine. Only difference is loading extra firmwares from your starlight_defconfig is not in my defconfig. The size of kernels from starlight_defconfig is about 1MiB smaller than revised defconfig so starlight_defconfig is definitely the first choice for the BeagleV developer’s.
Esmil: 10 days ago
That's good to hear. Thank you for testing it!
@stffrdhrn The upstream kernel under arch/arm64/configs end up having only one file, defconfig. So what can we do...