From: Peter Osterlund <petero2@telia.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Gerd Knorr <kraxel@bytesex.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-rc2
Date: 26 Sep 2004 09:05:05 +0200 [thread overview]
Message-ID: <m3pt49ik7y.fsf@telia.com> (raw)
In-Reply-To: <m3ekl5de7b.fsf@telia.com>
Peter Osterlund <petero2@telia.com> writes:
> Linus Torvalds <torvalds@osdl.org> writes:
>
> > Gerd Knorr:
> > o v4l: bttv driver update
>
> This patch,
>
> http://linus.bkbits.net:8080/linux-2.5/cset@4138a998OBJaigDdWZo3Y58C5Brqlg?nav=index.html|ChangeSet@-2w
>
> makes my computer lock up or instantly reboot when I try to do a tv
> recording with mplayer.
I think the patch below should be applied before 2.6.9. It fixes the
bug that made the card DMA lots of data to random memory locations,
causing lockups and instant reboots.
The problem was that the yoffset variable got modified inside the
loop, but the logic in the switch statement was meant to work on the
initial value of the yoffset variable.
(Bug fix extracted from
http://marc.theaimsgroup.com/?l=linux-kernel&m=109532814823565&w=2)
Signed-off-by: Peter Osterlund <petero2@telia.com>
---
linux-petero/drivers/media/video/bttv-risc.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff -puN drivers/media/video/bttv-risc.c~bttv-crash-fix drivers/media/video/bttv-risc.c
--- linux/drivers/media/video/bttv-risc.c~bttv-crash-fix 2004-09-26 08:39:52.627762048 +0200
+++ linux-petero/drivers/media/video/bttv-risc.c 2004-09-26 08:42:23.642804272 +0200
@@ -125,6 +125,7 @@ bttv_risc_planar(struct bttv *btv, struc
struct scatterlist *ysg;
struct scatterlist *usg;
struct scatterlist *vsg;
+ int topfield = (0 == yoffset);
int rc;
/* estimate risc mem: worst case is one write per page border +
@@ -153,13 +154,13 @@ bttv_risc_planar(struct bttv *btv, struc
chroma = 1;
break;
case 1:
- if (!yoffset)
+ if (topfield)
chroma = (line & 1) == 0;
else
chroma = (line & 1) == 1;
break;
case 2:
- if (!yoffset)
+ if (topfield)
chroma = (line & 3) == 0;
else
chroma = (line & 3) == 2;
_
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2004-09-26 7:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 16:40 Linux 2.6.9-rc2 Linus Torvalds
2004-09-13 20:03 ` Linux 2.6.9-rc2 : oops Christian Borntraeger
2004-09-13 20:39 ` Linus Torvalds
2004-09-13 21:00 ` Andrew Morton
2004-09-13 21:22 ` Christian Borntraeger
2004-09-13 21:15 ` Christian Borntraeger
2004-09-13 21:23 ` Linus Torvalds
2004-09-13 21:57 ` Linux 2.6.9-rc2 Peter Osterlund
2004-09-14 9:49 ` Gerd Knorr
2004-09-14 22:30 ` Peter Osterlund
2004-09-15 7:08 ` Gerd Knorr
2004-09-15 18:44 ` Peter Osterlund
2004-09-26 7:05 ` Peter Osterlund [this message]
2004-09-26 19:26 ` Gerd Knorr
2004-09-14 13:12 ` Geert Uytterhoeven
2004-09-15 10:22 ` Eric BEGOT
2004-09-20 17:07 ` Linux 2.6.9-rc2 (compile stats) John Cherry
2004-09-20 20:23 ` Giuseppe Bilotta
2004-09-20 20:46 ` Jesper Juhl
2004-09-20 22:23 ` Giuseppe Bilotta
2004-10-11 21:30 ` [PATCH] FrameMaster II build fix (was: Re: Linux 2.6.9-rc2) Geert Uytterhoeven
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=m3pt49ik7y.fsf@telia.com \
--to=petero2@telia.com \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox