From: Bogdan K. <li...@in...> - 2008-12-21 00:43:23
|
Hello! I have remote with USB receiver from COMPRO. His name is Videomate K100 and is 0x185b:0x3020 After modification lirc_mce_usb2.c with adding lines: In line 138: #define VENDOR_COMPRO 0x185b In line 204: /* COMPRO K100 */ { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, All works fine. Can anybody add this device to official source code? Best regards ===================== Bogdan Klaczkiewicz |
From: Bogdan K. <b.k...@sr...> - 2008-12-20 20:48:02
|
Hello! I have remote with USB receiver from COMPRO. His name is Videomate K100 and is 0x185b:0x3020 After modification lirc_mce_usb2.c with adding lines: In line 138: #define VENDOR_COMPRO 0x185b In line 204: /* COMPRO K100 */ { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, All works fine. Can anybody add this device to official source code? Best regards ===================== Bogdan Klaczkiewicz |
From: Jarod W. <ja...@wi...> - 2008-12-21 02:42:13
|
On Sun, 2008-12-21 at 01:23 +0100, Bogdan Klaczkiewicz wrote: > Hello! > I have remote with USB receiver from COMPRO. > His name is Videomate K100 and is 0x185b:0x3020 > After modification lirc_mce_usb2.c with adding lines: > In line 138: > #define VENDOR_COMPRO 0x185b > > In line 204: > /* COMPRO K100 */ > { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, > > All works fine. > Can anybody add this device to official source code? Done. --jarod |
From: Emile <emi...@gm...> - 2009-06-20 13:00:16
|
> > On Sun, 2008-12-21 at 01:23 +0100, Bogdan Klaczkiewicz wrote: > > Hello! > > I have remote with USB receiver from COMPRO. > > His name is Videomate K100 and is 0x185b:0x3020 > > After modification lirc_mce_usb2.c with adding lines: > > In line 138: > > #define VENDOR_COMPRO 0x185b > > > > In line 204: > > /* COMPRO K100 */ > > { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, > > > > All works fine. > > Can anybody add this device to official source code? > > Done. > > --jarod > > ------------------------------------------------------------------------------ > > Hi Jarod! I have been struggling with this particular remote as well and I noticed that it's showing up in lsusb as follows: Bus 001 Device 003: ID 185b:3082 Compro I added another line. /* Compro K100 */ { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, { USB_DEVICE(VENDOR_COMPRO, 0x3085) }, Once compiled up, it was detected. Jarod Wilson <jarod@...> writes: |
From: Jarod W. <ja...@wi...> - 2009-06-20 15:37:54
|
On 06/20/2009 08:58 AM, Emile wrote: > >> On Sun, 2008-12-21 at 01:23 +0100, Bogdan Klaczkiewicz wrote: >>> Hello! >>> I have remote with USB receiver from COMPRO. >>> His name is Videomate K100 and is 0x185b:0x3020 >>> After modification lirc_mce_usb2.c with adding lines: >>> In line 138: >>> #define VENDOR_COMPRO 0x185b >>> >>> In line 204: >>> /* COMPRO K100 */ >>> { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, >>> >>> All works fine. ... > I have been struggling with this particular remote as well and I noticed that > it's showing up in lsusb as follows: > > Bus 001 Device 003: ID 185b:3082 Compro > > I added another line. > /* Compro K100 */ > { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, > { USB_DEVICE(VENDOR_COMPRO, 0x3085) }, > > Once compiled up, it was detected. I can throw that into cvs once you confirm what the device ID really is... First you said 3082, then you said 3085... --jarod |
From: eddy_crim <edd...@ho...> - 2009-06-21 22:09:23
|
Jarod Wilson wrote: > > On 06/20/2009 08:58 AM, Emile wrote: >> >>> On Sun, 2008-12-21 at 01:23 +0100, Bogdan Klaczkiewicz wrote: >>>> Hello! >>>> I have remote with USB receiver from COMPRO. >>>> His name is Videomate K100 and is 0x185b:0x3020 >>>> After modification lirc_mce_usb2.c with adding lines: >>>> In line 138: >>>> #define VENDOR_COMPRO 0x185b >>>> >>>> In line 204: >>>> /* COMPRO K100 */ >>>> { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, >>>> >>>> All works fine. > ... >> I have been struggling with this particular remote as well and I noticed >> that >> it's showing up in lsusb as follows: >> >> Bus 001 Device 003: ID 185b:3082 Compro >> >> I added another line. >> /* Compro K100 */ >> { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, >> { USB_DEVICE(VENDOR_COMPRO, 0x3085) }, >> >> Once compiled up, it was detected. > > I can throw that into cvs once you confirm what the device ID really > is... First you said 3082, then you said 3085... > > --jarod > > > > Hi i can confirm its 3082. I have one of these ..... that said i can't get > it to work... but i'm probably a bit of a newb. Ive tried adding the lines > above to the lirc 0.8.4a which i grabbed from the ubuntu repos but no luck > (cant see anything in cat /proc/bus/input/devices - i think i should i be > able to?) > > Im going to have a go at building from CVS. ill let you know. > > > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge > conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: > $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > > -- View this message in context: http://www.nabble.com/New-MCE-Remote-from-COMPRO---K100-tp21110917p24139321.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Jarod W. <ja...@wi...> - 2009-06-22 14:46:30
|
On Jun 21, 2009, at 2:18 PM, Emile van der Merwe wrote: > My humble apologies, Jarod! That was a typo!! No problem, it happens... :) > It's 3082. Okay, its been added to cvs. > I see I'm not the only one to have found that. Check this out: > http://ubuntuforums.org/showthread.php?t=1162753 Ugh. Would be nice if when such people found that out they would actually let us know here... > On Sat, Jun 20, 2009 at 5:36 PM, Jarod Wilson <ja...@wi...> > wrote: > On 06/20/2009 08:58 AM, Emile wrote: > > On Sun, 2008-12-21 at 01:23 +0100, Bogdan Klaczkiewicz wrote: > Hello! > I have remote with USB receiver from COMPRO. > His name is Videomate K100 and is 0x185b:0x3020 > After modification lirc_mce_usb2.c with adding lines: > In line 138: > #define VENDOR_COMPRO 0x185b > > In line 204: > /* COMPRO K100 */ > { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, > > All works fine. > ... > I have been struggling with this particular remote as well and I > noticed that > it's showing up in lsusb as follows: > > Bus 001 Device 003: ID 185b:3082 Compro > > I added another line. > /* Compro K100 */ > { USB_DEVICE(VENDOR_COMPRO, 0x3020) }, > { USB_DEVICE(VENDOR_COMPRO, 0x3085) }, > > Once compiled up, it was detected. > > I can throw that into cvs once you confirm what the device ID really > is... First you said 3082, then you said 3085... > > --jarod > > > -- Jarod Wilson ja...@wi... |
From: eddy_crim <edd...@ho...> - 2009-06-23 21:32:04
|
Hi guys im really struggling geting this compro remote going. I think i must be missing something. Any pointers would be greatly appreciated. Im on a plain ubuntu jaunty 9.0.4 setup so lsusb | grep Compro returns Bus 001 Device 002: ID 185b:3082 Compro I check out the latest cvs from LIRC i open ~/lirc/drivers/lirc_mceusb2/lirc_mceusb2.c and i can see that the device listed in the file i run ./lirc/autogen.sh -runs without error I run ./lirc/setup.sh - select option 1->8(usb device) ->x (MCE new version) in option 2 (software config) i leave the defaults save and run configure make ( lots happens here but i dont see any errors) sudo make install seems to install fine sudo rmmod lirc_mceusb2 sudo modprobe lirc_mceusb2 /var/log/messages gives me Jun 23 22:07:44 ed-media kernel: [ 2155.660313] usbcore: deregistering interface driver lirc_mceusb2 Jun 23 22:08:25 ed-media kernel: [ 2197.122890] Jun 23 22:08:25 ed-media kernel: [ 2197.122895] lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.51 $ Jun 23 22:08:25 ed-media kernel: [ 2197.122899] lirc_mceusb2: Daniel Melander <li...@ra...>, Martin Blatter <mar...@ya...> Jun 23 22:08:25 ed-media kernel: [ 2197.126473] usbcore: registered new interface driver lirc_mceusb2 then i sudo /etc/init.d/lirc restart if i do a mode2 -d /dev/licr0 i get nothing im afraid am i missing something obvious? -- View this message in context: http://www.nabble.com/New-MCE-Remote-from-COMPRO---K100-tp21110917p24174828.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Jarod W. <ja...@wi...> - 2009-06-27 14:10:02
|
On Jun 23, 2009, at 5:32 PM, eddy_crim wrote: > > Hi guys im really struggling geting this compro remote going. I > think i must > be missing something. Any pointers would be greatly appreciated. > > Im on a plain ubuntu jaunty 9.0.4 setup > > so > > lsusb | grep Compro > > returns > > Bus 001 Device 002: ID 185b:3082 Compro > > I check out the latest cvs from LIRC > > i open ~/lirc/drivers/lirc_mceusb2/lirc_mceusb2.c > > and i can see that the device listed in the file > > i run ./lirc/autogen.sh -runs without error > I run ./lirc/setup.sh - select option 1->8(usb device) ->x (MCE new > version) > in option 2 (software config) i leave the defaults > save and run configure > make ( lots happens here but i dont see any errors) > sudo make install seems to install fine > > sudo rmmod lirc_mceusb2 > sudo modprobe lirc_mceusb2 > > /var/log/messages gives me > > Jun 23 22:07:44 ed-media kernel: [ 2155.660313] usbcore: deregistering > interface driver lirc_mceusb2 > Jun 23 22:08:25 ed-media kernel: [ 2197.122890] > Jun 23 22:08:25 ed-media kernel: [ 2197.122895] lirc_mceusb2: > Philips eHome > USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for > LIRC > $Revision: 1.51 $ > Jun 23 22:08:25 ed-media kernel: [ 2197.122899] lirc_mceusb2: Daniel > Melander <li...@ra...>, Martin Blatter > <mar...@ya...> > Jun 23 22:08:25 ed-media kernel: [ 2197.126473] usbcore: registered > new > interface driver lirc_mceusb2 > > then i sudo /etc/init.d/lirc restart > > if i do a mode2 -d /dev/licr0 i get nothing im afraid > > am i missing something obvious? Yep. It looks like the lirc_mceusb2 that shipped with your distro is being loaded when you modprobe, instead of the one you built. There should be output along the lines of... lirc_mceusb2[2]: SMK CORPORATION MCE TRANCEIVR Emulator Device 2006 on usb5:2 ...in your log. (The above is from one of my own mceusb2 devices). If you look at the output of 'modinfo lirc_mceusb2', you should see an alias line for your device if you're loading the right module. If not, its gotta be the old one. After you installed the updated kernel module, did you run depmod? Worst-case, you might need to move the stock one out of the way entirely and run depmod again (or overwrite the original w/the new), but sane distros should be set up such that the path the hand-built module lands in overrides the shipped module. I tend to just drop hand- built kernel modules into /lib/modules/<kver>/extra/ myself, then run depmod, and be on my way. -- Jarod Wilson ja...@wi... |