[pvrusb2] HVR 1950 Transmitter
Mike Ingardia
mike.ingardia at gmail.com
Tue Oct 13 20:34:01 CDT 2009
Mike,
Sorry for the delay in getting back to you but got pulled into various
"work" activities that distracted me from working on this.
Here is where I am:
After doing some reading I came across the following site:
http://www.blushingpenguin.com/mark/blog/?p=24&cp=2
Which if I follow I get painfully close:
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.859129] lirc_pvr150: probe
0x70 @ pvrusb2_a: yes
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.859500] lirc_pvr150: probe
0x71 @ pvrusb2_a: yes
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.859502] lirc_pvr150: chip
found with RX and TX
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.859565] lirc_pvr150: poll
thread started
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.861279] lirc_dev:
lirc_register_plugin: sample_rate: 0
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.861316] i2c ir driver 0-0070:
firmware: requesting haup-ir-blaster.bin
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.888847] lirc_pvr150: firmware
of size 302355 loaded
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.889184] lirc_pvr150: 743
codesets loaded
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.889215] lirc_pvr150: 01 60 00
01 5b<7>lirc_pvr150: 05 02 04 4b 1a<7>lirc_pvr150: 09 79 88 b1
1f<7>lirc_pvr150: 0d 87 f5 16 61<7>lirc_pvr150: 11 a6 d9 ec
9a<7>lirc_pvr150: 15 0f a7 ab 27<7>lirc_pvr150: 19 48 9d 7e
1a<7>lirc_pvr150: 1d d9 0c 0e 48<7>lirc_pvr150: 21 91 77 d6
3d<7>lirc_pvr150: 25 09 44 18 60<7>lirc_pvr150: 29 e5 12 c6
6c<7>lirc_pvr150: 2d ba 32 c4 26<7>lirc_pvr150: 31 e3 76 01
48<7>lirc_pvr150: 35 a2 7d 81 59<7>lirc_pvr150: 39 90 28 8f
48<7>lirc_pvr150: 3d 79 61 b4 0a<7>lirc_pvr150: 41 0b 57 21
6e<7>lirc_pvr150: 45 00 78 ad 62<7>lirc_pvr150: 49 b5 68 a2
27<7>lirc_pvr150: 4d 42 4e da 6c<7>lirc_pvr150: 51 94 63 0e
2a<7>lirc_pvr150: 55 1a 30 3b 45<7>lirc_pvr150: 59 fa 34 25
e5<7>lirc_pvr150: 5d cb 1e c1 ee<7>lirc_pvr150: 61 00 00 00
ee<3>lirc_pvr150: i2c_master_send failed with -5
Oct 6 14:00:14 amd-linuxmce64 kernel: [ 931.911775] lirc_pvr150: poll
thread ended
Now inorder to load the lirc_pvr150 I had to use the firmware referenced in
the site and I suspect that the firmware is either wrong or some how for
what ever reason causing a problem. Using the i2c module I can get the
remote control to work just fine but the transmitter is non-existent, and
from various posts I have concluded that the i2c module with *ir*-kbd-i2c
creates the approate devices but the ir transmitter part simply does not
work.
This leads me down two paths, one trying to build the latest pvrusb2 driver
on ubuntu 9.04 ( the system I have ) and 2 trying to see if I can get the
lirc_pvr150 module to actually work since it seems to have the right code to
drive the IR Blaster.
Question one: Mike any insight on why the lirc_pvr150 module would bomb out
on me? Is there a way to capture the "right" firmware for the ir blaster
from the device?
Question two: Building help on ubuntu:
When I look under:/lib/modules/2.6.28-15-generic I don't see a source
directory.
michael at amd-linuxmce:~/extract$ ls /lib/modules/2.6.28-15-generic/
build modules.ccwmap modules.ofmap modules.usbmap
initrd modules.dep modules.order updates
kernel modules.dep.bin modules.pcimap volatile
misc modules.ieee1394map modules.seriomap
modules.alias modules.inputmap modules.symbols
modules.alias.bin modules.isapnpmap modules.symbols.bin
Attempting to build with out setting any of the environment variables yields
the following error:
michael at amd-linuxmce:~/extract/pvrusb2-mci-20091011$ make --directory driver
make: Entering directory `/home/michael/extract/pvrusb2-mci-20091011/driver'
make INSTALL_MOD_DIR=pvrusb2 -C /lib/modules/2.6.28-15-generic/build
M=/home/michael/extract/pvrusb2-mci-20091011/driver CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_24XXX=y CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y CONFIG_VIDEO_PVRUSB2_DEBUGIFC=y
CONFIG_VIDEO_ADV_DEBUG=y modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-15-generic'
CC [M]
/home/michael/extract/pvrusb2-mci-20091011/driver/pvrusb2-devattr.o
/home/michael/extract/pvrusb2-mci-20091011/driver/pvrusb2-devattr.c:42:22:
error: tda18271.h: No such file or directory
/home/michael/extract/pvrusb2-mci-20091011/driver/pvrusb2-devattr.c:43:21:
error: tda8290.h: No such file or directory
Searching for the missing file yields:
michael at amd-linuxmce:~/extract/pvrusb2-mci-20091011$ locate tda18271.h
/usr/src/linux-headers-2.6.28-11-generic/include/config/media/tuner/tda18271.h
/usr/src/linux-headers-2.6.28-13-generic/include/config/media/tuner/tda18271.h
/usr/src/linux-headers-2.6.28-14-generic/include/config/media/tuner/tda18271.h
/usr/src/linux-headers-2.6.28-15-generic/include/config/media/tuner/tda18271.h
/usr/src/v4l-dvb/.hg/store/data/linux/drivers/media/common/tuners/tda18271.h.i
/usr/src/v4l-dvb/.hg/store/data/linux/drivers/media/dvb/frontends/tda18271.h.i
/usr/src/v4l-dvb/linux/drivers/media/common/tuners/tda18271.h
/usr/src/v4l-dvb/v4l/tda18271.h
michael at amd-linuxmce:~/extract/pvrusb2-mci-20091011$
Suggestions on the *right* settings for the environment variables?
Mike...
On Mon, Oct 12, 2009 at 1:00 PM, <pvrusb2-request at isely.net> wrote:
> Send pvrusb2 mailing list submissions to
> pvrusb2 at isely.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> or, via email, send a message with subject or body 'help' to
> pvrusb2-request at isely.net
>
> You can reach the person managing the list at
> pvrusb2-owner at isely.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pvrusb2 digest..."
>
>
> Today's Topics:
>
> 1. Re: pvrusb2 Digest, Vol 50, Issue 3 (Mike Isely)
> 2. Re: HVR 1950 Remote. (Mike Isely)
> 3. Re: HVR 1950 Remote. (Nicholas Robbins)
> 4. Re: HVR 1950 Remote. (Mike Isely)
> 5. New driver snapshot: pvrusb2-mci-20091011 (Mike Isely)
> 6. Re: HVR 1950 Remote. (Nicholas Robbins)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 11 Oct 2009 15:24:48 -0500 (CDT)
> From: Mike Isely <isely at isely.net>
> Subject: Re: [pvrusb2] pvrusb2 Digest, Vol 50, Issue 3
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Message-ID: <alpine.DEB.1.10.0910111520220.13876 at cnc.isely.net>
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, 6 Oct 2009, Michael wrote:
>
> > Sorry long day, 2.6.28-15 is the kernel version.
> >
> > Did some digging. It appears that there have been several changes to
> > the pvrusb2 driver related to the 1950 as of late, so now I am on the
> > road to trying to build the latest snapshot. Would not build can't find
> > the tda18271.h. In ubuntu that file is located
> > at
> /usr/src/linux-headers-2.6.28-15-generic/include/config/media/tuner/tda18271.h
> > but the build is not finding it. Have to keep looking I guess into how
> > it finds includes.
>
> Hmm, that should simply "work". I routinely test compile the standalone
> driver against a sample kernel tree for everything all the way back to
> 2.6.12.3 (whether the driver still actually works that far back is a
> different question). Compilation is fine here for all such cases. The
> only explanation I can come up with is a .config difference. I would
> expect that a distro-supplied kernel should have things like DVB
> enabled...
>
> -Mike
>
> --
>
> Mike Isely
> isely @ isely (dot) net
> PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 11 Oct 2009 15:30:42 -0500 (CDT)
> From: Mike Isely <isely at isely.net>
> Subject: Re: [pvrusb2] HVR 1950 Remote.
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Message-ID: <alpine.DEB.1.10.0910111526370.13876 at cnc.isely.net>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, 9 Oct 2009, Nicholas Robbins wrote:
>
> > Success!
> >
> > I was able to get the remote working. All I had to do was upgrade to
> 2.6.28. The hard part was getting my other tuner to work. (I won't bother
> you about that here.)
> >
> > My configuration is:
> > kernel: 2.6.28-gentoo-r5
> > pvrusb2: (in kernel)
> > lirc: 0.8.6-r1 (gentoo ebuild, built with LIRC_DEVICES="hauppauge" )
> > lirc modules: lirc_i2c and lirc_dev.
> >
> > afaict (using 'udevadm trigger') udev doesn't want to autoload the lirc
> modules. I may have to tell the boot process to autoload them. I assume
> putting them in the modules.autoload file should work. I haven't tried out
> restarting yet, since I just got it working before recordings were scheduled
> last night. I will probably get that working next week.
>
> Can you point out exactly which LIRC driver you are using in this
> configuration? (I'd expect it to be the pvr-150 variant, but it's
> useful to be sure.)
>
> Also when you said "working" was this just for IR reception or have you
> been able to get IR *transmit* working as well? I'm especially curious
> about IR blaster functionality because as far as I know right now,
> nobody has managed to get that working on the HVR-1950. The information
> I have however is fairly old and right now I'm no better equipped to
> test for this than anyone here on this list (i.e. I am *not* an LIRC
> expert).
>
> -Mike
>
> --
>
> Mike Isely
> isely @ isely (dot) net
> PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 11 Oct 2009 18:11:13 -0700 (PDT)
> From: Nicholas Robbins <nickrobbins at yahoo.com>
> Subject: Re: [pvrusb2] HVR 1950 Remote.
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Message-ID: <997953.2152.qm at web110313.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
>
> --- On Sun, 10/11/09, Mike Isely <isely at isely.net> wrote:
>
> > Can you point out exactly which LIRC driver you are using
> > in this
> > configuration?? (I'd expect it to be the pvr-150
> > variant, but it's
> > useful to be sure.)
>
> Is this what you mean: (From my /var/log/messages)
>
> Oct 11 20:30:41 babel lirc_dev: lirc_register_driver: sample_rate: 10
> Oct 11 20:30:41 babel lirc_i2c: chip 0x10005 found @ 0x71 (Hauppauge
> PVR150)
> >
> > Also when you said "working" was this just for IR reception
> > or have you
> > been able to get IR *transmit* working as well?
> Haven't tried the blaster at all.
>
> also, seems like I may have some rebooting issues, the soft boot seemed ok,
> but a hard reboot might have things a little foobared.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 11 Oct 2009 22:55:59 -0500 (CDT)
> From: Mike Isely <isely at isely.net>
> Subject: Re: [pvrusb2] HVR 1950 Remote.
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Message-ID: <alpine.DEB.1.10.0910112254050.13876 at cnc.isely.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Sun, 11 Oct 2009, Nicholas Robbins wrote:
>
> >
> >
> > --- On Sun, 10/11/09, Mike Isely <isely at isely.net> wrote:
> >
> > > Can you point out exactly which LIRC driver you are using
> > > in this
> > > configuration?? (I'd expect it to be the pvr-150
> > > variant, but it's
> > > useful to be sure.)
> >
> > Is this what you mean: (From my /var/log/messages)
> >
> > Oct 11 20:30:41 babel lirc_dev: lirc_register_driver: sample_rate: 10
> > Oct 11 20:30:41 babel lirc_i2c: chip 0x10005 found @ 0x71 (Hauppauge
> PVR150)
>
> Yeah, that's what I wanted to see. Thanks.
>
>
> > >
> > > Also when you said "working" was this just for IR reception
> > > or have you
> > > been able to get IR *transmit* working as well?
> > Haven't tried the blaster at all.
>
> OK, so to the best of my knowledge nobody has yet seen the IR blaster
> side work on the HVR-1950 :-(
>
> >
> > also, seems like I may have some rebooting issues, the soft boot
> > seemed ok, but a hard reboot might have things a little foobared.
>
> Can you be a little more specific? Hard reboot of the host? Power
> cycle the device?
>
> -Mike
>
> --
>
> Mike Isely
> isely @ isely (dot) net
> PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
>
> ------------------------------
>
> Message: 5
> Date: Sun, 11 Oct 2009 23:01:11 -0500 (CDT)
> From: Mike Isely <isely at isely.net>
> Subject: [pvrusb2] New driver snapshot: pvrusb2-mci-20091011
> To: pvrusb2 at isely.net
> Message-ID: <alpine.DEB.1.10.0910112300320.13876 at cnc.isely.net>
> Content-Type: text/plain; charset=us-ascii
>
>
> A new pvrusb2 driver snapshot is available. The driver changes are:
>
> (+) Log a description of the hardware when the driver is associated
> with said hardware.
>
> (+) Include hardware description in sysfs debuginfo output.
>
> (+) Implement some additional logic during initialization to
> differentiate between failures due to jammed hardware vs
> failures due to missing / messed up sub-device kernel modules.
> This should result in slightly more useful kernel messages about
> the problem.
>
> (+) Include patch from Mike Krufky to "disable the tda18271 slave
> tuner output / loop thru options when in low power mode" (this
> is specific to HVR-1950 and is only relevant for kernel 2.6.32
> or later).
>
> These are all small tweaks, nothing really fantastic.
>
> As usual, the pvrusb2 web site can be found at:
>
> http://www.isely.net/pvrusb2/pvrusb2.html
>
> Also, for those using v4l-dvb, the following URL points to a Mercurial
> repository which contains the same driver, suitably transformed for
> direct use inside of v4l-dvb:
>
> http://linuxtv.org/hg/~mcisely/pvrusb2-20091011/<http://linuxtv.org/hg/%7Emcisely/pvrusb2-20091011/>
>
>
> -Mike
>
> --
>
> Mike Isely
> isely @ isely (dot) net
> PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 12 Oct 2009 08:14:30 -0700 (PDT)
> From: Nicholas Robbins <nickrobbins at yahoo.com>
> Subject: Re: [pvrusb2] HVR 1950 Remote.
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Message-ID: <158573.25933.qm at web110309.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
>
>
> > > --- On Sun, 10/11/09, Mike Isely <isely at isely.net>
> > wrote:
> > >
> > Yeah, that's what I wanted to see.? Thanks.
> >
> >
> > >
> > > also, seems like I may have some rebooting issues, the
> > soft boot
> > > seemed ok, but a hard reboot might have things a
> > little foobared.
> >
> > Can you be a little more specific?? Hard reboot of the
> > host?? Power
> > cycle the device?
> >
> > ? -Mike
>
>
> Hard rebooting the host left the system in the following state: The other
> two tuners (one USB, on miniPCI) took a while (~2 minutes) before udev could
> sort them out. The system ignored usb keyboard input, and ssh sessions were
> hanging after about a minute.
>
> Again, a soft reboot fixed the problems.
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>
>
> End of pvrusb2 Digest, Vol 50, Issue 7
> **************************************
>
More information about the pvrusb2
mailing list