Skip to contentSkip to conversation

em28xx : can work on ARM beagleboard ?

DISCUSSION CB 5 participants 10 messages May 8, 2012 – Jun 21, 2012 Media (V4L/DVB)

lore
Share & tools
lore

CB

author
#0 lore raw

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

Thanks in advance,

Regards,
Chris

#1 lore raw
Quoted 7 lines · CB

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

It should work as I know one person ran PCTV NanoStick T2 290e using Pandaboard which is rather similar ARM hw.
http://www.youtube.com/watch?v=Wuwyuw0y1Fo

Did you tried it on x86 hardware?

regards
Antti

Signature · 1 line
http://palosaari.fi/
#2 lore raw
Quoted 3 lines · Antti Palosaari

It should work as I know one person ran PCTV NanoStick T2 290e using Pandaboard which is rather similar ARM hw.
http://www.youtube.com/watch?v=Wuwyuw0y1Fo

I ran into a couple of issues related to em28xx analog on ARM. Haven't had a chance to submit patches yet. To answer the question
though: yes, analog support for the em28xx is known to be broken on ARM right now.

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
#3 lore raw
Quoted 9 lines · Devin Heitmueller
Quoted 3 lines · Antti Palosaari

It should work as I know one person ran PCTV NanoStick T2 290e using Pandaboard which is rather similar ARM hw.
http://www.youtube.com/watch?v=Wuwyuw0y1Fo

I ran into a couple of issues related to em28xx analog on ARM. Haven't had a chance to submit patches yet. To answer the question
though: yes, analog support for the em28xx is known to be broken on ARM right now.

Aah, OK. I missed that was analog capture device. Devin surely knows what he speaks.

regards
Antti

Signature · 1 line
http://palosaari.fi/
author
#4 lore raw

I confirm it works fine on an x86 arch
i will have a look to the HCL to find a compatible usb video capture stick !

Thanks for your answers

Chris

Quoted 15 lines · Antti Palosaari
Quoted 9 lines · Devin Heitmueller
Quoted 3 lines · Antti Palosaari

It should work as I know one person ran PCTV NanoStick T2 290e using Pandaboard which is rather similar ARM hw.
http://www.youtube.com/watch?v=Wuwyuw0y1Fo

I ran into a couple of issues related to em28xx analog on ARM. Haven't had a chance to submit patches yet. To answer the question
though: yes, analog support for the em28xx is known to be broken on ARM right now.

Aah, OK. I missed that was analog capture device. Devin surely knows what he speaks.

regards
Antti

#5 lore raw
In reply to Devin Heitmueller
Quoted 6 lines · Devin Heitmueller <dheitmueller <at> kernellabs.com> writes:
Quoted 3 lines · On Tue, May 8, 2012 at 2:24 PM, Antti Palosaari <crope <at> iki.fi> wrote:

It should work as I know one person ran PCTV NanoStick T2 290e using Pandaboard which is rather similar ARM hw.
http://www.youtube.com/watch?v=Wuwyuw0y1Fo

Quoted 7 lines

I ran into a couple of issues related to em28xx analog on ARM. Haven't had a chance to submit patches yet. To answer the question
though: yes, analog support for the em28xx is known to be broken on ARM right now.

Devin

hi Devin,
i don't understand what you mean when you say "analog support for the em28xx is known to be broken on ARM right now'', I hope you can give me some advice.

I use Pinnacle DVC100 capture card on cm-t3530 card to capture analog images. cm-t3530 uses linux 2.6.32 kernel. at first the card can be correctly detected and by the cm-t3530 and generated as the device file /dev/video1.

but when I use some application to capture the images by use of v4l2,there is something wrong and the strace of the application shows the error message is
"ioctl(3, VIDIOC_DQBUF, 0xbeeb4a00) = ? ERESTARTSYS (To be restarted)". The
same application can correctly capture my usb-camera images.
does the problem can be solved? I am yearning for your advice.

Best regards
Julia

#6 lore raw
Quoted 9 lines · Julia

hi Devin,
i don't understand what you mean when you say "analog support for the em28xx is known to be broken on ARM right now'', I hope you can give me some advice.

I use Pinnacle DVC100 capture card on cm-t3530 card to capture analog images. cm-t3530 uses linux 2.6.32 kernel. at first the card can be correctly detected and by the cm-t3530 and generated as the device file /dev/video1.

Quoted 5 lines

but when I use some application to capture the images by use of v4l2,there is something wrong and the strace of the application shows the error message is "ioctl(3, VIDIOC_DQBUF, 0xbeeb4a00)      = ? ERESTARTSYS (To be restarted)". The same application can correctly capture my usb-camera images.
 does the problem can be solved?  I am yearning for  your advice.

Hello Julia,

Yeah, the driver is broken with analog on ARM. I did some work for a commercial customer (in fact, also on a Compulab board), but haven't had a chance to clean up any of the patches and get them upstream.

It's likely the problem you are hitting can be fixed by the patch described here:

http://www.mail-archive.com/[email protected]/msg28194.html

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
#7 lore raw
In reply to CB

Em 08-05-2012 15:18, CB escreveu:

Quoted 6 lines

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/

Quoted 11 lines

Thanks in advance,

Regards,
Chris

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
author
#8 lore raw

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

Quoted 31 lines · Mauro Carvalho Chehab

Em 08-05-2012 15:18, CB escreveu:

Quoted 6 lines

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/

Quoted 10 lines

Thanks in advance,

Regards,
Chris

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#9 lore raw

Sorry,
the link is broken,

see http://www.spinics.net/lists/linux-omap/msg64931.html

Regards,
Christian

Quoted 51 lines · chrbruno

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

Quoted 31 lines · Mauro Carvalho Chehab

Em 08-05-2012 15:18, CB escreveu:

Quoted 6 lines

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/

Quoted 10 lines

Thanks in advance,

Regards,
Chris

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html