On 01/11/2012 12:00 AM, Mauro Carvalho Chehab wrote:
On 10-01-2012 19:36, Antti Palosaari wrote:
Behaviour of new FE is strange for my eyes. Could you look and explain if it is
intentional?
I still see that it changes delivery system automatically to the DVB-T.
That is the latest commit:
On 01/15/2012 08:37 PM, Antti Palosaari wrote:
On 01/11/2012 12:00 AM, Mauro Carvalho Chehab wrote:
On 10-01-2012 19:36, Antti Palosaari wrote:
Behaviour of new FE is strange for my eyes. Could you look and
explain if it is intentional?
I still see that it changes delivery system
Em 15-01-2012 18:03, Antti Palosaari escreveu:
On 01/15/2012 08:37 PM, Antti Palosaari wrote:
On 01/11/2012 12:00 AM, Mauro Carvalho Chehab wrote:
On 10-01-2012 19:36, Antti Palosaari wrote:
Behaviour of new FE is strange for my eyes. Could you look and
explain if it is intentional?
I still
On 01/15/2012 11:08 PM, Mauro Carvalho Chehab wrote:
Em 15-01-2012 18:03, Antti Palosaari escreveu:
On 01/15/2012 08:37 PM, Antti Palosaari wrote:
On 01/11/2012 12:00 AM, Mauro Carvalho Chehab wrote:
On 10-01-2012 19:36, Antti Palosaari wrote:
That seems to be due to cxd2820r bug
On 01/15/2012 11:08 PM, Mauro Carvalho Chehab wrote:
There was a bug at the error code handling on dvb-fe-tool: basically, if it
can't open
a device, it were using a NULL pointer. It was likely fixed by this commit:
Em 15-01-2012 19:47, Antti Palosaari escreveu:
On 01/15/2012 11:08 PM, Mauro Carvalho Chehab wrote:
There was a bug at the error code handling on dvb-fe-tool: basically, if it
can't open
a device, it were using a NULL pointer. It was likely fixed by this commit:
Em 15-01-2012 22:16, Mauro Carvalho Chehab escreveu:
Em 15-01-2012 19:47, Antti Palosaari escreveu:
On 01/15/2012 11:08 PM, Mauro Carvalho Chehab wrote:
There was a bug at the error code handling on dvb-fe-tool: basically, if it
can't open
a device, it were using a NULL pointer. It was
Behaviour of new FE is strange for my eyes. Could you look and explain
if it is intentional?
[crope@localhost dvb]$ ./dvb-fe-tool
Device Sony CXD2820R (DVB-T/T2) (/dev/dvb/adapter0/frontend0) capabilities:
CAN_2G_MODULATION CAN_FEC_1_2 CAN_FEC_2_3 CAN_FEC_3_4 CAN_FEC_5_6
CAN_FEC_7_8
On 10-01-2012 19:36, Antti Palosaari wrote:
Behaviour of new FE is strange for my eyes. Could you look and explain if it
is intentional?
[crope@localhost dvb]$ ./dvb-fe-tool
Device Sony CXD2820R (DVB-T/T2) (/dev/dvb/adapter0/frontend0) capabilities:
CAN_2G_MODULATION CAN_FEC_1_2
On 07-01-2012 23:52, Mauro Carvalho Chehab wrote:
I decided to add support for DVB-S, even without signal for testing.
This probably means that it likely will not work ;) Well, seriously,
we need testers for it.
The current code should be doing the same that szap does, and should
work with
As previously commented at the ML, I'm developing a set of tools
using DVBv5 API. Instead of starting from something existing,
I decided to start from scratch, in order to avoid polluting it
with DVBv3 legacy stuff. Of course, I did some research inside
the existing tools, in order to fill in the
Hi Mauro.
2012/1/7 Mauro Carvalho Chehab mche...@redhat.com:
As previously commented at the ML, I'm developing a set of tools
using DVBv5 API. Instead of starting from something existing,
I decided to start from scratch, in order to avoid polluting it
with DVBv3 legacy stuff. Of course, I did
On 07-01-2012 15:29, Honza Petrouš wrote:
Hi Mauro.
2012/1/7 Mauro Carvalho Chehab mche...@redhat.com:
As previously commented at the ML, I'm developing a set of tools
using DVBv5 API. Instead of starting from something existing,
I decided to start from scratch, in order to avoid polluting
On 07-01-2012 10:19, Mauro Carvalho Chehab wrote:
As previously commented at the ML, I'm developing a set of tools
using DVBv5 API. Instead of starting from something existing,
I decided to start from scratch, in order to avoid polluting it
with DVBv3 legacy stuff. Of course, I did some
14 matches
Mail list logo
