All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Tinchev <atl@unixsol.org>
To: Norbert Auge <nauge@digitaldevices.de>, linux-media@vger.kernel.org
Cc: Georgi Chorbadzhiyski <gf@unixsol.org>,
	Marian Zahariev <marian@unixsol.org>
Subject: Bugs reporting
Date: Fri, 21 Aug 2015 17:32:50 +0300	[thread overview]
Message-ID: <55D73692.3040708@unixsol.org> (raw)

Hi,
can you point me where is usually reported the bugs with the cards firmware and/or drivers.
The combination is Cine S2 v6.5 with Duoflex S2 V4.

The miniDiSEqC (AB) is not working on the Duoflex S2 V4. Is not board fault, same behavior have
all cards i tested - about 20 Duoflex and 8 Cine modules.
For the protocol i tested:

Cine S2 v6.5 + Duoflex S2 V4:
  - ports 0 and 1 (Ports on Cine card) - miniDiSEqC is working
  - ports 0 and 1 (Ports on Cine card) - DiSEqC is working
  - ports 2 and up (Ports on Duflex cards) -   DiSEqC is working
  - ports 2 and up (Ports on Duflex cards) -   miniDiSEqC is NOT WORKING

Cine S2 v6.2 + Duoflex S2 older versions:
  - all ports - both Cine and Duoflex  - miniDiSEqC is working
  - all ports - both Cine and Duoflex - DiSEqC is working


Cine S2 v6.5 + Duoflex S2 older version:
  - Not tested, will test soon

Cine S2 v6.2 + Duoflex S2 V4:
  - Not tested, will test when purchase next batch.


Also there is tons of errors on i2c bus to Duoflex S2 V4 tabs.



This was tested with latest drivers, also was tested with stock drivers with several
kernel versions from 3.18.11 to 4.2 rc2 - same behavior

             reply	other threads:[~2015-08-21 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 14:32 Anton Tinchev [this message]
2015-08-24 12:26 ` AW: Bugs reporting Norbert Auge
2015-08-24 16:39   ` Anton Tinchev
     [not found]     ` <00cd01d0df1f$d4da9760$7e8fc620$@digitaldevices.de>
     [not found]       ` <55DC448C.6090004@digitaldevices.de>
2015-08-25 10:39         ` WG: " Norbert Auge

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=55D73692.3040708@unixsol.org \
    --to=atl@unixsol.org \
    --cc=gf@unixsol.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marian@unixsol.org \
    --cc=nauge@digitaldevices.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 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.