Playstation Eye

[ps3fanboy]

Poted here for review.

thanks. just a dumb question: which app are you using to test the driver?

mplayer:

Code: Select all

mplayer -tv driver=v4l2:device=/dev/video1 tv://

or

Code: Select all

gstreamer-properties

thanks.
but before i spend the effort and try it... let me doublecheck again:
you are able to capture 25 or 30 fps with this driver and mplayer?

[ao2]

mplayer:

Code: Select all

mplayer -tv driver=v4l2:device=/dev/video1 tv://

or

Code: Select all

gstreamer-properties

thanks.
but before i spend the effort and try it... let me doublecheck again:
you are able to capture 25 or 30 fps with this driver and mplayer?

Yes, it works, 30fps is the default frame rate, and you can go up to 50fps setting a module parameter at insmod time.

Anyway I haven't found a way to show exact fps value with mplayer or any other player, any hints?

[ps3fanboy]

I have submitted the driver for inclusion into the V4L source tree.

http://marc.info/?l=linux-video&m=121886284726264&w=2

so, i've added this patch, recompiled and installed the kernel... 2.6.28-rc4 on ps3...
ov534.ko seems to load nicely...

Code: Select all

Linux video capture interface: v2.00
Bluetooth: HCI USB driver ver 2.10
usbcore: registered new interface driver hci_usb
ov534: OmniVision OV534 compatible webcam detected
ov534: OmniVision OV534 compatible webcam detected
ov534: OmniVision OV534 compatible webcam detected
usbcore: registered new interface driver ov534
ov534: ov534 v0.0.5 module loaded

lsmod shows that it's loaded...

Code: Select all

odule                  Size  Used by
snd_ps3                20968  0
ov534                  31516  0
snd_pcm               123216  1 snd_ps3
videobuf_vmalloc        9908  1 ov534
videobuf_core          24476  2 ov534,videobuf_vmalloc
compat_ioctl32         26464  1 ov534
hci_usb                21288  0
videodev               41864  2 ov534,compat_ioctl32
usb_storage            66608  1
bluetooth              90108  1 hci_usb
v4l1_compat            21284  1 videodev
snd_page_alloc         11944  1 snd_pcm
snd_timer              35912  1 snd_pcm
ps3flash                9072  0
ps3_lpm                18664  0
snd                    77856  3 snd_ps3,snd_pcm,snd_timer
soundcore               2776  1 snd
sg                     45336  0
ps3rom                  9040  0
dm_mod                 93696  5
ps3disk                14816  3
ps3stor_lib             8040  3 ps3flash,ps3rom,ps3disk
ohci_hcd               33388  0
ehci_hcd               52132  0
usbcore               202280  6 ov534,hci_usb,usb_storage,ohci_hcd,ehci_hcd

but there is no /dev/video1...
what's wrong?
thanks.

[ao2]

I have submitted the driver for inclusion into the V4L source tree.

http://marc.info/?l=linux-video&m=121886284726264&w=2

so, i've added this patch, recompiled and installed the kernel... 2.6.28-rc4 on ps3...
ov534.ko seems to load nicely...

well, actually this is the old driver, look at more recent posts , the new one that is going to be merged in linux mailnine is this one:
http://marc.info/?l=linux-video&m=122710865923853&w=2
which depends on this patch to gspca:
http://shell.studenti.unina.it/~ospite/ ... bulk.patch

but there is no /dev/video1...
what's wrong?
thanks.

maybe you only have one video device? if so, use /dev/video0

[ps3fanboy]

maybe you only have one video device? if so, use /dev/video0

no, don't have any /dev/videoX :-(

[ps3fanboy]

@ao2:
with your patches i now have /dev/video0, thanks.

Code: Select all

lrwxrwxrwx 1 root root     6 2008-11-23 16:03 /dev/video -> video0
crw-rw---- 1 root root 81, 0 2008-11-23 16:03 /dev/video0

on to mplayer ;-)

[ps3fanboy]

one step further, but still not at the finish line :-)
i compiled mplayer on ps3, but all i get is a green box...
any help?

Code: Select all

./mplayer -vo fbdev -ao alsa -tv driver=v4l2:device=/dev/video0 tv://
MPlayer dev-SVN-r27999-4.1.2 (C) 2000-2008 MPlayer Team
AltiVec found
CPU: PowerPC

