From owner-freebsd-sparc64@freebsd.org Sun Sep 6 13:42:45 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 ED5AE9CC17F for ; Sun, 6 Sep 2015 13:42:45 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id DCA3B8E9; Sun, 6 Sep 2015 13:42:45 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id DB0F915C6; Sun, 6 Sep 2015 13:42:45 +0000 (UTC) Date: Sun, 6 Sep 2015 13:42:45 +0000 From: Alexey Dokuchaev To: Mark Cave-Ayland Cc: John Baldwin , "freebsd-sparc64@freebsd.org" Subject: Re: PCI range checking under qemu-system-sparc64 Message-ID: <20150906134245.GA21410@FreeBSD.org> References: <557C1162.3000106@FreeBSD.org> <557D82F8.50908@ilande.co.uk> <557DA6D5.4070800@FreeBSD.org> <557DCF54.7020606@ilande.co.uk> <557DF887.20508@ilande.co.uk> <20150906110308.GA68829@FreeBSD.org> <55EC2E8D.4020803@ilande.co.uk> <20150906124859.GA14919@FreeBSD.org> <55EC3949.1020508@ilande.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55EC3949.1020508@ilande.co.uk> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Sun, 06 Sep 2015 13:42:46 -0000 On Sun, Sep 06, 2015 at 02:02:01PM +0100, Mark Cave-Ayland wrote: > I wonder if the problem is just that suitable console drivers can't > be found? > > > ebus0: addr 0x14000003f8-0x14000003ff irq 43 (no driver attached) > > ebus0: addr 0x1400000060-0x1400000067 (no driver attached) > > The QEMU hardware model is still a WIP and the serial port currently > uses a 16550A UART (su) device rather than ESCC found in real hardware, > while the keyboard is a simple PS2 keyboard. > > If you alter your kernel configuration to include building of the su and > ps2 driver modules, does this help with detection of the serial and > keyboard devices and if so, does boot progress any further at all? Hmm, I'm running GENERIC, so it looks like everything should be already there, no? At least by looking at ./conf/files.sparc64 I don't see what else ("device ???") should I add to it to get su/kb_ps2 support... ./danfe