public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Jon Smirl <jonsmirl@gmail•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Access to PCI Expansion ROMs on PPC
Date: Mon, 26 Nov 2007 08:34:06 +1100	[thread overview]
Message-ID: <1196026446.7195.76.camel@pasglop> (raw)
In-Reply-To: <9e4733910711251324y5116d90pab54a1a033d024e3@mail.gmail.com>


> You can dump the PCI config block in /sys with hexdump and see if the
> PCI_COMMAND_MEMORY bit is set. I was also unable to locate where in
> the kernel PCI_COMMAND_MEMORY is being set. It could be that it is set
> by the BIOS at boot on the x86 and not on the ppc.

The kernel doesn't until somebody calls pci_enable_device(). So yes,
that's likely to be your problem.

Ben.

  reply	other threads:[~2007-11-25 21:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25  1:57 Access to PCI Expansion ROMs on PPC Robin H. Johnson
2007-11-25  2:13 ` Jon Smirl
2007-11-25 11:15   ` Robin H. Johnson
2007-11-25 11:49     ` Robin H. Johnson
2007-11-25 13:30       ` Jon Smirl
2007-11-25 19:41         ` Robin H. Johnson
2007-11-26  8:59           ` Robin H. Johnson
2007-11-26  9:20             ` Michel Dänzer
2007-11-26 10:24               ` Robin H. Johnson
2007-11-26 16:33                 ` Jon Smirl
2007-11-26 17:35                   ` Robin H. Johnson
2007-11-25 20:20         ` Benjamin Herrenschmidt
2007-11-25 20:51           ` Jon Smirl
2007-11-25 20:54             ` Benjamin Herrenschmidt
2007-11-25 21:24           ` Jon Smirl
2007-11-25 21:34             ` Benjamin Herrenschmidt [this message]
2007-11-25  9:42 ` Andreas Schwab
2007-11-25  9:58   ` Robin H. Johnson

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=1196026446.7195.76.camel@pasglop \
    --to=benh@kernel$(echo .)crashing.org \
    --cc=jonsmirl@gmail$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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