Playing tv://.
TV file format detected.
Selected driver: v4l2
 name: Video 4 Linux 2 input
 author&#58; Martin Olschewski <olschewski@zpr.uni-koeln.de>
 comment&#58; first try, more to come ;-&#41;
Selected device&#58; USB Camera-B4.04.27.1
 Capabilites&#58;  video capture  read/write  streaming
 supported norms&#58;
 inputs&#58; 0 = ov534;
 Current input&#58; 1870017843
 Current format&#58; YUYV
tv.c&#58; norm_from_string&#40;pal&#41;&#58; Bogus norm parameter, setting default.
v4l2&#58; ioctl enum norm failed&#58; Invalid argument
Error&#58; Cannot set norm!
Selected input hasn't got a tuner!
v4l2&#58; Cannot get fps
v4l2&#58; ioctl set mute failed&#58; Invalid argument
v4l2&#58; ioctl query control failed&#58; Invalid argument
v4l2&#58; ioctl query control failed&#58; Invalid argument
v4l2&#58; ioctl query control failed&#58; Invalid argument
v4l2&#58; ioctl query control failed&#58; Invalid argument
==========================================================================
Opening video decoder&#58; &#91;raw&#93; RAW Uncompressed Video
VDec&#58; vo config request - 640 x 480 &#40;preferred colorspace&#58; Packed YUY2&#41;
Could not find matching colorspace - retrying with -vf scale...
Opening video filter&#58; &#91;scale&#93;
VDec&#58; using Packed YUY2 as output csp &#40;no 0&#41;
Movie-Aspect is undefined - no prescaling applied.
SwScaler&#58; reducing / aligning filtersize 1 -> 1
SwScaler&#58; reducing / aligning filtersize 1 -> 1
SwScaler&#58; reducing / aligning filtersize 1 -> 1
SwScaler&#58; reducing / aligning filtersize 1 -> 1
&#91;swscaler @ 0x10af07f0&#93;BICUBIC scaler, from yuyv422 to rgb32 using AltiVec
&#91;swscaler @ 0x10af07f0&#93;using C scaler for horizontal scaling
&#91;swscaler @ 0x10af07f0&#93;using n-tap C scaler for vertical scaling &#40;BGR&#41;
&#91;swscaler @ 0x10af07f0&#93;using C YV12->BGR32 Converter
&#91;swscaler @ 0x10af07f0&#93;640x480 -> 640x480
VO&#58; &#91;fbdev&#93; 640x480 => 640x480 ARGB

videos play nicely with
mplayer -vo fbdev test.mpg

driver seems to be ok... except frame_rate = 0 maybe :-)

Code: Select all

usb 1-2.3: new high speed USB device using ps3-ehci-driver and address 11
usb 1-2.3: configuration #1 chosen from 1 choice
gspca: probing 1415:2000
ov534: bulk_size = 614400
ov534: frame_rate = 0
gspca: probe ok
gspca: probing 1415:2000
gspca: probing 1415:2000

[ao2]

one step further, but still not at the finish line :-)
i compiled mplayer on ps3, but all i get is a green box...
any help?

videos play nicely with
mplayer -vo fbdev test.mpg

Ah, I haven't tested it yet on PS3, I'll do this week.

driver seems to be ok... except frame_rate = 0 maybe :-)

Oh, just a misplaced print, it prints zero when using the default frame_rate=30 I'll fix that, thanks.

[jimparis]

Hi,

I am also porting the previously posted ov534 driver to gspca, a preview here.
It needs this patch on linux 2.6.28-rc series.

Regards, ao2

Poted here for review.

Hi ao2,
I finally got around to testing this driver and it seems to work pretty well :) There are some limitations (it plays fine in mplayer, but has trouble with most other applications including Skype) but it's probably not too hard to figure out why they're failing. It might be using a different resolution, for example. Nice work!

I will resubscribe to linux-video and post some comments on the driver there.

[ao2]

Hi,

I am also porting the previously posted ov534 driver to gspca, a preview here.
It needs this patch on linux 2.6.28-rc series.

Regards, ao2

Poted here for review.

Hi ao2,
I finally got around to testing this driver and it seems to work pretty well :) There are some limitations (it plays fine in mplayer, but has trouble with most other applications including Skype) but it's probably not too hard to figure out why they're failing. It might be using a different resolution, for example. Nice work!

I will resubscribe to linux-video and post some comments on the driver there.

Hi jimparis, it's great to get feedback from you.

