VoDisplay SDK for RasPi/Linux x86/amd64?

[STrRedWolf]

So I got two VoDisplays, since I was excited about a display which we could control over USB and the protocol would be relatively open, and I could maybe make a kernel framebuffer driver on it. At the very least, it wouldn't go on the VoCore 2's I have -- I would put it on my Linux amd64 systems to make a bit of a status display.

Hey, it beats having to work with an SPI display and an Arduino serving as a driver.

I pulled the VoDisplay SDK... and saw the MIPS compiled library and the Mac dynlib library. In other words, it's near useless.

Any chance I can get the library source, so we can try it out on regular PCs and also Raspberry Pi's?

Meanwhile, I'm 3D printing a small case for it. STL files soon.

==================admin: combine

Is there a way we can get the VoDisplay SDK for the Raspberry Pi or regular Linux on PC? I want to use the display on my main Gentoo rig.

Having the source opened up will help as well.

I'm designing a 3D printed case/stand for it right now.

[Vonger]

Will have. Just update SDK with linux64 driver for PC.
tomorrow I will add raspberrypi driver.

[Vonger]

later win64/win32 and etc...

[STrRedWolf]

Hmm... this needs to be run as root user to work. That's... troubling. You shouldn't need root to do that. This needs some udev rules.

I'll dig into it once I get my Gentoo Linux system updated and get some tools back on it. I'd love to help out here.

[Vonger]

Hmm... this needs to be run as root user to work. That's... troubling. You shouldn't need root to do that. This needs some udev rules.

I'll dig into it once I get my Gentoo Linux system updated and get some tools back on it. I'd love to help out here.

That is libusb require that, if there is anyway to avoid that, is the best. we just need the driver upload the firmware to screen and usb transfer data.

[STrRedWolf]

Finally got time to work this out. For "just get it working" access, put the following in /etc/udev/rules.d/98-vocore.rules:

Code: Select all

SUBSYSTEM=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="8613", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="1004", MODE="0666"


Then save it and execute:

Code: Select all

udevadm control --reload-rules

Plug in your VoDisplay (unplug it if it's plugged in first) and you'll be able to run ./vodisp as any person.

For a more secure way, put the intended user in the "video" group (use "usermod -a -G video usernamehere") and use the below:

Code: Select all

SUBSYSTEM=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="8613", MODE="0660", GROUP="video"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="1004", MODE="0660", GROUP="video"


Even more security can be have by dedicating a user to the VoDisplay, and writing up a display server... but that is left as an exercise to the reader.

[ameridroid]

I can run ./vodisp on my ARM Linux system and it displays a screen with the VoCore logo. Does anyone know how I can send it other data?

[Vonger]

I can run ./vodisp on my ARM Linux system and it displays a screen with the VoCore logo. Does anyone know how I can send it other data?

You can check the API, there is one vodisp_write_frame, actually it is directly write data to USB port by bulk mode, pixel format RGBRGB..., that's all.

[ameridroid]

If I'm not a C programmer, is there a way for me to send data to be displayed?

[ameridroid]

I just found the answer for displaying a single frame on Linux:

sudo ./vodisp bitmap t1.bmp

Is the "framebuffer" option for video? If so, what video format is supported?