Re: port-evbarm/52984 (RPI/earmv6hf and earmv7hf: omxplayer abort trap)

[Nick Hudson <nick.hudson%gmx.co.uk@localhost>]

The following reply was made to PR port-evbarm/52984; it has been noted by GNATS.

From: Nick Hudson <nick.hudson%gmx.co.uk@localhost>
To: Rin Okuyama <rokuyama%rk.phys.keio.ac.jp@localhost>, gnats-bugs%NetBSD.org@localhost,
 port-evbarm-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost, jun%soum.co.jp@localhost,
 "Jared D. McNeill" <jmcneill%invisible.ca@localhost>
Cc: 
Subject: Re: port-evbarm/52984 (RPI/earmv6hf and earmv7hf: omxplayer abort
 trap)
Date: Wed, 22 Aug 2018 09:05:55 +0100

 On 22/08/2018 04:00, Rin Okuyama wrote:
 > Finally, omxplayer works fine on -current kernel without any tricks!!
 >
 > According to this thread in official RPI repository in github,
 >
 > https://github.com/raspberrypi/firmware/issues/763
 >
 > when v3d, hdmi, pixelvalve, or hvs are enabled in FDT blog, firmware
 > turns off GPU functionality of VideoCore, expecting OS drivers control
 > it appropriately.
 >
 > Therefore, these features are explicitly disabled in *.dtb, till we
 > add drivers for them (hdmi is already turned off in our DTS):
 >
 > http://www.netbsd.org/~rin/rpi_dts_20180822.patch
 >
 > With this patch, omxplayer works fine on Raspberry Pi 3B. And
 > everything including genfb and X also works fine as before.
 >
 > OK to commit this fix?
 
 I think so, but Jared was keen to not touch the files directly and might 
 have an alternative method here
 
 >
 > rin
 
 Nick