Mplayer works fine because it can handle YUYV with no problems, other programs have to rely on libv4l (libv4lconvert) for format conversion, using the LD_PRELOAD mechanism.

About 320x240 I still have some problems using the settings from the windows driver.

[ps3fanboy]

Ah, I haven't tested it yet on PS3, I'll do this week.

any progress? thanks.

[ao2]

Ah, I haven't tested it yet on PS3, I'll do this week.

any progress? thanks.

I haven't found the time yet, but it should be a problem with usb control messages. Will post here as soon as I have something.

[jimparis]

Mplayer works fine because it can handle YUYV with no problems, other programs have to rely on libv4l (libv4lconvert) for format conversion, using the LD_PRELOAD mechanism.

My version of skype seems to be fine with YUYV (it doesn't complain), it just shows a green screen. libv4lconvert didn't help, although I only played with it a tiny bit. Not a big concern at this point.

Anyway, here's some random comments while I'm thinking about them:

First, it seems strange to call the driver "ov534" when it's really a driver for "ov534/538 + ov7720". And it's a shame there's so much repetition in v4l2 in general. For example, there's definitely some shared code between ov519 vs ov534. And there's a driver for "ov772x" and another driver for "ov7x20" -- seems we should be able to use at least one of those for the sensor part in the PS Eye.

On the other hand, they don't necessarily expose everything we'd want (like clock control), and I'd be hesitant to go modifying the common code because of other devices we'd break. Maybe it's better to just keep the pseye driver standalone.

Code: Select all

        ov534_reg_write(udev, 0x1c, 0x00);
        ov534_reg_write(udev, 0x1d, 0x40);
        ov534_reg_write(udev, 0x1d, 0x02);
        ov534_reg_write(udev, 0x1d, 0x00);
        ov534_reg_write(udev, 0x1d, 0x02);  // frame_h
        ov534_reg_write(udev, 0x1d, 0x57);  // frame_m
        ov534_reg_write(udev, 0x1d, 0xff);  // frame_l

These are indirect writes that set the ov534 frame size.
frame_size = ((frame_h << 16) + (frame_m << 8) + (frame_l)) * 4 = 0x0257ff * 4 = 614396
That's .sizeimage-4. I think setting this to 0x025800 would stop dropping the last 2 pixels, and you'd need to change it for 320x240.

Code: Select all

        switch (sd->frame_rate) {
        case 50:
                sccb_reg_write(gspca_dev->dev, 0x11, 0x01);
                sccb_check_status(gspca_dev->dev);
                sccb_reg_write(gspca_dev->dev, 0x0d, 0x41);
                sccb_check_status(gspca_dev->dev);
                ov534_reg_verify_write(gspca_dev->dev, 0xe5, 0x02);
                break;

The sccb_check_status should be unnecessary, sccb_reg_write does it already.

We could be smarter with the clock rates here. I've almost figured them out, and we can support more flexible framerates if we do. We'll need different numbers here based on the capture resolution. I'm not sure how to best work that into v4l2 though. The module option is easy, but it seems v4l2 has some frame rate enumeration stuff that could be used (v4l2_frmivalenum).

Same with resolution and pixel formats. We should be able to support a lot more than just YUYV and 640x480 and 320x240, and I think I can figure out some of that at the hardware level, I just don't know how to fit it into v4l2/gspca.

[ao2]

Anyway, here's some random comments while I'm thinking about them:

First, it seems strange to call the driver "ov534" when it's really a driver for "ov534/538 + ov7720". And it's a shame there's so much repetition in v4l2 in general. For example, there's definitely some shared code between ov519 vs ov534. And there's a driver for "ov772x" and another driver for "ov7x20" -- seems we should be able to use at least one of those for the sensor part in the PS Eye.

On the other hand, they don't necessarily expose everything we'd want (like clock control), and I'd be hesitant to go modifying the common code because of other devices we'd break. Maybe it's better to just keep the pseye driver standalone.

I had the exact thoughts, it's better to have a standalone driver for the time being, maybe even copying and pasting code from "ov772x". The current v4l infrastructure doesn't allow to share sensor drivers easily.

As I wrote on v4l mailing list a couple of times I think that at least the abstractions "bridge", "control protocol" and "sensor" should be added.

Code: Select all

        ov534_reg_write(udev, 0x1c, 0x00);
        ov534_reg_write(udev, 0x1d, 0x40);
        ov534_reg_write(udev, 0x1d, 0x02);
        ov534_reg_write(udev, 0x1d, 0x00);
        ov534_reg_write(udev, 0x1d, 0x02);  // frame_h
        ov534_reg_write(udev, 0x1d, 0x57);  // frame_m
        ov534_reg_write(udev, 0x1d, 0xff);  // frame_l

These are indirect writes that set the ov534 frame size.
frame_size = ((frame_h << 16) + (frame_m << 8) + (frame_l)) * 4 = 0x0257ff * 4 = 614396
That's .sizeimage-4. I think setting this to 0x025800 would stop dropping the last 2 pixels, and you'd need to change it for 320x240.

Ah, good. Actually only the last pixel (yuyv, 4 bytes) is dropped, and now we can have it back, great! I'll try adding also 320x240 following your advice.

Code: Select all

        switch (sd->frame_rate) {
        case 50:
                sccb_reg_write(gspca_dev->dev, 0x11, 0x01);
                sccb_check_status(gspca_dev->dev);
                sccb_reg_write(gspca_dev->dev, 0x0d, 0x41);
                sccb_check_status(gspca_dev->dev);
                ov534_reg_verify_write(gspca_dev->dev, 0xe5, 0x02);
                break;

The sccb_check_status should be unnecessary, sccb_reg_write does it already.

ok

We could be smarter with the clock rates here. I've almost figured them out, and we can support more flexible framerates if we do. We'll need different numbers here based on the capture resolution. I'm not sure how to best work that into v4l2 though. The module option is easy, but it seems v4l2 has some frame rate enumeration stuff that could be used (v4l2_frmivalenum).

Are you using the windows driver as reference?
Or just guessing from your original usb logs?

Same with resolution and pixel formats. We should be able to support a lot more than just YUYV and 640x480 and 320x240, and I think I can figure out some of that at the hardware level, I just don't know how to fit it into v4l2/gspca.

I think I can do the linux part.

What about switching this discussion to emails? vl4 mailing list would be OK to me, quoting properly on forums is quite stressing :)

[jimparis]

We could be smarter with the clock rates here. I've almost figured them out, and we can support more flexible framerates if we do. We'll need different numbers here based on the capture resolution. I'm not sure how to best work that into v4l2 though. The module option is easy, but it seems v4l2 has some frame rate enumeration stuff that could be used (v4l2_frmivalenum).

Are you using the windows driver as reference?
Or just guessing from your original usb logs?

A combination of logs and different references,
chip docs for similar chips, etc. :)

What about switching this discussion to emails? vl4 mailing list would be OK to me, quoting properly on forums is quite stressing :)

