From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: renesas-drivers-2015-12-01-v4.4-rc3
Date: Wed, 02 Dec 2015 00:32:35 +0000 [thread overview]
Message-ID: <20151202003235.GL27457@verge.net.au> (raw)
In-Reply-To: <1448970627-8690-1-git-send-email-geert+renesas@glider.be>
Hi Dirk,
On Tue, Dec 01, 2015 at 05:05:24PM +0100, Dirk Behme wrote:
> Hi Geert und Simon,
>
> On 01.12.2015 12:50, Geert Uytterhoeven wrote:
> >I've pushed renesas-drivers-2015-12-01-v4.4-rc3 to
> >https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
> >This tree is meant to ease development of platform support and drivers for
> >Renesas ARM ("shmobile") SoCs. It's created by merging (a) the for-next
> >branches of various subsystem trees and (b) branches with driver code
> >submitted or planned for submission to maintainers into the development
> >branch of Simon Horman's renesas.git tree.
>
>
> Many thanks for distilling this!
>
> Using this on the SalvatorX, we get the latest kernel with the latest
> drivers.
>
> On the other hand, there is
>
> https://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git/log/?h=v4.2/rcar-3.0.x
>
> which is on an older kernel using older driver versions. But, it seems to me
> that compared to renesas-drivers-2015-12-01-v4.4-rc3 it has some additional
> drivers / functionality.
>
> I wonder if we want to try to combine both to get something like the "latest
> and greatest" for the SalvatorX? I.e. take
> renesas-drivers-2015-12-01-v4.4-rc3 and extend it by the additional
> functionality from v4.2/rcar-3.0.x.
>
> To illustrate what I'm talking about I cherry picked some low hanging fruits
> from v4.2/rcar-3.0.x and put them on renesas-drivers-2015-12-01-v4.4-rc3:
>
> https://github.com/dirkbehme/linux-renesas-rcar-gen3/commits/dirk/gen3-latest-update
>
> The idea is to extend this step by step by additional parts of
> v4.2/rcar-3.0.x.
>
> What do you think?
>
> Maybe the first step would be to identify the parts from v4.2/rcar-3.0.x not
> yet in renesas-drivers-2015-12-01-v4.4-rc3. Having a quick look based on the
> defconfigs results in
>
> * more/extended USB functionality?
> * SATA?
> * I2C / ADV7482?
> * media / camera?
> * DRM / framebuffer / HDMI?
> * eMMC ?
> * ...?
We area in the (slow) process of doing more or less what you describe above.
Isolating portions of the BSP that look good for mainline and submitting
them for inclusion there. To be clear our goal is to make mainline as
feature-rich as possible but its a long road.
next prev parent reply other threads:[~2015-12-02 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 11:50 renesas-drivers-2015-12-01-v4.4-rc3 Geert Uytterhoeven
2015-12-01 16:05 ` renesas-drivers-2015-12-01-v4.4-rc3 Dirk Behme
2015-12-02 0:32 ` Simon Horman [this message]
2015-12-02 6:38 ` renesas-drivers-2015-12-01-v4.4-rc3 Dirk Behme
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=20151202003235.GL27457@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.