-peter

On Dec 19, 2013, at 11:27 AM, Mark Cave-Ayland <mark.cave-ayl...@ilande.co.uk> 
wrote:
> On 19/12/13 12:59, Artyom Tarasenko wrote:
> 
>> Hi Mark,
>> 
>> this patch breaks booting with OBP:
>> 
>> Probing /iommu@0,10000000/sbus@0,10001000 at 5,0  espdma esp sd st
>> SUNW,bpp ledma le
>> Probing /iommu@0,10000000/sbus@0,10001000 at 4,0  SUNW,CS4231 
>> power-management
>> Probing /iommu@0,10000000/sbus@0,10001000 at 1,0  Nothing there
>> Probing /iommu@0,10000000/sbus@0,10001000 at 2,0  Nothing there
>> Probing /iommu@0,10000000/sbus@0,10001000 at 3,0  SUNW,tcx Memory
>> Address not Aligned
>> 
>> ^^^^ After the unaligned access OBP is not properly initialized.
>> See the bug 1262081, reported by Peter Bartoli.
>> 
>> Artyom
> 
> Ah... I wonder if OBP doesn't like something in the QEMU,tcx.bin FCode 
> initialisation function? If you temporarily rename the file (which can be 
> found in the share directory) to something else, does boot start to work 
> again?
> 
> Thinking about it, I suspect I'll need to add some code to the OpenBIOS FCode 
> ROMs so that they only initialise if OpenBIOS is detected. This is because 
> there is code there that tries to get information from QEMU about the screen 
> width/height/depth etc. which will obviously fail on OBP.
> 
> 
> ATB,
> 
> Mark.


Out of curiosity, and please pardon my ignorance and separate bug filing about 
the tcx not working with OBP ... but why is it that this doesn't work?

-peter

Reply via email to