saa7146 firmware upload time?

saa7146 firmware upload time?

[John J Lee]

Hi

My "WinTV NOVA-t" PCI card is recognized by the saa7146 driver (ubuntu 
9.10 2.6.31-21-generic kernel), but I don't have a /dev/video0.  At some 
point I noticed messages in syslog about missing firmware (below), and 
rectified that by fetching the firmware and dropping it in /lib/firmware.

However, there's a big gap (over an hour and a half) between boot and the 
time when the driver complains about the firmware:

May  2 16:00:28 alice kernel: [   58.447825] saa7146: register extension 'budget_ci dvb'.
May  2 16:00:28 alice kernel: [   58.449357] budget_ci dvb 0000:05:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
May  2 16:00:28 alice kernel: [   58.449394] IRQ 17/: IRQF_DISABLED is not guaranteed on shared IRQs
May  2 16:00:28 alice kernel: [   58.449412] saa7146: found saa7146 @ mem ffffc90011348c00 (revision 1, irq 17) (0x13c2,0x1011).
May  2 16:00:28 alice kernel: [   58.449416] saa7146 (0): dma buffer size 192512
May  2 16:00:28 alice kernel: [   58.449417] DVB: registering new adapter (TT-Budget/WinTV-NOVA-T        PCI)
May  2 16:00:28 alice kernel: [   58.510969] adapter has MAC addr = 00:d0:5c:23:ed:cf
May  2 16:00:28 alice kernel: [   58.511252] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1e.0/0000:05:01.0/input/input7
May  2 16:00:28 alice kernel: [   58.587617] DVB: registering adapter 0 frontend 0 (Philips TDA10045H DVB-T)...
[...]
May  2 17:40:39 alice kernel: [ 6057.360792] tda1004x: found firmware revision 0 -- invalid
May  2 17:40:39 alice kernel: [ 6057.360795] tda1004x: waiting for firmware upload (dvb-fe-tda10045.fw)...
May  2 17:40:39 alice kernel: [ 6057.360800] budget_ci dvb 0000:05:01.0: firmware: requesting dvb-fe-tda10045.fw
May  2 17:40:39 alice kernel: [ 6057.449458] tda1004x: no firmware upload (timeout or file not found?)
May  2 17:40:39 alice kernel: [ 6057.449461] tda1004x: firmware upload failed
May  2 17:40:39 alice firmware.sh[4365]: Cannot find  firmware file 'dvb-fe-tda10045.fw'


I don't know anything about the kernel but looking at the source seemed to 
suggest the driver looks for the firmware at modprobe time, but rmmod 
followed by modprobe doesn't give me any messages about firmware (nor does 
a reboot).  What should I do to trigger this firmware upload process 
again?

Thanks


John

Re: saa7146 firmware upload time?

[Oliver Endriss]

Hi,

On Sunday 02 May 2010 20:13:08 John J Lee wrote:
> My "WinTV NOVA-t" PCI card is recognized by the saa7146 driver (ubuntu 
> 9.10 2.6.31-21-generic kernel), but I don't have a /dev/video0.  At some 
> point I noticed messages in syslog about missing firmware (below), and 
> rectified that by fetching the firmware and dropping it in /lib/firmware.
> 
> However, there's a big gap (over an hour and a half) between boot and the 
> time when the driver complains about the firmware:
> 
> May  2 16:00:28 alice kernel: [   58.447825] saa7146: register extension 'budget_ci dvb'.
> May  2 16:00:28 alice kernel: [   58.449357] budget_ci dvb 0000:05:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> May  2 16:00:28 alice kernel: [   58.449394] IRQ 17/: IRQF_DISABLED is not guaranteed on shared IRQs
> May  2 16:00:28 alice kernel: [   58.449412] saa7146: found saa7146 @ mem ffffc90011348c00 (revision 1, irq 17) (0x13c2,0x1011).
> May  2 16:00:28 alice kernel: [   58.449416] saa7146 (0): dma buffer size 192512
> May  2 16:00:28 alice kernel: [   58.449417] DVB: registering new adapter (TT-Budget/WinTV-NOVA-T        PCI)
> May  2 16:00:28 alice kernel: [   58.510969] adapter has MAC addr = 00:d0:5c:23:ed:cf
> May  2 16:00:28 alice kernel: [   58.511252] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1e.0/0000:05:01.0/input/input7
> May  2 16:00:28 alice kernel: [   58.587617] DVB: registering adapter 0 frontend 0 (Philips TDA10045H DVB-T)...
> [...]
> May  2 17:40:39 alice kernel: [ 6057.360792] tda1004x: found firmware revision 0 -- invalid
> May  2 17:40:39 alice kernel: [ 6057.360795] tda1004x: waiting for firmware upload (dvb-fe-tda10045.fw)...
> May  2 17:40:39 alice kernel: [ 6057.360800] budget_ci dvb 0000:05:01.0: firmware: requesting dvb-fe-tda10045.fw
> May  2 17:40:39 alice kernel: [ 6057.449458] tda1004x: no firmware upload (timeout or file not found?)
> May  2 17:40:39 alice kernel: [ 6057.449461] tda1004x: firmware upload failed
> May  2 17:40:39 alice firmware.sh[4365]: Cannot find  firmware file 'dvb-fe-tda10045.fw'
> 
> 
> I don't know anything about the kernel but looking at the source seemed to 
> suggest the driver looks for the firmware at modprobe time, but rmmod 
> followed by modprobe doesn't give me any messages about firmware (nor does 
> a reboot).  What should I do to trigger this firmware upload process 
> again?

Obviously, the firmware is not loaded at modprobe time. It is loaded
when an application opens the frontend for the first time.

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------

Re: saa7146 firmware upload time?

[John J Lee]

On Sun, 2 May 2010, Oliver Endriss wrote:
[...]
> Obviously, the firmware is not loaded at modprobe time. It is loaded
> when an application opens the frontend for the first time.
[...]

Thanks.

Before the frontend can be opened, open(2) must be called on a v4l device 
file, right?  I don't appear to have such a device file (no /dev/video*, 
no /dev/dvb/adaptor*/video*).  I had assumed the missing device file was 
caused by the failure to load the firmware.  So it's still not clear to me 
how to trigger the firmware loading process again (though clearly 
something I did today triggered it once), or indeed whether that is the 
problem I should be trying to solve.

Clues welcome


John

Re: saa7146 firmware upload time?

[John J Lee]

On Sun, 2 May 2010, John J Lee wrote:

> On Sun, 2 May 2010, Oliver Endriss wrote:
> [...]
>> Obviously, the firmware is not loaded at modprobe time. It is loaded
>> when an application opens the frontend for the first time.
> [...]
>
> Thanks.
>
> Before the frontend can be opened, open(2) must be called on a v4l device 
> file, right?  I don't appear to have such a device file (no /dev/video*, no 
> /dev/dvb/adaptor*/video*).  I had assumed the missing device file was caused 
> by the failure to load the firmware.  So it's still not clear to me how to 
> trigger the firmware loading process again (though clearly something I did 
> today triggered it once), or indeed whether that is the problem I should be 
> trying to solve.
>
> Clues welcome

OK, I still don't understand how it works, but I successfully triggered 
the firmware loading process by running kaffeine.  Thanks for your help.


John