Messages in this thread | | | Date | Wed, 08 Mar 2006 23:52:56 +0100 | From | Hartmut Hackmann <> | Subject | Re: [v4l-dvb-maintainer] 2.6.16-rc5: known regressions |
| |
Hi, Brian
Mauro Carvalho Chehab wrote: > Wow! Lots of people being c/c here! Since all pertinent guys are at > lkml, I've just removed all those spam, keeping copied just the lists, > and Adrian, who warned me about it. > > Em Qua, 2006-03-08 às 14:13 +0300, Brian Marete escreveu: > >>What you say is quite correct. >> >>However, my card is not known by the driver, and `card=3' has been working >>for me all the while, with no problems at all. In any case, removing >>`disable_ir=1' from the insmod options hides the problem for me. By the way, >>that option was there since in an an earlier -rc, loading the driver without >>it would cause an oops. > > The option disable_ir is, in fact, a workaround. If this is not needed > anymore, this is a progress ;) Anyway, having an OOPS is really bad. We > should go further to avoid oops on it. > > IR on some saa7134 cards are really a trouble. Sometimes, it just > generates lots of weird events, since you are gathering a generic io > port (GPIO) from hardware to generate keypressing. Using the wrong port > may generate troubles at the system, by sending wrong events to input. > With a wrong card, if somebody fixed the IR, it may broke for your > board.
<snip>
I tried to reproduce your problem but i didn't succeed yet. I also think that the IR support could be the problem. Card 3 defines a GPIO based remote support. As Mauro mentioned above, this is - at least - dangerous if you force this card type but you don't have a remote control or just a different one. This type of remote can use a GPIO port of the SAA713x to generate interrupts. If this pin is floating on your card, the driver can just be flooded with IRQs. We should have a look whether we can prevent this in the IRQ handler.
Best regards Hartmut - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |