Pavilion IR Remote and "inet" keys under linux

[Paul Webster_2]

I have a Pavilion ZD8004AP that has volume control, DVD and "Music" buttons in addition to the keyboard, and that also came with a PC-Card sized IR Remote.

I discovered that the Remote actually sends keyscans through the kernels atkbd module, and after doing some probing with xev, I've determined keyscan codes for all the keys except the DVD and "Music" buttons on both the remote, and the laptop. To be precise, these buttons do not seem to generate events under Linux.

I found resources elsewhere (a sourceforge project called oke) for the Omnibook series to enable such additional buttons, and in blind hope that they would do something, gave them a try, but to no avail.

Is there any advice available, firstly, on how to get these keys activated, and secondly, how to add support for the scancodes of the new keys - some are recognised as 2 consecutive button press and releases (ie press-1 release-1 press-2 release-2)

Thanks

Paul

[Steven E. Protter]

Linux might not support that hardware.

Pavillions are well know for being unix unfriendly in some small and large ways.

I have no idea how to accomplish what you wish short of writing and compiling your own hardware driver and building a new kernel.

SEP

[Paul Webster_2]

Hi Steven

>Linux might not support that hardware.
>
>Pavillions are well know for being unix >unfriendly in some small and large ways.

My linux experience with this one has been relatively painless. Wireless LAN worked no problems with ndiswrapper, Bluetooth is working with the latest Bluez release and the "Bonus Digital TV Tuner" the laptop was bundled with proved easy to get going. I'm only ironing out the last few niggling issues now: the afore mentioned media buttons, the bluetooth MAC address (bluetooth works, but the device's MAC isn't read by the tools), and the 5-in-1 card reader (searching for a datasheet for the ENE CB710 interface it uses to write my own).

>I have no idea how to accomplish what you >wish short of writing and compiling your own >hardware driver and building a new kernel.

No fear in that area. I'm running a Linux From Scratch. Amongst other things, the kernel has most definatly been hand-rolled.

I guess what I'm looking for is any advice/experiences in getting started with writing my own driver. I'm already researching how to create my own keymap to recognise the unrecognised single-press key scancodes.

[David Asgeirsson]

Hi,

The best advice I can give on writing your own Linux device driver is to get the O'Reilly book
http://www.oreilly.com/catalog/linuxdrive2/

Our lab used it to create some device drivers. As usual for O'Reilly, it is very thorough.

- Dave Asgeirsson

[Paul Webster_2]

Hi,

Thanks for the suggestion. I'm one step ahead of you tho - 2 weeks into a 3 week lead time on the above mentioned book :)

Correction to my second post: the sourceforge project was called "omke"