From owner-freebsd-current@FreeBSD.ORG Mon Feb 16 21:51:48 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 264CACB2 for ; Mon, 16 Feb 2015 21:51:48 +0000 (UTC) Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com [IPv6:2607:f8b0:4002:c01::22e]) (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 CE904827 for ; Mon, 16 Feb 2015 21:51:47 +0000 (UTC) Received: by mail-yh0-f46.google.com with SMTP id z6so15151591yhz.5 for ; Mon, 16 Feb 2015 13:51:47 -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=cVaiWuoFklRf3cnGWBMU39s5B0hGsL+8d2bv1DpgtIo=; b=yFzNEUgix3/1bMe5fnD+iMdPD9joM7CRqzgflv7iEjpU4b1L867ouuw8LMFsgKOMai JfpZ91TBYCnz6rzpoltGG2bFodXC9jDFKtHAJS8t+6r6wNJmCRY3fM8AnO2f1pZLqD4Y bmac0sHhw1gbTiRZA3aYe0j7LusTBIzhjN3RW4Ph9GLYVISdZybXp1p1bnC80MjEw7UE RE03Xamc+Zff14UqkW2g/A9ne4S/KIpYzzD3v/L0PL8ynF5Dd/CtFrTueUZ6Vr8V5tTl x6qrvVtp7Ga/dga4MYeIicaTGUioD4jTC3HUhYyj8VspM8DeRujye51G0Ct84lSVr+/C wgCw== MIME-Version: 1.0 X-Received: by 10.170.203.198 with SMTP id u189mr137674yke.107.1424123506949; Mon, 16 Feb 2015 13:51:46 -0800 (PST) Received: by 10.170.60.85 with HTTP; Mon, 16 Feb 2015 13:51:46 -0800 (PST) In-Reply-To: <54E26238.5080404@selasky.org> References: <54E11A57.3030105@selasky.org> <2245985.dTFM2y6A0x@shawn-work-laptop> <54E2247E.3000207@selasky.org> <54E26238.5080404@selasky.org> Date: Mon, 16 Feb 2015 13:51:46 -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:51:48 -0000 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-adapter-da-70450/ http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/usb-30-zu-dvi-adapter-da-70451/ http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/usb-30-zu-hdmi-adapter-da-70452/ http://www.digitus.info/pt/productos/multimedia/video/usb-grafik-adapter/mhl-micro-usb-20-adapterkabel-ak-300305-002-s/ My main aim is to use such devices to attach to a computer extra conventional monitors ( they may be very cheap or already present at hand ) and to divert stdin , stdout , and stderr to different monitors and study outputs during working on GUI desktops and programs to follow their execution steps for their debugging by defining stdin , stdout , stderr ports in boot loader.conf or elsewhere ( I need help on this subject also ) . Thank you very much . Mehmet Erol Sanliturk