From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 4/9] video: Add generic HDMI infoframe helpers
Date: Mon, 8 Apr 2013 14:52:40 +0300 [thread overview]
Message-ID: <20130408115240.GH4469@intel.com> (raw)
In-Reply-To: <20130307134412.GA25923@avionic-0098.mockup.avionic-design.de>
On Thu, Mar 07, 2013 at 02:44:12PM +0100, Thierry Reding wrote:
> On Thu, Mar 07, 2013 at 02:32:51PM +0100, Lucas Stach wrote:
> > Am Montag, den 04.03.2013, 16:02 +0100 schrieb Thierry Reding:
> > > On Mon, Mar 04, 2013 at 04:49:46PM +0200, Ville Syrjälä wrote:
> > > > On Fri, Feb 22, 2013 at 08:03:26AM +0100, Thierry Reding wrote:
> > > [...]
> > > > > diff --git a/drivers/video/hdmi.c b/drivers/video/hdmi.c
> > > > > new file mode 100644
> > > > > index 0000000..ab23c9b
> > > > > --- /dev/null
> > > > > +++ b/drivers/video/hdmi.c
> > > > > @@ -0,0 +1,308 @@
> > > > > +/*
> > > > > + * Copyright (C) 2012 Avionic Design GmbH
> > > > > + *
> > > > > + * This program is free software; you can redistribute it and/or modify
> > > > > + * it under the terms of the GNU General Public License version 2 as
> > > > > + * published by the Free Software Foundation.
> > > > > + */
> > > >
> > > > BTW was there any discussion about the license? drm is generally MIT.
> > > > Are people OK with depending on GPL code for infoframe support?
> > >
> > > I wasn't aware of that. I don't know how much of an issue it is really
> > > since all symbols are exported non-GPL.
> > >
> > > Thierry
> >
> > It's not about the export of the symbols, but more about porting DRM to
> > other UNIXes like BSD. Using the GPL here makes life for the BSD guys a
> > lot harder and they are already struggling really hard to keep up with
> > the pace of Linux. So if you don't care too much it would be nice to use
> > MIT here.
>
> Sure, I'll relicense it under MIT then.
It seems these got merged as GPL. Do you want to provide a patch for
changing the license?
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-04-08 11:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 7:03 [PATCH v5 0/9] Add HDMI infoframe helpers Thierry Reding
2013-02-22 7:03 ` [PATCH v5 1/9] drm: Remove duplicate drm_mode_cea_vic() Thierry Reding
2013-02-22 7:03 ` [PATCH v5 2/9] drm: Move mode tables to drm_edid.c Thierry Reding
2013-02-22 7:03 ` [PATCH v5 3/9] drm: Add some missing forward declarations Thierry Reding
2013-02-22 7:03 ` [PATCH v5 4/9] video: Add generic HDMI infoframe helpers Thierry Reding
2013-02-22 16:01 ` Ville Syrjälä
2013-03-04 14:49 ` Ville Syrjälä
2013-03-04 15:02 ` Thierry Reding
2013-03-07 13:32 ` Lucas Stach
2013-03-07 13:44 ` Thierry Reding
2013-04-08 11:52 ` Ville Syrjälä [this message]
2013-04-08 12:49 ` Thierry Reding
2013-02-22 7:03 ` [PATCH v5 5/9] drm: Add " Thierry Reding
2013-02-22 7:03 ` [PATCH v5 6/9] drm: Add EDID helper documentation Thierry Reding
2013-02-22 7:03 ` [PATCH v5 7/9] drm/tegra: Use generic HDMI infoframe helpers Thierry Reding
2013-02-22 7:03 ` [PATCH v5 8/9] drm/i915: " Thierry Reding
2013-02-22 7:03 ` [PATCH v5 9/9] drm/radeon: " Thierry Reding
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=20130408115240.GH4469@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=thierry.reding@avionic-design.de \
/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