From owner-freebsd-current@FreeBSD.ORG Tue Dec 10 16:36:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7913D790 for ; Tue, 10 Dec 2013 16:36:09 +0000 (UTC) Received: from mail-ea0-f170.google.com (mail-ea0-f170.google.com [209.85.215.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 080E61A98 for ; Tue, 10 Dec 2013 16:36:08 +0000 (UTC) Received: by mail-ea0-f170.google.com with SMTP id k10so2393455eaj.29 for ; Tue, 10 Dec 2013 08:36:01 -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-type:content-transfer-encoding:subject:from:date:to :message-id; bh=o56BVGh08FN6S7CLfdkWmPb0wU98OSh5Je9d6zvAb58=; b=kpzwtch+AX2srzhopHYLsK4y+WKHMXul9YmrdPPARyf2w/k6/yt+2s4gg5DPQglcj5 5SB7yrZbaXEXP9WKIlhsoacA1A8mk/+1w523eiyChb7kAl/I7b0xRw8Ena8qt99hdIp1 fgvuSd037vM3wDN402N4H4Hedd0+Pf7CHSvb5i/4D6hE5I2RRmNaSPuQMAEdgW+EDCYB RhLRsKd+ZcOgTBFvnb0Gtou2kwvVBjH4/dqmbv7QqZefjT2CaTsy9wNuWvu6xI6prsXW Bv9hBTrMe6SUrsxcGa+JFJsS1CwDFWYvPkweg1hZQC0PvTzdDChaYqqtu6bolkdfq05H AUXA== X-Gm-Message-State: ALoCoQn4MH8PoJLWnHNRPKJXR96OFl4xjiOkATIn4tJWwcPmE7NoF/oBbgWpJmJwgbc1LVmpTNCK X-Received: by 10.14.182.199 with SMTP id o47mr19102415eem.7.1386693361307; Tue, 10 Dec 2013 08:36:01 -0800 (PST) Received: from [100.80.194.44] ([37.73.199.156]) by mx.google.com with ESMTPSA id b41sm43115579eef.16.2013.12.10.08.35.58 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 10 Dec 2013 08:36:00 -0800 (PST) User-Agent: K-9 Mail for Android In-Reply-To: <52A7115F.4060702@dumbbell.fr> References: <201312052238.rB5McsVN020719@svn.freebsd.org> <20131208163610.86e9e1ccc892aaf255d4cfb2@gmail.com> <20131209173521.3d8543998dad2bc57cdc326c@ddteam.net> <20131210014926.840974dc.ray@ddteam.net> <52A7115F.4060702@dumbbell.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken From: Aleksandr Rybalko Date: Tue, 10 Dec 2013 18:16:34 +0200 To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= , freebsd-current@freebsd.org Message-ID: <5dda74ca-e6be-40cb-8292-a3852c1fa610@email.android.com> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 10 Dec 2013 16:36:09 -0000 "Jean-Sébastien Pédron" написав(ла): >On 10.12.2013 00:49, Aleksandr Rybalko wrote: >> It is not fatal in syscons case. We decide to mark this message as >> error, to get more attention when run with newcons. For newcons it >> indicate that vt will not be able to draw into framebuffer(memory >> region which contain image you see on display). >> But it have no impact on sc (syscons). > >Is there something we can check at build time or runtime to determine >which of syscons or newcons is used, and consequently, avoid this error >message? Because we'll probably have many reports of that in the >future. Yep, committed in r259179. Thanks! WBW ------ Aleksandr Rybalko