Hi Stefan, > ARMv8/7 are likely to deal with a whole range of boards, configured in detail > by device tree blobs, so there is a range of SoCs and pheripherals (PMICs, > GPUs, ...) covered by these architectures.
Correct. > > ARMv6 is mostly/only? targeted at Raspberries. So no PMIC, VC4 GPU, BCM2835 > SoC. Is this assumption valid? Yes, thats fully correct. the non-arch specific options should be inherited from i386/x86_64 configs, all arch specific options should be disabled unless they're needed for this one SoC. > > Also, the ARMv7 default config has e.g. CONFIG_SERIAL_BCM63XX=y and > CONFIG_LEDS_BCM6328=m, but BCM63xx is MIPS. Configuration error? Unfortunately CONFIG_SERIAL_BCM63XX says: Depends on: TTY [=y] && HAS_IOMEM [=y] && (MIPS || ARM [=y] || COMPILE_TEST [=n]) which means there seem to be ARM variants of that Serial component. you're right about the LED part though, I'll disable it. > Pheripherals connected via I2C and SPI (TFTs, touchscreens, ambient light > sensors, magnetometers ...) should be configured as modules? Yes. > The RPI has no RTC onboard, but these can be easily added and configured with > device tree overlays or (as uboot lacks dtbo support) patched device trees. > Module or builtin? if module works, then module is preferred. sicne as you mentioned its optional per user. Greetings, Dirk -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
