[linux-dvb] Microtune mt2131 driver wanted badly.
Hello, everyone. I am now using a usb card with mt2131 as its tuner. I googled these info on website: "b/linux/drivers/media/dvb/frontends/mt2131.c | 642 +++ > b/linux/drivers/media/dvb/frontends/mt2131.h | 70..." But I just can not find mt2131.c and mt2131.h on linuxtv.org Could someone give me some advice? By the way, could someone tell me the difference between the mt2131 and mt2060? Thank you . ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem about my driver module rmmod.
Dear timecop: It is just nothing when I modprobe mymodule and modprobe -r mymodule BEFORE my hardware present. The bad things happen when I modprobe -r mymodule AFTER my haredware present. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
Am Donnerstag, den 12.07.2007, 00:37 +0200 schrieb Johannes Stezenbach: > On Thu, Jul 12, 2007 at 03:49:30AM +1000, Julian wrote: > > Since this disscussion is public... > > I'm going to put in my 2 cents. > > > > If you actually read his posts - Like alot of end users are. Its the flames > > and personal attacks that are coming from the group mentality here (im sure > > theres a wiki that can explain that too) > > Hm, Markus complains that the community doesn't work, and you're > complaining that it _does_ work -- or what do you mean by > "group mentality"? > [snip] I would be happy enough if Markus' would start telling, why he still keeps this tuner=37 stuff for his MK3s. --everyone knows that THIS DOESN'T work for UHF. Instead some tell you meanwhile, that MK3/4/5/6 tuners work with the old Philips API and you should accept their patches. No move since more than one year on that. So, others wait too. Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On Thu, Jul 12, 2007 at 03:49:30AM +1000, Julian wrote: > Since this disscussion is public... > I'm going to put in my 2 cents. > > If you actually read his posts - Like alot of end users are. Its the flames > and personal attacks that are coming from the group mentality here (im sure > theres a wiki that can explain that too) Hm, Markus complains that the community doesn't work, and you're complaining that it _does_ work -- or what do you mean by "group mentality"? > So if we are talking about changes to the core and how v4l and dvb devices > will work under linux in the future. He/they with the best solution will win > via non-bias peer review and hopefully *beyond* the linuxtv project. So if > Markus persists enough (he seems the only one consistently reworking what he > has already done - but everyone seems to skim past that in his posts...) he > will succeed. > > I admire anyone that makes an effort against the status quo that fails to > move > anywhere really, and spends more effect resisting any kind of change than > actually doing anything or offering an alternative. > > Just because he is outnumbered with support here means absolutely nothing. > May the best code win. Markus always portrays it that way, that there is a group of evil guys who block his code, who mislead him, who want to retain the status quo etc. pp. And now he is the lonely hero who stands up against the establishment... IMHO that is complete rubbish. There isn't even a formal group of "linuxtv core developers". I'm glad that Mauro agreed to merge the DVB and V4L trees into one, and to do the patch handling for the combined tree. And I'm glad Mike and Trent do a lot of patch review and bugfixing work, unseen and unrewarded my most people. Does that give them any authority to ACK and NACK patches as they see fit? Hell, no! But the community process works that way that if someone reviews a patch and has objections, then these objections must either be addressed or shown to be wrong. (Read Documentation/ManagementStyle in the kernel to see how it works ;-) In Markus case, serveral people who looked at his patches had objections, but he refused to address them, but was unable to either show the objections as being wrong, or get a _single_ other developer to back up his position. Instead there were threats to "fork the linuxtv project" if his code wouldn't get merged... The sad thing is that only a relatively small part of Markus' code has problems, and the bulk of it could have been merged without it, leaving out the xc3028 v4l/dvb arbitration functionality. But Markus didn't want this. Anyway, there are many patches which are rejected from the Linux kernel or have to go through significant transformations before they are allowed into the kernel. You should read the linux kernel mailing list for a while, maybe you'd then see that the entry level for patches into v4l/dvb is fairly low compared to the high standards required for core kernel code like scheduler, timekeeping, networking, VM, block IO layer etc. > >Your attempts to force the merge with flames and ultimatums > >(yes, plural) failed. Surprise, surprise... > > how soft do people get with their drivers that they see a patch submission - > as a flame? That's not what I said, I can tell a patch submission from a flame quite well, thanks. Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help needed with dst
Hi, I had the same problem for a long time. For me it helps to boot in windows (with vendor driver installed) and reboot in linux (not poweroff). That helped for a while. Now the PCI subsystem ids of the card are incorrect. People say this happens quite often. I have patched the drivers to ignore the subsystem ids for bt8.. drivers. You are better off buying other cards. Twinhan cards have a lot of problems: - not very stable - signal and quality are not reported correctly. - eeprom gets corrupted and subsystem id are wrong. I can go on ... Regards, Ilariu On 7/11/07, Joel Michael <[EMAIL PROTECTED]> wrote: Joel Michael wrote: > The machine I'm running the card on is a Core2 Duo (x86_64 mode), on an > Asus P5B-VM motherboard, running the Gentoo distribution. I've tried > with and without preempt, and am going to try without SMP tonight, and > maybe try it in 32-bit mode. I've also tried removing the pair of > FlexCopII's, with no success. > I've dug into the source a bit, and it seems that in drivers/media/video/bt8xx/bttv-i2c.c, I get an interrupt from the card without BT848_INT_RACK set, but BT848_INT_I2CDONE is set. If someone can shed a bit of light on why this might be happening, it would be greatly appreciated. Right now, I'm off to see if it works at all in 32-bit mode. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] common philosophy
Am Mittwoch, 11. Juli 2007 18:36:06 schrieb Markus Rechberger: > On 7/11/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote: > > On Wed, Jul 11, 2007 at 05:18:35PM +0200, Markus Rechberger wrote: > > > Remember all that code could have been in the kernel for around 1 year > > > without breaking any device if these few core people (and there are > > > really only very few ones <5) wouldn't have tried to hit it down. > > > > This "the bad linuxtv guys blocked my drivers for years" > > allegation is unsubstancial as I tried to show in > > http://www.linuxtv.org/pipermail/linux-dvb/2007-June/018853.html > > "A few people offered to help you" is the same as: > > A few people (especially the ones which are mentioned later) partly > don't have a good overview about everything, and/or neither do they > care about several requirements which are needed to get something work > properly. > And these cool people would just work on the core and tell me that I > have to redo the code by myself and put all the work back to me just > because they're incapable of working together at all ... and hey we > had exactly the same situation 1 year ago and the only one who > seriously tried to get forward was Mauro. A few people like to hide > themself between their great DVB Code and try to play the masters here > which is not acceptable. YES! :( Hey people reading that: I am only a user / administrator. I know that my statement may not be relevant at all. But I like to state my opinion on the real bullshit that has been going on here, hoping for personal consequences of whatever kind! > > How comes that Manu tells me that he won't ask Mauro that he should > push any of his code? Great community. Personal disagreements - Mauro is very well doing v4l, but hasn't the slightest idea about DVB as a matter of fact! In spite of that he is intending to play the fascistoid "Big Boss" (i. e. the biggest asshole that one ever can imagine) on the "common project" > > > IMHO it is your inability to make compromises and work with > > the community which blocked the merge. Issues don't just > > magically resolve all by themselves if you just wait long enough. > > Your attempts to force the merge with flames and ultimatums > > (yes, plural) failed. Surprise, surprise... Maybe YES! > > > I'm sure the project would go on way faster if everyone who has never > > > investigated the dvb core project and who has no experience with that > > > piece of code (and writing a dvb driver doesn't shed much light about > > > the dvb framework) would just stay out of everything. NO! There are users with certain expecting manners! > > > > You think you're the only competent programmer, and everyone > > who dares to have different opinions just gets in the > > way and holds you up? Check this out: > > http://en.wikipedia.org/wiki/Narcissistic_personality_disorder#Diagnostic > >_criteria Mister Johannes Stezenbach, programmers are like musicians - very narcistic and highly emotional. Now if you can't take that you've missed something during your secondary socialisation of whatever kind, man! > For example you (first trying to help, afterwards doing nothing), YES! Johannes is nothing but a so-called "apparatschnik", i. e. not helpful at all! Proof: his motherfuckin' "scan utility" which is highly suboptimal, if not to say: Rubbish! But instead of investigating time to improve that bullshit utility he preferes to play the big "guru" of GPL philosophy and others which is pretty energy-saving for him, but not for the rest of the linux community world! Johannes sucks! > * Manu Abraham (who has his project split from the maintree for a very > long time too), YES! Manu Abraham promised me a bttv-free driver for his "holy kingdom, if not to say dvb-bt8xx clone cards of TwinHan months ago, thus freezing the current kernel driver state of TwinHan and clones, and I did a whole of testing and feedback effort (even more that I should or was expected), and Markus, although flamed and ignored, sent me a dummy driver apt to resolve the problem in Manu's project called cx878 (i. e. the bttv-free bt8xx-driver) and the result of this lazybone who has lots of time to rant around on linuxtv-irc was and is this: a.) http://www.thadathil.net (i. e. NO motherfuckin' development at all for TWO MONTHS now! b.) http://www.just.de/manu (incomplete drivers) c.) consequent ignorance of Markus's input, transformed by me for the cx878 project > * Marcel Siegert (who listens to other people's opinion and didn't > even spend a minute on thinking by himself how to find a solution) YES! He seems to care for dvb-utils, but is nothing but an incapable opportunist doing nothing - another goddam opportunistic inacceptable lazybone - nad dvb-utils are bullshit, aren't they? > * Oliver Endriss, did some tests and afterwards denied the merge > because he found a bug which got resolved right after he reported it. YES! In the past this bavarian guy fucked up dvb-frontend.c, and it was me takin
Re: [linux-dvb] Help needed with dst
Hi, Please check whether any of these works * change PCI slot * try a cold boot (remove the power completely, just soft switching OFF might not help) If not probably the card doesn't work ? On 7/11/07, Joel Michael <[EMAIL PROTECTED]> wrote: > Joel Michael wrote: > > The machine I'm running the card on is a Core2 Duo (x86_64 mode), on an > > Asus P5B-VM motherboard, running the Gentoo distribution. I've tried > > with and without preempt, and am going to try without SMP tonight, and > > maybe try it in 32-bit mode. I've also tried removing the pair of > > FlexCopII's, with no success. > > > I've dug into the source a bit, and it seems that in > drivers/media/video/bt8xx/bttv-i2c.c, I get an interrupt from the card > without BT848_INT_RACK set, but BT848_INT_I2CDONE is set. If someone > can shed a bit of light on why this might be happening, it would be > greatly appreciated. > > Right now, I'm off to see if it works at all in 32-bit mode. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Skystar HD
Hello! I've got a problem with: SKYSTAR HD Athlon 64 X2 3800+ Ubuntu 7.04 (32bit kernel 2.6.20-16 generic) Sources - Manus snapshot at http://jusst.de/manu/stb0899-v4l-dvb.tar.bz2 - the szap-sources from http://dev.kewl.org/tmp/hvr4000/szap2.tgz method by laasa from Mon May 21 22:36:43 CEST 2007 after patching: > [EMAIL PROTECTED]:~/Desktop/tt3200/v2$ patch -p0 patching file v4l-dvb/linux/drivers/media/dvb/dvb-core/dvb_frontend.c > Hunk #1 FAILED at 460. > Hunk #2 FAILED at 1559. > Hunk #3 FAILED at 1720. > Hunk #4 FAILED at 1747. > Hunk #5 FAILED at 1903. > 5 out of 5 hunks FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/dvb-core/dvb_frontend.c.rej > patching file v4l-dvb/linux/drivers/media/dvb/frontends/lnbp21.c > Hunk #1 FAILED at 127. > 1 out of 1 hunk FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/frontends/lnbp21.c.rej > patching file v4l-dvb/linux/drivers/media/dvb/frontends/stb0899_algo.c > Hunk #1 FAILED at 519. > Hunk #2 FAILED at 597. > Hunk #3 FAILED at 672. > Hunk #4 FAILED at 688. > Hunk #5 FAILED at 742. > Hunk #6 FAILED at 1223. > Hunk #7 FAILED at 1369. > Hunk #8 FAILED at 1393. > Hunk #9 FAILED at 1454. > Hunk #10 FAILED at 1573. > 10 out of 10 hunks FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/frontends/stb0899_algo.c.rej > patching file v4l-dvb/linux/drivers/media/dvb/frontends/stb0899_drv.c > Hunk #2 FAILED at 2014. > 1 out of 2 hunks FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/frontends/stb0899_drv.c.rej > patching file v4l-dvb/linux/drivers/media/dvb/frontends/stb6100.c > Hunk #1 FAILED at 27. > Hunk #2 FAILED at 423. > Hunk #3 FAILED at 459. > Hunk #4 FAILED at 561. > 4 out of 4 hunks FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/frontends/stb6100.c.rej > patching file v4l-dvb/linux/drivers/media/dvb/ttpci/budget-ci.c > Hunk #2 succeeded at 1088 with fuzz 1. > Hunk #3 FAILED at 2004. > Hunk #4 succeeded at 2118 with fuzz 1. > Hunk #5 FAILED at 2127. > 2 out of 5 hunks FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/ttpci/budget-ci.c.rej > patching file v4l-dvb/linux/drivers/media/dvb/ttpci/budget.h > Hunk #1 FAILED at 108. > 1 out of 1 hunk FAILED -- saving rejects to file v4l-dvb/linux/drivers/media/dvb/ttpci/budget.h.rej > patching file v4l-dvb/v4l-scripts-make_myconfig.pl and after make: > (...) > CC [M] /home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/stb0899_algo.o > /home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/stb0899_algo.c: In function 'stb0899_check_tmg': > /home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/stb0899_algo.c:203: warning: overflow in implicit constant conversion > CC [M] /home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/tuner-core.o (...) > CC [M] /home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/budget-ci.o > /home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/budget-ci.c:2095: error: 'BUDGET_TT3200' undeclared here (not in a function) > make[3]: *** [/home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l/budget-ci.o] Error 1 > make[2]: *** [_module_/home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-16-generic' > make[1]: *** [default] Błąd 2 > make[1]: Opuszczenie katalogu `/home/gasiu/Desktop/tt3200/v2/v4l-dvb/v4l' > make: *** [all] Błąd 2 "błąd" = error ;-) Any ideas? (with previous patch "make" was without errors, but it doesn't work in my configuration) -- Pozdrawiam! Gasiu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
Since this disscussion is public... I'm going to put in my 2 cents. If you actually read his posts - Like alot of end users are. Its the flames and personal attacks that are coming from the group mentality here (im sure theres a wiki that can explain that too) So if we are talking about changes to the core and how v4l and dvb devices will work under linux in the future. He/they with the best solution will win via non-bias peer review and hopefully *beyond* the linuxtv project. So if Markus persists enough (he seems the only one consistently reworking what he has already done - but everyone seems to skim past that in his posts...) he will succeed. I admire anyone that makes an effort against the status quo that fails to move anywhere really, and spends more effect resisting any kind of change than actually doing anything or offering an alternative. Just because he is outnumbered with support here means absolutely nothing. May the best code win. >Your attempts to force the merge with flames and ultimatums >(yes, plural) failed. Surprise, surprise... how soft do people get with their drivers that they see a patch submission - as a flame? great fear patch bomb? it another year or so you might find that no patch will save you at all..no..its called a re-write then. The more you put it off, the worse its going to get. Time will tell. Trial and error is what its all about. remember . So Just try it. -Jules On Thu, 12 Jul 2007, Markus Rechberger wrote: > On 7/11/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote: > > On Wed, Jul 11, 2007 at 05:18:35PM +0200, Markus Rechberger wrote: > > > Remember all that code could have been in the kernel for around 1 year > > > without breaking any device if these few core people (and there are > > > really only very few ones <5) wouldn't have tried to hit it down. > > > > This "the bad linuxtv guys blocked my drivers for years" > > allegation is unsubstancial as I tried to show in > > http://www.linuxtv.org/pipermail/linux-dvb/2007-June/018853.html > > "A few people offered to help you" is the same as: > > A few people (especially the ones which are mentioned later) partly > don't have a good overview about everything, and/or neither do they > care about several requirements which are needed to get something work > properly. > And these cool people would just work on the core and tell me that I > have to redo the code by myself and put all the work back to me just > because they're incapable of working together at all ... and hey we > had exactly the same situation 1 year ago and the only one who > seriously tried to get forward was Mauro. A few people like to hide > themself between their great DVB Code and try to play the masters here > which is not acceptable. > > How comes that Manu tells me that he won't ask Mauro that he should > push any of his code? Great community. > > > IMHO it is your inability to make compromises and work with > > the community which blocked the merge. Issues don't just > > magically resolve all by themselves if you just wait long enough. > > Your attempts to force the merge with flames and ultimatums > > (yes, plural) failed. Surprise, surprise... > > > > > I'm sure the project would go on way faster if everyone who has never > > > investigated the dvb core project and who has no experience with that > > > piece of code (and writing a dvb driver doesn't shed much light about > > > the dvb framework) would just stay out of everything. > > > > You think you're the only competent programmer, and everyone > > who dares to have different opinions just gets in the > > way and holds you up? Check this out: > > http://en.wikipedia.org/wiki/Narcissistic_personality_disorder#Diagnostic > >_criteria > > For example you (first trying to help, afterwards doing nothing), > * Manu Abraham (who has his project split from the maintree for a very > long time too), > * Marcel Siegert (who listens to other people's opinion and didn't > even spend a minute on thinking by himself how to find a solution) > * Oliver Endris, did some tests and afterwards denied the merge > because he found a bug which got resolved right after he reported it. > > There were a few options, freeze the development of v4l-dvb merge in > that code and fix whatever someone thinks he has to fix; there are > many requirements covered within that code and all you guys did is to > ignore it and nothing else.. Manu came up with something and didn't > even talk to me about it if it would be ok with the work I've done and > guess what he didn't even cover all the requirements which are already > solved. > > Now, all the other developers are far away from such a misbehaviour. > > > > It's now about 14.000 lines of code, around 7000 inkernel lines, and I > > > haven't received _any_ participation request of any developer and all > > > you get if you ask people to join the project is that they are busy > > > with their work (which is ok) but then don't try to manipulate someone > > > el
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On 7/11/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote: > On Wed, Jul 11, 2007 at 05:18:35PM +0200, Markus Rechberger wrote: > > > > Remember all that code could have been in the kernel for around 1 year > > without breaking any device if these few core people (and there are > > really only very few ones <5) wouldn't have tried to hit it down. > > This "the bad linuxtv guys blocked my drivers for years" > allegation is unsubstancial as I tried to show in > http://www.linuxtv.org/pipermail/linux-dvb/2007-June/018853.html > "A few people offered to help you" is the same as: A few people (especially the ones which are mentioned later) partly don't have a good overview about everything, and/or neither do they care about several requirements which are needed to get something work properly. And these cool people would just work on the core and tell me that I have to redo the code by myself and put all the work back to me just because they're incapable of working together at all ... and hey we had exactly the same situation 1 year ago and the only one who seriously tried to get forward was Mauro. A few people like to hide themself between their great DVB Code and try to play the masters here which is not acceptable. How comes that Manu tells me that he won't ask Mauro that he should push any of his code? Great community. > IMHO it is your inability to make compromises and work with > the community which blocked the merge. Issues don't just > magically resolve all by themselves if you just wait long enough. > Your attempts to force the merge with flames and ultimatums > (yes, plural) failed. Surprise, surprise... > > > I'm sure the project would go on way faster if everyone who has never > > investigated the dvb core project and who has no experience with that > > piece of code (and writing a dvb driver doesn't shed much light about > > the dvb framework) would just stay out of everything. > > You think you're the only competent programmer, and everyone > who dares to have different opinions just gets in the > way and holds you up? Check this out: > http://en.wikipedia.org/wiki/Narcissistic_personality_disorder#Diagnostic_criteria > For example you (first trying to help, afterwards doing nothing), * Manu Abraham (who has his project split from the maintree for a very long time too), * Marcel Siegert (who listens to other people's opinion and didn't even spend a minute on thinking by himself how to find a solution) * Oliver Endris, did some tests and afterwards denied the merge because he found a bug which got resolved right after he reported it. There were a few options, freeze the development of v4l-dvb merge in that code and fix whatever someone thinks he has to fix; there are many requirements covered within that code and all you guys did is to ignore it and nothing else.. Manu came up with something and didn't even talk to me about it if it would be ok with the work I've done and guess what he didn't even cover all the requirements which are already solved. Now, all the other developers are far away from such a misbehaviour. > > It's now about 14.000 lines of code, around 7000 inkernel lines, and I > > haven't received _any_ participation request of any developer and all > > you get if you ask people to join the project is that they are busy > > with their work (which is ok) but then don't try to manipulate someone > > else's work in the end. > > Nothing is getting better here if linuxtv.org people don't work together. > > If I look at hg or git logs I get the impression that the > community still works. > as long as they don't cross the mind of people which are mentioned right above. But as you wrote earlier "guess what the issues are still unsovled". -Markus > > Companies will for sure not like to rely on such a mess where finally > > a few wannabes try to play the smart guys and are responsible that > > support for alot devices won't get into the kernel. > > ... > > > Johannes > -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On Wed, Jul 11, 2007 at 05:18:35PM +0200, Markus Rechberger wrote: > > Remember all that code could have been in the kernel for around 1 year > without breaking any device if these few core people (and there are > really only very few ones <5) wouldn't have tried to hit it down. This "the bad linuxtv guys blocked my drivers for years" allegation is unsubstancial as I tried to show in http://www.linuxtv.org/pipermail/linux-dvb/2007-June/018853.html IMHO it is your inability to make compromises and work with the community which blocked the merge. Issues don't just magically resolve all by themselves if you just wait long enough. Your attempts to force the merge with flames and ultimatums (yes, plural) failed. Surprise, surprise... > I'm sure the project would go on way faster if everyone who has never > investigated the dvb core project and who has no experience with that > piece of code (and writing a dvb driver doesn't shed much light about > the dvb framework) would just stay out of everything. You think you're the only competent programmer, and everyone who dares to have different opinions just gets in the way and holds you up? Check this out: http://en.wikipedia.org/wiki/Narcissistic_personality_disorder#Diagnostic_criteria > It's now about 14.000 lines of code, around 7000 inkernel lines, and I > haven't received _any_ participation request of any developer and all > you get if you ask people to join the project is that they are busy > with their work (which is ok) but then don't try to manipulate someone > else's work in the end. > Nothing is getting better here if linuxtv.org people don't work together. If I look at hg or git logs I get the impression that the community still works. > Companies will for sure not like to rely on such a mess where finally > a few wannabes try to play the smart guys and are responsible that > support for alot devices won't get into the kernel. ... Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On 7/11/07, Alasdair Campbell <[EMAIL PROTECTED]> wrote: > On 11/07/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > > I would appreciate if you could stop spamming the em28xx ML since I > > prefer to use it for relevant issues; Currently there are around 200 > > people registered most of them aren't interested in internal linuxtv > > issues. > > As an outsider to this discussion - but nonetheless an interested > party - I find this sort of approach really dispiriting. Do I have to > point out that you yourself have been CC'ing the em28xx ML right up > until this very last post? > > Accusing anybody of "spamming" on a subject this important to all > parties - the licensing - serves very little purpose whatsoever, other > than inflaming emotions, and nobody wishes for that. > > as a postscript.. right that was my fault, sorry. > On 2007/7/10, Markus Rechberger <[EMAIL PROTECTED]> wrote: > > Stop that MPL discussion, I can put that code offline too and update > > it with some probably nonfunctional code for several devices but it > > won't help anyone in the end - so I won't do it. > > I don't want my work to be stolen by linuxtv people in the end. It's > > too easy to look over the code change a few lines and obfuscure my > > work, remove the copyright and that's what I'm concerned about. I > > wouldn't mind about it if it wouldn't happen with that linuxtv > > community. > > You can't pick and choose who receives their rights under the GPL and > who doesn't (surely this is one of the benefits!), you just have to > live with it. > Well I don't close the development because of all that it just goes another path around linuxtv.org. In general it's no big deal anymore with the existing code since I already put it into userspace. It will be an issue with newer drivers which I do not intend to share with a group of people who are unable to discuss technical issues and just try to cut everyone down. Remember all that code could have been in the kernel for around 1 year without breaking any device if these few core people (and there are really only very few ones <5) wouldn't have tried to hit it down. I'm sure the project would go on way faster if everyone who has never investigated the dvb core project and who has no experience with that piece of code (and writing a dvb driver doesn't shed much light about the dvb framework) would just stay out of everything. It's now about 14.000 lines of code, around 7000 inkernel lines, and I haven't received _any_ participation request of any developer and all you get if you ask people to join the project is that they are busy with their work (which is ok) but then don't try to manipulate someone else's work in the end. Nothing is getting better here if linuxtv.org people don't work together. Companies will for sure not like to rely on such a mess where finally a few wannabes try to play the smart guys and are responsible that support for alot devices won't get into the kernel. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On 11/07/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > I would appreciate if you could stop spamming the em28xx ML since I > prefer to use it for relevant issues; Currently there are around 200 > people registered most of them aren't interested in internal linuxtv > issues. As an outsider to this discussion - but nonetheless an interested party - I find this sort of approach really dispiriting. Do I have to point out that you yourself have been CC'ing the em28xx ML right up until this very last post? Accusing anybody of "spamming" on a subject this important to all parties - the licensing - serves very little purpose whatsoever, other than inflaming emotions, and nobody wishes for that. as a postscript.. On 2007/7/10, Markus Rechberger <[EMAIL PROTECTED]> wrote: > Stop that MPL discussion, I can put that code offline too and update > it with some probably nonfunctional code for several devices but it > won't help anyone in the end - so I won't do it. > I don't want my work to be stolen by linuxtv people in the end. It's > too easy to look over the code change a few lines and obfuscure my > work, remove the copyright and that's what I'm concerned about. I > wouldn't mind about it if it wouldn't happen with that linuxtv > community. You can't pick and choose who receives their rights under the GPL and who doesn't (surely this is one of the benefits!), you just have to live with it. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] PCTV dual pci pro aka 2000i support
Hiya, Does anybody know the actual state of development/support of the card in the subject? I get one to testdrive but at first sight it seems to be unsupported, this is the output of lspci -v 05:04.0 Multimedia controller: Pinnacle Systems Inc. Unknown device 0040 Subsystem: Pinnacle Systems Inc. Unknown device 0044 Flags: bus master, medium devsel, latency 32, IRQ 9 Memory at d030 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 05:04.1 Multimedia controller: Pinnacle Systems Inc. Unknown device 0041 Subsystem: Pinnacle Systems Inc. Unknown device 0044 Flags: bus master, medium devsel, latency 32, IRQ 9 Memory at d0301000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 05:04.2 Multimedia controller: Pinnacle Systems Inc. Unknown device 0042 Subsystem: Pinnacle Systems Inc. Unknown device 0044 Flags: bus master, medium devsel, latency 32, IRQ 9 Memory at d0302000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Tried out with the latest mercurial drivers, Regards, -- Emilio Castellano ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On 7/11/07, Marcel Siegert <[EMAIL PROTECTED]> wrote: > forwarded to linuxdvb as i used my private not the list account :/ One more reason why this list should have reply-to set to linux-dvb, its a total pain in the ass to reply to all and then cut linux-dvb email from CC into To: and remove everyone else from there. Spam, spam. -tc ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
forwarded to linuxdvb as i used my private not the list account :/ On Wednesday 11 July 2007, Markus Rechberger wrote: > I would appreciate if you could stop spamming the em28xx ML since I > prefer to use it for relevant issues; Currently there are around 200 > people registered most of them aren't interested in internal linuxtv > issues. > > Try to resolve all existing relevant problems first (since there are a > few other problems out there within the linuxtv "core developer(s)" > community) > > -Markus > hey markus, please calm down again. YOU sended an email to linux-dvb ml including a cc to your very own em28xx ml. it is normal to REPLY TO ALL if someone answers this. dont claim johannes to spam the em28xx ml, as this is a discussion that again shows how non-cooperative _you_ are, you may just want not your users to know it! regards marcel ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
I would appreciate if you could stop spamming the em28xx ML since I prefer to use it for relevant issues; Currently there are around 200 people registered most of them aren't interested in internal linuxtv issues. Try to resolve all existing relevant problems first (since there are a few other problems out there within the linuxtv "core developer(s)" community) -Markus On 7/11/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote: > On Wed, Jul 11, 2007, Markus Rechberger wrote: > > On 7/10/07, Trent Piepho <[EMAIL PROTECTED]> wrote: > > > On Tue, 10 Jul 2007, Markus Rechberger wrote: > > > > Stop that MPL discussion, I can put that code offline too and update > > > > it with some probably nonfunctional code for several devices but it > > > > won't help anyone in the end - so I won't do it. > > > > I don't want my work to be stolen by linuxtv people in the end. It's > > > > > > It's funny you should say this, since 99% of the code you are > distributing > > > came from linuxtv in the first place! > > > > Trent, I believe you're smart enough to see the problem behind > > everything .. the license stuff is the smallest part of everything; > > I don't steal and obfuscate code and remove the copyrights. > > And I for sure will not tell anyone how he has to do his work after a > > discussion where I didn't seriously participate. > > The code as it is will get removed sooner or later and replaced with a > > smaller package which only contains the necessary drivers. > > > > I wonder what you try to gain by bothering about the license there all > > you can win is the removal of the code there and the release of the > > replacement of the around 80% finished reworked code. So please stay > > serious and better try to fix the community problems that something > > like that won't happen again. > > I wonder what you mean by "I don't want my work to be stolen by > linuxtv people"? > > You had your code up for download on linuxtv.org and then on mcentral.de > for months, and you asked lots of people to download and test it, which > IMHO clearly is "distribution under the GPL". > > So everyone who downloaded it has every right granted by the GPL > to modify and redistribute your code under the GPL, which implies > it could be merged it into the main linuxtv.org tree and eventually > the kernel. Of course it doesn't make sense to merge unsupported code > (which even has known issues wich need to be resolved first), however if > someone would adopt it I see no (legal) reason for not merging it. > > Maybe you don't like this to happen, but IMHO all the > people who downloaded and tested your code, and contributed > back in form of bug reports, hardware information, patches etc. > wouldn't have done so if they had known that your code would > not be merged into the mainline kernel. Some people might even > have bought hardware after they read though your Wiki pages, > under the impression that it was well supported by Linux. > > Of course you are free to do whatever you like with the > code written by you, but everyone else is free to do > what the GPL permits them with the code distributed by > you under the GPL. > > > Johannes > -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On Wed, Jul 11, 2007, Markus Rechberger wrote: > On 7/10/07, Trent Piepho <[EMAIL PROTECTED]> wrote: > > On Tue, 10 Jul 2007, Markus Rechberger wrote: > > > Stop that MPL discussion, I can put that code offline too and update > > > it with some probably nonfunctional code for several devices but it > > > won't help anyone in the end - so I won't do it. > > > I don't want my work to be stolen by linuxtv people in the end. It's > > > > It's funny you should say this, since 99% of the code you are distributing > > came from linuxtv in the first place! > > Trent, I believe you're smart enough to see the problem behind > everything .. the license stuff is the smallest part of everything; > I don't steal and obfuscate code and remove the copyrights. > And I for sure will not tell anyone how he has to do his work after a > discussion where I didn't seriously participate. > The code as it is will get removed sooner or later and replaced with a > smaller package which only contains the necessary drivers. > > I wonder what you try to gain by bothering about the license there all > you can win is the removal of the code there and the release of the > replacement of the around 80% finished reworked code. So please stay > serious and better try to fix the community problems that something > like that won't happen again. I wonder what you mean by "I don't want my work to be stolen by linuxtv people"? You had your code up for download on linuxtv.org and then on mcentral.de for months, and you asked lots of people to download and test it, which IMHO clearly is "distribution under the GPL". So everyone who downloaded it has every right granted by the GPL to modify and redistribute your code under the GPL, which implies it could be merged it into the main linuxtv.org tree and eventually the kernel. Of course it doesn't make sense to merge unsupported code (which even has known issues wich need to be resolved first), however if someone would adopt it I see no (legal) reason for not merging it. Maybe you don't like this to happen, but IMHO all the people who downloaded and tested your code, and contributed back in form of bug reports, hardware information, patches etc. wouldn't have done so if they had known that your code would not be merged into the mainline kernel. Some people might even have bought hardware after they read though your Wiki pages, under the impression that it was well supported by Linux. Of course you are free to do whatever you like with the code written by you, but everyone else is free to do what the GPL permits them with the code distributed by you under the GPL. Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge HVR-3000
Hi, I'm trying to setup the above card to work in DVB-S mode without success. I'm using Suse 10.1, with kernel 2.6.16.21-0.8-smp (distro release) and the latest hg downloaded drivers from linuxtv.org, also I tried steven's branch. I cannot make work the dvb-s frontend, only CX22702 (dvb-t) is loaded. Many times I have to play with cx8800/cx8802 load to register the dvb-t frontend getting errors like... >> Jul 11 12:56:54 pinocho kernel: cx8802_register_driver() ->registering driver type=dvb access=shared Jul 11 12:56:54 pinocho kernel: CORE cx88[0]: subsystem: 0070:1402, board: Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T [card=53] Jul 11 12:56:54 pinocho kernel: cx88[0]/2: cx2388x based dvb card Jul 11 12:56:54 pinocho kernel: cx22702_readreg: readreg error (ret == -121) Jul 11 12:56:54 pinocho modprobe: FATAL: Error inserting cx88_dvb (/lib/modules/2.6.16.21-0.8-smp/kernel/drivers/media/video/cx88/cx88-dvb.ko): No such device Jul 11 12:56:54 pinocho kernel: cx88[0]: frontend initialization failed Jul 11 12:56:54 pinocho kernel: cx8802_dvb_probe dvb_register failed err = -1 Jul 11 12:56:54 pinocho kernel: cx8802_register_driver() ->probe failed err = -1 < this is the output of lsmod |grep cx > cx88_dvb 13700 0 cx8800 32368 0 compat_ioctl32 5120 1 cx8800 cx88_vp3054_i2c 6528 1 cx88_dvb mt352 9348 1 cx88_dvb dvb_pll13444 1 cx88_dvb or5113211396 1 cx88_dvb video_buf_dvb 9348 1 cx88_dvb nxt200x15364 1 cx88_dvb isl6421 5888 1 cx88_dvb zl10353 9096 1 cx88_dvb cx2412314472 1 cx88_dvb lgdt330x 11268 1 cx88_dvb cx22702 9092 1 cx88_dvb cx8802 18820 1 cx88_dvb cx88xx 63396 3 cx88_dvb,cx8800,cx8802 ir_common 37380 1 cx88xx i2c_algo_bit 12168 2 cx88_vp3054_i2c,cx88xx tveeprom 17552 1 cx88xx videodev 27392 2 cx8800,cx88xx v4l2_common19968 3 cx8800,cx88xx,videodev btcx_risc 8072 3 cx8800,cx8802,cx88xx video_buf 24708 5 cx88_dvb,cx8800,video_buf_dvb,cx8802,cx88xx i2c_core 23680 14 cx88_vp3054_i2c,mt352,dvb_pll,or51132,nxt200x,isl6421,zl10353,cx24123,lgdt330x,cx22702,cx88xx,i2c_algo_bit,tveeprom,i2c_i801 >>> and the kernel messages from dmesg Jul 11 12:58:29 pinocho kernel: compat_ioctl32: module not supported by Novell, setting U taint flag. Jul 11 12:58:29 pinocho kernel: cx8800: module not supported by Novell, setting U taint flag. Jul 11 12:58:29 pinocho kernel: cx2388x v4l2 driver version 0.0.6 loaded Jul 11 12:58:29 pinocho kernel: ACPI: PCI Interrupt :05:04.0[A] -> GSI 20 (level, low) -> IRQ 50 Jul 11 12:58:29 pinocho kernel: cx88[0]/0: found at :05:04.0, rev: 5, irq: 50, latency: 32, mmio: 0xd000 Jul 11 12:58:29 pinocho kernel: cx88[0]/0: registered device video0 [v4l2] Jul 11 12:58:29 pinocho kernel: cx88[0]/0: registered device vbi0 Jul 11 12:58:29 pinocho kernel: cx88[0]/0: registered device radio0 Jul 11 12:58:56 pinocho kernel: cx88_dvb: module not supported by Novell, setting U taint flag. Jul 11 12:58:56 pinocho kernel: cx2388x dvb driver version 0.0.6 loaded Jul 11 12:58:56 pinocho kernel: cx8802_register_driver() ->registering driver type=dvb access=shared Jul 11 12:58:56 pinocho kernel: CORE cx88[0]: subsystem: 0070:1402, board: Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T [card=53] Jul 11 12:58:56 pinocho kernel: cx88[0]/2: cx2388x based dvb card Jul 11 12:58:56 pinocho kernel: DVB: registering new adapter (cx88[0]) Jul 11 12:58:56 pinocho kernel: DVB: registering frontend 0 (Conexant CX22702 DVB-T)... Could someone post his modprobe.d file with the working load/parameters order to get the dvb-s frontend loaded? Thanking in advance, -- Emilio Castellano -- Emilio Castellano Leiva Departamento de Sistemas Abdón Terradas, 4 - 28015 Madrid (ESPAÑA) T.: +34 91 121 4430 | www.microgenesis.es ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-dvb Digest, Vol 30, Issue 16
Dear timecop: It is just nothing when I modprobe mymodule and modprobe -r mymodule BEFORE my hardware present. The bad things happen when I modprobe -r mymodule AFTER my haredware present. [EMAIL PROTECTED] 写道： Send linux-dvb mailing list submissions to linux-dvb@linuxtv.org To subscribe or unsubscribe via the World Wide Web, visit http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of linux-dvb digest..." Today's Topics: 1. Problems about the drivers rmmod. (lwtbenben) 2. Re: Problems about the drivers rmmod. (timecop) 3. Re: libdvbapi clarification (David H?rdeman) 4. Re: Help needed with dst (Joel Michael) 5. Re: [Em28xx] MPL-licensed V4L kernel modules (em2880) (Markus Rechberger) -- Message: 1 Date: Wed, 11 Jul 2007 11:34:18 +0800 (CST) From: lwtbenben <[EMAIL PROTECTED]> Subject: [linux-dvb] Problems about the drivers rmmod. To: linux-dvb@linuxtv.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="gbk" Hi,everyone I am now developing my own tv card's driver. While I am debugging, I just found a problem when I used "modprobe -r" to rmmod my driver module, it is like this: a. When I don't insert my hardware, modprobe dvb-usb-mymodule.ko and modprobe -r dvb-usb-mymodule.ko were well executed. b. First, I insmod my module: modprobe dvb-usb-mymodule.ko Then, I insert my own hareware. And if I want to rmmod my module: modprobe dvb-usb-mymodule.ko It is bad. The terminal is dead, and the modprobe thread is hanging on and can't be killed. I must reboot to make it. So, could anybody help me with this issue? Thank you very much. -- next part -- An HTML attachment was scrubbed... URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20070711/67464b46/attachment.html -- Message: 2 Date: Wed, 11 Jul 2007 12:44:06 +0900 From: timecop <[EMAIL PROTECTED]> Subject: Re: [linux-dvb] Problems about the drivers rmmod. To: linux-dvb@linuxtv.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=GB2312; format=flowed How is it that you're inserting driver for your hardware BEFORE the hardware is present? On 7/11/07, lwtbenben <[EMAIL PROTECTED]> wrote: > Hi,everyone > I am now developing my own tv card's driver. > While I am debugging, I just found a problem when I used "modprobe -r" > to rmmod my driver module, it is like this: > a. When I don't insert my hardware, > modprobe dvb-usb-mymodule.ko and modprobe -r dvb-usb-mymodule.ko > were well executed. > b. First, I insmod my module: modprobe dvb-usb-mymodule.ko > Then, I insert my own hareware. > And if I want to rmmod my module: modprobe dvb-usb-mymodule.ko > It is bad. > The terminal is dead, and the modprobe thread is hanging on and can't > be killed. I must reboot to make it. > > So, could anybody help me with this issue? > Thank you very much. > > > > > > > 150 ? ? ? ? ? ? ? ? ??? ? ? ? ? ? > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > -- Message: 3 Date: Wed, 11 Jul 2007 09:31:33 +0200 (CEST) From: David H?rdeman <[EMAIL PROTECTED]> Subject: Re: [linux-dvb] libdvbapi clarification To: linux-dvb@linuxtv.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain;charset=iso-8859-1 On Tue, July 10, 2007 10:56, Marcel Siegert wrote: > On Tuesday 10 July 2007, David H?rdeman wrote: >> I'm trying to understand the dvbdemux_set_section_filter function in >> dvp-apps/lib/libdvbapi/dvbdemux.c (lines 74 - 93). ... > > if you filter a section you can filter on e.g. the table id but NOT on the > size ect. (those are used as byte 2 + 3 of a section) Ok, now I'm confused...when I use one filter by calling dvbdemux_set_section_filter with filter[0] and mask[0] set to something, I get sections. If I use two filters by calling dvbdemux_set_section_filter with filter[0], mask[0], filter[3], mask[3] set to something, I get no sections at all... Do I need to do anything special to use multiple filters? Second, unused filter and mask values are set to 0x00, but how does the API distinguish between an unused filter/mask pair and a request for all sections? It seems that if I call dvbdemux_set_section_filter with mask[0] = 0x00 and filter[0] = 0x00 I do get all sections... -- David H?rdeman -
Re: [linux-dvb] [Em28xx] MPL-licensed V4L kernel modules (em2880)
On 7/10/07, Trent Piepho <[EMAIL PROTECTED]> wrote: > On Tue, 10 Jul 2007, Markus Rechberger wrote: > > Stop that MPL discussion, I can put that code offline too and update > > it with some probably nonfunctional code for several devices but it > > won't help anyone in the end - so I won't do it. > > I don't want my work to be stolen by linuxtv people in the end. It's > > It's funny you should say this, since 99% of the code you are distributing > came from linuxtv in the first place! > Trent, I believe you're smart enough to see the problem behind everything .. the license stuff is the smallest part of everything; I don't steal and obfuscate code and remove the copyrights. And I for sure will not tell anyone how he has to do his work after a discussion where I didn't seriously participate. The code as it is will get removed sooner or later and replaced with a smaller package which only contains the necessary drivers. I wonder what you try to gain by bothering about the license there all you can win is the removal of the code there and the release of the replacement of the around 80% finished reworked code. So please stay serious and better try to fix the community problems that something like that won't happen again. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help needed with dst
Joel Michael wrote: > The machine I'm running the card on is a Core2 Duo (x86_64 mode), on an > Asus P5B-VM motherboard, running the Gentoo distribution. I've tried > with and without preempt, and am going to try without SMP tonight, and > maybe try it in 32-bit mode. I've also tried removing the pair of > FlexCopII's, with no success. > I've dug into the source a bit, and it seems that in drivers/media/video/bt8xx/bttv-i2c.c, I get an interrupt from the card without BT848_INT_RACK set, but BT848_INT_I2CDONE is set. If someone can shed a bit of light on why this might be happening, it would be greatly appreciated. Right now, I'm off to see if it works at all in 32-bit mode. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] libdvbapi clarification
On Tue, July 10, 2007 10:56, Marcel Siegert wrote: > On Tuesday 10 July 2007, David Härdeman wrote: >> I'm trying to understand the dvbdemux_set_section_filter function in >> dvp-apps/lib/libdvbapi/dvbdemux.c (lines 74 - 93). ... > > if you filter a section you can filter on e.g. the table id but NOT on the > size ect. (those are used as byte 2 + 3 of a section) Ok, now I'm confused...when I use one filter by calling dvbdemux_set_section_filter with filter[0] and mask[0] set to something, I get sections. If I use two filters by calling dvbdemux_set_section_filter with filter[0], mask[0], filter[3], mask[3] set to something, I get no sections at all... Do I need to do anything special to use multiple filters? Second, unused filter and mask values are set to 0x00, but how does the API distinguish between an unused filter/mask pair and a request for all sections? It seems that if I call dvbdemux_set_section_filter with mask[0] = 0x00 and filter[0] = 0x00 I do get all sections... -- David Härdeman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
