search

linuxppc / issues

Issues repository for linuxppc
5 stars 0 forks source link

Wii U support #410

Open mpe opened 2 years ago

mpe commented 2 years ago

Some support for Wii U was posted:

http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=288561

There were some comments from Rob on the device tree bindings.

Waiting for a v2.

mpe commented 2 years ago

v3 posted: http://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=83551

chleroy commented 9 months ago

There a v4 now : http://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=83551

krzk commented 9 months ago

v4 was not tested, just like none of earlier versions, so cannot be really merged.

kth5 commented 9 months ago

I could help testing this on a EU 32GB model but I am not sure how to approach this properly. Is there a guide I could follow?

On Tue 20. Feb 2024 at 17:25, Krzysztof Kozlowski @.***> wrote:

v4 was not tested, just like none of earlier versions, so cannot be really merged.

— Reply to this email directly, view it on GitHub https://github.com/linuxppc/issues/issues/410#issuecomment-1954582542, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANTZIGQ6O7JVD6ZYP3TNGTYUTE6BAVCNFSM5WHIBACKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJVGQ2TQMRVGQZA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

krzk commented 9 months ago

Testing with automated tools, dt_binding_check and dtbs_check. Just like C code should be tested with static analyzers like smatch and sparse. See for example: https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/