From owner-freebsd-x11@freebsd.org  Sun Feb 24 04:44:05 2019
Return-Path: <owner-freebsd-x11@freebsd.org>
Delivered-To: freebsd-x11@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 460F5151197E;
 Sun, 24 Feb 2019 04:44:05 +0000 (UTC)
 (envelope-from ota@j.email.ne.jp)
Received: from mail01.asahi-net.or.jp (mail01.asahi-net.or.jp [202.224.55.13])
 by mx1.freebsd.org (Postfix) with ESMTP id B1CCD859A0;
 Sun, 24 Feb 2019 04:44:04 +0000 (UTC)
 (envelope-from ota@j.email.ne.jp)
Received: from rv515.advok.com (pool-72-76-119-135.nwrknj.fios.verizon.net
 [72.76.119.135]) (Authenticated sender: NR2Y-OOT)
 by mail01.asahi-net.or.jp (Postfix) with ESMTPSA id 6AC8E10AB3A;
 Sun, 24 Feb 2019 13:43:59 +0900 (JST)
Date: Sat, 23 Feb 2019 23:43:51 -0500
From: Yoshihiro Ota <ota@j.email.ne.jp>
To: Greg V <greg@unrelenting.technology>
Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org>, FreeBSD X11 mailing list
 <freebsd-x11@freebsd.org>
Subject: Re: DRM removal soon
Message-Id: <20190223234351.0addf9de71953eb31136322b@j.email.ne.jp>
In-Reply-To: <1550926557.1795.0@unrelenting.technology>
References: <CANCZdfptG6hwdDc=RFMUA+fA7eMijPycY24dcqPLi7aP-whR-A@mail.gmail.com>
 <20190223003126.4aec5a01b77ec9bf9ea0992a@j.email.ne.jp>
 <1550926557.1795.0@unrelenting.technology>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; i386-portbld-freebsd12.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: B1CCD859A0
X-Spamd-Bar: ------
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-6.85 / 15.00];
 NEURAL_HAM_MEDIUM(-0.99)[-0.993,0];
 NEURAL_HAM_SHORT(-0.85)[-0.854,0]; REPLY(-4.00)[];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11/>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Feb 2019 04:44:05 -0000

On Sat, 23 Feb 2019 15:55:57 +0300
Greg V <greg@unrelenting.technology> wrote:

> 
> 
> On Sat, Feb 23, 2019 at 8:31 AM, Yoshihiro Ota <ota@j.email.ne.jp> 
> wrote:
> > Hi,
> > 
> > How does this impact VMWare users?
> > I couldn't find much of documents.
> > 
> > I run few FreeBSD versions on MacBook VMWare.
> > 
> > Do we have a different driver for VMWare or go by MacBook's?
> > 
> > I looked at dmesg of another laptop and that reports "Radeon".
> > However, I don't find any "drm" in FreeBSD VMWare dmesg at all.
> > I'm not sure which driver FreeBSD has been picking up.
> 
> Hi, looks like you have not been using *any* GPU driver at all, just a 
> basic framebuffer (efifb or vga) and software rendering.
> 
> Only the new drm-kmod includes vmwgfx, which should bring you GPU 
> support :) https://twitter.com/johalun/status/1056549585106227201
> 

I also got some private emails, too.
Thanks for info.

I gave up VMWare for this one and tried on 3 physical machines.
All 3 machines I tried this time worked okay with ports drivers.

I also found that running kldstat was the easiest way to find which of driver to use instead of dmesg.

Hiro