From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Peter Fassberg <pf@leissner.se>
Cc: Andy Furniss <adf.lists@gmail.com>, linux-media@vger.kernel.org
Subject: Re: PCTV Triplestick and Raspberry Pi B+
Date: Tue, 7 Jul 2015 17:35:00 +0200 [thread overview]
Message-ID: <20150707173500.21041ab3@dibcom294.coe.adi.dibcom.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1507071722280.72900@nic-i.leissner.se>
On Tue, 7 Jul 2015 17:33:01 +0200 (SST) Peter Fassberg <pf@leissner.se>
wrote:
> On Sun, 5 Jul 2015, Patrick Boettcher wrote:
>
> > Your Intel platform is 64bit. I don't know the TripleStick nor the SI or
> > the EM28xx-driver but _maybe_ there is a problem with it on 32-bit
> > platforms. A long shot, I know, but you'll never know.
>
> That was a very good point.
>
> I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising.
>
> In 32-bit I couldn't even scan a DVT-T transponder! dvbv5-scan did Lock, but it didn't find any PSI PIDs. So there is for sure a problem with 32-bit platforms. And the DVT-T2 transponders didn't work either.
>
> Maybe the Raspberry problem can be a Endianess problem?
No, rpi (arm) is little-endian as Intel.
Which drivers is your device using again?
regards,
--
Patrick.
next prev parent reply other threads:[~2015-07-07 15:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 11:07 PCTV Triplestick and Raspberry Pi B+ Peter Fassberg
2015-07-05 9:50 ` Andy Furniss
2015-07-05 11:27 ` Peter Fassberg
2015-07-05 11:59 ` Andy Furniss
2015-07-05 13:44 ` Peter Fassberg
2015-07-05 14:43 ` Andy Furniss
2015-07-05 15:45 ` Peter Fassberg
2015-07-06 8:52 ` Andy Furniss
2015-07-05 16:44 ` Patrick Boettcher
2015-07-07 15:33 ` Peter Fassberg
2015-07-07 15:35 ` Patrick Boettcher [this message]
2015-07-07 15:38 ` Peter Fassberg
2015-07-07 16:25 ` Patrick Boettcher
2015-07-07 16:31 ` Patrick Boettcher
2015-07-07 16:44 ` Peter Fassberg
2015-07-07 16:51 ` Peter Fassberg
2015-07-08 7:33 ` Patrick Boettcher
2015-07-08 7:52 ` Olli Salonen
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=20150707173500.21041ab3@dibcom294.coe.adi.dibcom.com \
--to=patrick.boettcher@posteo.de \
--cc=adf.lists@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=pf@leissner.se \
/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