linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davor Emard <davoremard@gmail.com>
To: semiRocket <semirocket@gmail.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Compro Videomate T750F Vista digital+analog support
Date: Wed, 2 Jun 2010 19:22:36 +0200	[thread overview]
Message-ID: <20100602172224.GA15872@emard.lan> (raw)
In-Reply-To: <op.vdn7g9nj3xmt7q@crni>

> >HI!
> >
> >I just went to compro website and have seen that *f cards
> >have some identical MCE-alike but also slightly different remotes,
> >so we have to invent some better names to distinguish between
> >them (compro itself might have some names for them)
> >
> Tested your new patch with Gerd's input-events utility. input-events
> is reporting wrong key (KEY_MIN_INTERESTING) for KEY_MUTE, not sure
> why.

HI! Is at least tuner (and loading of the firmware) working now without 
preinitialization with windows?

About remote keys:
My evtest in debian is outdated (probably also your input-events). 
Not only it doesn't support all KEY_*s but also for some existing keys it 
reports the wrong names (like KEY_MIN_INTERESTING). 

Try it with xev, at least MUTE should work correctly there (reports XF86AudioMute).
However KEY_NUMERIC_* won't be recognized by xev because X11 doesn't map
them to anything by default

However only the input layer keycodes matter, we can ignore it's name interpreted 
by some application (every app may name it different or even wrong...).

The tools should be compiled against latest /usr/include/linux/input.h
and have all new key names there (and corrected some existing names).

My intention was to map remote key pictograms to most appropriate
event in latest kernel's input.h, avoiding PC keyboard ambiguity as
much as I can.

Because in the kernel they have expanded input.h with a number of new keys to 
better cover MCE remotes and new media keyboards, so you get those ??? for
old apps but the keycode numbers should still be correct according to the 
kernel's input layer. input layer Applications map key events to the keycode 
numbers, and have freedom to give any name to the key.

The KEY_PREVIOUS and KEY_NEXT are actually keys for prev page and
next page on the keyboard, used for scrolling text. PREVIOUSSONG 
NEXTSIONG are used to skip to songs and are also expanded to skipping
to video DVD chapters, so I thought they are more appropriate for the
remote pictograms "|<" ">|" at VCR key group. I wanted to avoid ambiguity
between keyboard events and remote, however I still have KEY_ENTER
and KEY_BACKSPACE and the cursors, which is in ambiguity to the
normal keyboard - any idea what to replace them with in MCE style?

I have no issue of mapping all current keys to VDR. If you have any real issue of
mapping keys to some other TV view application or to the linux console or X11, 
feel free to change them and suggest a patch

d.

  reply	other threads:[~2010-06-02 17:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-08 16:06 [PATCH] Compro Videomate T750F Vista digital+analog support Emard
     [not found] ` <op.vceiu5q13xmt7q@crni>
     [not found]   ` <AANLkTinMYcgG6Ac73Vgdx8NMYocW8Net6_-dMC3yEflQ@mail.gmail.com>
     [not found]     ` <AANLkTikbpZ0LM5rK70abVuJS27j0lT7iZs12DrSKB9wI@mail.gmail.com>
     [not found]       ` <op.vcfoxwnq3xmt7q@crni>
     [not found]         ` <20100509173243.GA8227@z60m>
2010-05-09 18:35           ` Samuel Rakitničan
2010-05-09 18:48             ` Emard
2010-05-27 17:18               ` Mauro Carvalho Chehab
2010-05-28  6:48                 ` Davor Emard
2010-05-09 23:15             ` Emard
2010-05-16 10:38               ` semiRocket
2010-05-16 10:41                 ` Samuel Rakitničan
2010-05-23 17:40                 ` Samuel Rakitničan
2010-05-27 16:55                   ` Davor Emard
2010-05-27 17:15                   ` Davor Emard
2010-05-30 23:48                   ` Davor Emard
2010-05-31  0:27                     ` hermann pitton
2010-05-31  0:33                       ` hermann pitton
2010-05-31  1:07                         ` Davor Emard
2010-05-31  7:52                     ` Davor Emard
2010-06-02 11:28                       ` semiRocket
2010-06-02 17:22                         ` Davor Emard [this message]
2010-06-02 18:27                         ` Davor Emard
2010-06-02 22:50                           ` Samuel Rakitničan
2010-06-03 14:04                             ` Davor Emard
2010-06-03 17:17                               ` semiRocket
2010-06-03 17:15                           ` semiRocket
2010-05-31  1:21                   ` Davor Emard
2010-05-11 22:35 ` davor emard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100602172224.GA15872@emard.lan \
    --to=davoremard@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=semirocket@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).