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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 20 Apr 2008 21:26:56 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	wmb@...mworks.com
Cc:	yhlu.kernel@...il.com, dilinger@...ued.net, hpa@...or.com,
	ebiederm@...ssion.com, mingo@...e.hu, akpm@...ux-foundation.org,
	jfannin@...il.com, linux-kernel@...r.kernel.org,
	jordan.crouse@....com
Subject: Re: [PATCH 1/2] OLPC: Add support for calling into Open Firmware

From: Mitch Bradley <wmb@...mworks.com>
Date: Sun, 20 Apr 2008 18:05:26 -1000

> 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.

In most current SPARC systems, OFW is not usable and is completely
forgotten right after bootup in order to accomodate LDOMs and CPU
hotplug.

It's a better idea, anyways, to develop more pervasive and usable
in-kernel debugger facilities.  Then it doesn't matter if you have
"cool" firmware or not. :-)

--
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/