Mailing List Archive: MythTV: Users

Call for iMON testing

1 2

View All

Index | Next | Previous | View Threaded

jarod at wilsonet

Jun 17, 2009, 9:14 PM

Post #1 of 37 (4402 views)
Permalink

Call for iMON testing

I'm probably going to regret turning on delivery of mail from this list
again, but I'd like to reach out to as many iMON users as possible...

I've done a *MASSIVE* overhaul of the lirc_imon driver over the past
week and a half, and would like people to test out the new code.

I've already tested extensively on the Antec Veris Premiere (rebranded
iMON UltraBay, device 0x0045), the iMON Touch 7" (0x0034 -- well,
actually, Rene, who helped out hugely w/the code tested it) and the iMON
Knob (one of many 0xffdc devices), so results with devices other than
those are of greatest interest.

So why would you want to test this?

1) recent iMON devices have two usb interface endpoints, which lirc has
historically set up as two different lirc devices (/dev/lirc0,
/dev/lirc1), and you had to bind them together in userspace. Setup is
ugly, and requires modifying init scripts. Well, that's a thing of the
past, dual-interface devices are now handled by a single lirc device.

2) that mouse/keyboard toggle button now actually does the same thing it
does under windows. If there's no IR client, the directional pad
operates as a mouse and ch+/- operate as a scroll wheel. Once an IR
client (like, say, mythtv) is connected, you can toggle back and forth
between mouse operation and lirc button operation (the way its always
behaved -- dpad is up, down, left, right).

3) the touchscreen devices are fully supported, both as an input
subsystem device and an lirc button matrix, so you can pick which way
you want to process touchscreen input data.

4) front-panel buttons and/or knobs are properly re-enabled if you've
gone and mucked with your iMON device under Windows

5) support for putting the IR receiver into either iMON protocol mode,
or Windows MCE (RC-6) protocol mode -- makes it *much* easier to use an
iMON receiver with something like a Logitech Harmony remote (only works
on the newer dual-interface devices, 0x0030 - 0x0046).

Is that enough for y'all? Now get to testing, please... Feedback much
appreciated.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jun 17, 2009, 9:17 PM

Post #2 of 37 (4317 views)
Permalink

Re: Call for iMON testing [In reply to]

On 06/18/2009 12:14 AM, Jarod Wilson wrote:
> I'm probably going to regret turning on delivery of mail from this list
> again, but I'd like to reach out to as many iMON users as possible...
>
> I've done a *MASSIVE* overhaul of the lirc_imon driver over the past
> week and a half, and would like people to test out the new code.

...which you can of course obtain from lirc cvs:

http://lirc.org/cvs.html

(I've also got a kernel git tree w/lirc patched in, but not enough
bandwidth for people to be pulling from that, so unless you know how to
grab linus' tree, then add mine as a remote, we'll let that be...)

> I've already tested extensively on the Antec Veris Premiere (rebranded
> iMON UltraBay, device 0x0045), the iMON Touch 7" (0x0034 -- well,
> actually, Rene, who helped out hugely w/the code tested it) and the iMON
> Knob (one of many 0xffdc devices), so results with devices other than
> those are of greatest interest.
>
> So why would you want to test this?
>
> 1) recent iMON devices have two usb interface endpoints, which lirc has
> historically set up as two different lirc devices (/dev/lirc0,
> /dev/lirc1), and you had to bind them together in userspace. Setup is
> ugly, and requires modifying init scripts. Well, that's a thing of the
> past, dual-interface devices are now handled by a single lirc device.
>
> 2) that mouse/keyboard toggle button now actually does the same thing it
> does under windows. If there's no IR client, the directional pad
> operates as a mouse and ch+/- operate as a scroll wheel. Once an IR
> client (like, say, mythtv) is connected, you can toggle back and forth
> between mouse operation and lirc button operation (the way its always
> behaved -- dpad is up, down, left, right).
>
> 3) the touchscreen devices are fully supported, both as an input
> subsystem device and an lirc button matrix, so you can pick which way
> you want to process touchscreen input data.
>
> 4) front-panel buttons and/or knobs are properly re-enabled if you've
> gone and mucked with your iMON device under Windows
>
> 5) support for putting the IR receiver into either iMON protocol mode,
> or Windows MCE (RC-6) protocol mode -- makes it *much* easier to use an
> iMON receiver with something like a Logitech Harmony remote (only works
> on the newer dual-interface devices, 0x0030 - 0x0046).
>
>
> Is that enough for y'all? Now get to testing, please... Feedback much
> appreciated.
>

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jan at horde

