[PATCH RFC v1] ARM: olpc: Add support for calling into the XO-1.75's OpenFirmware (OFW)
eric.y.miao at gmail.com
Thu Aug 4 19:32:06 EDT 2011
On Fri, Aug 5, 2011 at 12:25 AM, Andres Salomon <dilinger at queued.net> wrote:
> Add support for saving OFW's cif, and later calling into it to run OFW
> commands from the kernel. OFW remains resident in memory after boot,
> and the physical/virtual addresses are passed in a boot tag. We parse
> that, and map the addresses.
> This is currently only used by the OLPC XO-1.75, so it's named olpc_ofw().
> Signed-off-by: Andres Salomon <dilinger at queued.net>
> Documentation/arm/Setup | 2 +
> arch/arm/Kconfig | 8 ++
> arch/arm/include/asm/olpc_ofw.h | 23 ++++++
> arch/arm/include/asm/setup.h | 24 ++++++
> arch/arm/mach-mmp/Makefile | 1 +
> arch/arm/mach-mmp/include/mach/vmalloc.h | 2 +-
> arch/arm/mach-mmp/olpc-xo-1-75.c | 7 ++
> arch/arm/mach-mmp/olpc_ofw.c | 118 ++++++++++++++++++++++++++++++
> 8 files changed, 184 insertions(+), 1 deletions(-)
> create mode 100644 arch/arm/include/asm/olpc_ofw.h
> create mode 100644 arch/arm/mach-mmp/olpc_ofw.c
> I'm looking for input on our mechanism for calling into OLPC's openfirmware
> on arm. Some of the x86 folks are cc'd
> as they had lots of comment when we did this for x86 OLPC machines.
> There's a device tree patch on top of this that can be seen here:
> Unlike the XO-1, I'd like to get this OFW communication mechanism ACKed prior to
> OLPC's mass production of these units.
Not really sure if it's the standard way of calling back into GFW, Grant?
More information about the linux-arm-kernel