On Feb 4, 2016, at 4:55 PM, Alyssa Milburn wrote:
On Wed, Feb 03, 2016 at 09:58:50PM +0000, Mark Cave-Ayland wrote:
Note that currently we don't add the DBDMA properties at the end of the reg property because QEMU doesn't yet support serial DBDMA, but perhaps it is time to start turning on DBDMA logging to see if this is what's is causing OT to get stuck.
In fact, do we know if OT ever worked on MOL at all or did it provide its own drivers?
In any case, MOL has a comment /* this hack keeps MacOS 9 happy */ just above the point where it enables serial DBDMA on ch-b, so that sounds like a rather big hint for us. I might go try this now..
I did a little research and found out that some of the properties of the escc-legacy's ch-a and ch-b nodes are wrong.
ftp://ftp.software.ibm.com/rs6000/technology/spec/chrp/inwork/CHRP_IORef_1.0.pdf According to this CHRP specifications, page 246, the escc-legacy node is suppose to have a "ranges" property. This is missing. It is also missing the #size-cells properties. The escc-legacy/ch-a node also looks like it's device_type property should be "legacy" rather than serial.