Jun 18, 2009, 5:31 AM

Post #3 of 37 (4290 views)
Permalink

Re: Call for iMON testing [In reply to]

Zitat von Jarod Wilson <jarod [at] wilsonet>:

> Is that enough for y'all? Now get to testing, please... Feedback
> much appreciated.

Awesome! I'm really looking forward to the new code and hope to do
some basic testing before I leave to vacation.

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

pebender at san

Jun 18, 2009, 7:00 PM

Post #4 of 37 (4282 views)
Permalink

Re: Call for iMON testing [In reply to]

Jarod Wilson wrote:
> I'm probably going to regret turning on delivery of mail from this list
> again, but I'd like to reach out to as many iMON users as possible...
>
> I've done a *MASSIVE* overhaul of the lirc_imon driver over the past
> week and a half, and would like people to test out the new code.

I have added it to the latest MiniMyth test build. We will see what happens.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jun 18, 2009, 9:02 PM

Post #5 of 37 (4289 views)
Permalink

Re: Call for iMON testing [In reply to]

On Thursday 18 June 2009 22:00:06 Paul Bender wrote:
> Jarod Wilson wrote:
> > I'm probably going to regret turning on delivery of mail from this list
> > again, but I'd like to reach out to as many iMON users as possible...
> >
> > I've done a *MASSIVE* overhaul of the lirc_imon driver over the past
> > week and a half, and would like people to test out the new code.
>
> I have added it to the latest MiniMyth test build. We will see what happens.

Very cool, glad to hear it! Fingers crossed for nothing but positive
feedback... :)

That reminds me... I've tacked this onto the Fedora 10, 11 and devel
kernel trees as well, so Real Soon Now, there will be test kernels
folks running Fedora (and/or MythDora) can grab.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

seven at seven

Jul 14, 2009, 1:44 AM

Post #6 of 37 (4062 views)
Permalink

Re: Call for iMON testing [In reply to]

>
> Very cool, glad to hear it! Fingers crossed for nothing but positive
> feedback... :)
>
> That reminds me... I've tacked this onto the Fedora 10, 11 and devel
> kernel trees as well, so Real Soon Now, there will be test kernels
> folks running Fedora (and/or MythDora) can grab.
>
> --
> Jarod Wilson
>

Hey Jarod,

Are these test kernels now available?

I'm having problems with the IR/VFD on my 15c2:0036 Device in my recently
upgraded Mythdora 10.21 system.

I can see the /dev/lirc0 & /dev/lirc1 devices and cat /proc/bus/usb/devices
confirms that lirc_imon is loaded on that device but I cannot get the VFD
working

T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=15c2 ProdID=0036 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=02 Driver=lirc_imon
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=lirc_imon
E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms

LCDd fails with the following errors

LCDd -f -r 5 -s 0

driver_load(name="imon", filename="/usr/lib64/lcdproc/imon.so")
imon: using Device /dev/lcd0
imon: ERROR opening /dev/lcd0 (No such file or directory).
imon: Did you load the iMON VFD kernel module?
imon: More info in lcdproc/docs/README.imon
Driver [imon] init failed, return code < 0
Module /usr/lib64/lcdproc/imon.so could not be loaded
Could not load driver imon
There is no output driver
Critical error while initializing, abort.

I'm also having issues with a Dvico remote but I don't believe that's
related as lircd appears to be picking up the button presses just mythtv is
not actioning them.

Cheers,

Anthony

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 14, 2009, 12:04 PM

Post #7 of 37 (4048 views)
Permalink

Re: Call for iMON testing [In reply to]

On 07/14/2009 04:44 AM, Anthony Giggins wrote:
>> Very cool, glad to hear it! Fingers crossed for nothing but positive
>> feedback... :)
>>
>> That reminds me... I've tacked this onto the Fedora 10, 11 and devel
>> kernel trees as well, so Real Soon Now, there will be test kernels
>> folks running Fedora (and/or MythDora) can grab.
>>
>> --
>> Jarod Wilson
>>
>
> Hey Jarod,
>
> Are these test kernels now available?

This build should do the trick for MythDora 10.21:

http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29.6/93.fc10/

> I'm having problems with the IR/VFD on my 15c2:0036 Device in my recently
> upgraded Mythdora 10.21 system.
>
> I can see the /dev/lirc0& /dev/lirc1 devices and cat /proc/bus/usb/devices
> confirms that lirc_imon is loaded on that device but I cannot get the VFD
> working
>
> T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=15c2 ProdID=0036 Rev= 0.01
> C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
> I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=02 Driver=lirc_imon
> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
> I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=lirc_imon
> E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
>
>
> LCDd fails with the following errors
>
> LCDd -f -r 5 -s 0
>
> driver_load(name="imon", filename="/usr/lib64/lcdproc/imon.so")

For your device, I believe you actually need the imonlcd2 lcdproc
driver, if you've got a 0.5.2 lcdproc build. For the 0.5.3 lcdproc
build, you need the imonlcd driver, with Protocol=1. (it was an
out-of-tree patch or two in 0.5.2, finally merged in 0.5.3).

For my 15c2:0045 w/lcdproc 0.5.3, LCDd.conf contains:
...
Driver=imonlcd
...
[imonlcd]
Device=/dev/lcd0
Contrast=200
OnExit=2
Protocol=1

> I'm also having issues with a Dvico remote but I don't believe that's
> related as lircd appears to be picking up the button presses just mythtv is
> not actioning them.

Yeah, unrelated.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv.lists at burns

Jul 14, 2009, 12:07 PM

Post #8 of 37 (4044 views)
Permalink

Re: Call for iMON testing [In reply to]

Jarod Wilson <jarod [at] wilsonet> wrote:

> I've done a *MASSIVE* overhaul of the lirc_imon driver

Sounds worthwhile, pehaps I'll be able to park the wireless
keyboard/trackpad a litte further away from the sofa ;-)

> I've tacked this onto the Fedora 10, 11 and devel kernel trees

Any clue as to what build to keep an eye out for in F11 updates-testing repo?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv.lists at burns

Jul 14, 2009, 12:12 PM

Post #9 of 37 (4044 views)
Permalink

Re: Call for iMON testing [In reply to]

2009/7/14 Andy Burns <mythtv.lists [at] burns>:

> Any clue as to what build to keep an eye out for in F11 updates-testing repo?

[Answering myself]

Is this build worth testing?

http://koji.fedoraproject.org/koji/buildinfo?buildID=112238
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 14, 2009, 12:13 PM

Post #10 of 37 (4042 views)
Permalink

Re: Call for iMON testing [In reply to]

On 07/14/2009 03:07 PM, Andy Burns wrote:
> Jarod Wilson<jarod [at] wilsonet> wrote:
>
>> I've done a *MASSIVE* overhaul of the lirc_imon driver
>
> Sounds worthwhile, pehaps I'll be able to park the wireless
> keyboard/trackpad a litte further away from the sofa ;-)
>
>> I've tacked this onto the Fedora 10, 11 and devel kernel trees
>
> Any clue as to what build to keep an eye out for in F11 updates-testing repo?

I *think* kernel-2.6.29.6-213.fc11 is supposed to hit the
updates-testing repo any day now...

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 14, 2009, 12:14 PM

Post #11 of 37 (4051 views)
Permalink

Re: Call for iMON testing [In reply to]

On 07/14/2009 03:12 PM, Andy Burns wrote:
> 2009/7/14 Andy Burns<mythtv.lists [at] burns>:
>
>> Any clue as to what build to keep an eye out for in F11 updates-testing repo?
>
> [Answering myself]
>
> Is this build worth testing?
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=112238

This one's better:

http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29.6/213.fc11/

206 had some unrelated nasty crasher bug in it that was fixed in 209 or
so, iirc.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv.lists at burns

Jul 14, 2009, 1:02 PM

Post #12 of 37 (4036 views)
Permalink

Re: Call for iMON testing [In reply to]

2009/7/14 Jarod Wilson <jarod [at] wilsonet>:

> This one's better:
> http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29.6/213.fc11/

Just tried that version, boots OK, mouse automatically recognised by
lirc and functioning on the gdm greeter screen (well pointer movement
works and seems to be proportional to mousepad pressure, but
left/right clicks don't work, mouse/kbd toggle had no apparent
effect).

Within mythfrontend only the CH+/CH- keys seem to do anything, acting
as up/down keys in the menus, couldn't dind any other keys that worked
as enter/right/escape etc.

My hardware is an iMON LCD (15c2:ffdc) in a silverstone ML02 case, I
have an older iMON VFD in an LC11 lurking somewhere.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

seven at seven

Jul 14, 2009, 7:11 PM

Post #13 of 37 (4035 views)
Permalink

Re: Call for iMON testing [In reply to]