OK, agreed. :)
I might still post some reverse engineering stuff here while it's still just a guess, but sure, I'll get involved in driver discussions there.

[ao2]

one step further, but still not at the finish line :-)
i compiled mplayer on ps3, but all i get is a green box...
any help?

found the problem, a solution will be posted soon.

[ps3fanboy]

one step further, but still not at the finish line :-)
i compiled mplayer on ps3, but all i get is a green box...
any help?

found the problem, a solution will be posted soon.

great, looking forward to it...

[jimparis]

Mplayer works fine because it can handle YUYV with no problems, other programs have to rely on libv4l (libv4lconvert) for format conversion, using the LD_PRELOAD mechanism.

My version of skype seems to be fine with YUYV (it doesn't complain), it just shows a green screen. libv4lconvert didn't help, although I only played with it a tiny bit.

I got it working with Skype. It was a silly mistake: I need to use v4l2convert.so, not libv4lconvert.so.

Code: Select all

$ LD_PRELOAD=/usr/lib32/libv4l/v4l2convert.so ./skype

[ps3fanboy]

one step further, but still not at the finish line :-)
i compiled mplayer on ps3, but all i get is a green box...
any help?

found the problem, a solution will be posted soon.

please define soon... before xmas, after xmas, in 1 year, 10 years? :-)

[ao2]

one step further, but still not at the finish line :-)
i compiled mplayer on ps3, but all i get is a green box...
any help?

found the problem, a solution will be posted soon.

please define soon... before xmas, after xmas, in 1 year, 10 years? :-)

Sorry for the delay.

With the latest code from http://linuxtv.org/hg/~jfrancois/gspca/ it works on PS3.
Clone the repository using mercurial:

Code: Select all

hg clone http://linuxtv.org/hg/~jfrancois/gspca/

and then

