From owner-freebsd-mips@FreeBSD.ORG Sun Apr 3 21:29:26 2011 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40C06106564A for ; Sun, 3 Apr 2011 21:29:26 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by mx1.freebsd.org (Postfix) with ESMTP id CEA788FC13 for ; Sun, 3 Apr 2011 21:29:25 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKTZjmtfCT+d9bX9v3AVZYzukS2SqSIRLu@postini.com; Sun, 03 Apr 2011 14:29:25 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 3 Apr 2011 14:27:35 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sun, 3 Apr 2011 17:29:13 -0400 From: Andrew Duane To: "mips@freebsd.org" Date: Sun, 3 Apr 2011 17:29:12 -0400 Thread-Topic: Toiling away on booting the new blades Thread-Index: AQHL8kYsPMWbnl7x+ka4JX8mqbSZ3A== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: Toiling away on booting the new blades X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2011 21:29:26 -0000 I've made real progress on getting our Octeon blades to boot with the other= bootstraps. After learning all about the app_descriptors and the octeon_bo= otinfo structures, I've decided on a slightly more modular approach. Rathe= r than faking out the code by hand-crafting these structures, I've decided = to teach the Octeon startup code how decode a standard MIPS bootinfo struct= ure. FreeBSD already has this defined, and I can make it do pretty much eve= rything I want. It's also completely deterministic as to which structure yo= u have in "a3" based on the other registers. It turns out this is pretty simple. I added a parallel routine to octeon_pr= ocess_app_desc_ver_6 to parse a bootinfo and call cvmx_sysinfo_minimal_init= ialize with the info I get from it. Very clean and tidy, and minimal disrup= tion. After that, everything else "just works". I even found a routine to c= raft a phy_mem_desc structure, but it doesn't look like I need it. Since the MIPS bootinfo structure is already part of FreeBSD, is this code = in the startup path something you'd be interested in taking in? -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418