From owner-freebsd-ppc@FreeBSD.ORG Thu Oct 18 19:27:53 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB289226 for ; Thu, 18 Oct 2012 19:27:53 +0000 (UTC) (envelope-from robballantyne3@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 709898FC08 for ; Thu, 18 Oct 2012 19:27:52 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id x43so6589222wey.13 for ; Thu, 18 Oct 2012 12:27:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lQc+6uInGbMmhyD3OkhkVL8WXk+R/efOdyerYCT9SQg=; b=ssFRfVY2POir0Y64wUj9SvnZSEPjckB4W93amNq2F0gAsSmUKCf7yrNWNPB2De1VIe 5mRleYNgFbPwJ6W9agJE1suQVZ17uCI+aFLXjjg5oVtjxcm2hgBL0BU3AWQTTs1QrCyv HZxW/yIggN6uRA2RyVjFn3UmhvbRLlcT+Z6r4HQTMhfaCmjZwkIKhQxIv0sKsSLycp3a BTWN/allEXhOD2rGv/D8YZcifKNSlrruB0G6evWsBqsG4bKlqbI9YCzW5twZ7Pyc6aPt 5tAM+Qtgz4CVXxZ1aIK+BlJtkUNOXwVb0esUvEKt2fex3ZI460LUfIoeBlbKvsTkEfN6 6WTQ== MIME-Version: 1.0 Received: by 10.216.72.5 with SMTP id s5mr13693957wed.154.1350588471904; Thu, 18 Oct 2012 12:27:51 -0700 (PDT) Received: by 10.223.159.207 with HTTP; Thu, 18 Oct 2012 12:27:51 -0700 (PDT) Date: Thu, 18 Oct 2012 12:27:51 -0700 Message-ID: Subject: Open Firmware available after kernel is running? From: Rob Ballantyne To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2012 19:27:54 -0000 Hi All, I was wondering if the Open Firmware client interface is available after the kernel is booted. For example, could I write a kernel module that accessed Open Firmware via the client interface? I'm supposing that there is likely a static variable that points to the client interface that is stashed there in early startup -- I understand open firmware passes it's own address to the client program on the stack. However, I'm also guessing that the kernel may have taken completely over the machine in a way that doesn't permit access to the OF client interface. It appears that ~/sys/powerpc/aim/locore64.S stashes the entry point for OF in openfirmware_entry - is this still usable after the system is up and running? Thanks, Rob