Re: Devicetree specification process

[Grant Likely]

On Sat, Apr 30, 2016 at 12:23 AM, Grant Likely  wrote:
> I'm pleased to announce the first *very early draft* of the new
> devicetree specification that I and several others have been working
> on since January. This document picks up where ePAPR left off in 2012.
> I'm announcing it now along with the new devicetree.org organization
> which will handle governance for the spec.
>
> We're still in the process of getting all the details sorted out (not
> everything on the website is accurate at the moment), but in the mean
> time you can look at the current state of the document. At the moment,
> it is little more than repackaging the ePAPR text. The next step will
> be pulling in the new core bindings that were never covered by ePAPR.
> You can look at a draft copy of the document here:
>
> https://github.com/kvekaria/devicetree-specification-released/blob/master/prerelease/DevicetreeSpecification-20160429-pre1.pdf

Oops, wrong link. This should be:

https://github.com/devicetree-org/devicetree-specification-released/blob/master/prerelease/devicetree-specification-v0.1-pre1-20160429.pdf

g.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Fwd: Devicetree specification process

[Grant Likely]

I'm pleased to announce the first *very early draft* of the new
devicetree specification that I and several others have been working
on since January. This document picks up where ePAPR left off in 2012.
I'm announcing it now along with the new devicetree.org organization
which will handle governance for the spec.

We're still in the process of getting all the details sorted out (not
everything on the website is accurate at the moment), but in the mean
time you can look at the current state of the document. At the moment,
it is little more than repackaging the ePAPR text. The next step will
be pulling in the new core bindings that were never covered by ePAPR.
You can look at a draft copy of the document here:

https://github.com/kvekaria/devicetree-specification-released/blob/master/prerelease/DevicetreeSpecification-20160429-pre1.pdf

If you want to help out, the document source markup can be cloned from
GitHub. You can find the project page here:

https://github.com/devicetree-org/devicetree-specification

Feedback is greatly appreciate. Please send any comments and/or
changes to the devicetree specification mailing list:

devicetree-s...@vger.kernel.org

For more information, you can refer to the slides presented at BKK16 and ELC[1].

[1] 
http://elinux.org/images/b/b7/Devicetree_specification_linaro_connect_bangkok_2016.pdf

Thanks,
g.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: radeonhd and xorg issues on powerpc p5020 and G5

[luigi burdo]

hi michel, 
sorry for extra email.

about kernels i been test from 3.3 to 4. to lastest rc nothing change the 
situation still the same.
another thing, can be this issue generated because our kernel are ppc64 and the 
distros are ppc32?

thanks 
luigi

Inviato da iPad

> Il giorno 30 apr 2016, alle ore 09:20, Michel Dänzer  ha 
> scritto:
> 
>> On 23.04.2016 02:06, luigi burdo wrote:
>> 
>> On Quad G5 with 2 video boards
>> if i set radeon.modeset=1  nouveau.modeset=1 Xorg -configure dont found
>> at all the video boards
>> if i set radeon.modeset=0  nouveau.modeset=1 Xorg -configure dont found
>> the nouveau board
>> if i set radeon.modeset=1  nouveau.modeset=0 Xorg -configure dont found
>> the radeon board
> 
> Xorg -configure has various known issues and shouldn't be used anymore.
> Xorg is normally able to automatically detect and use all GPUs in a
> system without any xorg.conf file.
> 
> 
>> if i set radeon.modeset=0  nouveau.modeset=0 no video working ... no tty
>> too ;-)
> 
> That disables both kernel drivers, which are required for fbcon and Xorg.
> 
> 
>> On P5020
>> last of my test is this machine with a  radeon hd 7770 core edition
>> if radeon drv is running the system run in softpipe mode and i face many
>> drm errors and fence issue.
>> i atteched the dmesg files.
> 
> Which kernel version are you testing? There were some fixes in 4.4/4.5
> which may help for the kernel driver issues, but note that the Mesa
> radeonsi driver for >= 7xxx Radeons still needs a lot of work to be
> usable on big endian systems.
> 
> 
> -- 
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
> ___
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: radeonhd and xorg issues on powerpc p5020 and G5

[luigi burdo]

hi michel,
without xorg conf on cyrus+ p5020, and g5 quad i have only the black screen 
with pulse cursor. i need to made it and put in etc/X11/ or not desktop at all.

about modeset=0 on both cards:
yes i know is normal dont have video but i think the more strange is have the 
opposite compared the kernel options . with kernel radeon. modeset=0 and 
nouveau.modeset=1 look like xorg understand to activate the radeon and 
deactivate the nouveau .
and this make the system stalling without any way to recover.

about radeonsi, will check  on 7750 too and report.
for now 4xxx,5xxx,6xxx can say are running on ppc system with 3d too , yes many 
endianess on egl and egl2 colors not right and some creazy texture on some 
games but ... running ;-)

ciao
luigi




Inviato da iPad

> Il giorno 30 apr 2016, alle ore 09:10, Michel Dänzer  ha 
> scritto:
> 
>> On 23.04.2016 02:06, luigi burdo wrote:
>> 
>> On Quad G5 with 2 video boards
>> if i set radeon.modeset=1  nouveau.modeset=1 Xorg -configure dont found
>> at all the video boards
>> if i set radeon.modeset=0  nouveau.modeset=1 Xorg -configure dont found
>> the nouveau board
>> if i set radeon.modeset=1  nouveau.modeset=0 Xorg -configure dont found
>> the radeon board
> 
> Xorg -configure has various known issues and shouldn't be used anymore.
> Xorg is normally able to automatically detect and use all GPUs in a
> system without any xorg.conf file.
> 
> 
>> if i set radeon.modeset=0  nouveau.modeset=0 no video working ... no tty
>> too ;-)
> 
> That disables both kernel drivers, which are required for fbcon and Xorg.
> 
> 
>> On P5020
>> last of my test is this machine with a  radeon hd 7770 core edition
>> if radeon drv is running the system run in softpipe mode and i face many
>> drm errors and fence issue.
>> i atteched the dmesg files.
> 
> Which kernel version are you testing? There were some fixes in 4.4/4.5
> which may help for the kernel driver issues, but note that the Mesa
> radeonsi driver for >= 7xxx Radeons still needs a lot of work to be
> usable on big endian systems.
> 
> 
> -- 
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: radeonhd and xorg issues on powerpc p5020 and G5

[Michel Dänzer]

On 23.04.2016 02:06, luigi burdo wrote:
> 
> On Quad G5 with 2 video boards
> if i set radeon.modeset=1  nouveau.modeset=1 Xorg -configure dont found
> at all the video boards
> if i set radeon.modeset=0  nouveau.modeset=1 Xorg -configure dont found
> the nouveau board
> if i set radeon.modeset=1  nouveau.modeset=0 Xorg -configure dont found
> the radeon board

Xorg -configure has various known issues and shouldn't be used anymore.
Xorg is normally able to automatically detect and use all GPUs in a
system without any xorg.conf file.


> if i set radeon.modeset=0  nouveau.modeset=0 no video working ... no tty
> too ;-)

That disables both kernel drivers, which are required for fbcon and Xorg.


> On P5020
> last of my test is this machine with a  radeon hd 7770 core edition
> if radeon drv is running the system run in softpipe mode and i face many
> drm errors and fence issue.
> i atteched the dmesg files.

Which kernel version are you testing? There were some fixes in 4.4/4.5
which may help for the kernel driver issues, but note that the Mesa
radeonsi driver for >= 7xxx Radeons still needs a lot of work to be
usable on big endian systems.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev