From owner-svn-src-head@FreeBSD.ORG Fri Feb 7 22:10:43 2014 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 992C6A2E for ; Fri, 7 Feb 2014 22:10:43 +0000 (UTC) Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 277061DFF for ; Fri, 7 Feb 2014 22:10:42 +0000 (UTC) Received: by mail-ee0-f41.google.com with SMTP id e51so1532795eek.14 for ; Fri, 07 Feb 2014 14:10:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type:subject:from:date:to:cc :message-id; bh=V+21M2kYZtx4CvKOewsFCRT4LBdZvwDmHiHSpxmOBsM=; b=DhkwTjGrw9m008efPQ3aewCNc4tODMZWoO5coyUMSotIAVwA7TINCz/SfCqiYLTChn pEgaKbDEmcZekSRFSaijvWfSUQ4lDkuorSIjlWyHPuxshFylFixWOEbxLLL5FKbv5JN9 XniT0aj8OleCT7APJzHYnghMXgQXCIjvIsffuiPaJAYEXpubTUtV8357qMjDa8BI0eJA jBgU5dUiKHVRwONOstcdyi9StvlilALgW7j1UFkdULjcZHCjENKu54VGFzqLze7rQheO dd2M2LecWSVilDbN0ZK5dqGileUfSMi5SUymxwSYXJC6aR15UM16JjP03GCrh3duHdgi myEw== X-Gm-Message-State: ALoCoQkcEljdcSvOXHgwgZl1QZlUicR06zwG8x3ALS9GDeU8r1/JXQ3exiJ3wFXIup2xvU+rC7bw X-Received: by 10.15.26.8 with SMTP id m8mr19372879eeu.25.1391809515119; Fri, 07 Feb 2014 13:45:15 -0800 (PST) Received: from [192.168.1.81] (87-94-133-95.pool.ukrtel.net. [95.133.94.87]) by mx.google.com with ESMTPSA id k6sm21213010eep.17.2014.02.07.13.45.12 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 07 Feb 2014 13:45:13 -0800 (PST) User-Agent: K-9 Mail for Android In-Reply-To: References: <201402071239.s17CdwIH007683@svn.freebsd.org> <20140207171025.d33b95770f6b0d7d00b4aab3@freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: svn commit: r261585 - head/sys/dev/vt/hw/vga From: Aleksandr Rybalko Date: Fri, 07 Feb 2014 23:44:54 +0200 To: Ed Schouten ,Aleksandr Rybalko Message-ID: Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 22:10:43 -0000 On 7 лютого 2014 р. 23:27:58 GMT+02:00, Ed Schouten wrote: >Hi Aleksandr, > >On 7 February 2014 16:10, Aleksandr Rybalko wrote: >> On Fri, 7 Feb 2014 15:04:47 +0100 >> Ed Schouten wrote: >>> On 7 February 2014 13:39, Aleksandr Rybalko wrote: >> Also people asking me about advanced features of vt(9), like use >> multiple displays. I'm not sure, but signed coordinates may help with >> some things on that way (or makes more problems :) ). > >But if you were to have multiple displays, you should have separate >coordinate systems per display. It should not be seen as a single >pane. I don't really know yet how that will be implemented. :-) > >>> Furthermore, I think it's a bit weird that vga_bitbltchr() contains >>> explicit bounds checking. What happened there? I remember at one >point >>> in time, we had the nice invariant that vt(9) never attempted to >draw >>> outside of the display resolution. What caused us to give up on >that? >> >> Mouse cursor allowed to partially go out of screen, so we have to >check >> (or use special function for mouse cursor). > >Well, that's a compelling argument. Still, it's a bit weird then that >the bitblt function itself does not take signed coordinates. Would it >make sense to bring that in sync then? Yup, this is good idea to sync them. Will do that a bit later. Thanks a lot Ed! Let me know if you will have something more. WBW ------ Aleksandr Rybalko