Linux Media Controller development
 help / color / mirror / Atom feed
From: Andy Walls <awalls@md.metrocast.net>
To: jgauthier@lastar.com
Cc: linux-media@vger.kernel.org
Subject: Re: zilog and IR
Date: Sat, 08 Jan 2011 10:19:37 -0500	[thread overview]
Message-ID: <1294499977.2443.106.camel@localhost> (raw)
In-Reply-To: <AANLkTi=yLo8A==TXLYN6g72RZVsk4ydQthf29=i=A36j@mail.gmail.com>

On Sat, 2011-01-08 at 10:44 -0500, Jason Gauthier wrote:
> Andy,
> 
>    Firstly, I apologize for reaching out to you directly.

The list could have answered this, so I adding the Cc:.

BTW, I normally ignore direct emails asking for free support, as the
N-to-1 free support problem is too costly for me personally.  The N-to-M
free support problem on the list is a little easier to bear, and is
consistent with Linux's community development model. 


>  I stumbled into your git tree, which looks like it does exactly what
> I want.

But it doesn't.  It's a bleeding edge tree of mine used to develop a
changeset.  Be warned that such trees come with no guarantees that at
any one moment in time it will compile and not damage your hardware.

I only subjected the changes to personal review, compilation check, and
inspection by others on the list.  That was sufficient for me for
software defect removal, since the change was a cut-and-paste from the
cx18 and ivtv modules and the code is not yet called by hdpvr anyway.


> I grabbed the source but, unfortunately, it is not compiling for me
> because one of the constants is not defined.
> 
> in hdprv_new_i2c_ir, the line:
>     init_data->type = RC_TYPE_RC5;

> I have not been able to find any traces of RC_TYPE_RC5 in my 2.6.37
> kernel source.
> Is this a #define that you've made specific to your git tree?

No:

http://git.linuxtv.org/media_tree.git?a=commit;h=e58462f45e39e01799d8b1ebab4816bd0ca68ddc

That media_tree.git repository is the bleeding edge tree recommended for
developers and advanced users wanting the latest drivers.

The alternate is the media_build.git repository when has ability to
build the modules with some not so old kernels.

Regards,
Andy


       reply	other threads:[~2011-01-08 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=yLo8A==TXLYN6g72RZVsk4ydQthf29=i=A36j@mail.gmail.com>
2011-01-08 15:19 ` Andy Walls [this message]
2011-01-08 20:34   ` zilog and IR Jason Gauthier

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=1294499977.2443.106.camel@localhost \
    --to=awalls@md.metrocast.net \
    --cc=jgauthier@lastar.com \
    --cc=linux-media@vger.kernel.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