From owner-freebsd-stable@FreeBSD.ORG  Thu Sep 11 09:52:10 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@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 CC316345
 for <freebsd-stable@freebsd.org>; Thu, 11 Sep 2014 09:52:10 +0000 (UTC)
Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au
 [IPv6:2001:8000:1000:1801::36])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mta1.riverwillow.net.au",
 Issuer "Riverwillow Root Certificate 2010-04-12" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 39F97B5B
 for <freebsd-stable@freebsd.org>; Thu, 11 Sep 2014 09:52:10 +0000 (UTC)
Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au
 [IPv6:2001:8000:1000:1801::46])
 by mta1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s8B9q1WV007907
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK)
 for <freebsd-stable@freebsd.org>; Thu, 11 Sep 2014 19:52:01 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au;
 s=mta1002; t=1410429122;
 bh=FQenigsF/xm/k3cz93Ff+zp5rpLjxXj2UhhkRrIk9f4=;
 h=Date:From:To:Subject:References:In-Reply-To;
 b=o875i7B4sCeiI/XAlm76RSxY3ohHtL8PaYiRRTDXKeRTdT6zaxtCfEBkNdt315Mhm
 /tjfTgv4331sIsxlV0sr9x9S2G1eyXqtEZxTlmBZK8oLLR7RSvjgaZ0/lFjL+w6WHH
 3nNVWKDQrP2RnPZTFniSrkIAnjGw6CCMk4jF7LYs=
Received: from rwpc15.gfn.riverwillow.net.au (rwpc15.gfn.riverwillow.net.au
 [IPv6:2001:8000:1000:18e1:20c:76ff:fe0a:2117])
 (authenticated bits=56)
 by mail1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s8B9ps5c007896
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL)
 for <freebsd-stable@freebsd.org>; Thu, 11 Sep 2014 19:51:58 +1000 (AEST)
Date: Thu, 11 Sep 2014 19:51:54 +1000
From: John Marshall <john.marshall@riverwillow.com.au>
To: freebsd-stable@freebsd.org
Subject: Re: 10.1 kernel device config for drm2 and kms drivers
Message-ID: <20140911095154.GA18182@rwpc15.gfn.riverwillow.net.au>
Mail-Followup-To: freebsd-stable@freebsd.org
References: <20140911064731.GA15930@rwpc15.gfn.riverwillow.net.au>
 <54115D2A.5020802@FreeBSD.org> <20140911084624.GK2737@kib.kiev.ua>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX"
Content-Disposition: inline
In-Reply-To: <20140911084624.GK2737@kib.kiev.ua>
OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 09:52:11 -0000


--huq684BweRXVnRxX
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, 11 Sep 2014, 11:46 +0300, Konstantin Belousov wrote:
> On Thu, Sep 11, 2014 at 10:28:26AM +0200, Jean-S??bastien P??dron wrote:
> > On 11.09.2014 08:47, John Marshall wrote:
> > > I cannot find any kernel device configuration statements for drm2 or =
KMS
> > > (e.g. i915kms) drivers in any of the NOTES files in 10-STABLE.
> > > Presumably configurtation statements for these ought to be available =
for
> > > use in kernel configuration files for 10.1-RELEASE?
> >=20
> > Currently, building DRM drivers into the kernel isn't supported. I guess
> > it's mostly a lack of time and demand.
> I did not added file list to the static kernel config due to display
> becoming blank after the driver initialization, which is very early
> for the syscons setup.  Might be, since vt is functional, this may
> be reconsidered.

That's fair enough if the drivers are deemed to be not yet
production-ready.  I am guessing that NEW_XORG will be delivered as
default for 10.1-RELEASE just like it was for 9.3-RELEASE, so lots more
desktop users (unless they explicitly disable NEW_XORG) will find
themselves using these drivers.

> Driver initialization was never tested when loaded from loader, I
> have no idea how i915 starts up with interrupts still disabled.

The console display goes blank for several seconds and then comes to
life with the smaller font and the backlog of dmesg output displayed.

Perhaps I am doing all the wrong things.  I just assumed these new
drivers were functional replacements for drm and i915drm which could be
included in a custom kernel.

--=20
John Marshall

--huq684BweRXVnRxX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlQRcLoACgkQw/tAaKKahKLalACgjmWKcO4HYSapfjWikn0Qqlt1
+K4An33psjsle/HhTn8xw4ayhBp777LN
=USOE
-----END PGP SIGNATURE-----

--huq684BweRXVnRxX--