Quantcast

irrecord --list-namespace not working?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

irrecord --list-namespace not working?

Craig Treleaven
Hi:

I’ve been playing with the IguanaIR connected to my Mac.  The driver is now working after a fashion but I’ve noticed a minor issue with irrecord—listing the namespace doesn’t produce any output:

CT-MBP11:iguanair craigtreleaven$ head A1156.lircd.conf
# this config file was automatically generated
# using lirc-0.8.1(iguanaIR) on Fri Mar 30 19:20:40 2007
#
# contributed by Matthias Urlichs <matthias|urlichs.de>
#
# brand:                       Apple
# model no. of remote control: A1156
# devices being controlled by this remote: new (late 2006) MacBook
#
# This config files are for non-Apple receivers only.
CT-MBP11:iguanair craigtreleaven$ irrecord -l A1156.lircd.conf
CT-MBP11:iguanair craigtreleaven$ irrecord --list-namespace A1156.lircd.conf
CT-MBP11:iguanair craigtreleaven$

I’ve tried with several different remote configuration files with the same result.  I am able to update an existing file when ignoring the namespace.

Is this a known issue?  Something specific to my Mac build (missing dep, etc)?

Craig
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: irrecord --list-namespace not working?

Alec Leamas
Hi!

On 08/03/17 14:37, Craig Treleaven wrote:

> Hi:
>
> I’ve been playing with the IguanaIR connected to my Mac.  The driver is now working after a fashion but I’ve noticed a minor issue with irrecord—listing the namespace doesn’t produce any output:
>
> CT-MBP11:iguanair craigtreleaven$ head A1156.lircd.conf
> # this config file was automatically generated
> # using lirc-0.8.1(iguanaIR) on Fri Mar 30 19:20:40 2007
> #
> # contributed by Matthias Urlichs <matthias|urlichs.de>
> #
> # brand:                       Apple
> # model no. of remote control: A1156
> # devices being controlled by this remote: new (late 2006) MacBook
> #
> # This config files are for non-Apple receivers only.
> CT-MBP11:iguanair craigtreleaven$ irrecord -l A1156.lircd.conf
> CT-MBP11:iguanair craigtreleaven$ irrecord --list-namespace A1156.lircd.conf
> CT-MBP11:iguanair craigtreleaven$
>
> I’ve tried with several different remote configuration files with the same result.  I am able to update an existing file when ignoring the namespace.
>
> Is this a known issue?

No.

> Something specific to my Mac build (missing dep, etc)?

Most likely, yes. The build uses the linux header input.h to determine
the keycodes available. Obviously, this will fail on MacOS/FreeBSD

Diving into this, there are two reasons to used the standardized keycode
names:

- Synchronizing with the linux kernel, e. g. when using the devinput
driver or lircd-uinput tool.'
- Making the lircrc files independent of the actual driver/lircd.conf
file used.

While the first reason makes no sense on non-linux hosts the second is
still valid. So this needs to be fixed. What we could do could is
similar to lirc.h: bundle the linux kernel header and use it if there is
no system-wide copy available.

I would appreciate if you filed a bug on this.


Cheers!

--alec

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: irrecord --list-namespace not working?

Craig Treleaven
> On Mar 9, 2017, at 4:10 AM, Alec Leamas <[hidden email]> wrote:
> On 08/03/17 14:37, Craig Treleaven wrote:
>> I’ve been playing with the IguanaIR connected to my Mac.  The driver is now working after a fashion but I’ve noticed a minor issue with irrecord—listing the namespace doesn’t produce any output:
>>
>> CT-MBP11:iguanair craigtreleaven$ head A1156.lircd.conf
>> # this config file was automatically generated
>> # using lirc-0.8.1(iguanaIR) on Fri Mar 30 19:20:40 2007
>> #
>> # contributed by Matthias Urlichs <matthias|urlichs.de>
>> #
>> # brand:                       Apple
>> # model no. of remote control: A1156
>> # devices being controlled by this remote: new (late 2006) MacBook
>> #
>> # This config files are for non-Apple receivers only.
>> CT-MBP11:iguanair craigtreleaven$ irrecord -l A1156.lircd.conf
>> CT-MBP11:iguanair craigtreleaven$ irrecord --list-namespace A1156.lircd.conf
>> CT-MBP11:iguanair craigtreleaven$
>>
>> I’ve tried with several different remote configuration files with the same result.  I am able to update an existing file when ignoring the namespace.
>>
>> Is this a known issue?
>
> No.
>
>> Something specific to my Mac build (missing dep, etc)?
>
> Most likely, yes. The build uses the linux header input.h to determine
> the keycodes available. Obviously, this will fail on MacOS/FreeBSD
>
> Diving into this, there are two reasons to used the standardized keycode
> names:
>
> - Synchronizing with the linux kernel, e. g. when using the devinput
> driver or lircd-uinput tool.'
> - Making the lircrc files independent of the actual driver/lircd.conf
> file used.
>
> While the first reason makes no sense on non-linux hosts the second is
> still valid. So this needs to be fixed. What we could do could is
> similar to lirc.h: bundle the linux kernel header and use it if there is
> no system-wide copy available.
>
> I would appreciate if you filed a bug on this.

Done:

https://sourceforge.net/p/lirc/tickets/273/

Craig


------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
Loading...