I seee. Do you know whether it's possible to use pure acpi functions only w/o reading the conf space manually? I'm just wondering how much could I acpi-ed my kernel<br><br>Hilfi Alkaff<br><br><div class="gmail_quote">
On Mon, Aug 15, 2011 at 11:42 AM, Timothy Roscoe <span dir="ltr"><<a href="mailto:troscoe@inf.ethz.ch">troscoe@inf.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hilfi,<br>
<br>
We do low-level PCI reads/writes to configuration space just like<br>
everyone else does - the only difference is the use of the Mackerel<br>
DSL to specify register formats. pci_hdr1.dev is a Mackerel<br>
specification of the PCI type 1 (bridge) header; the format is<br>
documented in the Mackerel manual (Technical note #2). If you read<br>
that documentation, plus the pci_hdr1.dev file, you'll see that<br>
pci_hdr1_vendor_id_rd() is the function to read the vendor id field of<br>
a PCI config header.<br>
<br>
-- Mothy<br>
<div><div></div><div class="h5"><br>
At Mon, 15 Aug 2011 11:03:41 -0700, hilfi alkaff <<a href="mailto:hilfialkaff@berkeley.edu">hilfialkaff@berkeley.edu</a>> wrote:<br>
> Hi,<br>
><br>
> I have some follow up questions regarding the same topic. how do you guys<br>
> read the device ID, vendor ID of the pci? I see this function<br>
> pci_hdr1_vendor_id_rd() but I don't really understand about the .dev file<br>
> format. Do you guys read from the pci conf headers or using acpi commands?<br>
><br>
> Thanks,<br>
> Hilfi Alkaff<br>
><br>
> On Thu, Aug 4, 2011 at 5:01 PM, hilfi alkaff <<a href="mailto:hilfialkaff@berkeley.edu">hilfialkaff@berkeley.edu</a>>wrote:<br>
><br>
> > Oh, of course, how I did not realize that, >.<,, Thanks!<br>
> ><br>
> > Hilfi Alkaff<br>
> ><br>
> ><br>
> > On Thu, Aug 4, 2011 at 4:16 PM, Baumann Andrew <<a href="mailto:andrewb@inf.ethz.ch">andrewb@inf.ethz.ch</a>>wrote:<br>
> ><br>
> >> Hi,****<br>
> >><br>
> >> ** **<br>
> >><br>
> >> I’m not sure what you mean by this, since pci_add_root() is a function in<br>
> >> Barrelfish and not ACPICA, but the general answer to your question is<br>
> >> probably that you can’t use the ACPICA reference in isolation: you also need<br>
> >> to grok parts of the PCI spec (or just the bad Mindshare books), the ACPI<br>
> >> spec, the PNPBIOS spec (mainly just for the device IDs), and if in doubt<br>
> >> also the source code to something clean like FreeBSD to make sense of it<br>
> >> all.****<br>
> >><br>
> >> ** **<br>
> >><br>
> >> Good luck :)****<br>
> >><br>
> >> ** **<br>
> >><br>
> >> Andrew****<br>
> >><br>
> >> ** **<br>
> >><br>
> >> *From:* hilfi alkaff [mailto:<a href="mailto:hilfialkaff@berkeley.edu">hilfialkaff@berkeley.edu</a>]<br>
> >> *Sent:* Thursday, 04 August, 2011 15:47<br>
> >> *To:* <a href="mailto:barrelfish-users@lists.inf.ethz.ch">barrelfish-users@lists.inf.ethz.ch</a><br>
> >> *Subject:* [Barrelfish-users] Details regarding pci support with acpi****<br>
> >><br>
> >> ** **<br>
> >><br>
> >> Hi,<br>
> >><br>
> >> I'm an undergraduate currently working on a research operating system and<br>
> >> I'm having problems when initializing pci and mapping its interrupts with<br>
> >> ACPI. I'm wondering how do you guys figure out the pci_add_root() function<br>
> >> because I could not find any meaningful details in Intel's acpica reference.<br>
> >><br>
> >> Thanks,<br>
</div></div>> >> Hilfi Alkaff****<br>
> >><br>
> ><br>
> ><br>
><br>
</blockquote></div><br>