public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Marcos Alejandro Saldivia Delgado <marcos.saldivia@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: Problem with em28xx driver in Gumstix Overo
Date: Mon, 03 Jan 2011 19:02:28 -0200	[thread overview]
Message-ID: <4D223964.4060107@redhat.com> (raw)
In-Reply-To: <AANLkTi=AVjhEbsqZOWJbwkYRo+HLoHfdWxuFO7Bs_a7H@mail.gmail.com>

Hi Marcos,

Em 03-01-2011 18:13, Linus Torvalds escreveu:
> Hi Marcos,
> 
> [ full email quoted for new cc's ]
> 
> you really would be much better off sending a diff rather than trying
> to explain what changes you did, but quite frankly, even if you did
> that, I'd still want this to go through the actual maintainers of the
> em28xx driver.

As I explained to the email you sent me in priv, It seems that
there's a bug at the scaling function. Not sure why this but doesn't 
show on x86. 

I intend to do some tests with em28xx and fix the issue, but I can't 
do it this week. I have a few arm boards, and I'll test on them with
some em28xx devices.

> The USB error sounds like some independent unrelated issue, I have no
> ideas on it.

Yes, it seems to be unrelated. Those video drivers generate a lot of ISOC
traffic at the USB bus. I suspect that the hardware have some problems
to keep that high bandwidth rate.  Maybe one of the ARM maintainers could
give us some light around this issue, as this driver doesn't suffer any
known issue of this kind on x86 arch. We even did a large stress test on 
em28xx driver in the past, in order to fix a memory leak there.

Cheers,
Mauro.

      parent reply	other threads:[~2011-01-03 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinPEYyLrTWqt1r0QgoYmsv2Xg16qGKo5yTqu9FO@mail.gmail.com>
     [not found] ` <AANLkTinimPHSRXfWtu+eiv3Y4WZ6PGrbB3sZKBvw2Muy@mail.gmail.com>
2011-01-03 20:13   ` Problem with em28xx driver in Gumstix Overo Linus Torvalds
2011-01-03 20:22     ` Devin Heitmueller
2011-01-04 16:46       ` Martin Seekatz
2011-01-03 21:02     ` Mauro Carvalho Chehab [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=4D223964.4060107@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=marcos.saldivia@gmail.com \
    --cc=torvalds@linux-foundation.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