From mboxrd@z Thu Jan 1 00:00:00 1970 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 m396IF3m030975 for ; Wed, 9 Apr 2008 02:18:15 -0400 Received: from smtp1.mtw.ru (smtp1.mtw.ru [194.135.105.241]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m396HpoP000888 for ; Wed, 9 Apr 2008 02:17:52 -0400 Date: Wed, 9 Apr 2008 10:17:44 +0400 From: Andrew Junev Message-ID: <1271819320.20080409101744@a-j.ru> To: hermann pitton In-Reply-To: <1207702576.5135.42.camel@pc08.localdom.local> References: <1115343012.20080318233620@a-j.ru> <200803200048.15063@orion.escape-edv.de> <1206067079.3362.10.camel@pc08.localdom.local> <200803210742.57119@orion.escape-edv.de> <1206912674.3520.58.camel@pc08.localdom.local> <1063704330.20080331082850@a-j.ru> <1206999694.7762.41.camel@pc08.localdom.local> <1112443057.20080402224744@a-j.ru> <1207179525.14887.13.camel@pc08.localdom.local> <1207265002.3364.12.camel@pc08.localdom.local> <20080403221833.34d3c4d6@gaivota> <1207275545.3365.26.camel@pc08.localdom.local> <1076827621.20080406215420@a-j.ru> <1207522685.6334.29.camel@pc08.localdom.local> <1135983778.20080408193408@a-j.ru> <1207702576.5135.42.camel@pc08.localdom.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: video4linux-list@redhat.com, linux-dvb@linuxtv.org Subject: Re: [linux-dvb] TT S-1401 problem with kernel 2.6.24 ??? Reply-To: Andrew Junev 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: > Hi Andrew, > Am Dienstag, den 08.04.2008, 19:34 +0400 schrieb Andrew Junev: >> Hello Hermann, >> >> Monday, April 7, 2008, 2:58:05 AM, you wrote: >> >> > you always drop the lists. >> >> Not always. :) I do it just sometimes, when I feel my message doesn't >> contain useful information for everybody on the list. >> But we can move back to the lists, if you think it's more appropriate. >> >> > I come back to you, if nobody else who is more fluently in just add a >> > patch and compile a vanilla kernel does not move in. >> >> Well, I believe I can do it, if noone else does. It shouldn't be that >> hard. >> >> > I of course know for sure the fix is correct, but the stable team wants >> > a report from a user on 2.6.24 and support for my stuff is new and it is >> > nonsense to bring it down to 2.6.24 to demonstrate it working for >> > someone on 2.6.24 ... >> >> I wonder how the unpatched driver made its way to 2.6.24 stable... >> Or maybe it's just me who gets affected by this problem that much. >> >> > B.T.W, why you don't use at least the v4l-dvb master stuff to come over >> > it. Needs no patching :) >> >> If I ever need to move to 2.6.24 and it gets no patch included by >> then, I'll surely do so! :) >> At the moment I'm perfectly fine with 2.6.23... >> > however it will go out for now, seems in the end you will have something > to test ;) I have no problems with that! :) Ok, can you point me to a guide on how to do this? Otherwise I'm affraid I'll waste lots of time just by trying something that I should not... I'm ready to test it sometime this week. -- Best regards, Andrew -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list