All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Michael Yang <yze007@gmail.com>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: The em28xx driver error
Date: Thu, 15 Nov 2012 17:31:36 +0100	[thread overview]
Message-ID: <50A518E8.8060002@googlemail.com> (raw)
In-Reply-To: <CAGoCfiwd0Dt49sZO_XEkv5rGwCj+nEDz0sGxw_j8oxKXE=NQAQ@mail.gmail.com>

Am 14.11.2012 18:05, schrieb Devin Heitmueller:
> On Wed, Nov 14, 2012 at 11:58 AM, Frank Schäfer
> <fschaefer.oss@googlemail.com> wrote:
>> This looks indeed like a bug.
>> a >>= b means a = a >> b, which in this case means shifting height 480
>> or 576 bits to the right...
>> height >> 1 means height /= 2 which seems to be sane for interlaced devices.
>> OTOH, I wonder why it seems to be working on other platforms !?
>> Unfortunately I don't have an interlaced device here for testing. :(
> It's definitely a bug.  I think Mauro put a patch in for 3.7 or 3.8.
> The reason it works under x86 is because shifting an arbitrary number
> of bits > 32 causes indeterminate behavior, and out of dumb luck it
> has no effect on x86.
>
> But yeah, I changed the code to shift by one bit and it's been working
> fine on ARM for months in my environment (DM3730).
>
> Devin
Hmm... I've made some experiments to find out what gcc does on x86 and
it seems to ignore bit shifting > 32.
I also noticed that this line has been removed in 3.7-rc.
So we do NOT want to halve the height for interlaced devices here, right ?

Regards,
Frank

  reply	other threads:[~2012-11-15 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11  4:46 The em28xx driver error Michael Yang
2012-11-14 16:58 ` Frank Schäfer
2012-11-14 17:05   ` Devin Heitmueller
2012-11-15 16:31     ` Frank Schäfer [this message]
2012-11-15 16:35       ` Devin Heitmueller
2012-11-15 16:58         ` Frank Schäfer

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=50A518E8.8060002@googlemail.com \
    --to=fschaefer.oss@googlemail.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=yze007@gmail.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 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.