public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Junev <a-j@a-j.ru>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: video4linux-list@redhat.com, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TT S-1401 problem with kernel 2.6.24 ???
Date: Tue, 13 May 2008 19:55:59 +0400	[thread overview]
Message-ID: <1455396550.20080513195559@a-j.ru> (raw)
In-Reply-To: <1207782190.5554.47.camel@pc08.localdom.local>


Thursday, April 10, 2008, 3:03:10 AM, you wrote:

> Am Mittwoch, den 09.04.2008, 10:17 +0400 schrieb Andrew Junev:
>> > 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.
>> 

> Hi Andrew,

> Mike has forwarded the patch to the stable kernel team. (Thanks!)

> Likely it will be fixed in 2.6.24.5 then.

> To build a vanilla kernel is still a very easy task, but there are
> distribution specific helper scripts and customs.

> The real problem, that could appear, is that dependencies on other
> utilities are not resolved on your current distribution version anymore
> and you run into some circular dependencies, not easy to resolve and
> then you must know what you are doing exactly or upgrade.

> If a 2.6.24 is available for your current stuff, just install it and see
> the missing. If you then install the kernel source for it, we can apply
> the patch also there and build a new kernel.

> Cheers,
> Hermann


Sorry for my slow response...
I just installed kernel 2.6.24.5 and my S-1401 works good now!

Thanks a million to everyone who was involved!

And once again sorry for not providing my feedback fast enough.


-- 
Best regards,
 Andrew

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-05-13 15:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 20:36 [linux-dvb] TT S-1401 problem with kernel 2.6.24 ??? Andrew Junev
2008-03-19 23:48 ` Oliver Endriss
2008-03-20 18:23   ` Andrew Junev
2008-03-21  2:37   ` hermann pitton
2008-03-21  6:42     ` Oliver Endriss
2008-03-21 18:29       ` Andrew Junev
     [not found]       ` <1206912674.3520.58.camel@pc08.localdom.local>
     [not found]         ` <1063704330.20080331082850@a-j.ru>
     [not found]           ` <1206999694.7762.41.camel@pc08.localdom.local>
     [not found]             ` <1112443057.20080402224744@a-j.ru>
2008-04-02 23:38               ` hermann pitton
2008-04-03 23:23                 ` hermann pitton
2008-04-04  0:32                   ` Oliver Endriss
2008-04-04  0:43                     ` hermann pitton
     [not found]                       ` <20080403222937.3b234a40@gaivota>
2008-04-04  2:56                         ` Oliver Endriss
2008-04-04  4:14                           ` Michael Krufky
2008-04-04 11:44                             ` Mauro Carvalho Chehab
2008-04-04 12:56                               ` Michael Krufky
2008-04-04 13:23                                 ` Michael Krufky
2008-04-04 17:59                                   ` Oliver Endriss
2008-04-04 23:08                                     ` hermann pitton
2008-04-08 21:01                                       ` mkrufky
2008-04-08 22:10                                         ` hermann pitton
2008-04-08 22:27                                         ` Oliver Endriss
2008-04-08 22:36                                           ` Mauro Carvalho Chehab
2008-04-04 12:02                             ` Oliver Endriss
     [not found]                   ` <20080403221833.34d3c4d6@gaivota>
2008-04-04  2:19                     ` hermann pitton
     [not found]                       ` <1076827621.20080406215420@a-j.ru>
     [not found]                         ` <1207522685.6334.29.camel@pc08.localdom.local>
     [not found]                           ` <1135983778.20080408193408@a-j.ru>
2008-04-09  0:56                             ` hermann pitton
2008-04-09  6:17                               ` Andrew Junev
2008-04-09 23:03                                 ` hermann pitton
2008-05-13 15:55                                   ` Andrew Junev [this message]
2008-05-15  0:23                                     ` hermann pitton
2008-04-04 14:15                   ` ldvb
2008-04-04 14:17                     ` ldvb
2008-04-04 23:20                       ` hermann pitton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1455396550.20080513195559@a-j.ru \
    --to=a-j@a-j.ru \
    --cc=hermann-pitton@arcor.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox