From owner-freebsd-current@FreeBSD.ORG Mon Feb 16 21:32:58 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B14763EF for ; Mon, 16 Feb 2015 21:32:58 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AC4D389 for ; Mon, 16 Feb 2015 21:32:57 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id B390B1FE022; Mon, 16 Feb 2015 22:32:54 +0100 (CET) Message-ID: <54E26238.5080404@selasky.org> Date: Mon, 16 Feb 2015 22:33:44 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Mehmet Erol Sanliturk Subject: Re: Pluggable frame buffer devices References: <54E11A57.3030105@selasky.org> <2245985.dTFM2y6A0x@shawn-work-laptop> <54E2247E.3000207@selasky.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current , Shawn Webb X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 21:32:58 -0000 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