Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n2ABrS6O005373 for ; Tue, 10 Mar 2009 07:53:28 -0400 Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id n2ABr9gp008958 for ; Tue, 10 Mar 2009 07:53:09 -0400 Received: from tervel.nabble.com ([192.168.236.150]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Lh0WD-0003TB-4h for video4linux-list@redhat.com; Tue, 10 Mar 2009 04:53:09 -0700 Message-ID: <1236685989139-2454732.post@n2.nabble.com> Date: Tue, 10 Mar 2009 04:53:09 -0700 (PDT) From: alexWe To: video4linux-list@redhat.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <510940.57134.qm@web51804.mail.re2.yahoo.com> <1228565373925-1621999.post@n2.nabble.com> Subject: Re: bttv timeouts List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: video4linux-list-bounces@redhat.com Errors-To: video4linux-list-bounces@redhat.com List-ID: Brian Phelps wrote: > > This seems to be a bug in the bttv-risc.c code, at least according to > Vegard > Nossum on the Kernel Dev list: > Hi, is there any progress? Bye, Alex -- View this message in context: http://n2.nabble.com/bttv-timeouts-tp1614747p2454732.html Sent from the video4linux-list mailing list archive at Nabble.com. -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list