In-Reply-To: <1110241206.12485.27.camel@localhost.localdomain>
References: <1110234742.2456.37.camel@localhost.localdomain> <9e47339105030715034a8f8ff9@mail.gmail.com> <1110241206.12485.27.camel@localhost.localdomain>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <77E20AAF-8F8E-11D9-A2CF-000393ACC76E@mac.com>
Content-Transfer-Encoding: 7bit
Cc: greg@kroah.com, linux-pci@atrey.karlin.mff.cuni.cz,
       linux-kernel@vger.kernel.org, Jon Smirl <jonsmirl@gmail.com>,
       len.brown@intel.com
From: Kyle Moffett <mrmacman_g4@mac.com>
Subject: Re: [RFC][PATCH] PCI bridge driver rewrite (rev 02)
Date: Mon, 7 Mar 2005 23:56:44 -0500
To: Adam Belay <abelay@novell.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1226
Lines: 34

On Mar 07, 2005, at 19:20, Adam Belay wrote:
> 6.) Open Firmware
>       * I don't know much about it, but I believe it does do similar
>         things to ACPI.
>       * Hopefully it uses EISA ids, but not really sure.  If not, it
>         wouldn't be included.

OpenFirmware is very similar to ACPI, except OpenFirmware interprets the
FORTH programs in the firmware itself, whereas ACPI does it in the OS.  
The
reason for the difference is that on Intel/x86 there is no compatible 
way to
call directly into the firmware from 32-bit code.  You won't find the 
two
on the same system, and they basically provide the same services: device
tree, power management, etc.

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r  
!y?(-)
------END GEEK CODE BLOCK------


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