Re: [Ksummit-discuss] [CORE TOPIC] Mainline kernel on a cellphone

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]

On Wed, Aug 26, 2015 at 10:22:11AM +0900, Krzysztof Kozlowski wrote:

> Thanks for updated numbers. Interesting that for the same SoC vendor
> (MSM) the difference between phone vendors is significant, e.g. 3.1M of
> Samsung/MSM insertions, 2.6M of LG insertions and only 1.8M of Sony and
> Motorola.

> In the same time number of mainline contributors from LG, Sony and
> Motorola is similar... so why LG and Samsung/MSM need more than 1M of
> additional code out of tree?

One thing that happens here is that there's a wide variation in how much
the hardware gets customized from the reference designs provided by the
SoC vendors which has knock on effect on the amount of additional work
that is needed in order to support a given board.  I know the Korean
manufacturers do tend to make quite a few modifications to their designs
so I'd not be surprised if that were contributing to the number of code
changes required.

> Mali GPU drivers are an interesting case:
> 1. They are open (I believe Linux version is entirely under GPLv2).

Well, there's the in kernel stubs and the actual driver...

> 2. They are developed for many OS-es.

> 3. They are present on may end-user products (using SoCs from Allwinner,
> Mediatek, Rockchip, Samsung and more).

> 4. Their coding style is so different that I can't imagine mainlining
> them into staging area... Recently I was digging into Mali400 and it was
> literally hurting my eyes to see that coding style. It's like opposite
> of kernel.

The other thing here is that they don't (AIUI) offer a stable ABI, the
ABI can change between IP revisions.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]