From owner-freebsd-current@freebsd.org Fri Jan 20 23:11:43 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A570CBA35E for ; Fri, 20 Jan 2017 23:11:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 2931A1C52 for ; Fri, 20 Jan 2017 23:11:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id c206so67076619wme.0 for ; Fri, 20 Jan 2017 15:11:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TRZQGSSd8Xf2Lu2XW6IsEyXaHMbe6s/fQk2cq8Vjc0k=; b=IMdpauSnyJfCVYRjDxDADTgOJXzGb8X0sJxfduPHu6yBsrd4eCOHB8ZRBB6I5vG0Go 73O55sMRm15VM0hTsQ6SZuaVKSp3+oHmi/NYdbkFFgKKl1937tpJQE5StujmavkkRrz7 i2rG/w1Y66JIxvZ1d37sJSH4TJun8AoxezmCFwGIgcl+WTH8GGBcVwMvNs9n9ZSH6Nxc aF+WY5VFwrJe3h98u2uauunB4Z+JvGEWe3BOq4MuVhUIrufg4DSOBV19awUpklESPr33 zUfCHsD1jcnLkR/wnRWkunrbXivHhjHfw1PT3HoEBEDYIUePqu3911YOr2UkBTjdY8Lu lLqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TRZQGSSd8Xf2Lu2XW6IsEyXaHMbe6s/fQk2cq8Vjc0k=; b=X2dn2LlpyZTMWoPuHd7QSj8y8etkFGQlqqOLqPN/FYs2K+r61943pD5d0BR+RbPN2l O3GYT5XOu4hPFq9rvEBgiQBCHhicPBk1BoCIUTK0pigwz5555RHwtvIuOku9Oda9axBq ox1Y9tc2qCtdnjSL/ZO5kUqmYzjvNHVBTRsqlmn63Cxa5iU/OIo0C3Um1/714Qi5/S3j Xs9osQMmA/fuPtxiZCMbajqVYWYMPNfnsR0qhuWD07voSOcFziszyLc9zS2bszUFYHso P+MeA7x5h8tOhFGRtt6AKdmDORwAajbGRdImZIKv3sPdoXx+RNiBQFWZD06hvDgGKWyk PygQ== X-Gm-Message-State: AIkVDXLa4U5FCsKHSmYanre4gy3UU7TaDYP4E1/Zy0P+jYxZm745f5/cd4Xmph8Gtu9dKtY4kYHLHe5o6DZd8w== X-Received: by 10.223.173.80 with SMTP id p74mr13230016wrc.168.1484953901733; Fri, 20 Jan 2017 15:11:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.82.162 with HTTP; Fri, 20 Jan 2017 15:11:40 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Fri, 20 Jan 2017 15:11:40 -0800 Message-ID: Subject: Re: vt(4) chops off the leftmost three columns To: Anindya Mukherjee Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 20 Jan 2017 23:11:43 -0000 hiya, Mechanically it doesn't look /that/ hard: * vesa.ko pulls in the vesa.c bits and the syscons vesa control bits. Ideally we'd have them as two separate modules, so you could load "vesa" without needing the syscons bits. * Maybe then write a vt 'fb' interface to talk to the old-school framebuffer interface * Then (if we're lucky) we can have vt use the same VGA, VESA, (mach, creator, etc!) through the fb interface, rather than reimplementing its own. I looked at it and it doesn't look /that/ hard. If you only cared about vesa, then you could do something like what 'creator' and 'creator_vt' did in sys/dev/fb/ . It's just sad that the vt interface to the screen buffer isn't as complete as the older school framebuffer interface is. -adrian On 19 January 2017 at 12:35, Anindya Mukherjee wrote: > Hi Adrian, > > I was looking at the source for the vt driver. Wondering how much work it is to add VESA support to the VGA backend? As you say ATM it's hardcoded to use 640x480. Pardon my ignorance, but can we reuse any VESA code from syscons? > > Also, how dependent is splash/screensaver support on the VESA implementation? > > Thanks, > Anindya