Date: Wed, 19 Nov 2014 13:40:53 -0800 From: "Waitman Gobble" <waitman@waitman.net> To: "Felix Palmen" <felix@palmen-it.de> Cc: freebsd-x11@freebsd.org Subject: Re: DRI not working, AMD E 300 with Radeon HD 6310 Message-ID: <516cd95e7ad593562f85b7b8a42f4296.squirrel@mx.waitman.net> In-Reply-To: <2674870.PTfXXQznk8@nexus> References: <546CAD30.3060600@palmen-it.de> <2351316.QielfSBzBO@nexus> <7ceb971998008827645f5ea2b3989bac.squirrel@mx.waitman.net> <2674870.PTfXXQznk8@nexus>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, November 19, 2014 1:06 pm, Felix Palmen wrote: > Am Mittwoch, 19. November 2014, 10:41:03 schrieben Sie: > >> I've found numerous posts about 'how buggy' the HD 6310 is, for example >> mozilla.org mailing lists (posters there claiming it's the worst). The >> PALM firmware is supposedly Northern Islands series, the 6310 seems to >> have been manufactured about the time these were introduced on the >> market. Radeon support has been further developed since 3.8. But it's >> some work to import the code, which may be an understatement, I'm >> definitely not an expert but casual browsing it seems the threading >> calls need changed, and these drivers use the i2c interface which AFAIK >> has been deprecated in FreeBSD for some time. >> > > Ok, this sounds quite bad. Just out of curiosity: what's the replacement > for i2c then? This would require a major porting effort? I'm still a > little confused by the fact someone obviously tested the HD 6310 > successfully, according to the wiki page. > > Meanwhile, still waiting for buildworld to finish, I found this: > https://bugs.freedesktop.org/show_bug.cgi?id=66963#c175 > > > Different chip, different OS, but at least same error. I prepared a > similar patch against freebsd head (completely disabling the DMA ring for > my chip) just for testing purposes. I'll report here whether this does any > good, just in case someone else faces the same problem. Of course, this is > an ugly hack, intentionally disabling a feature in the driver, but if it > really helps, I could polish the patch so it only affects exactly the > 0x9802 chip. But, let's > see first... > > -- > Dipl.-Inform. Felix Palmen <felix@palmen-it.de> ,.//.......... > {web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de > {pgp public key} http://palmen-it.de/pub.txt // """"""""""" > {pgp fingerprint} ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 > > > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > I read an ml thread about i2c interface several months ago, can't seem to find it at the moment. But I think the i2c calls would have to be reworked around include/dev/iicbus/iic.h -- Waitman Gobble Los Altos California USA +1.510-830-7975
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?516cd95e7ad593562f85b7b8a42f4296.squirrel>