Attached to this bug report is a patch for pcmcia-cs. This new version adds support for the Margi DVD-to-Go card as described at http://www.linuxtv.org/developer/margi.xml . This ebuild code needs some help, though. This is my first contribution whatsoever to any OpenSource project and consequently an 'ebuild/compile' command produced alot of the following warnings, which I didn't see come out of the original 3.2.0.ebuild. In file included from ../include/linux/module.h:5, . . . ../include/linux/kernel.h:10: warning: `EXPORT_SYMTAB' redefined *Initialization*:1: warning: this is the location of the previous definition I've only ebuild/compiled it, but all modules (including the orinoco sources) that compiled under 3.2.0-r0 compiled (although with those strange warnings) under this patch. The USE margi construct works as intended, no margi cvs download if margi is not present; downloaded/compiled successfully if it is present. I'm sorry if the default settings for the diff command are not too your liking, but I'd be happy to fix that in the future. joeG
Created attachment 2854 [details, diff] Update for pcmcia-cs-3.2.0 Patch made with no extra options with the diff from diffutils 2.7.7
Created attachment 2888 [details, diff] 2nd round; this time a bit more complete patches agains the 3.2.0 ebuild Contains a pcmcia-wide file: margi-devfsd.conf the updated patch file: pcmcia-cs-3.2.0-update-bis.patch Adds support for the complete merge process. Would appreciate input concerning the /dev stuff and how to integrate that with Gentoo. This obsoletes the first patch (which for some reason I am unable to obsolete myself)
Created attachment 2889 [details, diff] 2nd round; this time a bit more complete patches agains the 3.2.0 ebuild Contains a pcmcia-wide file: margi-devfsd.conf the updated patch file: pcmcia-cs-3.2.0-update-bis.patch Adds support for the complete merge process. Would appreciate input concerning the /dev stuff and how to integrate that with Gentoo. This obsoletes the first patch (which for some reason I am unable to obsolete myself)
There are several problems with this approach which will lead me not to add this to the Portage tree. Firstly pcmcia-cs is a system critical package.. Adding unstable CVS code to it is something I will not do. Secondly the only way CVS items go into Portage is when they can be versioned such as snapshots. If I emerge this on Monday and there is a fix checked into CVS on Friday for a problem I am having. There is no way that we can or you can know if you have the fix or not. This is why there is versioning. If you would like to patch this in yourself that is perfectly fine. As far as being able to open and look at the 2nd patch... That is something I can't even do. It looks like a binary file.
