From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Subject: Re: Status update on 1.0
Date: Fri, 15 Mar 2019 13:54:34 +0100
Message-ID: <877ed05md1.fsf@gnu.org>
References: <871s3a4xd4.fsf@gnu.org> <87y35i4woe.fsf@nckx>
	<87ef7au5l4.fsf@ambrevar.xyz>
	<20190313193345.5c8bfb64@scratchpost.org>
	<878sxitxv6.fsf@ambrevar.xyz>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:50752)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1h4mTl-0002il-Sn
	for guix-devel@gnu.org; Fri, 15 Mar 2019 09:02:33 -0400
In-Reply-To: <878sxitxv6.fsf@ambrevar.xyz> (Pierre Neidhardt's message of
	"Wed, 13 Mar 2019 19:47:41 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>, Mathieu Othacehe <m.othacehe@gmail.com>

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> Or find out why on earth KMSCON needs the prorietary amdgpu kernel modul=
e.
>>
>> It's not exactly 3D graphics, so what is going on?  Furthermore, vesafb =
should
>> always work regardless (if slowly, but who cares).
>
> Simply because modern AMD cards don't support KMS without the
> proprietary kernel module (yet).

They should still support VESA, no?

Mathieu, any idea?  Do you think we could detect it when kmscon fails?
Or simply avoid it?

Ludo=E2=80=99.