public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Will <nico@youplala.net>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [patch] support for key repeat with dib0700 ir	receiver
Date: Fri, 22 Feb 2008 11:07:07 +0000	[thread overview]
Message-ID: <1203678427.6708.5.camel@acropora> (raw)
In-Reply-To: <950c7d180802220256q71556eaahf17816d5e9e2f3d4@mail.gmail.com>


On Fri, 2008-02-22 at 19:56 +0900, Matthew Vermeulen wrote:
> Hi all,
> 
> My remote seems to be totally working now, I've played around with the
> keymaps to set it all up nicely :)
> 
> Thanks so much to everyone who helped out..

Happy to hear that.


> 
> May end up posting some sort of howto to help any other users with my
> remote stuck in the same boat (although it doesn't seem to be a
> particularly common piece of hardware)

This would be good.

I really would like to understand the process properly.

Could you write something either directly in the wiki, or send it to me
by email, and I'll post it in the wiki.

Thanks much,

Nico


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-02-22 11:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.77.1203547335.926.linux-dvb@linuxtv.org>
2008-02-21  9:54 ` [linux-dvb] [patch] support for key repeat with dib0700 ir receiver Eduard Huguet
2008-02-21 15:42   ` Filippo Argiolas
2008-02-22 10:56     ` Matthew Vermeulen
2008-02-22 11:07       ` Nicolas Will [this message]
2008-02-19 16:33 Eduard Huguet
2008-02-19 16:49 ` Filippo Argiolas
2008-02-19 17:07   ` Eduard Huguet
  -- strict thread matches above, loose matches on Subject: below --
2008-02-19 15:17 Filippo Argiolas
2008-02-19 17:21 ` Nicolas Will
2008-02-19 17:30   ` Filippo Argiolas
2008-02-19 19:19   ` Nicolas Will
2008-02-19 19:30     ` Nicolas Will
2008-02-19 21:10       ` Matthew Vermeulen
2008-02-19 22:09         ` Nicolas Will
2008-02-20  7:39           ` Matthew Vermeulen
2008-02-20  7:54             ` Nicolas Will
2008-02-20 13:10               ` Matthew Vermeulen
2008-02-20  8:22         ` Filippo Argiolas
2008-02-20  8:27           ` Filippo Argiolas
2008-02-20 12:36             ` Matthew Vermeulen
2008-02-20 13:23               ` Nicolas Will
2008-02-20 13:43                 ` Matthew Vermeulen
2008-02-20 14:15                   ` Filippo Argiolas
     [not found]                     ` <1203517472.6682.37.camel@acropora>
2008-02-20 20:09                       ` Patrik Hansson
2008-02-20 22:57                     ` Matthew Vermeulen
2008-02-20 23:08                       ` Matthew Vermeulen
2008-02-20  8:22     ` Filippo Argiolas
2008-02-19 21:14 ` Patrick Boettcher
2008-02-19 21:41   ` Jonas Anden
2008-02-19 22:16     ` Nicolas Will
2008-02-19 22:29       ` Patrick Boettcher
2008-02-19 22:50         ` hermann pitton
2008-02-19 22:52         ` Nicolas Will
2008-02-20  9:00         ` Jonas Anden
2008-02-20  2:05   ` Darren Salt
2008-02-20  9:27   ` Filippo Argiolas
2008-02-20  9:39     ` Nicolas Will
2008-02-20 10:06       ` Filippo Argiolas
2008-03-02 19:45     ` Filippo Argiolas
2008-03-10 22:17       ` Nicolas Will
2008-02-27 11:04 ` Nicolas Will

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=1203678427.6708.5.camel@acropora \
    --to=nico@youplala.net \
    --cc=linux-dvb@linuxtv.org \
    /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