Code: Select all

make && make install

[ps3fanboy]

it really works, that's great, thanks!

now on to the next question:
what's the best way to read the video stream from an app?
just open /dev/video, read the bytes and save them in an mpeg2 file?

[ao2]

it really works, that's great, thanks!

now on to the next question:
what's the best way to read the video stream from an app?
just open /dev/video, read the bytes and save them in an mpeg2 file?

see v4l2-apps/test/capture_example.c in the repository you cloned, mmap is the recommender way AFAIK.

mencoder does the job tho, and I think that you can have some fun with motion too.

[ps3fanboy]

thanks ao2.
i compiled and ran the capture_example, specified /dev/video0, 1 frame, output to stdout, redirected the output to a file.... and get a file of about 600 kb size.
so far, so good :-)
but which format is it? any chance i can view it with an image viewer, maybe gimp?

[ao2]

thanks ao2.
i compiled and ran the capture_example, specified /dev/video0, 1 frame, output to stdout, redirected the output to a file.... and get a file of about 600 kb size.
so far, so good :-)
but which format is it? any chance i can view it with an image viewer, maybe gimp?

It is raw YUYV, if you don't know what to do with it then you don't need it :)
jokes apart, I think you can convert it using 'yuvtoppm' from netpbm, but I can't try right now.

[ps3fanboy]

thanks ao2.
i compiled and ran the capture_example, specified /dev/video0, 1 frame, output to stdout, redirected the output to a file.... and get a file of about 600 kb size.
so far, so good :-)
but which format is it? any chance i can view it with an image viewer, maybe gimp?

It is raw YUYV, if you don't know what to do with it then you don't need it :)
jokes apart, I think you can convert it using 'yuvtoppm' from netpbm, but I can't try right now.

thanks, i thought it was some sort of yuv and already tried the elecard viewer and was able to see some blurry picture :-)

[ps3fanboy]

thanks ao2.
i compiled and ran the capture_example, specified /dev/video0, 1 frame, output to stdout, redirected the output to a file.... and get a file of about 600 kb size.
so far, so good :-)
but which format is it? any chance i can view it with an image viewer, maybe gimp?

It is raw YUYV, if you don't know what to do with it then you don't need it :)
jokes apart, I think you can convert it using 'yuvtoppm' from netpbm, but I can't try right now.

thanks, i thought it was some sort of yuv and already tried the elecard viewer and was able to see some blurry picture :-)

added a little yuyv to rgb converter and voila can see the image with gimp :-)
thanks for the help!

[patsu]

I just installed YDL 6.1. Where do I get the library and driver to interact with PS Eye ? Would like to experiment during the 1 week break. Thanks in advance for any pointers !

[ps3fanboy]

With the latest code from http://linuxtv.org/hg/~jfrancois/gspca/ it works on PS3.
Clone the repository using mercurial:

Code: Select all

hg clone http://linuxtv.org/hg/~jfrancois/gspca/

and then

Code: Select all

make && make install

[ps3fanboy]

@ao2:
my app and dirver works, but dmesg shows:

Code: Select all

usb 1-2.3: new high speed USB device using ps3-ehci-driver and address 8
usb 1-2.3: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
gspca: main v2.4.0 registered
gspca: probing 1415:2000
ov534: sensor is ov7721
ov534: frame_rate: 30
gspca: probe ok
gspca: probing 1415:2000
gspca: probing 1415:2000
usbcore: registered new interface driver ov534
ov534: registered
compat_ioctl32: VIDIOC_ENUMINPUT
ioctl32(powerpc-linux-s:3542): Unknown cmd fd(9) cmd(c050561a){t:'V';sz:80} arg(ffef5dc8) on /dev/video0
compat_ioctl32: VIDIOC_ENUMSTD
ioctl32(powerpc-linux-s:3542): Unknown cmd fd(9) cmd(c0485619){t:'V';sz:72} arg(ffef5d80) on /dev/video0

looks like the driver doesn't support 2 ioctls... or I am missing something here...

also... is it the driver or my app? the stream quality is not quite stellar...
looks like the stream is slightly flickering... like water waves... i know... it's really hard to describe... thanks.

[jimparis]

Are you running 32-bit userspace and 64-bit kernel on PPC? I don't know if that's been tested extensively, looks like you're hitting some problem with the compat_ioctl32 stuff. Have you tried other applications that are known to work on other platforms (e.g. mplayer)?