From owner-freebsd-x11@freebsd.org Thu Apr 14 20:30:24 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79DE2AEC6CA for ; Thu, 14 Apr 2016 20:30:24 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AF8D10F5 for ; Thu, 14 Apr 2016 20:30:24 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqnu9-0005ol-RS; Thu, 14 Apr 2016 23:30:21 +0300 Subject: Re: clarifying the state of drm-next-3.9 and next steps To: Matthew Macy References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> Cc: freebsd-x11@freebsd.org From: Arto Pekkanen Message-ID: <570FFDD8.1080700@kapsi.fi> Date: Thu, 14 Apr 2016 23:30:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B09IxhN945GF4JM2m52Chim4cNXHrt2SJ" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2016 20:30:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --B09IxhN945GF4JM2m52Chim4cNXHrt2SJ Content-Type: multipart/mixed; boundary="A07V0MebMp7D13X0f5Xc4MtQQPRrt2SLI" From: Arto Pekkanen To: Matthew Macy Cc: freebsd-x11@freebsd.org Message-ID: <570FFDD8.1080700@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> In-Reply-To: <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> --A07V0MebMp7D13X0f5Xc4MtQQPRrt2SLI Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Can't promise anything for certain. I don't have a Radeon chip or a spare rig right now, but I might get one later. If not, I might be able to fix a cheap, older laptop with a Radeon GPU. I've no experience systems level programming or anything like that. I was thinking more about *coin mining or SETI@Home, you know, the kinda entry level, brick layer stuff wannabe hackers run on their petty home servers. I could try enabling AMD GPGPU option in some *coin miner in the ports tree, or if there is no such miner app available try to port one for FreeBSD, provided that the required libraries are made available at the time. On 14.04.2016 22:08, Matthew Macy wrote: >=20 >=20 > Thanks for the heads up :) >=20 > I am especially interested in the GPGPU support for AMDs, since thi= s > would actually make FreeBSD x86 rigs very useful for power efficien= t > cluster computing. Thus far cheapest alternatives (on x86 hardware)= have > been based on Windows or Linux. >=20 >=20 > Can I count you as a volunteer to help jmd with user level runtime > support? :D >=20 >=20 > -M >=20 >=20 >=20 > On 12.04.2016 22:57, Matthew Macy wrote: > > There seems to be some confusion about the state of drm-next-3.9.= > All the work is currently going on in jmd's fork of > freebsd-base-graphics: > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > The emphasis has been on bringing i915 and the drm code in > dev/drm2 closer to upstream as opposed to a simple driver refresh. > I'm currently implementing missing linuxkpi bits and hope to > actually be testing in the next week or so. > > > > As of this moment there is nothing available for general > consumption. I very much hope to have this phase done before code > freeze. I will update the list as soon as there is anything to test= =2E > Until then, hold your horses. > > > > The next phase will be more interesting to anyone who isn't simpl= y > waiting on bug fixes for Haswell support. My plan is to update DRM > to 4.6 and import amdgpu and amdkfd support. I would like to be abl= e > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgp= u > support is difficult to come up with. But certainly it will _not_ b= e > any earlier than end of May. > > > > -M > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing = list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to > "freebsd-x11-unsubscribe@freebsd.org > " > > >=20 --A07V0MebMp7D13X0f5Xc4MtQQPRrt2SLI-- --B09IxhN945GF4JM2m52Chim4cNXHrt2SJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcP/dgACgkQTBivhqtJa26iQgD9HXw+9inEtrtWRPmDLnkNKSe0 29+vnKaW5q4KoHbRRcsA/3i7UDqx+wn34O3552/yIEEXIAE13cD0QrLVDyYB8EEh =pDdy -----END PGP SIGNATURE----- --B09IxhN945GF4JM2m52Chim4cNXHrt2SJ--