Date: Fri, 25 Jul 2014 11:24:05 +0200 From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= <jean-sebastien.pedron@dumbbell.fr> To: freebsd-x11@freebsd.org Subject: Re: Supporting i386-wine-devel WITH_NEW_XORG Message-ID: <53D22235.6030504@dumbbell.fr> In-Reply-To: <2625382.dAdXyb0tIr@dragon.dg> References: <2625382.dAdXyb0tIr@dragon.dg>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RKp8kJ7DJddGmL3S1L1DutJikhqRpX91D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 24.07.2014 20:46, David Naylor wrote: > Hi, Hello! > I read on the quarterly report that some changes were required to i386-= wine- > devel to properly support WITH_NEW_XORG. =20 >=20 > As maintainer I am interested in integrating those changes (happy to=20 > review/approve patches) :-D. =20 Yeah, sorry to not contact you earlier, I didn't take time to clean my notes :) At the time of my test, i386-wine-devel wasn't expecting WITH_NEW_XORG's flavor of graphics/dri, but you changed this since. Next, to run StarCraft II, I needed libtxc_dxtn.so. This library is dlopened by libGL to enable texture compression. I prepared a port in xorg-dev's repository: http://trillian.chruetertee.ch/ports/browser/trunk/graphics/libtxc_dxtn It's not in the ports tree yet; I hope Koop can push it soon :) Now, my notes regarding StarCraft II (not i386-wine-devel): The Battle.Net installer copied the files but got stuck at some point. It's not a problem and it can be killed. The Battle.Net application starts an agent in the background. This agent doesn't work for me out-of-the-box and the connection times out. If instead, I start the agent manually, it works fine. I start it with the following command: wine Agent.exe --nohttpauth (the agent is installed in ~/.wine/drive_c/users/Public/Application\ Data/Battle.net/Agent) At this point, Battle.Net works fine and you can download and play StarCraft II. Diablo III doesn't work (black screen) but I saw many reports about this in the Mesa/dri bugtracker. We need an update to the Radeon kernel driver to fix this. Some extra notes: o I didn't test with an Intel GPU. o I used the latest version of Mesa at that time (10.1 I think). Mesa 10.x works *way* better with Radeon GPUs, but Mesa 9.2+ can't work with our Intel driver. Thus I don't know if Mesa 9.1.7 from ports will work. --=20 Jean-S=E9bastien P=E9dron --RKp8kJ7DJddGmL3S1L1DutJikhqRpX91D 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 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJT0iI6AAoJEDnpl2Gl/ZTMs8QP/RE+3bpcF33Dt1/cB0K0EySU 2OUj41sIZ1lHND4UKMAe6tEkhsogY/OMcpy57QrpNoIVyFTQw56R63fWA+rzEo2U hvhRZqZTKnHFVvHB1WmRAmFwbAWUezJgbcysYx34YJ48pBP8amLF0e8lVhzgYHgL 9quJgl5IsBXQciA5gUG2JO/tG8zuKy4wpc+ZI47asteA5//NZhvDigZWVDRY34cN ptMlOqnTZOV4h7kQIjc1cLmdzbFataDevGM5/k9vH3JjoXzFvku7RrSJClpwseVL pYf900uEubqFLsxXQ8QEv60d4n31Fflf9Xu1FkNDW2ir7AZSQjMsDCWYLrHJ27LF aWfYcSpgB8JfGoI9OVRswXpi0y0W3tq+t8mdGSkcddB3+jNoAePwvIaJzYPo8R2a Y+lhe7A+QPrmJxV6CxM6pfWInzzEKdkPhK6148dVRk2xs5mBqiU6vkIqbFF9TpYv FxqSubfj0CgCcIXTM9U0gJFH1Fk5NaBd7DQgudc28WNiE6Yav+OdmL7ckH9XN/ze +Ffy1oksCeJBKj1pufVk2Q475jt7XJdhkSlbLyYg0odpLR3yjzXyjTlliqxk6ztn 3LdgnNQW1ymUmJ2ukZKE/uvyL70oz0UerTi0AWptuv9tp0dolNmSVlS1Ui5tkX13 OI+4xwpSdiJ6RmSBzjKg =25n5 -----END PGP SIGNATURE----- --RKp8kJ7DJddGmL3S1L1DutJikhqRpX91D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D22235.6030504>