PCI range checking under qemu-system-sparc64

Mark Cave-Ayland mark.cave-ayland at ilande.co.uk
Sat Sep 19 22:38:30 UTC 2015


On 19/09/15 20:49, Marius Strobl wrote:

> On Fri, Sep 18, 2015 at 07:56:57AM +0100, Mark Cave-Ayland wrote:
>> On 16/09/15 22:19, Marius Strobl wrote:
>>
>>>>> Log is identical to the one I posted earlier (modulo the build timestamps),
>>>>> except this part:
>>>>>
>>>>>  eeprom0: <EEPROM/clock> addr 0x1400002000-0x1400003fff on ebus0
>>>>> -eeprom0: cannot allocate resources
>>>>> -device_attach: eeprom0 attach returned 6
>>>>> +eeprom0: model mk48t59
>>>>>  ebus0: <fdthree> addr 0 (no driver attached)
>>>>> -ebus0: <su> addr 0x14000003f8-0x14000003ff irq 43 (no driver attached)
>>>>> +uart0: <16550 or compatible> addr 0x14000003f8-0x14000003ff irq 43 on ebus0
>>>>> +uart0: console (9600,n,8,1)
>>>>>  ebus0: <kb_ps2> addr 0x1400000060-0x1400000067 (no driver attached)
>>>>
>>>> Well this is definitely progress - at least the ebus attach is now
>>>> sorted :)  I've sent the patch upstream (see
>>>> http://www.openfirmware.info/pipermail/openbios/2015-September/008802.html)
>>>> and will commit it soon if there are no objections.
>>>>
>>>> Next I'll see if I can get the 8042 part of the device tree correct in
>>>> order to attach the PS/2 keyboard driver.
>>
>> Last night I spent a few hours trying to fix up the device model for the
>> keyboard device (whilst also inserting an 8042 node). The binary I have
>> works for a NetBSD 7 ISO, although they have included a workaround for a
>> missing interrupt-map property which I've also added in.
>>
>> I've updated the image at https://www.ilande.co.uk/tmp/openbios-sparc64
>> with these fixes if someone could test and confirm that FreeBSD now
>> reports an attach of the kb_ps2 device.
> 
> With that version OpenBIOS is getting better regarding the 8042 part
> but isn't quite there, yet. For atkbdc(4) to attach, besides "kb_ps2"
> there also needs to be the "kdmouse" node beneath the "8042" one and
> the latter must have a second address identical to the first one in
> its "reg" property.

Interesting. On both NetBSD and OpenBSD I get a successful attach with
just the kb_ps2 device node. I guess that advertising a non-existent
mouse port shouldn't do any harm, as attempted accesses will just be
ignored. I'll add the kdmouse device and report back.


ATB,

Mark.



More information about the freebsd-sparc64 mailing list