ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Tim Bird <tim.bird@sonymobile.com>, Pavel Machek <pavel@ucw.cz>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
	"John Stultz" <john.stultz@linaro.org>,
	"Andersson, Björn" <Bjorn.Andersson@sonymobile.com>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Mainline kernel on a cellphone
Date: Wed, 26 Aug 2015 10:22:11 +0900	[thread overview]
Message-ID: <55DD14C3.8090707@samsung.com> (raw)
In-Reply-To: <55DCBB21.8070009@sonymobile.com>

On 26.08.2015 03:59, Tim Bird wrote:
> On 07/29/2015 12:40 AM, Pavel Machek wrote:
>> Hi!
>>
>>>> There is now a wiki page at:
>>>> See http://elinux.org/Kernel_areas_of_focus_for_mainlining
>>>> In particular it has a table showing certain areas that tend to have
>>>> a lot of out-of-tree code (e.g. most phones have between 80K to
>>>> 100K of lines of wireless driver support out-of-mainline)
>>>
>>> Did anyone see successful attempts of mainlining such vendor code? I
>>> mean mainlining by individuals, not by vendor company itself.
>>
>> That is what is happening on Nokia N900. It took some time, but we
>> have almost usable phone at this point. We'll have usable one once
>> power management is working and once we get some more reasonable code
>> to control ofono.
> 
> Just an update on this thread.  We held a BOF at LinuxCon last week
> on this topic.  I gave a presentation with some background, and
> then we had a discussion.  Notes from the meeting (and a link to the
> presentation) are at: 
> http://elinux.org/LCNA_2015_Device_Mainlining_BOF_meeting_notes

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?


I made also a diff with Tizen (developer) kernel source code. These are
kernel trees not used directly by end-market products, but for devices
released to developers. Sometimes these are the same as market-products,
but the kernel is developed in a more open-source way:

1. 4.0 kernel (for Odroid XU3):
   https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git
   1404 files changed,
   4566 insertions(+),
   162026 deletions(-),
   1761 hunks

2. 3.10 kernel (for Gear2, Trats2/Galaxy S3, Odroid U3):
   https://review.tizen.org/git/?p=platform/kernel/linux-3.10.git
   5804 files changed,
   84175 insertions(+),
   536798 deletions(-),
   17917 hunks

I think the numbers are reversed (insertions <-> deletions) because
adding only Mali 400 should give ~50 000 of insertions.


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

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.


Best regards,
Krzysztof

  reply	other threads:[~2015-08-26  1:22 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 10:57 Pavel Machek
2015-07-23 11:21 ` Linus Walleij
2015-07-23 12:14   ` Pavel Machek
2015-07-23 12:42     ` Steven Rostedt
2015-07-23 15:40       ` Mark Brown
2015-07-28 22:09         ` Tim Bird
2015-07-28 23:07           ` Bjorn Andersson
2015-07-31 16:18             ` Rob Herring
2015-07-31 16:56               ` Bjorn Andersson
2015-08-11  9:34                 ` Johannes Berg
2015-07-31 17:25               ` Tim Bird
2015-08-03 15:29                 ` John W. Linville
2015-08-03  7:42               ` Linus Walleij
2015-08-03 21:34                 ` Rob Herring
2015-08-03 22:36                   ` Marcel Holtmann
2015-08-05  8:40                     ` Linus Walleij
2015-08-05  8:46                       ` Linus Walleij
2015-08-05  9:11                         ` Samuel Ortiz
2015-08-05 11:54                         ` Pavel Machek
2015-08-05  9:09                       ` Samuel Ortiz
2015-08-05 17:19                       ` Marcel Holtmann
2015-08-05 16:02                     ` Rob Herring
2015-08-05 17:00                       ` Marcel Holtmann
2015-08-07 12:40                         ` Linus Walleij
2015-07-29  0:45           ` Krzysztof Kozlowski
2015-07-29  6:12             ` Laurent Pinchart
2015-07-29  7:40             ` Pavel Machek
2015-08-25 18:59               ` Tim Bird
2015-08-26  1:22                 ` Krzysztof Kozlowski [this message]
2015-08-26  4:25                   ` Sudip Mukherjee
2015-08-26  4:52                     ` Krzysztof Kozlowski
2015-08-26  5:30                       ` Laurent Pinchart
2015-08-26  5:33                         ` Krzysztof Kozlowski
2015-08-26  6:15                           ` Josh Triplett
2015-08-26  7:23                             ` Heiko Stuebner
2015-08-26  8:05                               ` Krzysztof Kozlowski
2015-08-28  8:20                                 ` Nicolas Ferre
2015-08-26 11:33                   ` Mark Brown
2015-08-26 12:56                   ` Jason Cooper
2015-08-26 13:35                     ` Geert Uytterhoeven
2015-08-26 13:58                     ` Sudip Mukherjee
2015-08-26 14:51                       ` Jason Cooper
2015-08-26 17:13                         ` Sudip Mukherjee
2015-08-26 20:09                           ` Greg Kroah-Hartman
2015-08-28  7:44                             ` Pavel Machek
2015-08-28  8:42                               ` Heiko Stuebner
2015-08-29 15:47                                 ` Sudip Mukherjee
2015-07-29  8:18             ` Heiko Stübner
2015-07-29  0:56           ` Rafael J. Wysocki
2015-07-29  6:43           ` Daniel Vetter
2015-07-29 17:42             ` Tim Bird
2015-07-29  7:14           ` Bintian
2015-07-29 18:07             ` Tim Bird
2015-07-31  1:50               ` Bintian
2015-07-23 20:29       ` Pavel Machek
2015-07-23 20:34         ` Pavel Machek
2015-07-24  4:34           ` NeilBrown
2015-07-24  6:00             ` Tony Lindgren
2015-07-24 22:26               ` Rafael J. Wysocki
2015-07-28 22:03                 ` NeilBrown
2015-07-29  0:51                   ` Rafael J. Wysocki
2015-07-29 23:23                     ` Rafael J. Wysocki
2015-07-29 23:59                       ` NeilBrown
2015-07-30  0:57                         ` Rafael J. Wysocki
2015-07-31 17:55                           ` Mark Brown
2015-08-01  0:08                             ` Rafael J. Wysocki
2015-07-23 21:00         ` josh
2015-07-23 21:29           ` Pavel Machek
2015-07-29 13:32         ` Mark Brown
2015-07-31 12:22           ` Pavel Machek
2015-07-31 17:52             ` Mark Brown
2015-07-31 22:03               ` Pavel Machek
2015-08-01 10:55                 ` Mark Brown
2015-08-01 19:03                   ` Pavel Machek
2015-08-04 17:17                     ` Mark Brown
2015-08-03  5:33                 ` Tony Lindgren
2015-07-23 13:23     ` Krzysztof Kozlowski
2015-07-23 21:56       ` Pavel Machek
2015-07-24  1:37         ` Krzysztof Kozlowski
2015-07-24  4:40       ` Kyungmin Park
2015-07-23 14:48 ` Shuah Khan
2015-07-23 15:08 ` Heiko Stübner
2015-08-04 19:39 ` Pavel Machek
2015-08-05  7:05   ` Bintian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55DD14C3.8090707@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=Bjorn.Andersson@sonymobile.com \
    --cc=john.stultz@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=pavel@ucw.cz \
    --cc=tim.bird@sonymobile.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox