public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: mkrufky@linuxtv.org
To: hermann-pitton@arcor.de
Cc: video4linux-list@redhat.com, mchehab@infradead.org,
	linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TT S-1401 problem with kernel 2.6.24 ???
Date: Tue, 8 Apr 2008 17:01:54 -0400	[thread overview]
Message-ID: <47FBDD42.2030608@linuxtv.org> (raw)
In-Reply-To: <1207350513.4591.41.camel@pc08.localdom.local>

hermann pitton wrote:
> Hi,
>
> Am Freitag, den 04.04.2008, 19:59 +0200 schrieb Oliver Endriss:
>   
>> Michael Krufky wrote:
>>     
>>> On Fri, Apr 4, 2008 at 8:56 AM, Michael Krufky <mkrufky@linuxtv.org>
wrote:
>>>       
>>>>  Guys,
>>>>
>>>>  Please test this patch against 2.6.24.4 -stable.
>>>>
>>>>  I don't have this hardware, or any way to test this myself, so I will
wait on your feedback before sending this to the -stable team.  (Please try
to test it and get back to me quickly -- I'd like to send this over before
the 2.6.24.5 review cycle begins)
>>>>         
>>> I also uploaded the patch to linuxtv.org, in case of mailer
whitespace-mangling:
>>>
>>>
http://linuxtv.org/~mkrufky/stable/2.6.24.y/0002-DVB-tda10086-make-the-22kHz
-tone-for-DISEQC-a-conf.patch
>>>
>>> Please test.
>>>       
>> The following devices are affected by the patch:
>>
>> driver: budget
>> - Technontrend DVB-S 1401, pci subsystem id: 13c2:1018
>>
>> driver ttusb2:
>> - USB_PID_PCTV_400E
>> - USB_PID_PCTV_450E
>>
>> driver: saa7134
>> - SAA7134_BOARD_FLYDVB_TRIO
>> - SAA7134_BOARD_MEDION_MD8800_QUADRO
>> - SAA7134_BOARD_FLYDVBS_LR300
>> - SAA7134_BOARD_PHILIPS_SNAKE
>> - SAA7134_BOARD_MD7134_BRIDGE_2
>>
>> Sorry, cannot do any tests, I do not own any of these devices.
>>
>> CU
>> Oliver
>>
>>     
>
> good, we are likely not dead by external bureaucracy then, but explicit
> tests on 2.6.24 are needed.
>
> For saa7134 only the FLYBVBS_LR300 and the FLYDVB_TRIO are on 2.6.24.
>
> Here are two slightly different versions of the MEDION_MD8800_QUADRO,
> one in an orange MSI nforce3 amd64 and one in a normal PCI slot, means
> only the first 16be:0007 subdevice is functional, but I can use the
> second LNB connector for loop through to an external receiver.
>
> Also one of the new Medion/Creatix triple CTX948 low profile PCI cards,
> a version sold in Austria, which is auto detected as 16be:0005 and
> covered by the MD8800 config. We might add it to the name string.
>
> I would have to down port all our new stuff, including isl6405 support,
> to 2.6.24 and likely that is not the sort of test intended.
>
> BTW, the patch in question is in 2.6.25, but none of the new DVB-S
> support.
>
> Andrew, since you are waiting for the fix on 2.6.24, can you test the
> patch on 2.6.24.4 and report?

...all of this noise was made, and now not a single person is willing to 
test the proposed solution?

I don't think that there will be many more 2.6.24.y releases.  I have an 
ivtv patch queued for 2.6.24.5, and this tda10086 patch is sitting in my 
outbox, waiting for test results.

I suspect that 2.6.25 will be released in a few days, after which, 
2.6.24.y -stable release turnaround gets slower and slower, and most 
likely will end by the time 2.6.26 is released.

If you want this fixed, then the fix needs testing .... NOW.


Regards,

Mike

--
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-04-08 21:04 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 [this message]
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
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=47FBDD42.2030608@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --cc=hermann-pitton@arcor.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=mchehab@infradead.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