From: Mike Krufky <mkrufky@linuxtv.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: saa7134 broken in 2.6.15-rc2
Date: Mon, 28 Nov 2005 10:55:41 -0500 [thread overview]
Message-ID: <438B287D.9030607@linuxtv.org> (raw)
In-Reply-To: <200511281035.18541.gene.heskett@verizon.net>
Gene Heskett wrote:
>On Monday 28 November 2005 10:17, Mike Krufky wrote:
>
>
>>Marco d'Itri wrote:
>>
>>
>>>On Nov 28, Duncan Sands <duncan.sands@math.u-psud.fr> wrote:
>>>
>>>
>>>>here seems to be something rotten in v4l land; here's one I got with
>>>>2.6.15-rc1-git1
>>>>
>>>>
>>>Yes, I should have STFW better:
>>>http://lkml.org/lkml/fancy/2005/11/24/194 .
>>>
>>>video-buf is still broken for me in -rc2, I can make xawtv work if I
>>>set capture to "overlay", but it still complain about no input
>>>sources other than "default".
>>>
>>>
>>Please try again, using the current -git snapshot.... The memory
>>problems have been fixed by Hugh Dickins in 2.6.15-rc2-git3 , and
>>Dmitry has submitted some input fixes after that.....
>>
>>I am running 2.6.15-rc2-git6 with no problems.
>>
>>
>>
>Whats the patch sequence to arrive at rc2-git6 please?
>
Umm... If I am understanding your question correctly:
Start with 2.6.14
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.bz2
Apply 2.6.15-rc2
http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.15-rc2.bz2
Apply 2.6.14-rc2-git6
http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.15-rc2-git6.bz2
Is this what you're asking???
Hope this helps,
Michael Krufky
next prev parent reply other threads:[~2005-11-28 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 13:52 saa7134 broken in 2.6.15-rc2 Marco d'Itri
2005-11-28 14:01 ` Duncan Sands
2005-11-28 14:10 ` Marco d'Itri
2005-11-28 15:17 ` Mike Krufky
2005-11-28 15:35 ` Gene Heskett
2005-11-28 15:55 ` Mike Krufky [this message]
2005-11-29 15:48 ` Randy.Dunlap
2005-12-03 18:30 ` Duncan Sands
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=438B287D.9030607@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.