Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Nova-T FE_GET_FRONTEND
I'm going on in my tries to let my nova-t card work:
00:0e.0 Class 0480: 1131:7146 (rev 01)
Subsystem: 13c2:1005
Flags: bus master, medium devsel, latency 64, IRQ 5
Memory at fde00000 (32-bit, non-prefetchable)
I'm using last CVS drivers and apps, here the dmesg:
saa7146: found saa7146 @ mem 42a2e000 (revision 1, irq 5)
(0x13c2,0x1005).
DVB: registering new adapter (TT-Budget/WinTV-NOVA-T PCI).
dvbfe_l64781: Trying to attach to adapter
0x60000:TT-Budget/WinTV-NOVA-T PCI.
dvbfe_l64781: l64781_command
DVB: registering frontend 0 (Grundig 29504-401 (LSI L64781 Based))...
adapter has MAC addr = 00:d0:5c:21:2a:2f
For more detailed info look at http://www.geocities.com/simon3z/nova-t
Tring to let work dvbscan with this file:
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 706000000 8MHz 1/2 NONE QAM64 8k 1/4 NONE
I decided to patch scan.c to have a feedback of the parameters I'm going
to set in the frontend, so after (about line 1300):
if (ioctl(frontend_fd, FE_SET_FRONTEND, &p) == -1)
{
errorn("Setting frontend parameters failed");
return -1;
}
I added:
if (ioctl(frontend_fd, FE_GET_FRONTEND, &p) == -1)
{
errorn("Getting frontend parameters failed");
return -1;
}
fprintf(stderr, ">>> dumped: ");
zap_dump_dvb_parameters(stderr, t->type, &p, sat_polarisation(t),
sat_number(t));
fprintf(stderr, "\n");
In this way I think I can check the parameters I'm actually setting in
the tuner. With a great disappoint I got this output:
initial transponder 706000000 0 1 9 3 1 3 0
>>> tune to:
706000000:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_1_2:FEC_AUTO:QAM_64:
TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
>>> dumped:
706122880:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:
TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
As you can see the frequency, FECs, the TRANSMISSION_MODE and the
GUARD_INTERVAL are different!!!
Is this the right behaviour?
Could be this the problem about tuning the card?
How can I solve this problem?
An other question:
If FECs and GUARD_INTERVAL are wrong, should I get any signal but no
lock? Or I wont even get any signal?
Thanks in advance
--
Simon.
Home |
Main Index |
Thread Index