From: Oliver Endriss <o.endriss@gmx.de>
To: John J Lee <jjl@pobox.com>
Cc: linux-media@vger.kernel.org
Subject: Re: saa7146 firmware upload time?
Date: Sun, 2 May 2010 21:54:36 +0200 [thread overview]
Message-ID: <201005022154.37226@orion.escape-edv.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1005021904150.4041@alice>
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/
----------------------------------------------------------------
next prev parent reply other threads:[~2010-05-02 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 18:13 saa7146 firmware upload time? John J Lee
2010-05-02 19:54 ` Oliver Endriss [this message]
2010-05-02 21:07 ` John J Lee
2010-05-02 21:24 ` John J Lee
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=201005022154.37226@orion.escape-edv.de \
--to=o.endriss@gmx.de \
--cc=jjl@pobox.com \
--cc=linux-media@vger.kernel.org \
/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