Summary: | Crash, bug, bad image | ||
---|---|---|---|
Product: | Wayland | Reporter: | Andrew <Search_terminal> |
Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | bad image |
Please provide more information: the hardware platform, GPU model and the drivers used, operating system and version, and Weston log. Explain what you did, what you expected, and what happened exactly. Thanks. GPU Videocore VC4 in Mesa v17. Crash independed include in system raspberrypi-userland or not. If i run --use-pixman (software rendering) work current but slowly. I want run with hardware acceleration. Board Raspberry Pi v3. Include latest Xorg, xwayland, wayland version 1.14.0. Weston version from git latest. Bug in 1.9.0, 1.10.0, and others. Its strange.. because pixman work correct. (In reply to Pekka Paalanen from comment #1) > Please provide more information: the hardware platform, GPU model and the > drivers used, operating system and version, and Weston log. Explain what you > did, what you expected, and what happened exactly. > > Thanks. New information!!! I install old version mesa v13.x.x [gentoo linux - stable] and accelleration and weston work excellent. ########### BUT!! MESA V17.X.X CRASH WORK WESTON. I THINK YOU NEED TO TALK THIS TO MESA TEAM... BECAUSE ITS PROBLEM FROM MESA. PLEASE, WRITE TO MESA TEAM THIS PROBLEM. AND.. PLEASE, TEST IT. ############ IN NEW VERSIONS OF MESA V17.X.X AS STABLE, I SEE BAD WORKS WESTON. I THINK ITS BECAUSE MESA WRITE BAD CODE WAYLAND IMPLEMENTATION ..OR GLES2.0 IMPLEMENTATION. SORRY, I KNOW ENGLISH VERY BAD. ############# MESSAGE FOR USERS: I HIGHT RECOMEMBER USING MESA V13 FOR ALL WAYLAND VERSIONS. MESSAGE FOR USERS: I HIGHT RECOMEMBER USING MESA V13 FOR ALL WAYLAND and WESTON VERSIONS. Mesa v13.x.x excellent work on BCM SOC. Please, do not shout. That or setting the bug priority will do no good. When testing things on RPi, please be absolutely sure you are not mixing up the FOSS and the proprietary VC4 driver stacks. Weston is expected to not work on the proprietary driver stack (raspberrypi-userland and the respective firmware and software packages). I could have reassigned this bug to Mesa, but given the shouting I think it is better if you calm down and submit another bug report against Mesa. Please, include all the information you have given here, plus weston logs from both working and failing configurations. Thanks. (In reply to Pekka Paalanen from comment #5) > Please, do not shout. That or setting the bug priority will do no good. > > When testing things on RPi, please be absolutely sure you are not mixing up > the FOSS and the proprietary VC4 driver stacks. > > Weston is expected to not work on the proprietary driver stack > (raspberrypi-userland and the respective firmware and software packages). > > I could have reassigned this bug to Mesa, but given the shouting I think it > is better if you calm down and submit another bug report against Mesa. > Please, include all the information you have given here, plus weston logs > from both working and failing configurations. > > Thanks. I dont accept with you! Because i told you about crash works weston without userland, crash works with mesa v17.x.x. In mesa free implementation VC4(Gallium driver VC4). But i downgrade version to 13.x.x and solve it. Problem in new Mesa. Yes, thank you. I will be write bug report about Mesa. Forgive me, its false call. Now problem in new mesa <->weston (wayland). (In reply to Pekka Paalanen from comment #5) > Please, do not shout. That or setting the bug priority will do no good. > > When testing things on RPi, please be absolutely sure you are not mixing up > the FOSS and the proprietary VC4 driver stacks. > > Weston is expected to not work on the proprietary driver stack > (raspberrypi-userland and the respective firmware and software packages). > > I could have reassigned this bug to Mesa, but given the shouting I think it > is better if you calm down and submit another bug report against Mesa. > Please, include all the information you have given here, plus weston logs > from both working and failing configurations. > > Thanks. Thanks for all. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 135161 [details] bad image Bad image, running, waiting one minutes and crash. It mouse leave laucher momentaly crash..