On 23 February 2016 at 12:45, Tomi Valkeinen <tomi.valkeinen@xxxxxx> wrote: > So, true, there's probing going on, but it's all board specific, > requiring a board specific driver to support it in the kernel. And I > think that makes the bootloader much better place for supporting it. This doesn't seem to me like a reason to put the requirement in the bootloader. A huge part of the purpose of the kernel is to support the hardware (whether that's completely generic and probeable, like PCI, or generic but not probeable, or completely specific to a particular board). The kernel has to support the hardware, and just because it happens to be board specific hardware rather than generic hardware doesn't seem to me to imply that the kernel gets to drop part of its core purpose. > I think one of the core questions here is: do we want to start adding > board specific drivers to the kernel, instead of dealing with it in the > bootloader when possible? My understanding is that we've been trying to > reduce board specific code from the kernel. I think there's a difference between "reduce board specific code in the kernel by replacing it with the combination of generic or parameterisable code in the kernel plus a kernel data structure (DT) that supplies the parameterisation needed", and "reduce board specific code in the kernel by forcing the bootloader to do the kernel's job for it". thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
