Re: Adding PCTV80e support to linuxtv.
On Wed, 02 Nov 2011 23:10:23 +0100, Patrick Dickey pdickeyb...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/02/2011 01:44 PM, semiRocket wrote: On Wed, 26 Oct 2011 02:10:56 +0200, Patrick Dickey pdickeyb...@gmail.com wrote: Hello everyone, Since my repository isn't under the linuxtv.org banner, I'm not sure how to create an actual patch or pull request for the code. It needs some cleanup work, but essentially the code works (for the ATSC portion, but possibly not the QAM portion). The repository is located at https://github.com/patrickdickey52761/PCTV80e so I'd imagine that either git clone git://github.com/patrickdickey52761/PCTV80e or git remote add git://github.com/patrickdickey52761/PCTV80e will pull the code in for you (it's a public repository). If this doesn't work, I'm asking for assistance in getting the code into a repository that can be pulled in (or assistance in how to prepare a patch/pull request from my current repository). If this does work, then I'm asking for assistance in cleanup of the code--and specifics on what I need to do to clean up the code (breaking lines up into fewer than 80 columns, whitespace, etc). One thing to note is that I haven't removed the trailing whitespace from the drxj_map.h file, as it was an automatically generated file. I wasn't sure what implications could arise from altering the file. Thank you, and have a great day:) Patrick. Hi, I'm not a developer, but I have some basic understanding how v4l patching works. You don't have to have a repository online, you can simply submit patches from your local tree using git or hg or even diff tools. Patches should come from newer trees (preferably current development tree) so they could apply cleanly. Please read the following links and see if they could help: http://linuxtv.org/wiki/index.php/Developer_Section http://linuxtv.org/wiki/index.php/Development:_How_to_submit_patches Thanks for the reply. I've looked through most of the links on those pages, and am almost ready to send the patches. The main problem that I have is that even after rebasing my branch (per the instruction on the media_git.git page), when I do a format patch there are 350+ patches generated (all but the last 29 are from other submitters). So, I either have to wait for all of those other patches to be added to the master repository, or I need to figure out how to isolate my specific patches from the list (so I can send them). If you've got any suggestions on that, I'd greatly appreciate it. I'm more new to git than anything else--as most of my programming was in classes, and they don't teach this stuff there. Have a great day:) Patrick. Hello, don't know the answer, so I am adding list back. Maybe someone else would know how to synchronize your old tree against current development tree (except by manually cut/paste). -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Adding PCTV80e support to linuxtv.
On Wed, 26 Oct 2011 02:10:56 +0200, Patrick Dickey pdickeyb...@gmail.com wrote: Hello everyone, Since my repository isn't under the linuxtv.org banner, I'm not sure how to create an actual patch or pull request for the code. It needs some cleanup work, but essentially the code works (for the ATSC portion, but possibly not the QAM portion). The repository is located at https://github.com/patrickdickey52761/PCTV80e so I'd imagine that either git clone git://github.com/patrickdickey52761/PCTV80e or git remote add git://github.com/patrickdickey52761/PCTV80e will pull the code in for you (it's a public repository). If this doesn't work, I'm asking for assistance in getting the code into a repository that can be pulled in (or assistance in how to prepare a patch/pull request from my current repository). If this does work, then I'm asking for assistance in cleanup of the code--and specifics on what I need to do to clean up the code (breaking lines up into fewer than 80 columns, whitespace, etc). One thing to note is that I haven't removed the trailing whitespace from the drxj_map.h file, as it was an automatically generated file. I wasn't sure what implications could arise from altering the file. Thank you, and have a great day:) Patrick. Hi, I'm not a developer, but I have some basic understanding how v4l patching works. You don't have to have a repository online, you can simply submit patches from your local tree using git or hg or even diff tools. Patches should come from newer trees (preferably current development tree) so they could apply cleanly. Please read the following links and see if they could help: http://linuxtv.org/wiki/index.php/Developer_Section http://linuxtv.org/wiki/index.php/Development:_How_to_submit_patches -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: freeze/crash
On Sat, 15 Oct 2011 09:35:13 +0200, James bjloc...@lockie.ca wrote: On 10/14/11 17:53, semiRocket wrote: On Fri, 14 Oct 2011 20:38:46 +0200, James bjloc...@lockie.ca wrote: On 10/14/11 07:10, semiRocket wrote: On Fri, 14 Oct 2011 01:51:37 +0200, James bjloc...@lockie.ca wrote: It always crashes when I access the hardware but the place it crashes is random. Maybe you would want to pass those crash logs for debugging purposes What crash logs? The kernel locks up, is there a log somewhere? System log under /var/log/messages or command dmesg Also, if you keep your terminal window open crash should pop-up by itself so called kernel oops. For example see first post in the following link: http://stackoverflow.com/questions/316131/how-do-you-diagnose-a-kernel-oops There was no kernel oops, everything just froze. dmesg seems to clear when I reboot. Yes, log is regenerated with reboot. If everything just froze those pci slot swap seems like a good solution :) It sounds to me like some hardware problem (maybe dust preventing a good contact in slot). -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: freeze/crash
On Fri, 14 Oct 2011 01:51:37 +0200, James bjloc...@lockie.ca wrote: It always crashes when I access the hardware but the place it crashes is random. Maybe you would want to pass those crash logs for debugging purposes :) It's possible for developers to track from them where the crash occurs in driver. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: freeze/crash
On Fri, 14 Oct 2011 20:38:46 +0200, James bjloc...@lockie.ca wrote: On 10/14/11 07:10, semiRocket wrote: On Fri, 14 Oct 2011 01:51:37 +0200, James bjloc...@lockie.ca wrote: It always crashes when I access the hardware but the place it crashes is random. Maybe you would want to pass those crash logs for debugging purposes What crash logs? The kernel locks up, is there a log somewhere? System log under /var/log/messages or command dmesg Also, if you keep your terminal window open crash should pop-up by itself so called kernel oops. For example see first post in the following link: http://stackoverflow.com/questions/316131/how-do-you-diagnose-a-kernel-oops -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Compro Videomate T750F Vista digital+analog support
On Thu, 03 Jun 2010 16:04:07 +0200, Davor Emard davorem...@gmail.com wrote: 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; Thanx for testing it out, If it doesn't work, try this: saa_andorl(SAA7134_GPIO_GPMODE0 2, /* keep */ 0x8082c000, /* keep */ 0x8082c000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, /* keep */ 0x8082c000, /* modify */ 0x0080c000); modify only the indicated number, try 0, try 0x8082c000 and if you have time try all combinations of bits 0x8082c000 optionally set to 0 e.g. 0x8002c000, 0x8080c000, 0x80828000, 0x0080c000 etc... It is possible that you and I don't have same revision of the card and you need a slightly different initialization procedure. If you get something to work for your card then I can try it back at mine there's a changes that we get a common setup which works for both. OK, do I need to do cold boot or reboot anytime I try different gpio value? -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Compro Videomate T750F Vista digital+analog support
On Mon, 31 May 2010 09:52:14 +0200, Davor Emard davorem...@gmail.com wrote: 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) d. Hi, 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. input-events is reporting ??? for all KEY_NUMERIC_*. Perhaps you could use KEY_PREVIOUS and KEY_NEXT instead of KEY_PREVIOUSSONG and KEY_NEXTSONG. For the naming you could use K100 http://www.comprousa.com/en/pctv_remote.php Lirc has definitions for K300 and it seems that it's using totally different codes: http://lirc.sourceforge.net/remotes/compro/VideoMate-K300 So I think too this would be a better naming sheme. Regards, Samuel -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Compro Videomate T750F Vista digital+analog support
On Mon, 10 May 2010 01:15:35 +0200, Emard davorem...@gmail.com wrote: HI This is even more cleanup from spaces into tabs and replacing KEY_BACKSPACE with KEY_BACK which I think is more appropriate for this remote. compro t750f patch v17 About the remote - I noticed 2-10% of the keypresses are not recognized, seems like it either looses packets or saa7134 gpio should be scanned faster/better/more_reliable? I think this may be the issue with other 7134 based remotes too Best Regards, Emard Hi Davor, Unfortunately it doesn't work for me. It can't load firmware like before, I've attached patch against recent hg tree I applied manually (without IR code part) and dmesg output. In tvtime it shows black screen in PAL mode, if switch to SECAM, it's still black screen but with some random flickering occurring represented by horizontal red/green lines. No white/black dots noise present. Thanks, Samuel -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
On Wed, 09 Sep 2009 10:31:46 +0200, Morvan Le Meut mlem...@gmail.com wrote: Morvan Le Meut a écrit : i can use the remote now ( using devinput in lirc ) but a few quirks remains : - dmesg gives a lot of saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=1 - in irw most keys are misidentified ( Power as RECORD, Mute as Menu, Down as DVD and DVD is correctly identified ) i guess using ir_codes_adstech_dvb_t_pci was not such a bright idea after all :p ( i included a full dmesg output ) For now, it is enough work on my part, i'll try to correct those keycodes later. It is amazing what you can do even when you don't understand most of it :D . Working on it, but i don't think everything is correct : some totaly unrelated keys have the same keycode. For example Jump and Volume+ or Search and Volume-. Beside, i keep getting Sep 9 10:17:16 debian kernel: [ 2029.892014] saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=0 Sep 9 10:17:16 debian kernel: [ 2029.944029] saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=1 for each recognized keypress I'll need a lot of help there : i don't know what to do. I think that correct gpio mask in saa7134-input.c would give unique keycodes for every keypress. It's most likely that you need to invent new gpio mask, but I'm not sure about this: (http://linuxtv.org/wiki/index.php/Remote_controllers-V4L#How_to_add_remote_control_support_to_a_card_.28GPIO_remotes.29) I'm sorry that I can't help you any further, it's getting far beyond my knowledge. I'm leaving this to somebody else... -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC] Infrared Keycode standardization
On Thu, 27 Aug 2009 19:06:13 +0200, Peter Brouwer pb.mailli...@googlemail.com wrote: After years of analyzing the existing code and receiving/merging patches related to IR, and taking a looking at the current scenario, it is clear to me that something need to be done, in order to have some standard way to map and to give precise key meanings for each used media keycode found on include/linux/input.h. snip Hi all, Some end user thoughts, perhaps unwelcome but here it goes :) I think that standardization of buttons is really needed that application programmers can relly on, for example I see this like following: I think that specific MCE compatible buttons need to be implemented that are specific on most todays remotes. And I imagine a Linux Media Center that works out-of-the-box. I plug in my Linux supported card, point my remote and press Media center button which runs media center application. Because it's standard and that's applications programers implemeted it as key that triggers their app. If press Videos button on my remote, the app switches to videos directory, because it's standard, and most remotes have it, etc. http://www.spinics.net/lists/linux-media/msg07705.html And thinking of that, I have configuring nothing, it's already configured because of standardization of buttons. And, if some advanced user doesn't like this behavior, he can always tamper configuration files to suite his need. Forgive me if I'm missing something, as I don't know how it all works together, but I think you've figured out the point of the meaning :). I also welcome this effort. Cheers, Samuel -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
