For the port of Mageia on a Banana Pro, I saw that the default kernel configuration boot and the kernel from Mageia.Org doesn't seem to boot.

After a small comparison between our kernel configuration
http://svnweb.mageia.org/packages/updates/7/kernel/current/SOURCES/defconfig-arm-desktop?view=markup
and the default sunxi configuration which boots
https://github.com/torvalds/linux/blob/master/arch/arm/configs/sunxi_defconfig
I could see for main differences, what is defined in the sunxi_defconfig and not on Mageia's kernel :

```
  CONFIG_ROOT_NFS=y               If you want your system to mount its root file system via NFS, choose Y here.
  CONFIG_CPU_FREQ=y               CPU Frequency scaling allows you to change the clock speed of CPUs on the fly. This is a nice method to save power, because the lower the CPU clock speed, the less power the CPU consumes.
  CONFIG_CPUFREQ_DT=y             This adds a generic DT based cpufreq driver for frequency management. It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) systems.
  CONFIG_IP_PNP=y                 This enables automatic configuration of IP addresses of devices and of the routing table during kernel boot, based on either information supplied on the kernel command line or by BOOTP or RARP protocols. You need to say Y only for diskless machines requiring network access to boot (in which case you want to say Y to "Root file system on NFS" as well), because all other machines configure the network in their startup scripts.
  CONFIG_IP_PNP_DHCP=y            If you want your Linux box to mount its whole root file system (the one containing the directory /) from some other computer over the net via NFS and you want the IP address of your computer to be discovered automatically at boot time using the DHCP protocol (a special protocol designed for doing this job), say Y here. In case the boot ROM of your network card was designed for booting Linux and does DHCP itself, providing all necessary information on the kernel command line, you can say N here.
  CONFIG_IP_PNP_BOOTP=y           If you want your Linux box to mount its whole root file system (the one containing the directory /) from some other computer over the net via NFS and you want the IP address of your computer to be discovered automatically at boot time using the BOOTP protocol (a special protocol designed for doing this job), say Y here. In case the boot ROM of your network card was designed for booting Linux and does BOOTP itself, providing all necessary information on the kernel command line, you can say N here.
  CONFIG_CAN=y                    Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial communications protocol. Development of the CAN bus started in 1983 at Robert Bosch GmbH, and the protocol was officially released in 1986. The CAN bus was originally mainly for automotive, but is now widely used in marine (NMEA2000), industrial, and medical applications. More information on the CAN network protocol family PF_CAN is contained in <Documentation/networking/can.rst>.
M CONFIG_CAN_SUN4I=y              Say Y here if you want to use CAN controller found on Allwinner A10/A20 SoCs. To compile this driver as a module, choose M here: the module will be called sun4i_can.
  CONFIG_STMMAC_ETH=y             This is the driver for the Ethernet IPs built around a Synopsys IP Core.
  CONFIG_SERIAL_8250_DW=y         Selecting this option will enable handling of the extra features present in the Synopsys DesignWare APB UART.
  CONFIG_SERIAL_OF_PLATFORM=y     This option is used for all 8250 compatible serial ports that are probed through devicetree, including Open Firmware based PowerPC systems and embedded systems on architectures using the flattened device tree format.
M CONFIG_I2C_MV64XXX=y            If you say yes to this option, support will be included for the built-in I2C interface on the Marvell 64xxx line of host bridges. This driver is also used for Allwinner SoCs I2C controllers. This driver can also be built as a module. If so, the module will be called i2c-mv64xxx.
  CONFIG_CPU_THERMAL=y            This implements the generic cpu cooling mechanism through frequency reduction. An ACPI version of this already exists (drivers/acpi/processor_thermal.c). This will be useful for platforms using the generic thermal interface and not the ACPI interface.
M CONFIG_SUNXI_WATCHDOG=y         Say Y here to include support for the watchdog timer in Allwinner SoCs. To compile this driver as a module, choose M here: the module will be called sunxi_wdt.
  CONFIG_MFD_AC100=y              If you say Y here you get support for the X-Powers AC100 audio codec IC. This driver include only the core APIs. You have to select individual components like codecs or RTC under the corresponding menus.
  CONFIG_REGULATOR_GPIO=y         This driver provides support for regulators that can be controlled via gpios. It is capable of supporting current and voltage regulators and the platform has to provide a mapping of GPIO-states to target volts/amps.
  CONFIG_RC_CORE=y                Enable support for Remote Controllers on Linux. This is needed in order to support several video capture adapters, standalone IR receivers/transmitters, and RF receivers.
  CONFIG_RC_DEVICES=y             (none)
  CONFIG_DRM_DUMB_VGA_DAC=y       Support for non-programmable RGB to VGA DAC bridges, such as ADI ADV7123, TI THS8134 and THS8135 or passive resistor ladder DACs.
  CONFIG_USB_EHCI_HCD_PLATFORM=y  Adds an EHCI host driver for a generic platform device, which provides a memory space and an irq.
  CONFIG_USB_OHCI_HCD_PLATFORM=y  Adds an OHCI host driver for a generic platform device, which provides a memory space and an irq.
  CONFIG_USB_GADGET=y             USB is a master/slave protocol, organized with one master host (such as a PC) controlling up to 127 peripheral devices. The USB hardware is asymmetric, which makes it easier to set up: you can't connect a "to-the-host" connector to a peripheral.
  CONFIG_LEDS_GPIO=y              This option enables support for the LEDs connected to GPIO outputs. To be useful the particular board must have LEDs and they must be connected to the GPIO lines. The LEDs must be defined as platform devices and/or OpenFirmware platform devices. The code to use these bindings can be selected below.
M CONFIG_RTC_DRV_AC100=y          If you say yes here you get support for the real-time clock found in X-Powers AC100 family peripheral ICs. This driver can also be built as a module. If so, the module will be called rtc-ac100.

  CONFIG_MFD_AXP20X_I2C=y         If you say Y here you get support for the X-Powers AXP series power management ICs (PMICs) controlled with I2C. This driver include only the core APIs. You have to select individual components like regulators or the PEK (Power Enable Key) under the corresponding menus.
  CONFIG_MFD_AXP20X_RSB=y         If you say Y here you get support for the X-Powers AXP series power management ICs (PMICs) controlled with RSB. This driver include only the core APIs. You have to select individual components like regulators or the PEK (Power Enable Key) under the corresponding menus.
  CONFIG_AXP20X_POWER=y           This driver provides support for the power supply features of AXP20x PMIC.
M CONFIG_INPUT_AXP20X_PEK=y       Say Y here if you want to enable power key reporting via the AXP20X PMIC. To compile this driver as a module, choose M here. The module will be called axp20x-pek.
M CONFIG_CHARGER_AXP20X=y         Say Y here to enable support for X-Powers AXP20X and AXP22X PMICs' AC power supply. This driver can also be built as a module. If so, the module will be called axp20x_ac_power.
M CONFIG_BATTERY_AXP20X=y         Say Y here to enable support for X-Powers AXP20X PMICs' battery power supply. This driver can also be built as a module. If so, the module will be called axp20x_battery.
  CONFIG_REGULATOR_AXP20X=y       This driver provides support for the voltage regulators on the AXP20X PMIC.
M CONFIG_AXP20X_ADC=y             Say yes here to have support for X-Powers power management IC (PMIC) AXP20X and AXP22X ADC devices. To compile this driver as a module, choose M here: the module will be called axp20x_adc.
```
So I tried and turns CONFIG_SERIAL_OF_PLATFORM to n instead of y, the default sunxi kernel boots, and turns CONFIG_SERIAL_8250_DW to n instead of y, then, the boot seems to freeze at "starting kernel" (uboot). I tried also setting it to m to be integrated as a module, but same bad result.

Is it possible to integrate CONFIG_SERIAL_8250_DW into Mageia's arm kernel ?
And, in general, I thing it could be a good point if integrate also into the kernel CONFIG_SERIAL_OF_PLATFORM .

Jybz