From: chrbruno <chrbruno@yahoo.fr>
To: linux-media <linux-media@vger.kernel.org>
Subject: Re: em28xx : can work on ARM beagleboard ?
Date: Thu, 10 May 2012 18:52:32 +0200 [thread overview]
Message-ID: <4FABF250.60706@yahoo.fr> (raw)
In-Reply-To: <4FABF027.3020405@yahoo.fr>
Sorry,
the link is broken,
see http://www.spinics.net/lists/linux-omap/msg64931.html
Regards,
Christian
Le 10/05/2012 18:43, chrbruno a écrit :
> Hi,
> I'm not sure about the fix (it could break the driver for other em28xx
> cards) but I will try to post a patch for the em28xx problem on ARM
>
> Next, I have encountered the same USB problem you described : USB
> stopping after a long capture (and ethernet stops too)
> For this problem, I think a patch is available about the PHY update
> frequency
> Have a look to :
> http://rcn-ee.homeip.net:81/testing/beagleboard/sprz319-erratum-2.1/
> I found it in a thread on the google beagleboard list)
> I will try and post the results here
>
> Regards,
> Chris
>
> Le 10/05/2012 15:39, Mauro Carvalho Chehab a écrit :
>> Em 08-05-2012 15:18, CB escreveu:
>>> Hello,
>>>
>>> I would like to know if someone has already used the em28xx driver
>>> on a beagleboard xM
>>> (the connected device is a Dazzle DVC 100)
>>>
>>> I have tried with an Angstrom Narcissus image and a Debian but I
>>> still get "select timeouts" and skipped frames with mencoded or the
>>> capture.c sample
>> Not sure if something changed, but on previous tests I did with USB
>> 2.0 isoc
>> and Beagleboard, it seems that it has something broken at its USB
>> driver:
>> after some time, it stops working when submitted to a high traffic.
>>
>> I noticed this behavior not only with USB capture cards, but also
>> when using
>> it to sniff traffic, using Google's GoC sniffer[1].
>>
>> [1] http://beagleboard.org/project/usbsniffer/
>>
>>> Thanks in advance,
>>>
>>> Regards,
>>> Chris
>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>> linux-media" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-05-10 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 18:18 em28xx : can work on ARM beagleboard ? CB
2012-05-08 18:24 ` Antti Palosaari
2012-05-08 18:47 ` Devin Heitmueller
2012-05-08 18:53 ` Antti Palosaari
2012-05-09 10:34 ` chrbruno
2012-06-21 2:12 ` Julia
2012-06-21 2:32 ` Devin Heitmueller
2012-05-10 13:39 ` Mauro Carvalho Chehab
2012-05-10 16:43 ` chrbruno
2012-05-10 16:52 ` chrbruno [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=4FABF250.60706@yahoo.fr \
--to=chrbruno@yahoo.fr \
--cc=linux-media@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.