public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "nibble.max" <nibble.max@gmail.com>
To: "Konstantin Dimitrov" <kosio.dimitrov@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>,
	"Andreas Mair" <amair.sob@googlemail.com>
Subject: Re: Re: Mystique SaTiX-S2 Sky Xpress DUAL card
Date: Mon, 13 Feb 2012 23:31:38 +0800	[thread overview]
Message-ID: <201202132331357092722@gmail.com> (raw)
In-Reply-To: CAJZeATR2RcbhH9zNQwkHRoy4hKTK02xzk8LBwCzvkSisoZePCg@mail.gmail.com

Hello Konstantin,
I think "Bestunar" do make the two wrong things.
One, they put the copyright without your permission. 
But I doute that you copy and paste the Montage Technology's reference code and why not put Montage copyright?
Two, they write the code based on the ds3000.c file which you created, even they enhance and fix some bugs.

They build the products based on Montage Technology advanced M88DS3103 chip, which is totally a new chip different from old ds3000.
And they are the first company to adopt this new chip on the Satellite DVB-S2 tuner cards.
They do the right thing now that create a new file named m88ds3103.c for the new chip in linux media tree.
http://www.dvbsky.net/download/bst-patch.tar.gz 

Br,

2012-02-13 



nibble.max 



发件人: Konstantin Dimitrov 
发送时间: 2011-12-29  18:25:37 
收件人: Andreas Mair 
抄送: linux-media 
主题: Re: Mystique SaTiX-S2 Sky Xpress DUAL card 
hello Andreas,
i've checked the Linux drivers for the card you referred to and
whoever made it is breaking all the rules claiming copyright over the
whole driver adding at the beginning:
"Copyright (C) 2010 Bestunar Inc."
when they just patched the driver very slightly adding only new
initialization values - if they wish they can claim copyright only
over those small changes (even they are just number constants provided
by the chip maker). in any case that's ridiculous, because i made that
driver and the copyright notice is:
http://git.linuxtv.org/media_tree.git/blob/61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf:/drivers/media/dvb/frontends/ds3000.c
    Montage Technology DS3000/TS2020 - DVBS/S2 Demodulator/Tuner driver
    Copyright (C) 2009 Konstantin Dimitrov <kosio.dimitrov@gmail.com>
    Copyright (C) 2009 TurboSight.com
and i strongly opposed that copyright massage can be changed in the
way like they did especially over the changes they made.
also, the whole 'ds3000' driver, even it's licensed under GPL, was
submitted to the Linux kernel without my formal permission that to be
done, i.e. you can think for that as it was leaked to the Linux kernel
from third-parties and not the driver author and copyright-holder.
so, it seems to me "Bestunar Inc" is some obscure Chinese company most
probably cloning hardware rather than spent any time doing
development, which or course also don't honor the work put in
development of open-source driver for the chips they're using and try
very hard to make it look like they did it or that they did something
more significant than what they actually did. i'm sure you can
understand my position and my opinion that such companies shouldn't be
supported in any possible way.
best regards,
konstantin
On Thu, Dec 29, 2011 at 11:07 AM, Andreas Mair <amair.sob@googlemail.com> wrote:
> Hello,
>
> I'm using that card in my Linux VDR box:
> http://www.dvbshop.net/product_info.php/info/p2440_Mystique-SaTiX-S2-Sky-Xpress-DUAL--USALS--DiseqC-1-2--Win-Linux.html
>
> That's the lspci output:
> =========== SNIP =========
> $ lspci -vvvnn
> 02:00.0 Multimedia video controller [0400]: Conexant Systems, Inc.
> CX23885 PCI Video and Audio Decoder [14f1:8852] (rev 02)
>        Subsystem: Device [4254:0952]
>        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>        Latency: 0, Cache Line Size: 64 bytes
>        Interrupt: pin A routed to IRQ 16
>        Region 0: Memory at fe400000 (64-bit, non-prefetchable) [size=2M]
>        Capabilities: [40] Express (v1) Endpoint, MSI 00
>                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
> <64ns, L1 <1us
>                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
>                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
>                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
>                        MaxPayload 128 bytes, MaxReadReq 512 bytes
>                DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+
> AuxPwr- TransPend-
>                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
> Latency L0 <2us, L1 <4us
>                        ClockPM- Surprise- LLActRep- BwNot-
>                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
>                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
> SlotClk+ DLActive- BWMgmt- ABWMgmt-
>        Capabilities: [80] Power Management version 2
>                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
> PME(D0+,D1+,D2+,D3hot+,D3cold-)
>                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>        Capabilities: [90] Vital Product Data
>                Product Name: "
>                End
>        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
>                Address: 0000000000000000  Data: 0000
>        Capabilities: [100] Advanced Error Reporting
>                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
>                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
>                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
>                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
>                AERCap: First Error Pointer: 14, GenCap- CGenEn- ChkCap- ChkEn-
>        Capabilities: [200] Virtual Channel <?>
>        Kernel driver in use: cx23885
>        Kernel modules: cx23885
> =========== SNAP =========
>
> So this is different to what's written at
> http://linuxtv.org/wiki/index.php/Mystique_SaTiX-S2_Dual
> I guess it's more like that card: http://linuxtv.org/wiki/index.php/DVBSKY_S952
>
> I'm using the drivers found at http://www.dvbsky.net/Support.html
> (http://www.dvbsky.net/download/linux-3.0-media-20111024-bst-111205.tar.gz).
> I didn't get that card running with kernel 3.0.6 and haven't seen
> support for that card in any linuxtv.org repository I've looked into.
>
> Now I wonder:
> - Who is responsible for that drivers? Someone at DVBSky.net?
> - Is there a chance to get that drivers into the kernel?
> - Has anybody else on this list this card running?
>
> Best regards,
> Andreas
> --
> http://andreas.vdr-developer.org --- VDRAdmin-AM & EnigmaNG & VDRSymbols
> VDR user #303
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-02-13 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  9:07 Mystique SaTiX-S2 Sky Xpress DUAL card Andreas Mair
2011-12-29 10:25 ` Konstantin Dimitrov
2012-02-13 15:31 ` nibble.max [this message]
     [not found] ` <201202132327590699588@gmail.com>
2012-02-13 15:56   ` Konstantin Dimitrov
2012-02-14  3:15   ` nibble.max

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=201202132331357092722@gmail.com \
    --to=nibble.max@gmail.com \
    --cc=amair.sob@googlemail.com \
    --cc=kosio.dimitrov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox