I want to add a X86 SOC, and summit to github. I want to add a new folder target/linux . But there are more APP depend the define "CONFIG_TARGET_x86".
as the code in include/target.mk PLATFORM_DIR:=$(TOPDIR)/target/linux/$(BOARD)
X86 have a lot of SOC, now and future. I think the define "CONFIG_TARGET_x86" need to set as a independent define. we need to make it irrelevant to the folder “X86”.
Disclaimer: I'm not an OpenWrt developer and can't speak for the project in any way, shape or form.
You'll have to provide a very strong reason why a new target- or sub-target would be necessary for any x86/ x86_64 based board (or SOC), a reason why it can't be supported in the generic targets or would profit significantly (for mostly router-like uses, not some obscure benchmarks involving floating point, SSE or similar stuff that won't be used in the predominant use cases for OpenWrt). In general, the answer to these requests would be a firm 'no', x86/ x86_64 should be generic enough to boot from a shared boot medium using BIOS- or (unsigned-) UEFI mechanisms, everything beyond that can be solved by installing additional packages at runtime.
Thanks slh!
My consideration is that if AMD / Intel has more and more CPU and more and more customers, the patch under x86 will become chaotic. Nowadays, enterprise routers want to use more powerful CPUs, so that more and more customers will use x86 CPUs as routers.
There shouldn't be any patches at all necessary for x86/ x86_64[0], you might need a newer kernel or have to backport a handful of patches to the latest LTS kernel (v5.4 for the next OpenWrt stable release, but this is about to be branched off soon and development closed - so any major changes would have to target v5.10 anyways), but these should be small and short-lived (as being consumed into the next mainline kernel).
--
[0] yes, there are currently 5 patches present for x86/ x86_64, all of them very tiny/ specific - most of them should go mainline or probably have in the mean time.