From owner-freebsd-current@FreeBSD.ORG Mon Feb 16 21:30:50 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D5322DC for ; Mon, 16 Feb 2015 21:30:50 +0000 (UTC) Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7C9F2E4 for ; Mon, 16 Feb 2015 21:30:49 +0000 (UTC) Received: by mail-yh0-f45.google.com with SMTP id a41so15113375yho.4 for ; Mon, 16 Feb 2015 13:30:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8znkUcDvNxR7kk3no3dPNA/tcXmbXF3b8UslC64w+fU=; b=SbzzZ9ffBvflbYIHbkWi09XpjnstEi2QaO5goLgQCAn3dhqGXnWKwjG4uiP/1YADGD ny+tPyRazkMdEdk7+ssfQ7zZpPzRXt0KWH9s4KRdjVwRALoeXSP1Rd84RB98w1PD0r+U cxI1qPPfeD87c9QjrsCb1J0yheS709z8lPSezfwofSEwZcUCZG6zlgE1rxATgYnXdSDz I6wjgkPIO+gIVPorQCxi0sT9lY4bpvAqoMI7qBsQNSIAHxCTSnmJKa3kme3YYYRdY0vT okfL4QIZBBgBV/xoW5fR56eTif9WJgDsljk3FNMwaRq9BuO9rwHuUVkKWwwWz2b4+QwS MR8g== MIME-Version: 1.0 X-Received: by 10.236.228.162 with SMTP id f32mr185558yhq.53.1424122248937; Mon, 16 Feb 2015 13:30:48 -0800 (PST) Received: by 10.170.60.85 with HTTP; Mon, 16 Feb 2015 13:30:48 -0800 (PST) In-Reply-To: <54E2247E.3000207@selasky.org> References: <54E11A57.3030105@selasky.org> <2245985.dTFM2y6A0x@shawn-work-laptop> <54E2247E.3000207@selasky.org> Date: Mon, 16 Feb 2015 13:30:48 -0800 Message-ID: Subject: Re: Pluggable frame buffer devices From: Mehmet Erol Sanliturk To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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:30:50 -0000 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