linux-kernel - Re: [PATCH 1/2] OLPC: Add support for calling into Open Firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440804202150l535519c9mcb635c7ca55216ed@mail.gmail.com>
Date:	Sun, 20 Apr 2008 21:50:07 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Mitch Bradley" <wmb@...mworks.com>
Cc:	"Andres Salomon" <dilinger@...ued.net>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Joseph Fannin" <jfannin@...il.com>, linux-kernel@...r.kernel.org,
	jordan.crouse@....com
Subject: Re: [PATCH 1/2] OLPC: Add support for calling into Open Firmware

On Sun, Apr 20, 2008 at 9:05 PM, Mitch Bradley <wmb@...mworks.com> wrote:
>
>
>
>  Yinghai Lu wrote:
>
> > On Sun, Apr 20, 2008 at 8:09 PM, Mitch Bradley <wmb@...mworks.com> wrote:
> >
> >
> > >
> > >  Yinghai Lu wrote:
> > >
> > >
> > >
> > > > how about changing to ofw_32.c?
> > > >
> > > > YH
> > > >
> > > >
> > > >
> > > >
> > >  Is your suggestion to change the filename from "ofw.c" to "ofw_32.c"?
> That
> > > seems like a good idea to me.
> > >
> > >
> >
> > Yes.
> >
> > BTW,  why olpc need OFW runtime service?
> > why not just put the info in in ram with some signiture, so
> > kernel/util just need to loot at the table if needed?
> >
> >
>
>  In SPARC land, at least on SunOS and Solaris, it was very convenient for
> debugging to interrupt the OS with Stop-A and use OFW to inspect the system
> state.  That was especially handy for live crash analysis.  Dumps are useful
> as far as they go, but they often fail to capture detailed I/O device state.
>
>  I was hoping to do that on x86 too.  So far we (OLPC) haven't implemented a
> sysrq hook to enter OFW, but I haven't given up hope yet.  It doesn't cost
> much to leave OFW around, but once you decide to eject it, you can't easily
> get it back.

geode is using SMI to simulate the pci conf space, wonder that could be problem.

later you have 64 runtime service for 64 platform like UEFI?

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/