mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Adam Belay <abelay@novell.com>
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
Subject: Re: [RFC][PATCH] PCI bridge driver rewrite (rev 02)
Date: Mon, 7 Mar 2005 23:56:44 -0500	[thread overview]
Message-ID: <77E20AAF-8F8E-11D9-A2CF-000393ACC76E@mac.com> (raw)
In-Reply-To: <1110241206.12485.27.camel@localhost.localdomain>

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



  reply	other threads:[~2005-03-08  4:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 22:32 Adam Belay
2005-03-07 23:03 ` Jon Smirl
2005-03-08  0:20   ` Adam Belay
2005-03-08  4:56     ` Kyle Moffett [this message]
2005-03-07 23:39 ` Jon Smirl
2005-03-07 23:43   ` Jesse Barnes
2005-03-07 23:57     ` Adam Belay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=77E20AAF-8F8E-11D9-A2CF-000393ACC76E@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=abelay@novell.com \
    --cc=greg@kroah.com \
    --cc=jonsmirl@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®