Re: radeon driver bug?

also, it stull has some bugs, because the colors of some
parts are different from those of original ones.

Kenji


2018年12月6日(木) 15:10 岡本健二 <keoknj55@gmail.com>:

> Sorry, I'm a novice to OpenBSD.
> Yes, it's current branch of xenocara.
> I updated my xenocara (stable) to that current, and build new xenocara
> here.
>
> Wow, it makes the Jahshaka works!
>
> However, it still has some bugs, because it moves and stop suddenly and
> then
> move again. Whine the animation stops, the system seems to halting...
>
> Anyway it makes much advance, I included the screenshot of it.
>
> Kenji
>
> PS: sorry tfrohwein, this is doubled to you
>
> 2018年12月6日(木) 13:26 岡本健二 <keoknj55@gmail.com>:
>
>> in-current means stable 6.4?
>>
>> Kenji
>>
>> 2018年12月5日(水) 23:58 tfrohwein@fastmail.com <tfrohwein@fastmail.com>:
>>
>>> On December 5, 2018 9:41:44 AM UTC, "岡本健二" <keoknj55@gmail.com> wrote:
>>> >This errors come from
>>> >/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
>>> >The mesa version of OpenBSD6.4 is 13.0.6.
>>> >I'm running this Jahshaka on Ubutu 18.04, where the mesa version is
>>> >18.x.
>>> >
>>> >So, it may be the mesa problem...
>>> >
>>> >Kenji
>>> >
>>> >
>>> >2018年12月4日(火) 16:19 岡本健二 <keoknj55@gmail.com>:
>>> >
>>> >> I'm using AMD HD6450 graphic card which I reported before, and faced
>>> >a
>>> >> curious thing
>>> >> during running Jahshaka Studio (dev version 7.03a).
>>> >> To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
>>> >> temporally, which
>>> >> is not the problem now.
>>> >>
>>> >> After start to run 'Jahshaka Studio', I got start 3D animation sample
>>> >> 'Skeletal Animation' data to load, then
>>> >> I got many errors included below which seems to come from radeon drm
>>> >> driver's bug to me.
>>> >> If you interested please check it.
>>> >>
>>> >> Thanks in advance
>>> >>
>>> >> Kenji
>>> >>
>>> >>
>>>
>>> There's a known bug where the shader on r600 uses too many registers:
>>>
>>> https://bugs.freedesktop.org/show_bug.cgi?id=99349
>>>
>>> I encountered this bug with godot on a Radeon HD 7570, too, and it went
>>> away with the updated mesa that's in -current.
>>>
>>