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 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
