All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abylay Ospan <aospan@netup.ru>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: LinuxTV ported to Windows
Date: Thu, 01 Dec 2011 10:05:38 +0300	[thread overview]
Message-ID: <4ED72742.6020608@netup.ru> (raw)
In-Reply-To: <CAGoCfiwShvPSgAPHKaxj=sMG-Fs9RdH0_3mLHYWuY96Z33AOag@mail.gmail.com>

Hi Devin,

Thanks for this idea. Need to investigate.
Currently we've made porting and released the results without any 
license violations in mind ...

On 30.11.2011 20:23, Devin Heitmueller wrote:
> 2011/11/30 Abylay Ospan<aospan@netup.ru>:
>> Hello,
>>
>> We have ported linuxtv's cx23885+CAM en50221+Diseq to Windows OS (Vista, XP,
>> win7 tested). Results available under GPL and can be checkout from git
>> repository:
>> https://github.com/netup/netup-dvb-s2-ci-dual
>>
>> Binary builds (ready to install) available in build directory. Currently
>> NetUP Dual DVB-S2 CI card supported (
>> http://www.netup.tv/en-EN/dual_dvb-s2-ci_card.php ).
>>
>> Driver based on Microsoft BDA standard, but some features (DiSEqC, CI)
>> supported by custom API, for more details see netup_bda_api.h file.
>>
>> Any comments, suggestions are welcome.
>>
>> --
>> Abylai Ospan<aospan@netup.ru>
>> NetUP Inc.
> Am I the only one who thinks this is a legally ambigious grey area?
> Seems like this could be a violation of the GPL as the driver code in
> question links against a proprietary kernel.
>
> I don't want to start a flame war, but I don't see how this is legal.
> And you could definitely question whether it goes against the
> intentions of the original authors to see their GPL driver code being
> used in non-free operating systems.
>
> Devin
>

-- 
Abylai Ospan<aospan@netup.ru>
NetUP Inc.


  parent reply	other threads:[~2011-12-01  7:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 16:39 LinuxTV ported to Windows Abylay Ospan
2011-11-30 17:23 ` Devin Heitmueller
2011-11-30 18:02   ` Andreas Oberritter
2011-11-30 19:33     ` Devin Heitmueller
2011-11-30 19:58       ` Andreas Oberritter
2011-11-30 20:11         ` Devin Heitmueller
2011-12-01 19:42         ` Laurent Pinchart
2011-12-01 21:18           ` Steven Toth
2011-12-01 23:10             ` Andreas Oberritter
2011-12-01 23:43               ` Steven Toth
2011-12-01 22:31           ` Andreas Oberritter
2011-12-01  7:05   ` Abylay Ospan [this message]
2011-12-02 18:03   ` Rémi Denis-Courmont
2011-12-02 22:10     ` Patrick Dickey
2011-11-30 18:46 ` Walter Van Eetvelt
2011-12-01  7:05   ` Abylay Ospan
  -- strict thread matches above, loose matches on Subject: below --
2011-12-02  9:35 Issa Gorissen
2011-12-02 12:48 ` Felipe Magno de Almeida

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=4ED72742.6020608@netup.ru \
    --to=aospan@netup.ru \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@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.