linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/2] Add a display driver to the Allwinner H3
Date: Wed, 6 Jan 2016 22:20:46 +0100	[thread overview]
Message-ID: <20160106212046.GD9631@lukather> (raw)
In-Reply-To: <cover.1452021349.git.moinejf@free.fr>

Hi,

Thanks a lot for your work!

On Tue, Jan 05, 2016 at 08:15:49PM +0100, Jean-Francois Moine wrote:
> The proposed DRM driver works on a Orange PI 2 with a kernel 4.4-rc1
> and the H3 patches found in Hans de Goede's GIT repository.
> 
> As there is no documentation about the DE2 nor about the HDMI which
> are found in the H3, this driver has been built from Allwiiner's
> sources.

That's unfortunate :/

Have you checked in the A64 BSP if there was some useful information?

> So, there may be license problems, especially for the file
> de2_hdmi_h3.c which contains a lot of magic values.

I guess it's the biggest issue with your code right now. What licenses
issues are we talking about here?

Remember that having your Signed-off-by tag on a commit means that you
certify that you have the right to submit the patch under the license
you indicate in the files added and / or modified.

If you don't have such right, for example because you don't have the
right and / or authorization from the initial author to re-license
that code, you cannot put your SoB.

> The associated DT and documentation will be submitted when the H3 DTs
> will be in the kernel.

Having the DT binding documentation would really help in the review.

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160106/80c37335/attachment.sig>

  parent reply	other threads:[~2016-01-06 21:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 19:15 [PATCH RFC 0/2] Add a display driver to the Allwinner H3 Jean-Francois Moine
2016-01-05 18:28 ` [PATCH RFC 1/2] clk: sunxi: Add sun8i display support Jean-Francois Moine
2016-01-06  2:39   ` Chen-Yu Tsai
2016-01-08 17:50     ` Jean-Francois Moine
2016-01-18 19:09   ` Maxime Ripard
2016-01-19  8:09     ` Jean-Francois Moine
2016-01-27 21:50       ` Maxime Ripard
2016-01-28 14:55         ` Jean-Francois Moine
2016-01-05 18:40 ` [PATCH RFC 2/2] drm: sunxi: Add a basic DRM driver for Allwinner DE2 Jean-Francois Moine
2016-01-05 20:38   ` Russell King - ARM Linux
2016-01-11 18:56     ` Jean-Francois Moine
2016-01-06 20:41   ` Jens Kuske
2016-01-13 17:37     ` Jean-Francois Moine
2016-01-06 21:20 ` Maxime Ripard [this message]
2016-01-08 17:13   ` [PATCH RFC 0/2] Add a display driver to the Allwinner H3 Jean-Francois Moine
2016-01-18 10:18     ` Maxime Ripard
2016-01-19  8:49       ` Jean-Francois Moine
2016-02-02 16:58         ` Maxime Ripard

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=20160106212046.GD9631@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).