From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: "Pavel Machek" <pavel@ucw.cz>,
"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 08:30:16 +0300 [thread overview]
Message-ID: <75821461.TO3mbjAQav@avalon> (raw)
In-Reply-To: <55DD4607.2030308@samsung.com>
On Wednesday 26 August 2015 13:52:23 Krzysztof Kozlowski wrote:
> On 26.08.2015 13:25, Sudip Mukherjee wrote:
> > On Wed, Aug 26, 2015 at 10:22:11AM +0900, Krzysztof Kozlowski wrote:
> >> On 26.08.2015 03:59, Tim Bird wrote:
> >>> On 07/29/2015 12:40 AM, Pavel Machek wrote:
> > <snip>
> >
> >> 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.
> >
> > Hi,
> > I have seen Mali code once few months ago and true that the styling
> > there is exactly opposite of what we use. But anyway, I hope including
> > that in staging will be beneficial for all of you.
>
> Looking at the list of SoCs using Mali:
> https://en.wikipedia.org/wiki/Mali_(GPU)
> then clearly a lot of vendors could benefit from that. I would be happy
> to see Mali in staging/mainline.
>
> > And I can also guess
> > that it will be a waste of your time if you add it to staging and
> > refactor the code ultimately merging it to the main part of the kerel.
> >
> > I am not an experienced Mali developer but if you all are ok with it then
> > I can take up the task of adding it to staging. But I will need to have
> > a board for that as without hardware Greg will not allow the code to be
> > added. And Krzysztof has suggested ODROID-U3 for this purpose.
>
> Right, I suggested Odroid-U3 (with Mali 400 and Exynos4412) because the
> board works quite well with mainline. Most of stuff is upstreamed.
> However I am using Tizen TV profile (public) on it with 4.0 kernel (not
> entirely public).
>
> There are a lot of more devices with Mali 400 or newer so the question
> would be rather - which board would work the best (with less problems)
> on mainline.
>
> Anyway good luck :)
Given that DRM drivers can't be merged to mainline without an open-source
userspace we're stuck until ARM decides to play fair (unlikely) or the Lima
driver project rises back from the deaths.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-08-26 5:30 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
2015-08-26 4:25 ` Sudip Mukherjee
2015-08-26 4:52 ` Krzysztof Kozlowski
2015-08-26 5:30 ` Laurent Pinchart [this message]
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=75821461.TO3mbjAQav@avalon \
--to=laurent.pinchart@ideasonboard.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 \
/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