Display HP S410u possible workling with RaspberryPi
i've an Display HP S140u (DL 41xx). I would like to use this display on a RaspberryPi 2. Currently, I've translated dkms to evdi module. The udev.rules are installed, and the modules are successfully loaded. At the moment, i´ve got no alternative for the "DisplayManager".
According to the description, the firmware should not be the problem? Debug output: Quote:
Quote:
|
After testing this, i've loaded the udl and the evdi module. The LED of this display, blinked white for 1 second.
lsusb: Code:
Bus 001 Device 004: ID 17e9:ff06 DisplayLink Code:
evdi 43794 0 Has anyone got an idea to get the ad running on a Raspberry or ARM platform? |
These are your options:
1. Hope that DisplayLink releases the DisplayLinkManager code as open source 2. Hope that DisplayLink releases a DisplayLinkManager build for ARM 3. Hope that someone is able to reverse engineer the protocol for these devices and write their own (hopefully open source) driver. That's all you can do. DisplayLink has not been doing well at all when it comes to supporting Linux users IMO. |
is it possible that DisplayLink will support ARM in the near future?
Especially in the ARM environment, there are many solutions that may work very fine with such a display. At my company we have already installed & configured such a display. |
tl;dr: no compatible ARM platform found yet, except for Chromebooks and Android devices.
The main use case we'd like to enable is being able to extend screens - to be able to use multiple monitors simultaneously. While DisplayLinkManager can be compiled for ARM (and in fact it already has been compiled for ARM; there are Chromebooks which use ARM binary of DLM, as well as our Android app), that's not all you need. We have not yet seen an ARM based platform which would support cross-device DRM prime support well (necessary to use output offloading, think xrandr --setprovideroutputsource ...). This is required for evdi to get pixels that we display on a device. Last time I tried, Raspberry Pi was almost there - with Eric Anholt's experimental vc4 module for the GPU. However, I only managed to use one screen at a time - i.e. only DisplayLink-connected screen was operable, not the built-in HDMI. Other devices I tried (e.g. BBB) didn't even get close to this. You could argue that certain use cases would be fine with just accessing a plain framebuffer through /dev/fbX - so, legacy fbdev interface. Sadly, neither UDL nor evdi don't support this mode anymore - last driver that did was pre-DRM legacy driver "udlfb" - which only supported USB2.0-era devices. If someone confirms he's successful with second screen driven by UDL on any ARM-based platform, configured in a way that both screens can be used - both the built-in and UDL-driven, I think we'd be happy to release ARM binary of DLM for use with evdi. Regards, Michal |
Thanks for the note.
After some testing this , i got some problems with the new kernel. At the first bootup the "rainbowscreen" comes up too. The kernel 4.9.0-rc2 works _not_ fine. I`ve builded the kernel 4.4.26 (stable) and the newest versions from the extra modules e.g. libdrm, mesa, xserver, evdev .. After this, i activated experimental opengl (vc4) and rebooted the system - works fine. The output from glxgears -info Code:
Running synchronized to the vertical refresh. The framerate should be Code:
Module Size Used by I need this display as the primary (standalone) display on my RaspberryPi2 (raspian jessie). Has anyone some experience to get the display working on an rasperrypi? |
See, but that's just half way through. The only thing that changed so far is using a DRM-compatible module for the built-in GPU (vc4).
Now, the trick is to add `udl` (for older devices) or evdi (for newer) on top of that, and call `xrandr --setprovideroutputsource ...`. So - what you could do now is to try to build evdi (I remember I used rpi-update and rpi-source combo for getting kernel sources and building the module afterwards). Then, despite lacking DLM, you can try to build and run monitorsim from here. Alternatively, if you have an older device that can be driven with UDL, try this instead. If everything works, meaning that you still get to see the main HDMI output, plus additionally you see the second screen (in a window, in case of monitorsim), please do report back. Note: I'd recommend to experiment via ssh. Fingers crossed! Cheers, Michal |
Hi Michal,
i've built the evdi module and it works fine. here is the output from lsmod: Code:
#lsmod | grep evdi After 'make install' the build breaks up with the following message: Code:
make install Best regards Michael |
Hi,
You need a C++14 compliant compiler. For the reasons I can't fully understand you sometimes must pass CXX flags manually, as cmake setting that I think should work doesn't :) Have a look at https://github.com/mlukaszek/evdipp/...er/.travis.yml - this is the configuration for Travis CI. I was forced to run cmake with -DCMAKE_CXX_FLAGS="-std=c++14" as you'll see. Cheers, Michal |
Hi Michal,
i've built the evdipp package without errors. After reboot and plug in the HP s140u Monitor and type "sudo monitorsim EDIDv1_1600x900" a new clear window opened and after 10 seconds the window closed automatically. The output of the terminal window is at follows: Code:
pi@raspberrypi:~ $ sudo monitorsim EDIDv1_1600x900 Please i need some help and i havent any ideas anymore. Best regards Michael |
All times are GMT. The time now is 03:30 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.