> On 07/14/2009 04:44 AM, Anthony Giggins wrote:
>>> Very cool, glad to hear it! Fingers crossed for nothing but positive
>>> feedback... :)
>>>
>>> That reminds me... I've tacked this onto the Fedora 10, 11 and devel
>>> kernel trees as well, so Real Soon Now, there will be test kernels
>>> folks running Fedora (and/or MythDora) can grab.
>>>
>>> --
>>> Jarod Wilson
>>>
>>
>> Hey Jarod,
>>
>> Are these test kernels now available?
>
> This build should do the trick for MythDora 10.21:
>
> http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29.6/93.fc10/
>
>
>> I'm having problems with the IR/VFD on my 15c2:0036 Device in my
>> recently
>> upgraded Mythdora 10.21 system.
>>
>> I can see the /dev/lirc0& /dev/lirc1 devices and cat
>> /proc/bus/usb/devices
>> confirms that lirc_imon is loaded on that device but I cannot get the
>> VFD
>> working
>>
>> T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0
>> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
>> P: Vendor=15c2 ProdID=0036 Rev= 0.01
>> C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
>> I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=02 Driver=lirc_imon
>> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
>> I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=lirc_imon
>> E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
>>
>>
>> LCDd fails with the following errors
>>
>> LCDd -f -r 5 -s 0
>>
>> driver_load(name="imon", filename="/usr/lib64/lcdproc/imon.so")
>
> For your device, I believe you actually need the imonlcd2 lcdproc
> driver, if you've got a 0.5.2 lcdproc build. For the 0.5.3 lcdproc
> build, you need the imonlcd driver, with Protocol=1. (it was an
> out-of-tree patch or two in 0.5.2, finally merged in 0.5.3).
>
> For my 15c2:0045 w/lcdproc 0.5.3, LCDd.conf contains:
> ...
> Driver=imonlcd
> ...
> [imonlcd]
> Device=/dev/lcd0
> Contrast=200
> OnExit=2
> Protocol=1

Hmmmm my device is a VFD not an LCD are you sure its still imonlcd2? as
its still not working....

The wierd thing is I was constantly getting these errors before I added
the modprobe options to modeprobe.conf "options lirc_imon display_type=1"

lcd_write: invalid payload size: 32 (expecting 8)

Are there any packages for lcdproc 0.5.3 for Mythdora 10.21 around?

>
>
>> I'm also having issues with a Dvico remote but I don't believe that's
>> related as lircd appears to be picking up the button presses just mythtv
>> is
>> not actioning them.
>
> Yeah, unrelated.

Completely as I just had not copied my old .lircrc file over, now thats
all working :)

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 14, 2009, 8:27 PM

Post #14 of 37 (4018 views)
Permalink

Re: Call for iMON testing [In reply to]

On Tuesday 14 July 2009 16:02:16 Andy Burns wrote:
> 2009/7/14 Jarod Wilson <jarod [at] wilsonet>:
>
> > This one's better:
> > http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29.6/213.fc11/
>
> Just tried that version, boots OK, mouse automatically recognised by
> lirc and functioning on the gdm greeter screen (well pointer movement
> works and seems to be proportional to mousepad pressure, but
> left/right clicks don't work,

Heh, oh yeah... There were some buglets reported w/the mouse buttons
on the ffdc devices, which I *think* I just got fixed today, but you
would have to try lirc cvs and/or building from my git tree to verify,
or wait for me to get an updated kernel build together.

> mouse/kbd toggle had no apparent effect).

They won't until there is an IR client (such as mythtv) attached to
lircd. Before that, it'll just stay in mouse mode, since if there's no
attached IR client, why run in IR mode?

> Within mythfrontend only the CH+/CH- keys seem to do anything, acting
> as up/down keys in the menus, couldn't dind any other keys that worked
> as enter/right/escape etc.

Got an appropriate lircd.conf and .lircrc in place?

> My hardware is an iMON LCD (15c2:ffdc) in a silverstone ML02 case, I
> have an older iMON VFD in an LC11 lurking somewhere.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 14, 2009, 8:31 PM

Post #15 of 37 (4018 views)
Permalink

Re: Call for iMON testing [In reply to]

On Tuesday 14 July 2009 22:11:33 Anthony Giggins wrote:
> > For your device, I believe you actually need the imonlcd2 lcdproc
> > driver, if you've got a 0.5.2 lcdproc build. For the 0.5.3 lcdproc
> > build, you need the imonlcd driver, with Protocol=1. (it was an
> > out-of-tree patch or two in 0.5.2, finally merged in 0.5.3).
> >
> > For my 15c2:0045 w/lcdproc 0.5.3, LCDd.conf contains:
> > ...
> > Driver=imonlcd
> > ...
> > [imonlcd]
> > Device=/dev/lcd0
> > Contrast=200
> > OnExit=2
> > Protocol=1
>
> Hmmmm my device is a VFD not an LCD are you sure its still imonlcd2? as
> its still not working....

Oh, hrm... You know, I'm not actually sure now...

> The wierd thing is I was constantly getting these errors before I added
> the modprobe options to modeprobe.conf "options lirc_imon display_type=1"
>
> lcd_write: invalid payload size: 32 (expecting 8)

I think the 0036 was mis-identified as an LCD for a while, but the
current driver properly identifies it as a VFD.

> Are there any packages for lcdproc 0.5.3 for Mythdora 10.21 around?

Not at the moment, but there could be...

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

chrisznews4 at rogers

Aug 28, 2009, 5:22 PM

Post #16 of 37 (3663 views)
Permalink

Re: Call for iMON testing [In reply to]

Jarod Wilson wrote:
>> I'm probably going to regret turning on delivery of mail from this list
>> again, but I'd like to reach out to as many iMON users as possible...
>>
>> I've done a *MASSIVE* overhaul of the lirc_imon driver over the past
>> week and a half, and would like people to test out the new code.
>
> ...which you can of course obtain from lirc cvs:
>
> http://lirc.org/cvs.html

Hi Jarod,

I finally got a chance to test this on KnoppMyth 5.5 with device:
Bus 003 Device 002: ID 15c2:0043 SoundGraph Inc.

I wanted to verify this ahead of mythtv 0.22 and LinHes 6 so we could
simplify the scripting.

This device used to create both lirc0 and lirc1 but now with the cvs
version it successfully merges them both on lirc0. Yippee! yes I know
this was intended.

It seems to work well for the tests I did. However I did notice that the
IR codes changed somewhat. For example, eliminating toggle bit on one
stream (so neither requires it) and returning 64bit values, for example:

On /dev/lirc1 I used to have:
PrevChapter 0x2B9115B7

I now get on /dev/lirc0:
PrevChapter 0x2B9115B700000201

On /dev/lirc0 I used to have:
1 0x200001E

I now have:
1 0x0200001E00000000

So I guess we will have to regenerate the lircd.conf (unless someone has
already done this).

Also note that I could not get lirc-0.8.6pre1 to compile on knoppmyth
however the cvs version compiles just fine. With pre1 I was getting the
following make failure:

make -f scripts/Makefile.build obj=/usr/src/lirc-0.8.6pre1/drivers/lirc_imon
gcc -m32
-Wp,-MD,/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/.lirc_imon.o.d
-nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.3.2/include
-D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -O2 -pipe -msoft-float -mregparm=3
-freg-struct-return -mpreferred-stack-boundary=2 -march=i586
-mtune=generic -ffreestanding -maccumulate-outgoing-args
-DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-Iinclude/asm-i386/mach-default -fomit-frame-pointer
-fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign
-DIRCTL_DEV_MAJOR=61 -DEXPORT_SYMTAB -DHAVE_CONFIG_H -I. -I. -I../..
-I/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/.
-I/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/
-I/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/../..
-I/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/../..
-I/lib/modules/2.6.23-chw-4/build//include/
-I/lib/modules/2.6.23-chw-4/build//drivers/media/video/ -DMODULE
-D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(lirc_imon)"
-D"KBUILD_MODNAME=KBUILD_STR(lirc_imon)" -c -o
/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/lirc_imon.o
/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/lirc_imon.c
/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/lirc_imon.c: In function
'imon_probe':
/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/lirc_imon.c:1810: error:
implicit declaration of function 'BIT_MASK'
/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/lirc_imon.c:1811: error:
implicit declaration of function 'BIT_WORD'
make[6]: *** [/usr/src/lirc-0.8.6pre1/drivers/lirc_imon/lirc_imon.o] Error 1
make[5]: *** [_module_/usr/src/lirc-0.8.6pre1/drivers/lirc_imon] Error 2
...snip...

Christian

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Aug 28, 2009, 8:12 PM

Post #17 of 37 (3655 views)
Permalink

Re: Call for iMON testing [In reply to]

On Friday 28 August 2009 20:22:28 Christian Szpilfogel wrote:
> Jarod Wilson wrote:
> >> I'm probably going to regret turning on delivery of mail from this list
> >> again, but I'd like to reach out to as many iMON users as possible...
> >>
> >> I've done a *MASSIVE* overhaul of the lirc_imon driver over the past
> >> week and a half, and would like people to test out the new code.
> >
> > ...which you can of course obtain from lirc cvs:
> >
> > http://lirc.org/cvs.html
>
> Hi Jarod,
>
> I finally got a chance to test this on KnoppMyth 5.5 with device:
> Bus 003 Device 002: ID 15c2:0043 SoundGraph Inc.

Can you verify exactly what device that is? I don't know if I've got
it marked 100% correct in the lirc_imon source... I have:

/* Antec Veris Multimedia Station Basic Internal */

> I wanted to verify this ahead of mythtv 0.22 and LinHes 6 so we could
> simplify the scripting.
>
> This device used to create both lirc0 and lirc1 but now with the cvs
> version it successfully merges them both on lirc0. Yippee! yes I know
> this was intended.

Indeed, that was one of the major reasons for the massive overhaul.

> It seems to work well for the tests I did. However I did notice that the
> IR codes changed somewhat. For example, eliminating toggle bit on one
> stream (so neither requires it) and returning 64bit values, for example:
>
> On /dev/lirc1 I used to have:
> PrevChapter 0x2B9115B7
>
> I now get on /dev/lirc0:
> PrevChapter 0x2B9115B700000201
>
> On /dev/lirc0 I used to have:
> 1 0x200001E
>
> I now have:
> 1 0x0200001E00000000

Yeah, using the full 64 bits is necessary for handling all the possible
codes on the newer devices.

> So I guess we will have to regenerate the lircd.conf (unless someone has
> already done this).

See lircd.conf.imon-antec-veris, it should actually work for any device
in the 0x0034 to 0x0046 range, antec-branded or soundgraph-branded. I
use this myself with both the iMON remote and my Harmony 880 now.

> Also note that I could not get lirc-0.8.6pre1 to compile on knoppmyth
> however the cvs version compiles just fine. With pre1 I was getting the
> following make failure:

Yeah, that was a targeted fix in cvs. lirc-0.8.6pre2 ought to be out
this weekend, fwiw.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

chrisznews4 at rogers

Aug 29, 2009, 8:22 AM

Post #18 of 37 (3620 views)
Permalink

Re: Call for iMON testing [In reply to]

Jarod Wilson wrote:
>> I finally got a chance to test this on KnoppMyth 5.5 with device:
>> Bus 003 Device 002: ID 15c2:0043 SoundGraph Inc.
>>
>
> Can you verify exactly what device that is? I don't know if I've got
> it marked 100% correct in the lirc_imon source... I have:
>
> /* Antec Veris Multimedia Station Basic Internal */
>
>
yes. That is exactly what it is. Incredible value given it sees all codes.

I'll also be testing it on my Antec Veris Black 430 which has an LCD. It
has ID:
Bus 004 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller

Can both of these now use either imon or mce rc-6?

>> It seems to work well for the tests I did. However I did notice that the
>> IR codes changed somewhat. For example, eliminating toggle bit on one
>> stream (so neither requires it) and returning 64bit values, for example:
>>
>> On /dev/lirc1 I used to have:
>> PrevChapter 0x2B9115B7
>>
>> I now get on /dev/lirc0:
>> PrevChapter 0x2B9115B700000201
>>
>> On /dev/lirc0 I used to have:
>> 1 0x200001E
>>
>> I now have:
>> 1 0x0200001E00000000
>>
>
> Yeah, using the full 64 bits is necessary for handling all the possible
> codes on the newer devices.
>
>
>> So I guess we will have to regenerate the lircd.conf (unless someone has
>> already done this).
>>
>
> See lircd.conf.imon-antec-veris, it should actually work for any device
> in the 0x0034 to 0x0046 range, antec-branded or soundgraph-branded. I
> use this myself with both the iMON remote and my Harmony 880 now.
>
>
I was concerned that the codes ended in different suffixes (000 vs 201)
as I hadn't noticed the mask before. But it works.

I only note a few missing codes. I can make the mods to the lircd.conf
and send it to you for inclusion if you wish. For reference, I am using
a Harmony remote with RM200 codes programmed in.
>> Also note that I could not get lirc-0.8.6pre1 to compile on knoppmyth
>> however the cvs version compiles just fine. With pre1 I was getting the
>> following make failure:
>>
>
> Yeah, that was a targeted fix in cvs. lirc-0.8.6pre2 ought to be out
> this weekend, fwiw.
>
>
Perfect, I will re-verify in pre2 as well and discuss picking up pre2
with the LinHes team.

jarod at wilsonet

Aug 29, 2009, 12:29 PM

Post #19 of 37 (3620 views)
Permalink

Re: Call for iMON testing [In reply to]

