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:58:35 +0100 [thread overview]
Message-ID: <50A51F3B.9050400@googlemail.com> (raw)
In-Reply-To: <CAGoCfiw6zPmFbMRMXZEE1NTGfc3cBJqwdh55S9Hk50fmktbEJQ@mail.gmail.com>
Am 15.11.2012 17:35, schrieb Devin Heitmueller:
> On Thu, Nov 15, 2012 at 11:31 AM, Frank Schäfer
> <fschaefer.oss@googlemail.com> wrote:
>> 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 ?
> Even with the datasheets, it was never clear to me what role the
> accumulator size played. It appeared to work regardless of whether it
> was halved (although making it zero obviously caused problems).
>
> Hence, since we couldn't see any visible difference, Mauro just
> removed the code. My guess is that it effects the on-chip internal
> buffering hence it's possible that performance/reliability could be
> effected under extreme load or some edge case, but I don't have any
> data to back up that assertion at this time.
>
> Devin
>
Interesting.
As the buggy line seemed to have no effect on x86 and the driver was
working fine, it makes indeed sense to stay with the full height to
avoid regressions.
Regards,
Frank
prev parent reply other threads:[~2012-11-15 16:58 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
2012-11-15 16:35 ` Devin Heitmueller
2012-11-15 16:58 ` Frank Schäfer [this message]
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=50A51F3B.9050400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).