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

[Rin Okuyama <rokuyama%rk.phys.keio.ac.jp@localhost>]

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

From: Rin Okuyama <rokuyama%rk.phys.keio.ac.jp@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-evbarm/52984 RPI/earmv6hf and earmv7hf: omxplayer abort trap
Date: Sun, 19 Aug 2018 21:10:32 +0900

 I did bisect kernel for earmv6hf on Raspberry Pi 3B.
 Userland and omxplayer are taken from Jun's image of NetBSD 8.0:
 
 http://cdn.netbsd.org/pub/NetBSD/misc/jun/raspberry-pi/NetBSD-8.0/
 
 (a) Kernel as of 2017-12-10 00:00:00 UTC (just BEFORE FDTization)
 ---> OK
 
 (b) Kernel as of 2017-12-11 00:00:00 UTC (just AFTER FDTization)
 ---> NG
 
 The problem turned out to be due to FDTization, as Jun expected.
 
 However, our code itself does not matter, perhaps; I tried to convert
 kernel (a) into netbsd.img (format for FDTizaed kernel), and copy it to
 /boot/kernel7.img. Then, kernel boots normally, and dmesg is not changed
 from original netbsd.bin of (a). But, only omxplayer aborts!
 
 I expect that firmware initializes vchiq in different manners depending
 on whether kernel supports FDT or not. As a result, omxplayer does not
 work on kernel after FDTization.
 
 P.S.
 I changed category of PR from pkg to port-evbarm. But, edit-pr did not
 ask me why...