On Saturday 29 August 2009 11:22:55 Christian Szpilfogel wrote:
> Jarod Wilson wrote:
> >> I finally got a chance to test this on KnoppMyth 5.5 with device:
> >> Bus 003 Device 002: ID 15c2:0043 SoundGraph Inc.
> >>
> >
> > Can you verify exactly what device that is? I don't know if I've got
> > it marked 100% correct in the lirc_imon source... I have:
> >
> > /* Antec Veris Multimedia Station Basic Internal */
> >
> yes. That is exactly what it is. Incredible value given it sees all codes.

Excellent, thank you for the confirmation.

> I'll also be testing it on my Antec Veris Black 430 which has an LCD. It
> has ID:
> Bus 004 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
>
> Can both of these now use either imon or mce rc-6?

Only devices 0034 through 0046 support mce rc6. The ffdc devices do not.
At least, not under Linux. If they *do* support it, its enabled in a
different way than the newer devices, and would require someone doing
some investigation under Windows to figure out how to enable it... But
it may also be a hardware limitation, not sure.

> > See lircd.conf.imon-antec-veris, it should actually work for any device
> > in the 0x0034 to 0x0046 range, antec-branded or soundgraph-branded. I
> > use this myself with both the iMON remote and my Harmony 880 now.
> >
> I was concerned that the codes ended in different suffixes (000 vs 201)
> as I hadn't noticed the mask before. But it works.

These codes at the end actually specify (to some extent) what class of
button was pressed, and what receiver they came in on. For example, the
front-panel buttons typically have a different suffix than standard
remote button presses, and the mouse bits have yet another suffix. And
different receivers have different suffixes too, for some reason.

> I only note a few missing codes. I can make the mods to the lircd.conf
> and send it to you for inclusion if you wish. For reference, I am using
> a Harmony remote with RM200 codes programmed in

Odd. I've got an RM200 myself, and all the buttons work perfectly, as
do all the buttons on my Harmony 880, which is programmed via a config
found in Logitech's db by looking for Antec Veris, iirc...

But sure, hit me with any additions you've got, and I'll put them into
lirc cvs. Doesn't hurt to have more codes added.

> > Yeah, that was a targeted fix in cvs. lirc-0.8.6pre2 ought to be out
> > this weekend, fwiw.
> >
> Perfect, I will re-verify in pre2 as well and discuss picking up pre2
> with the LinHes team.

pre2 tarball was just posted a bit earlier today.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jyavenard at gmail

Aug 29, 2009, 4:03 PM

Post #20 of 37 (3599 views)
Permalink

Re: Call for iMON testing [In reply to]

Hi

>
> Odd. I've got an RM200 myself, and all the buttons work perfectly, as
> do all the buttons on my Harmony 880, which is programmed via a config
> found in Logitech's db by looking for Antec Veris, iirc...

I have a RM200, with an Antec Fusion Remote Black ... I use a Harmony
880 remote as well that got automatically programmed.

Using lirc 0.8.2 (the one that came with Jaunty, with extra patch for
working with the Antec).

When using the Harmony, when I press any buttons it only repeats a few
times (maybe a dozen times at best). This is quite annoying when
scrolling down a long list..

Do you get the same with your harmony 880?

I always assumed that the problem came from the logitech codes ; IIRC
I chose Antec Fusion Remote in their db.

Jean-Yves
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

chrisznews4 at rogers

Aug 29, 2009, 5:45 PM

Post #21 of 37 (3599 views)
Permalink

Re: Call for iMON testing [In reply to]

Jean-Yves Avenard wrote:
> I have a RM200, with an Antec Fusion Remote Black ... I use a Harmony
> 880 remote as well that got automatically programmed.
>
> Using lirc 0.8.2 (the one that came with Jaunty, with extra patch for
> working with the Antec).
>
> When using the Harmony, when I press any buttons it only repeats a few
> times (maybe a dozen times at best). This is quite annoying when
> scrolling down a long list..
>
> Do you get the same with your harmony 880?
>
> I always assumed that the problem came from the logitech codes ; IIRC
> I chose Antec Fusion Remote in their db.
I think this is the Harmony codes that are probably too long or set to
repeat. They could use some tidying up. I believe someone on the
knoppmyth boards was working with Logitech to tighten those up as a
general update.

I use both an 880 and an 890 (two different front ends). I do get
repeats but I am able to absorb them using the "repeat" command in
lircrc. The guy I mentioned on the knoppmyth board was using a 500
series Harmony and he was not able to absorb the extra IR commands.
Logtech techs worked with him on fixing that.

