Re: Pluggable frame buffer devices
Hello I have an AOC e2251fwu monitor which I have used under debian using libdlo with success in the past. I have used the same driver under OpenBSD for testing purpose only with "make check" and it's rendering the test on the attached monitor. I have spend one week and trying to figure out how to make the monitor work under FreeBSD. I have recompile the kernel using you're support for the udl.c and loaded the module in the kernel. kldstat: Id Refs AddressSize Name 41 0x81fd6000 9e20 udl.ko 52 0x81fe 71b0 videomode.ko I have installed the xf86-video-scfb from the ports. And I'm stuck, can't figure out why in the dmsg the adapter is still recognize as a generic usb device shouldn't the drivers kicked in at this point making the monitor available as a framebuffer adapter in /dev ? dmsg | grep DisplayLink ugen2.3: at usbus2 Can you please provide some instructions regarding the steps involved in making this monitor work? Thank you. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Pluggable-frame-buffer-devices-tp5989022p6017846.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On 03/11/15 01:58, Shawn Webb wrote: On Monday, March 09, 2015 08:25:05 AM Shawn Webb wrote: On Sat, 2015-03-07 at 21:57 +0100, Hans Petter Selasky wrote: Hi Shawn, I've just put some more pieces into the kernel. https://svnweb.freebsd.org/changeset/base/279752 https://svnweb.freebsd.org/changeset/base/279753 Can you give the current code a spin? To get X.org/X11 working simply create a config file under /usr/local/etc/X11/xorg.conf.d which contains the device section given by "man xf86-video-scfb". Open issues: - Restoring the frame buffer does not always work. I looks like the restored text console size is 1x1 afterwards. At least there is no panic. And you can re-plug the UDL device again. - You need to unplug the UDL device before rebooting. - UDL device must be connected to a monitor before you plug it to USB, or you can load/unload the driver to re-probe the video format. --HPS Sorry for the silence on my part. I've been quite busy. I hope to test out the recent commits over the week and report back by Friday or Saturday. Thanks, Shawn Still no go. Xorg fails to even start. It doesn't even know that my DisplayLink device is plugged in (which it was even before boot). I'm getting USB timeout errors on that device only. Thanks, Can you show the error messages when you plug your device? Also, what USB controllers do you have? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On Monday, March 09, 2015 08:25:05 AM Shawn Webb wrote: > On Sat, 2015-03-07 at 21:57 +0100, Hans Petter Selasky wrote: > > Hi Shawn, > > > > I've just put some more pieces into the kernel. > > > > https://svnweb.freebsd.org/changeset/base/279752 > > https://svnweb.freebsd.org/changeset/base/279753 > > > > Can you give the current code a spin? > > > > To get X.org/X11 working simply create a config file under > > /usr/local/etc/X11/xorg.conf.d which contains the device section given > > by "man xf86-video-scfb". > > > > Open issues: > > > > - Restoring the frame buffer does not always work. I looks like the > > restored text console size is 1x1 afterwards. At least there is no > > panic. And you can re-plug the UDL device again. > > > > - You need to unplug the UDL device before rebooting. > > > > - UDL device must be connected to a monitor before you plug it to USB, > > or you can load/unload the driver to re-probe the video format. > > > > --HPS > > Sorry for the silence on my part. I've been quite busy. I hope to test > out the recent commits over the week and report back by Friday or > Saturday. > > Thanks, > > Shawn Still no go. Xorg fails to even start. It doesn't even know that my DisplayLink device is plugged in (which it was even before boot). I'm getting USB timeout errors on that device only. Thanks, -- Shawn Webb HardenedBSD GPG Key ID:0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: This is a digitally signed message part.
Re: Pluggable frame buffer devices
On Sat, 2015-03-07 at 21:57 +0100, Hans Petter Selasky wrote: > Hi Shawn, > > I've just put some more pieces into the kernel. > > https://svnweb.freebsd.org/changeset/base/279752 > https://svnweb.freebsd.org/changeset/base/279753 > > Can you give the current code a spin? > > To get X.org/X11 working simply create a config file under > /usr/local/etc/X11/xorg.conf.d which contains the device section given > by "man xf86-video-scfb". > > Open issues: > > - Restoring the frame buffer does not always work. I looks like the > restored text console size is 1x1 afterwards. At least there is no > panic. And you can re-plug the UDL device again. > > - You need to unplug the UDL device before rebooting. > > - UDL device must be connected to a monitor before you plug it to USB, > or you can load/unload the driver to re-probe the video format. > > --HPS Sorry for the silence on my part. I've been quite busy. I hope to test out the recent commits over the week and report back by Friday or Saturday. Thanks, Shawn signature.asc Description: This is a digitally signed message part
Re: Pluggable frame buffer devices
Hi Shawn, I've just put some more pieces into the kernel. https://svnweb.freebsd.org/changeset/base/279752 https://svnweb.freebsd.org/changeset/base/279753 Can you give the current code a spin? To get X.org/X11 working simply create a config file under /usr/local/etc/X11/xorg.conf.d which contains the device section given by "man xf86-video-scfb". Open issues: - Restoring the frame buffer does not always work. I looks like the restored text console size is 1x1 afterwards. At least there is no panic. And you can re-plug the UDL device again. - You need to unplug the UDL device before rebooting. - UDL device must be connected to a monitor before you plug it to USB, or you can load/unload the driver to re-probe the video format. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On 02/21/15 23:59, Shawn Webb wrote: On Friday, February 20, 2015 09:29:20 AM Hans Petter Selasky wrote: On 02/20/15 02:15, Shawn Webb wrote: On Thursday, February 19, 2015 07:04:50 PM Shawn Webb wrote: On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: Hi, I've added support for USB display link adapters to FreeBSD-11-current, but the kernel panics once "vt_fb_attach(info)" is called from "fbd_register(struct fb_info* info)" when the USB device is plugged or udl.ko is loaded. Is this a known issue? REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c --HPS I just bought a DisplayLink adapter that's compatible. Compiling a new kernel with device udl brings this error: Hi, You need to also build the "sys/modules/videomode" and install and kldload. Does your device need a power supply? Can you plug the device through an external USB HUB after boot? Also you need some VT patches, before it will attach to VT which I can send you. See attachment. Beware the unplugging the device is not supported. It will crash / panic which needs to be resolved. --HPS (FYI: I'm switching email accounts from latt...@gmail.com to shawn.w...@hardenedbsd.org) So I'm a little unsure how to test this. Could you provide some instructions? I bought this device: http://www.iogear.com/support/dm/driver/GUC2020DW6 It's listed in udl.c as supported: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c?revision=278852&view=markup#l151 What kind of setup should I have in my xorg.conf to tell xorg to use that instead of the built-in laptop display? Can you provide an example xorg.conf? Xorg config is here: http://pastebin.com/W9yPBvcR I'll see if I can put the rest of the patches in place this week, so that it will be more easy for you. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On Friday, February 20, 2015 09:29:20 AM Hans Petter Selasky wrote: > On 02/20/15 02:15, Shawn Webb wrote: > > On Thursday, February 19, 2015 07:04:50 PM Shawn Webb wrote: > >> On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: > >>> Hi, > >>> > >>> I've added support for USB display link adapters to FreeBSD-11-current, > >>> but the kernel panics once "vt_fb_attach(info)" is called from > >>> "fbd_register(struct fb_info* info)" when the USB device is plugged or > >>> udl.ko is loaded. Is this a known issue? > >>> > >>> REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c > >>> > >>> --HPS > >> > >> I just bought a DisplayLink adapter that's compatible. Compiling a new > > >> kernel with device udl brings this error: > Hi, > > You need to also build the "sys/modules/videomode" and install and kldload. > > Does your device need a power supply? > > Can you plug the device through an external USB HUB after boot? > > Also you need some VT patches, before it will attach to VT which I can > send you. See attachment. > > Beware the unplugging the device is not supported. It will crash / panic > which needs to be resolved. > > --HPS (FYI: I'm switching email accounts from latt...@gmail.com to shawn.w...@hardenedbsd.org) So I'm a little unsure how to test this. Could you provide some instructions? I bought this device: http://www.iogear.com/support/dm/driver/GUC2020DW6 It's listed in udl.c as supported: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c?revision=278852&view=markup#l151 What kind of setup should I have in my xorg.conf to tell xorg to use that instead of the built-in laptop display? Can you provide an example xorg.conf? -- Shawn Webb HardenedBSD GPG Key ID:0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: This is a digitally signed message part.
Re: Pluggable frame buffer devices
On 02/20/15 02:15, Shawn Webb wrote:
On Thursday, February 19, 2015 07:04:50 PM Shawn Webb wrote:
On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote:
Hi,
I've added support for USB display link adapters to FreeBSD-11-current,
but the kernel panics once "vt_fb_attach(info)" is called from
"fbd_register(struct fb_info* info)" when the USB device is plugged or
udl.ko is loaded. Is this a known issue?
REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c
--HPS
I just bought a DisplayLink adapter that's compatible. Compiling a new
kernel with device udl brings this error:
Hi,
You need to also build the "sys/modules/videomode" and install and kldload.
Does your device need a power supply?
Can you plug the device through an external USB HUB after boot?
Also you need some VT patches, before it will attach to VT which I can
send you. See attachment.
Beware the unplugging the device is not supported. It will crash / panic
which needs to be resolved.
--HPS
diff --git a/sys/dev/fb/fbd.c b/sys/dev/fb/fbd.c
index f9b4d8e..11cb30e 100644
--- a/sys/dev/fb/fbd.c
+++ b/sys/dev/fb/fbd.c
@@ -51,6 +51,9 @@ __FBSDID("$FreeBSD$");
#include
#include
+#include
+#include
+
#include "fb_if.h"
LIST_HEAD(fb_list_head_t, fb_list_entry) fb_list_head =
@@ -167,14 +170,21 @@ fb_mmap(struct cdev *dev, vm_ooffset_t offset, vm_paddr_t *paddr, int nprot,
info = dev->si_drv1;
- if ((info->fb_flags & FB_FLAG_NOMMAP) || info->fb_pbase == 0)
+ if (info->fb_flags & FB_FLAG_NOMMAP)
return (ENODEV);
-
- if (offset < info->fb_size) {
+ if (offset >= info->fb_size)
+ return (EINVAL);
+ if (info->fb_pbase == 0) {
+ /*
+ * If there is no physical address
+ * assume there is a virtual address
+ * which is mappable:
+ */
+ *paddr = vtophys((uint8_t *)info->fb_vbase + offset);
+ } else {
*paddr = info->fb_pbase + offset;
- return (0);
}
- return (EINVAL);
+ return (0);
}
static int
@@ -354,5 +364,6 @@ devclass_t fbd_devclass;
DRIVER_MODULE(fbd, fb, fbd_driver, fbd_devclass, 0, 0);
DRIVER_MODULE(fbd, drmn, fbd_driver, fbd_devclass, 0, 0);
+DRIVER_MODULE(fbd, udl, fbd_driver, fbd_devclass, 0, 0);
MODULE_VERSION(fbd, 1);
diff --git a/sys/dev/vt/hw/fb/vt_fb.c b/sys/dev/vt/hw/fb/vt_fb.c
index 5a0fe4f..bd1b881 100644
--- a/sys/dev/vt/hw/fb/vt_fb.c
+++ b/sys/dev/vt/hw/fb/vt_fb.c
@@ -37,10 +37,14 @@ __FBSDID("$FreeBSD$");
#include
#include
#include
+
#include
#include
#include
+#include
+#include
+
static struct vt_driver vt_fb_driver = {
.vd_name = "fb",
.vd_init = vt_fb_init,
@@ -135,7 +139,7 @@ vt_fb_mmap(struct vt_device *vd, vm_ooffset_t offset, vm_paddr_t *paddr,
return (ENODEV);
if (offset >= 0 && offset < info->fb_size) {
- *paddr = info->fb_pbase + offset;
+ *paddr = vtophys(info->fb_vbase + offset);
#ifdef VM_MEMATTR_WRITE_COMBINING
*memattr = VM_MEMATTR_WRITE_COMBINING;
#endif
@@ -423,7 +427,7 @@ vt_fb_init(struct vt_device *vd)
if (info->fb_size == 0)
return (CN_DEAD);
- if (info->fb_pbase == 0)
+ if (info->fb_pbase == 0 && info->fb_vbase == 0)
info->fb_flags |= FB_FLAG_NOMMAP;
if (info->fb_cmsize <= 0) {
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On Thursday, February 19, 2015 07:04:50 PM Shawn Webb wrote: > On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: > > Hi, > > > > I've added support for USB display link adapters to FreeBSD-11-current, > > but the kernel panics once "vt_fb_attach(info)" is called from > > "fbd_register(struct fb_info* info)" when the USB device is plugged or > > udl.ko is loaded. Is this a known issue? > > > > REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c > > > > --HPS > > I just bought a DisplayLink adapter that's compatible. Compiling a new > kernel with device udl brings this error: > > -- > > >>> stage 3.2: building everything > > -- > linking kernel.debug > udl.o: In function `udl_attach': > /usr/src/sys/dev/usb/video/udl.c:(.text+0xa07): undefined reference to > `edid_parse' > /usr/src/sys/dev/usb/video/udl.c:(.text+0xa0f): undefined reference to > `edid_print' > --- kernel.debug --- > *** [kernel.debug] Error code 1 > > Thanks, > > Shawn I got it building. I had to add "device videomode" to my kernel as well. It looks like when I plug in the device I bought, identifying the device just stalls out. Log posted below: [3] uhub3: on usbus2 [3] ugen1.2: at usbus1 [3] uhub4: on usbus1 [3] uhub4: 6 ports with 6 removable, self powered [3] ugen0.3: at usbus0 [4] Root mount waiting for: usbus2 usbus0 [5] Root mount waiting for: usbus2 usbus0 [6] Root mount waiting for: usbus2 usbus0 [6] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [7] Root mount waiting for: usbus2 usbus0 [7] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [8] uhub_attach: Getting USB 2.0 HUB descriptor failed,error=USB_ERR_TIMEOUT [8] device_attach: uhub3 attach returned 6 [8] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [9] Root mount waiting for: usbus0 [10] Root mount waiting for: usbus0 [10] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [10] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [11] Root mount waiting for: usbus0 [11] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [12] Root mount waiting for: usbus0 [12] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [13] Root mount waiting for: usbus0 [14] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [14] Root mount waiting for: usbus0 [14] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [14] ugen0.4: at usbus0 (disconnected) [14] uhub_reattach_port: could not allocate new device [15] Root mount waiting for: usbus0 [16] Root mount waiting for: usbus0 [17] Root mount waiting for: usbus0 [18] Root mount waiting for: usbus0 [19] Root mount waiting for: usbus0 [20] Root mount waiting for: usbus0 [21] usbd_setup_device_desc: getting device descriptor at addr 4 failed, USB_ERR_TIMEOUT [21] usbd_req_re_enumerate: addr=4, set address failed! (USB_ERR_IOERROR, ignored) signature.asc Description: This is a digitally signed message part.
Re: Pluggable frame buffer devices
On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: > Hi, > > I've added support for USB display link adapters to FreeBSD-11-current, > but the kernel panics once "vt_fb_attach(info)" is called from > "fbd_register(struct fb_info* info)" when the USB device is plugged or > udl.ko is loaded. Is this a known issue? > > REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c > > --HPS I just bought a DisplayLink adapter that's compatible. Compiling a new kernel with device udl brings this error: -- >>> stage 3.2: building everything -- linking kernel.debug udl.o: In function `udl_attach': /usr/src/sys/dev/usb/video/udl.c:(.text+0xa07): undefined reference to `edid_parse' /usr/src/sys/dev/usb/video/udl.c:(.text+0xa0f): undefined reference to `edid_print' --- kernel.debug --- *** [kernel.debug] Error code 1 Thanks, Shawn signature.asc Description: This is a digitally signed message part.
Re: Pluggable frame buffer devices
On Mon, Feb 16, 2015 at 06:10:22PM +0100, Hans Petter Selasky wrote: > On 02/16/15 16:39, Shawn Webb wrote: > > On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: > >> Hi, > >> > >> I've added support for USB display link adapters to FreeBSD-11-current, > >> but the kernel panics once "vt_fb_attach(info)" is called from > >> "fbd_register(struct fb_info* info)" when the USB device is plugged or > >> udl.ko is loaded. Is this a known issue? > >> > >> REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c > >> > >> --HPS > > > > I personally can't answer your question. But I'd love to help test this, > > especially since Haswell graphics isn't supported, yet, and my laptop is > > running Haswell. What would be a good USB display device to buy to help test > > this awesome work out? > > Hi Shawn, > > I think any USB device that uses the brand name "DisplayLink" will work. Hi HPS, I thought the later generations, especially the ones with USB3 support, used a propretary encryption between the host and the adapter that was not currently supported by any F/OSS operating system? If you look on the DisplayLink forums there are angry threads about the lack of Linux support for the later generation dongles. e.g. http://displaylink.org/forum/showthread.php?s=77a3ad0ad0f21031f0996325f249f584&t=61689 (there's a much longer thread somewhere which is more angry, but I've lost the link) Regards, Gary ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On Mon, Feb 16, 2015 at 1:33 PM, Hans Petter Selasky
wrote:
> On 02/16/15 22:30, Mehmet Erol Sanliturk wrote:
>
>> On Mon, Feb 16, 2015 at 9:10 AM, Hans Petter Selasky
>> wrote:
>>
>> On 02/16/15 16:39, Shawn Webb wrote:
>>>
>>> On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote:
Hi,
>
> I've added support for USB display link adapters to FreeBSD-11-current,
> but the kernel panics once "vt_fb_attach(info)" is called from
> "fbd_register(struct fb_info* info)" when the USB device is plugged or
> udl.ko is loaded. Is this a known issue?
>
> REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c
>
> --HPS
>
>
I personally can't answer your question. But I'd love to help test this,
especially since Haswell graphics isn't supported, yet, and my laptop is
running Haswell. What would be a good USB display device to buy to help
test
this awesome work out?
>>> Hi Shawn,
>>>
>>> I think any USB device that uses the brand name "DisplayLink" will work.
>>>
>>> Current list of supported devices:
>>>
>>> /*
>>>
* Matching devices.
*/
static const STRUCT_USB_HOST_ID udl_devs[] = {
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
LCD4300U,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
LCD8000U,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
GUC2020,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_LD220,
DL165)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
VCUD60,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_DLDVI,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_VGA10,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_WSDVI,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_EC008,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
HPDOCK,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_NL571,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
M01061,
DL195)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
NBDOCK,
DL165)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_SWDVI,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_UM7X0,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_CONV,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
PLUGABLE,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK,
USB_PRODUCT_DISPLAYLINK_LUM70,
DL125)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
POLARIS2,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_
LT1421,
DLUNK)}
};
>>>
>>> Also see:
>>>
>>> man udl
>>>
>>> Some work needs to be done to fully integrate with the VT console
>>> subsystem. I had Xorg up and running today with the DisplayLink I
>>> adapter I
>>> have, and I works quite well. With USB 3.0 ones I think we can expect
>>> more.
>>>
>>> --HPS
>>> ___
>>>
>>>
>>>
>>
>> Will there be support for the devices like the following USB video
>> adapters
>> ?
>>
>>
>> http://www.amazon.com/gp/product/B00GUE5LGS/ref=s9_
>> simh_gw_p147_d0_i11?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=
>> 1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
>>
>>
>> http://www.amazon.com/gp/product/B00A2E1MQA/ref=s9_
>> simh_gw_p147_d0_i3?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=
>> 1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
>>
>>
>> http://www.amazon.com/gp/product/B00612ZPQA/ref=s9_
>> simh_gw_p147_d0_i2?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=
>> 1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
>>
>>
> Depending on what USB protocol they are using we can add support for them.
> Maybe you need to buy one and dump the USB descriptors :-)
>
> --HPS
>
>
I will attempt to find sample ones ( this may require some time ) and send
their descriptors .
( Some of the following are sold in Turkey )
http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/r-grafikadapter-usb-20-auf-vga-da-70833/
http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/r-grafikadapter-usb-20-auf-dvi-da-70834/
http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/usb-20-auf-hdmi-videoadapter-da-70851/
http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/r-usb-30-zu-vga-ad
Re: Pluggable frame buffer devices
On 02/16/15 22:30, Mehmet Erol Sanliturk wrote:
On Mon, Feb 16, 2015 at 9:10 AM, Hans Petter Selasky
wrote:
On 02/16/15 16:39, Shawn Webb wrote:
On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote:
Hi,
I've added support for USB display link adapters to FreeBSD-11-current,
but the kernel panics once "vt_fb_attach(info)" is called from
"fbd_register(struct fb_info* info)" when the USB device is plugged or
udl.ko is loaded. Is this a known issue?
REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c
--HPS
I personally can't answer your question. But I'd love to help test this,
especially since Haswell graphics isn't supported, yet, and my laptop is
running Haswell. What would be a good USB display device to buy to help
test
this awesome work out?
Hi Shawn,
I think any USB device that uses the brand name "DisplayLink" will work.
Current list of supported devices:
/*
* Matching devices.
*/
static const STRUCT_USB_HOST_ID udl_devs[] = {
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LCD4300U,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LCD8000U,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_GUC2020,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LD220,
DL165)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_VCUD60,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_DLDVI,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_VGA10,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_WSDVI,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_EC008,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_HPDOCK,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_NL571,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_M01061,
DL195)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_NBDOCK,
DL165)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_SWDVI,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_UM7X0,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_CONV,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_PLUGABLE,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LUM70,
DL125)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_POLARIS2,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LT1421,
DLUNK)}
};
Also see:
man udl
Some work needs to be done to fully integrate with the VT console
subsystem. I had Xorg up and running today with the DisplayLink I adapter I
have, and I works quite well. With USB 3.0 ones I think we can expect more.
--HPS
___
Will there be support for the devices like the following USB video adapters
?
http://www.amazon.com/gp/product/B00GUE5LGS/ref=s9_simh_gw_p147_d0_i11?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
http://www.amazon.com/gp/product/B00A2E1MQA/ref=s9_simh_gw_p147_d0_i3?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
http://www.amazon.com/gp/product/B00612ZPQA/ref=s9_simh_gw_p147_d0_i2?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
Depending on what USB protocol they are using we can add support for
them. Maybe you need to buy one and dump the USB descriptors :-)
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On Mon, Feb 16, 2015 at 9:10 AM, Hans Petter Selasky
wrote:
> On 02/16/15 16:39, Shawn Webb wrote:
>
>> On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote:
>>
>>> Hi,
>>>
>>> I've added support for USB display link adapters to FreeBSD-11-current,
>>> but the kernel panics once "vt_fb_attach(info)" is called from
>>> "fbd_register(struct fb_info* info)" when the USB device is plugged or
>>> udl.ko is loaded. Is this a known issue?
>>>
>>> REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c
>>>
>>> --HPS
>>>
>>
>> I personally can't answer your question. But I'd love to help test this,
>> especially since Haswell graphics isn't supported, yet, and my laptop is
>> running Haswell. What would be a good USB display device to buy to help
>> test
>> this awesome work out?
>>
>
> Hi Shawn,
>
> I think any USB device that uses the brand name "DisplayLink" will work.
>
> Current list of supported devices:
>
> /*
>> * Matching devices.
>> */
>> static const STRUCT_USB_HOST_ID udl_devs[] = {
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LCD4300U,
>> DL120)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LCD8000U,
>> DL120)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_GUC2020,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LD220,
>> DL165)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_VCUD60,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_DLDVI,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_VGA10,
>> DL120)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_WSDVI,
>> DLUNK)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_EC008,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_HPDOCK,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_NL571,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_M01061,
>> DL195)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_NBDOCK,
>> DL165)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_SWDVI,
>> DLUNK)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_UM7X0,
>> DL120)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_CONV,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_PLUGABLE,
>> DL160)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LUM70,
>> DL125)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_POLARIS2,
>> DLUNK)},
>> {USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LT1421,
>> DLUNK)}
>> };
>>
>
>
> Also see:
>
> man udl
>
> Some work needs to be done to fully integrate with the VT console
> subsystem. I had Xorg up and running today with the DisplayLink I adapter I
> have, and I works quite well. With USB 3.0 ones I think we can expect more.
>
> --HPS
> ___
>
>
Will there be support for the devices like the following USB video adapters
?
http://www.amazon.com/gp/product/B00GUE5LGS/ref=s9_simh_gw_p147_d0_i11?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
http://www.amazon.com/gp/product/B00A2E1MQA/ref=s9_simh_gw_p147_d0_i3?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
http://www.amazon.com/gp/product/B00612ZPQA/ref=s9_simh_gw_p147_d0_i2?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-2&pf_rd_r=1QXWR8TQVH25A4KZWMDM&pf_rd_t=36701&pf_rd_p=1970566542&pf_rd_i=desktop
Thank you very much .
Mehmet Erol Sanliturk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On 02/16/15 18:10, Hans Petter Selasky wrote: Some work needs to be done to fully integrate with the VT console subsystem. I had Xorg up and running today with the DisplayLink I adapter I have, and I works quite well. With USB 3.0 ones I think we can expect more. s/DisplayLink I adapter I have, and I works/DisplayLink adapter I have, and it works/g --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On 02/16/15 16:39, Shawn Webb wrote:
On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote:
Hi,
I've added support for USB display link adapters to FreeBSD-11-current,
but the kernel panics once "vt_fb_attach(info)" is called from
"fbd_register(struct fb_info* info)" when the USB device is plugged or
udl.ko is loaded. Is this a known issue?
REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c
--HPS
I personally can't answer your question. But I'd love to help test this,
especially since Haswell graphics isn't supported, yet, and my laptop is
running Haswell. What would be a good USB display device to buy to help test
this awesome work out?
Hi Shawn,
I think any USB device that uses the brand name "DisplayLink" will work.
Current list of supported devices:
/*
* Matching devices.
*/
static const STRUCT_USB_HOST_ID udl_devs[] = {
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LCD4300U,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LCD8000U,
DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_GUC2020,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LD220, DL165)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_VCUD60,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_DLDVI, DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_VGA10, DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_WSDVI, DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_EC008, DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_HPDOCK,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_NL571, DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_M01061,
DL195)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_NBDOCK,
DL165)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_SWDVI, DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_UM7X0, DL120)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_CONV, DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_PLUGABLE,
DL160)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LUM70, DL125)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_POLARIS2,
DLUNK)},
{USB_VPI(USB_VENDOR_DISPLAYLINK, USB_PRODUCT_DISPLAYLINK_LT1421, DLUNK)}
};
Also see:
man udl
Some work needs to be done to fully integrate with the VT console
subsystem. I had Xorg up and running today with the DisplayLink I
adapter I have, and I works quite well. With USB 3.0 ones I think we can
expect more.
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pluggable frame buffer devices
On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: > Hi, > > I've added support for USB display link adapters to FreeBSD-11-current, > but the kernel panics once "vt_fb_attach(info)" is called from > "fbd_register(struct fb_info* info)" when the USB device is plugged or > udl.ko is loaded. Is this a known issue? > > REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c > > --HPS I personally can't answer your question. But I'd love to help test this, especially since Haswell graphics isn't supported, yet, and my laptop is running Haswell. What would be a good USB display device to buy to help test this awesome work out? Thanks, Shawn signature.asc Description: This is a digitally signed message part.
Pluggable frame buffer devices
Hi, I've added support for USB display link adapters to FreeBSD-11-current, but the kernel panics once "vt_fb_attach(info)" is called from "fbd_register(struct fb_info* info)" when the USB device is plugged or udl.ko is loaded. Is this a known issue? REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
