-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manager desktop #12
Comments
This driver is only a prove of concept from Fresco Logic, with no DRM support
currently only a DRM concept with no further functionality. |
I'm trying to add DRM using https://github.com/DisplayLink/evdi to this driver but I couldn't even get the monitor to display a static image maybe my unit is faulty, it is a little funky even on Windows. @ulli-kroll your last commit on your fork causes system wide hangup when closing /dev/fl2000-X |
@CanNuhlar For the fork of FL2000 The output above if from my drm branch, which if (of course) in not working state.
what is still missing And the last one is, as I said before a challenging work. |
@ulli-kroll Yeah of course, I wasn't expecting a fully working version just wanted to let you know. From the evdi page: "The Extensible Virtual Display Interface (EVDI) is a Linux® kernel module that enables management of multiple screens, allowing user-space programs to take control over what happens with the image. It is essentially a virtual display you can add, remove and receive screen updates for, in an application that uses the libevdi library." This is a part of the ubuntu usb displaylink vga converter driver. I've compiled it inserted the module into the kernel and it lists itself as a provider on xrandr, so I thought maybe we can use libevdi library to "redirect" desktop image to the device itself using fl2000 driver as it is. Btw, i am quite new to this kernel programming stuff, I have only therotical information that I've been taught on the University so I might be completely wrong. |
hope this makes sense Signed-off-by: Hans Ulli Kroll <ulli.kroll@googlemail.com>
@ulli-kroll What exactly would be involved in 'testing' and 'reviewing'? Perhaps a way for users to 'dial in' the hsync/vsync settings and report back their findings would help? I don't know much about video - how can I test fb transfer? are you just testing buffer sizes? |
My biggest problem is not hsync/vsync It's data transfer and how to get this really big huge amount of data to the device. For full hd aka 1920 * 1080 you need to transfer ~ 6MByte for each frame It ist possible to reduce the data
For testing I use 1378 * 768 |
FWIW:
Note here the debugfs output from the driver, 29 frames per second
And for those who want to know, something crazy |
Would you mind commiting these changes to your fork as it is? @ulli-kroll |
If you want a driver which is
|
I don't want a driver I just want the see its code at its current state. So I'm totally okay with all that. |
@ulli-kroll it's probably a question for the devs but there must be a way to do it since it works on Windows |
In which way ? This chip supports natively VGA output. Also the I2C is aligned to 32bit wide data transfers for read and write. Some small note about I2C So you must readout the EDID (around 1024 bytes) from HDMI/DVI trough one 8bit register Other thing I have done some tests with my APU (some AMD T40E SoC). |
@ulli-kroll just the advertised features as listed here http://www.frescologic.com/product/single/fl2000/ I don't understand the hardware details (but definitely useful to others who do), just that it relies on the high data rate of USB3 (the dev also mentioned this) for it to work |
hi my post is not a problem but is question for use this driver (fl2000.ko) on linux...
with success make it and insmod this driver and i test it success,
but use this driver in Linux it's possible?
your know some program for use this in "normal mode" normal mirror desktop and others?
I understand perfectly that this repository for driver and testing on Linux.
but in addition to testing there were additions on linux?
thanks for reading
The text was updated successfully, but these errors were encountered: