[Mjpeg-users] capture card not working with nvidia driver
Hello everyone, My older machine with a cheap bttv capture card works well with nv module driving GFORCE 2 MX card. Framebuffer and tiny penguin at boot up shows, xawtv, glav, etc. works well for video capture and editing. Recently I installed the proprietary nvidia driver (92.43.23). I had to recompile the kernel (2.6.32.71) because the nvidia driver conflicted with the kernel's drm and framebuffer modules. OK, now I have the full capability of my 24" LCD display with the nvidia driver; AGP is fully functional and glxgears runs fast. However, video capture is not possible anymore: xawt screen is blue, but the setup screen lacks sections starting with video source. I can play existing video files, just capture capability is dead. So now I made my machine to dual boot with nv driver or nvidia; I also switch xorg.conf at boot via rc.local by sensing kernel version loaded. I'm writing to this forum with a hope that somebody has some idea how to make nvidia proprietary driver to work with video capture card. Maybe I should go to some nvidia forum, but I trust the expertise of those who follow mjpeg-users bulletin board. One more info: the sysrcd-5.0.0 with 4.9.24 kernel works on my machine; it loads the nouveau driver, screen resolution is identical with nvidia driver. I tried to compile 2.6.33.1 kernel from source (the first kernel that has the nouveau driver), but could not configure to include the nouveau module. I thought that with the nouveau module, instead of nvidia driver, capture would work again. Thanks for your attention - Janos ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] bringing back media/zoran driver
On Mon, Sep 23, 2019 at 10:05:09AM +0200, Hans Verkuil wrote: > On 9/21/19 7:03 PM, Corentin Labbe wrote: > > hello > > > > I am the owner of a zoran based DC10+ card. > > I am in the need of using it since yesterday and I found that its driver > > was removed. > > > > Reverting the removing patch made to a temporary working situation. > > > > If I understand correctly, it was removed due to lack of vb2 convertion. > > If I am able to do this vb2 conversion, does bring it back in mainline will > > be posssible ? > > In that case I am ready to assume to be the maintainer if needed. > > It would be nice to get it back. The conversion to vb2 is the main > requirement, but in > general this driver needed some TLC in general: it's a very old driver and > the coding > standards were quite a bit lower than they are today. > > But the vb2 conversion is the most important part. > > It's unfortunately not the easiest thing to do (if it was, we'd have done it > already!), > and it is also a 'big bang' patch, i.e. one very large patch that converts > the driver > to vb2. It's all or nothing, you can't have half a vb2 conversion, so that > makes it hard > to review. Hello Yes I started a bit to do it by using other conversion patch as helper and I saw this "one big step" problem. > > The easiest way is to use the v4l2-compliance utility to verify the > conversion. Running > 'v4l2-compliance -s' is a good way of verifying this. > > My recommended approach is to: > > 1) first revert the removal patch (commit 8dce4b265a53) > 2) clean up the coding style. Probably easiest to create one patch per source. >Use 'checkpatch.pl --strict -f ' for this. Doing this should make > the >source code easier to understand/review. > 3) Run v4l2-compliance (without the -s option) and fix any failures it finds. > 4) Convert to vb2, using 'v4l2-compliance -s' to test. > > Be aware that the code is messy compared to modern standards. Do not be afraid > to create cleanup patches, it's probably needed. > > The v4l2-compliance utility is part of https://git.linuxtv.org/v4l-utils.git/. > See the README on how to build. Always use the v4l2-compliance version from > this > git repo since that's always the latest and greatest. > > I recommend that you join the #v4l irc channel on freenode.org. Most core > devs that > can help with advice are there during office hours (and often outside of > office hours > as well). That's for the European timezones since most devs are based in > Europe. > Thanks, I has planned to ask this question about the priority between v4l2-compliance and vb2. Regards ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] bringing back media/zoran driver
On 9/21/19 7:03 PM, Corentin Labbe wrote: > hello > > I am the owner of a zoran based DC10+ card. > I am in the need of using it since yesterday and I found that its driver was > removed. > > Reverting the removing patch made to a temporary working situation. > > If I understand correctly, it was removed due to lack of vb2 convertion. > If I am able to do this vb2 conversion, does bring it back in mainline will > be posssible ? > In that case I am ready to assume to be the maintainer if needed. It would be nice to get it back. The conversion to vb2 is the main requirement, but in general this driver needed some TLC in general: it's a very old driver and the coding standards were quite a bit lower than they are today. But the vb2 conversion is the most important part. It's unfortunately not the easiest thing to do (if it was, we'd have done it already!), and it is also a 'big bang' patch, i.e. one very large patch that converts the driver to vb2. It's all or nothing, you can't have half a vb2 conversion, so that makes it hard to review. The easiest way is to use the v4l2-compliance utility to verify the conversion. Running 'v4l2-compliance -s' is a good way of verifying this. My recommended approach is to: 1) first revert the removal patch (commit 8dce4b265a53) 2) clean up the coding style. Probably easiest to create one patch per source. Use 'checkpatch.pl --strict -f ' for this. Doing this should make the source code easier to understand/review. 3) Run v4l2-compliance (without the -s option) and fix any failures it finds. 4) Convert to vb2, using 'v4l2-compliance -s' to test. Be aware that the code is messy compared to modern standards. Do not be afraid to create cleanup patches, it's probably needed. The v4l2-compliance utility is part of https://git.linuxtv.org/v4l-utils.git/. See the README on how to build. Always use the v4l2-compliance version from this git repo since that's always the latest and greatest. I recommend that you join the #v4l irc channel on freenode.org. Most core devs that can help with advice are there during office hours (and often outside of office hours as well). That's for the European timezones since most devs are based in Europe. Regards, Hans ___ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
