Thank you for the link. I just thought the kernels from kernel.org also contains #ifdef ARM ... #endif sections to specify hardware differences, because we can set ARCH variable and use toolchain so the kernel will be built for ARM architecture.The Traveler wrote: ↑Thu Nov 02, 2017 12:49 amKernels are compiled for different architectures and different capabilities. A kernel contains code that tells it how to interact with hardware, address memory, handle I/O and a number of other things. Config files are specific to the kernel they produce so you really don't want to try and use a config from one kernel to another.
Here's a starting point: https://www.linuxhint.com/linux-kernel- ... beginners/
No, please following these instructions.
Hmm, someone tried to get the bcm2835-sdhost driver into the mainline kernel but the main issue is that the existing driver is quite out of date. They dropped the thread a year ago as far as I can tell, but the maintainer was helping them with code reviews, so it's not like it couldn't be done.swahren wrote: ↑Sat Nov 11, 2017 2:19 pm
It's possible to use a Raspberry Pi with the generic Linux kernel, but there are currently some missing features (Bluetooth, devicetree overlay) and boards (both Compute Modules, Sense hat). Also the Raspberry Pi kernel uses optimized drivers which will never be accepted for the upstream Kernel like the dwc_otg or the BCM2835 MMC driver.
There are multiple MMC drivers, which could be very confusing. Which driver is quite out of date (sdhci-bcm2835 or bcm2835 aka sdhost)?
There is no need for another MMC driver since both interfaces are supported now. The only disadvantage is the missing DMA support in sdhci-iproc.
Users browsing this forum: Baidu [Spider] and 3 guests