From owner-freebsd-sparc64@freebsd.org Sat Sep 19 22:38:30 2015 Return-Path: Delivered-To: freebsd-sparc64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86A08A059DC for ; Sat, 19 Sep 2015 22:38:30 +0000 (UTC) (envelope-from mark.cave-ayland@ilande.co.uk) Received: from s16892447.onlinehome-server.info (s16892447.onlinehome-server.info [82.165.15.123]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4412C1B2C; Sat, 19 Sep 2015 22:38:29 +0000 (UTC) (envelope-from mark.cave-ayland@ilande.co.uk) Received: from cpc2-slam8-2-0-cust642.2-4.cable.virginm.net ([82.24.206.131] helo=[192.168.0.5]) by s16892447.onlinehome-server.info with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1ZdQlt-0004bs-OO; Sat, 19 Sep 2015 23:38:20 +0100 Message-ID: <55FDE3CA.2030707@ilande.co.uk> Date: Sat, 19 Sep 2015 23:38:02 +0100 From: Mark Cave-Ayland User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Marius Strobl CC: Alexey Dokuchaev , "freebsd-sparc64@freebsd.org" References: <20150907203152.GA70457@alchemy.franken.de> <55EDFE00.9090109@ilande.co.uk> <20150913022143.GA7862@alchemy.franken.de> <20150913103940.GA60101@FreeBSD.org> <20150913180126.GC7862@alchemy.franken.de> <55F89861.1030107@ilande.co.uk> <20150916031030.GA6711@FreeBSD.org> <55F9C2B8.7030605@ilande.co.uk> <20150916211914.GD18789@alchemy.franken.de> <55FBB5B9.7020401@ilande.co.uk> <20150919194915.GJ18789@alchemy.franken.de> In-Reply-To: <20150919194915.GJ18789@alchemy.franken.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 82.24.206.131 X-SA-Exim-Mail-From: mark.cave-ayland@ilande.co.uk Subject: Re: PCI range checking under qemu-system-sparc64 X-SA-Exim-Version: 4.2.1 (built Sun, 08 Jan 2012 02:45:44 +0000) X-SA-Exim-Scanned: No (on s16892447.onlinehome-server.info); Unknown failure X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 22:38:30 -0000 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: addr 0x1400002000-0x1400003fff on ebus0 >>>>> -eeprom0: cannot allocate resources >>>>> -device_attach: eeprom0 attach returned 6 >>>>> +eeprom0: model mk48t59 >>>>> ebus0: addr 0 (no driver attached) >>>>> -ebus0: 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: 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.