Re: Question to module options of lirc_atiusb

[Paul M. <pa...@pi...>]

IIRC, the Aux data doesn't show up until after you press the next=20
button.  I'm not sure what the remote sends if it is already in that=20
mode.

Watch syslog (ie., tail -f /var/log/syslog) when you're pressing=20
buttons.

=2DPaul

On Thursday 24 March 2005 6:56 pm, Simon Sch=E4fer wrote:
> Here is the debug output you wanted:
> first i pressed Aux1 (00XX3f)
> then Play (00XX2c)
> then Aux2 (01XX3f)
> then Play (01XX2c)
> and so on Aux5 is the PC button.
> Now my problem again is there a posabillity to map the playbutton
> five times? couse irrecord only gave me one code for this
> (00000000022c0000 0? play /tmp/output.lirc)
>
> Mar 25 01:18:26 [kernel] lirc_atiusb[2]: data received 00 01 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:26 [kernel] lirc_atiusb[2]: data received 00 02 3f
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:26 [kernel] lirc_atiusb[2]: data received 00 00 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:40 [kernel] lirc_atiusb[2]: data received 00 01 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:40 [kernel] lirc_atiusb[2]: data received 00 02 2c
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:40 [kernel] lirc_atiusb[2]: data received 00 00 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:43 [kernel] lirc_atiusb[2]: data received 01 01 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:43 [kernel] lirc_atiusb[2]: data received 01 02 3f
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:43 [kernel] lirc_atiusb[2]: data received 01 00 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:45 [kernel] lirc_atiusb[2]: data received 01 01 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:45 [kernel] lirc_atiusb[2]: data received 01 02 2c
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:45 [kernel] lirc_atiusb[2]: data received 01 00 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:47 [kernel] lirc_atiusb[2]: data received 02 01 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:47 [kernel] lirc_atiusb[2]: data received 02 02 3f
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:47 [kernel] lirc_atiusb[2]: data received 02 00 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:48 [kernel] lirc_atiusb[2]: data received 02 01 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:48 [kernel] lirc_atiusb[2]: data received 02 02 2c
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:49 [kernel] lirc_atiusb[2]: data received 02 00 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:50 [kernel] lirc_atiusb[2]: data received 03 01 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:50 [kernel] lirc_atiusb[2]: data received 03 02 3f
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:50 [kernel] lirc_atiusb[2]: data received 03 00 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:51 [kernel] lirc_atiusb[2]: data received 03 01 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:51 [kernel] lirc_atiusb[2]: data received 03 02 2c
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:52 [kernel] lirc_atiusb[2]: data received 03 00 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:52 [kernel] lirc_atiusb[2]: data received 04 01 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:53 [kernel] lirc_atiusb[2]: data received 04 02 3f
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:53 [kernel] lirc_atiusb[2]: data received 04 00 3f
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:53 [kernel] lirc_atiusb[2]: data received 04 01 2c
> (ep=3D0x82 length=3D3)
> Mar 25 01:18:53 [kernel] lirc_atiusb[2]: data received 04 02 2c
> (ep=3D0x82 length=3D3)
>                 - Last output repeated twice -
> Mar 25 01:18:54 [kernel] lirc_atiusb[2]: data received 04 00 2c
> (ep=3D0x82 length=3D3)
>
> Paul Miller schrieb:
> >lirc_atiusb should already properly handle both endpoints.
> >
> >On Wednesday 23 March 2005 1:59 pm, Simon Sch=E4fer wrote:
> >>sorry for the bad english was a little late
> >>i mean i only got 46 keys to konfigure not 200 and somewhat
> >>
> >>i started a userspace driver my own (look for linremoted on sf to
> >>get my source) in the beginning of the last year (but stopped
> >> couse i saw that lirc was to supporting my remote in the 0.7
> >> release)so i have all the protokoll stuff you need (i hope) only
> >> problem it is in german *g* so i have to translate it.
> >>there are two interfaces
> >>Interface 0 has the entry point 0x81   (mouse)
> >>Interface 1 has the entry point 0x82   (keys)
> >>mouse EP:
> >>only basics couse i didn't know how to write a userspace
> >>mousedriver if you need more stuf in this way i will check it
> >> wich my usb tools
> >>
> >>
> >>key EP:
> >>basicly the three chars are seperated to:
> >>
> >>AU ST KE
> >>
> >>where
> >>AU is the Aux channel
> >>ST is the State
> >>KE is the keycode
> >>
> >>AU can be:
> >>00:     AUX 1
> >>01:     AUX 2
> >>02:     AUX 3
> >>03:     AUX 4
> >>04:     PC
> >>
> >>ST:
> >>00:       released
> >>01:       pressed (initial)
> >>02:       pressed (if you hold the button)
> >>
> >>KE:
> >>00:     0
> >>01:     1
> >>02:     2
> >>03:     3
> >>04:     4
> >>05:     5
> >>06:     6
> >>07:     7
> >>08:     8
> >>09:     9
> >>0c:     Shutdown
> >>0d:     Mute
> >>
> >>10:     Vol+
> >>11:     Vol-
> >>
> >>20:     Channel+
> >>21:     Channel-
> >>28:     forward
> >>29:     rewind
> >>2c:     Play
> >>
> >>30:     Pause
> >>31:     Stop
> >>37:     Record
> >>38:     DVD
> >>39:     TV
> >>3f:     mouse was touched
> >>
> >>54:     list (left of 0)
> >>58:     Cursor up
> >>59:     Cursor down
> >>5a:     Cursor left
> >>5b:     Cursor right
> >>5c:     OK (@ Cursor)
> >>
> >>78:     A
> >>79:     B
> >>7a:     C
> >>7b:     D
> >>7c:     E
> >>7d:     F
> >>
> >>82:     hook
> >>8e:     ATI - Button
> >>
> >>96:     Timer
> >>
> >>a9:     left Mousebutton
> >>aa:     right Mousebutton
> >>
> >>be:     ? (it a key labeled with the ?)
> >>
> >>d0:     hand - Button
> >>d5:     resize - Button
> >>
> >>f9:     i (information key)
> >>
> >>greetz Simon
> >>
> >>Paul Miller schrieb:
> >>>The RW-II does not emit codes for the auxiliary keys in the same
> >>>manner as it does for the other keys.  Instead, the auxiliary
> >>>keys, in a sense, change the channel, and thus changing the
> >>> codes to all the other keys.  By default, we ignore the channel
> >>> code such that all keys respond the same for all auxiliaries.=20
> >>> This choice greatly simplifies configuration files.  The
> >>>emit_modekeys=3D1 parameter tells the driver not to ignore these
> >>>channel codes.
> >>>
> >>>I don't know what you mean by only getting the keys once instead
> >>>of five times...?
> >>>
> >>>I don't have a RW-II and I haven't tested anything myself.  If
> >>> you post the debugging output (debug=3D1), I can further help
> >>> you.
> >>>
> >>>-Paul
> >>>
> >>>On Tuesday 22 March 2005 3:10 pm, Simon Sch=E4fer wrote:
> >>>>Hello together
> >>>>
> >>>>I just installed "lirc-0.7.1pre2" for my Ati Remote Wonder II
> >>>> and I got it to work. So far so good.
> >>>>But the main feature of the Aux Keys aren't working so I "only"
> >>>>got the keys once instead of five times.
> >>>>so I searched in the source of the module and found the option
> >>>>'emit_modekeys' and tried values 1 and 2 but both times it
> >>>> wasn't working. so I think I did something wrong and hope you
> >>>> can help me.
> >>>>
> >>>>What I've done:
> >>>>1) edited /etc/modules.conf and put this 'options lirc_atiusb
> >>>>emit_modekeys=3D1' in it.
> >>>>2) reloaded the modules: rmmod lirc_atiusb; rmmod lirc_dev;
> >>>>modprobe lirc_atiusb
> >>>>3) started lircd with: "/usr/local/sbin/lircd
> >>>> --device=3D/dev/lirc --output=3D/dev/lircd
> >>>> --pidfile=3D/var/run/lircd.pid --nodaemon" 4) used irrecord and
> >>>> switched the aux keys during the key reading
> >>>>
> >>>>after it I looked in the file and the same keys with different
> >>>>aux's had the same keycodes
> >>>>
> >>>>greetz
> >>>>Simon
> >>>>
> >>>>
> >>>>-------------------------------------------------------
> >>>>This SF.net email is sponsored by: 2005 Windows Mobile
> >>>>Application Contest Submit applications for Windows
> >>>>Mobile(tm)-based Pocket PCs or Smartphones for the chance to
> >>>> win $25,000 and application distribution. Enter today at
> >>>>http://ads.osdn.com/?ad_id=3D6882&alloc_id=3D15148&op=3Dclick
> >>>
> >>>-------------------------------------------------------
> >>>This SF.net email is sponsored by: 2005 Windows Mobile
> >>> Application Contest Submit applications for Windows
> >>> Mobile(tm)-based Pocket PCs or Smartphones for the chance to
> >>> win $25,000 and application distribution. Enter today at
> >>>http://ads.osdn.com/?ad_idh82&alloc_id=15148&op=3Dclick
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by Microsoft Mobile & Embedded
> >>DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about
> >>the latest Windows Embedded(r) & Windows Mobile(tm) platforms,
> >>applications & content.  Register by 3/29 & save $300
> >>http://ads.osdn.com/?ad_id=3D6883&alloc_id=3D15149&op=3Dclick
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by Microsoft Mobile & Embedded
> > DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about
> > the latest Windows Embedded(r) & Windows Mobile(tm) platforms,
> > applications & content.  Register by 3/29 & save $300
> > http://ads.osdn.com/?ad_idh83&alloc_id=15149&op=3Dclick
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users. Discover which products truly live up to the hype. Start
> reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick