From: "Samuel Rakitničan" <samuel.rakitnican@gmail.com>
To: semiRocket <semirocket@gmail.com>, "Davor Emard" <davoremard@gmail.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Compro Videomate T750F Vista digital+analog support
Date: Thu, 03 Jun 2010 00:50:45 +0200 [thread overview]
Message-ID: <op.vdo22vmundeod6@crni> (raw)
In-Reply-To: <20100602182757.GA22171@emard.lan>
On Wed, 02 Jun 2010 20:27:59 +0200, Davor Emard <davoremard@gmail.com>
wrote:
> HI!
>
> Have you tested my lastest GPIO suggestion, or come up
> with your own initialization? Does it allow
> to load firmware without windows booting?
>
Didn't have time to look for gpios, tomorrow I will have. But I can tell
that this change is not working for me:
case SAA7134_BOARD_VIDEOMATE_T750:
dev->has_remote = SAA7134_REMOTE_GPIO;
saa_andorl(SAA7134_GPIO_GPMODE0 >> 2, 0x8082c000, 0x8082c000);
saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x8082c000, 0x0080c000);
break;
> Key namings of the remote must be some from linux input.h
> I welcome you to change whatever is needed to fit any of your
> application if current scheme is not suitable. I use VDR whcih
> can adapt to just anything event layer gives.
>
> d.
OK, I'm not having any personal opinion about the keys nor a application
which I'm using, I'm just noticed that the keys differ against standard
keys defined at linuxtv wiki. But if the keys at wiki are not correct,
then perhaps should we change them there and let all use the same keys.
If we have standard keys, than userspace applications programmers can make
a use of it and assign the keys to their applications and to have just
work experience to their users. But maybe I'm terrible wrong...
Best regards,
Samuel
next prev parent reply other threads:[~2010-06-02 22:50 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
2010-06-02 18:27 ` Davor Emard
2010-06-02 22:50 ` Samuel Rakitničan [this message]
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=op.vdo22vmundeod6@crni \
--to=samuel.rakitnican@gmail.com \
--cc=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