On Sunday 04 October 2015 12:45:41 Andreas Färber wrote:
Am 04.10.2015 um 04:12 schrieb Stefan Bruens:
since OBS revision 407 of Kernel:stable  no
kernel is built for armv6hl
(it is no longer in ExclusiveArch:). Whats the reasoning behind this?
ARM kernels don't get updated by magic. Some volunteer needs to submit
patches, making decisions on which drivers are relevant or not.
Otherwise the build would just fail and therefore gets disabled.
Matwey has been a great help in keeping the armv7hl configs updated, but
when I recently applied his patch for master (v4.3-rc1) and then also
updated armv6hl, I noticed that no one had done the work for 4.2 while
it was in Kernel:HEAD, and now you notice that in Kernel:stable:
That's the overall problem we have with armv6hl: Many people complain,
but too few people help updating, investigating and fixing things...
So, welcome to the openSUSE community - here's what you can do:
Thanks for the welcome, but I am already here since 1999 ;-)
Thanks for the walkthrough, that was very useful. Your "tutorial" is somewhat
similar to https://en.opensuse.org/openSUSE:Kernel_git
, although it targets
source changes/patches. Maybe you could add an section about config changes?
The policy is to enable all drivers for generic things
like USB devices
or sensors as module (m) and to disable (n) any drivers for ARMv7 or
ARMv8 SoCs. Serial and RTC drivers are the only things to build in (y)
when you are offered a choice, but they'd be unlikely for Raspberry Pi.
Yes, will do. Some clarifications would be useful:
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.
ARMv6 is mostly/only? targeted at Raspberries. So no PMIC, VC4 GPU, BCM2835
SoC. Is this assumption valid?
Also, the ARMv7 default config has e.g. CONFIG_SERIAL_BCM63XX=y and
CONFIG_LEDS_BCM6328=m, but BCM63xx is MIPS. Configuration error?
Pheripherals connected via I2C and SPI (TFTs, touchscreens, ambient light
sensors, magnetometers ...) should be configured as modules?
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?
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
work: +49 2405 49936-424
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org