Now with Antec Fusion Black I thought that used the ffdc device only
which I believe is only a RC-6 receiver (not imon rm200).

Christian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

chrisznews4 at rogers

Aug 29, 2009, 5:56 PM

Post #22 of 37 (3598 views)
Permalink

Re: Call for iMON testing [In reply to]

Jarod Wilson wrote:
>
>> I only note a few missing codes. I can make the mods to the lircd.conf
>> and send it to you for inclusion if you wish. For reference, I am using
>> a Harmony remote with RM200 codes programmed in
>>
>
> Odd. I've got an RM200 myself, and all the buttons work perfectly, as
> do all the buttons on my Harmony 880, which is programmed via a config
> found in Logitech's db by looking for Antec Veris, iirc...
>
> But sure, hit me with any additions you've got, and I'll put them into
> lirc cvs. Doesn't hurt to have more codes added.
>
>
ok. I have two missing codes and one that does not work at all:

The following are missing but are codes that I can send from my harmony
890 and receive through your driver:
KEY_MENU 0x2ba385b700000201
## The above is very close to your KEY_MENU value and I noticed in other
web entries that both can show up (perhaps slightly different remotes)
KEY_DVD 0x29a295b700000201
## Note for KEY_DVD above, the Harmony's version of RM200 labels this
also as "Purple"

Oddly the following code for MouseKeyboard does not work. I don't even
receive the IR code with mode2. yet with the previous driver (0.8.5pre1)
this code worked fine. Your lircd.conf has the correct code that I use
in 0.8.5pre1 as well, it just never shows up. Strange.

Christian

jyavenard at gmail

Aug 29, 2009, 7:29 PM

Post #23 of 37 (3591 views)
Permalink

Re: Call for iMON testing [In reply to]

2009/8/30 Christian Szpilfogel <chrisznews4 [at] rogers>:

>
> Now with Antec Fusion Black I thought that used the ffdc device only which I
> believe is only a RC-6 receiver (not imon rm200).

My remote is definitely a RM200 remote ...

The imon device is Bus 003 Device 002: ID 15c2:0038 SoundGraph Inc.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Aug 29, 2009, 8:15 PM

Post #24 of 37 (3589 views)
Permalink

Re: Call for iMON testing [In reply to]

On Saturday 29 August 2009 19:03:22 Jean-Yves Avenard wrote:
> Hi
>
> >
> > Odd. I've got an RM200 myself, and all the buttons work perfectly, as
> > do all the buttons on my Harmony 880, which is programmed via a config
> > found in Logitech's db by looking for Antec Veris, iirc...
>
> I have a RM200, with an Antec Fusion Remote Black ... I use a Harmony
> 880 remote as well that got automatically programmed.
>
> Using lirc 0.8.2 (the one that came with Jaunty, with extra patch for
> working with the Antec).

That's an ancient version of lirc. A *ton* of stuff in the lirc_imon
driver has been improved post-0.8.5 (0.8.6pre2 was put out earlier
today, contains all of said improvements).

> When using the Harmony, when I press any buttons it only repeats a few
> times (maybe a dozen times at best). This is quite annoying when
> scrolling down a long list..
>
> Do you get the same with your harmony 880?

Hm, haven't noticed any such issue, but I don't have all that many
recordings on my system at the moment, so not a lot to scroll through.

> I always assumed that the problem came from the logitech codes ; IIRC
> I chose Antec Fusion Remote in their db.

I do see most keys repeating a lot more than they do w/the stock RM-200
remote, which is probably an issue w/the config that Logitech has in
their db, as Christian suggested, but its taken care of by having
relatively high 'repeat = x' entries in ~/.lircrc.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Aug 29, 2009, 8:16 PM

Post #25 of 37 (3589 views)
Permalink

Re: Call for iMON testing [In reply to]

On Saturday 29 August 2009 22:29:29 Jean-Yves Avenard wrote:
> 2009/8/30 Christian Szpilfogel <chrisznews4 [at] rogers>:
>
> >
> > Now with Antec Fusion Black I thought that used the ffdc device only which I
> > believe is only a RC-6 receiver (not imon rm200).

No, the ffdc, at least under linux, only supports the imon native
remotes, its only 0034 - 0046 devices that can do RC-6 as well.

> My remote is definitely a RM200 remote ...
>
> The imon device is Bus 003 Device 002: ID 15c2:0038 SoundGraph Inc.

Yeah, that's the newer iMON LCD. I have more or less the same thing,
just Antec-branded, with device ID 0045 instead.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads