From: olof@lixom.net (Olof Johansson)
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: Geary Sean-R60898 <sean.geary@freescale.com>,
linuxppc-dev@ozlabs.org,
Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Subject: Re: Update on: MPC85xx git/MPC8548cds - PCI/PCIE problemS with Marvel SATA driver...
Date: Fri, 23 Feb 2007 21:16:49 -0600 [thread overview]
Message-ID: <20070224031649.GA26751@lixom.net> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D901053E84AA@EMPBEDEX.empirix.com>
On Fri, Feb 23, 2007 at 05:47:22PM -0500, Morrison, Tom wrote:
> Olof,
>
> Are you saying that it must 'know' about the PCI id(s)
> for this SATA card before it even probes that device???
>
> Even though the module is compiled into the kernel and
> I've verified that:
>
> a) the pci scan bus has detected this device
> b) that the sata_mv driver is registering itself
> as a PCI Device driver?
Yes. There's the device on the bus, and there's the PCI bus code that will
walk all busses and enumerate all devices. Then there's the driver. All
drivers have a small table that they use to specify which PCI devices
they are usable with, so if the device isn't listed, the driver won't
get involved.
See the sata_mv sources for more info, search for '7042' and you'll find
the table, at least if you're looking at the 2.6.20 sources.
> Also, fyi, its also complaining about the PCI Express
> Root Bridge on the MPC8548 as an unknown device...
>
> manufacturer: 0x1957 (aka: Freescale)
> class: 0xFFFF
What complains? lspci? Or the kernel? lspci is just a high-level program
that has a database that maps the numerical codes to manufacturers and
devices. The database might be out of date, or someone forgot to submit
the device IDs to it. It happens all the time.
> although that doesn't explain why the same PCI
> Express SATA card / ~same sata_mv driver on an
> Intel X86 platform doesn't get recognized either.
Same thing -- PCI id missing from the driver.
> Thank you for any additional insight you have on this Olof!
-Olof
next prev parent reply other threads:[~2007-02-24 3:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 20:25 MPC85xx git branch - problem with Marvel SATA driver Morrison, Tom
2007-02-16 20:43 ` Andy Fleming
2007-02-16 22:02 ` Morrison, Tom
2007-02-20 19:41 ` Andy Fleming
2007-02-20 20:58 ` Morrison, Tom
2007-02-23 19:57 ` Update on: MPC85xx git/MPC8548cds - PCI/PCIE problemS " Morrison, Tom
2007-02-23 20:29 ` Olof Johansson
2007-02-23 22:47 ` Morrison, Tom
2007-02-24 3:16 ` Olof Johansson [this message]
2007-02-24 8:25 ` Benjamin Herrenschmidt
2007-02-26 0:18 ` Timur Tabi
2007-02-26 17:01 ` Morrison, Tom
2007-02-27 16:45 ` Another Update (SUCCESS) on: MPC85xx git/MPC8548cds - PCI/PCIE problemS w/ " Morrison, Tom
2007-02-27 17:16 ` Kumar Gala
2007-02-28 15:38 ` Andy Fleming
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=20070224031649.GA26751@lixom.net \
--to=olof@lixom.net \
--cc=Wei.Zhang@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sean.geary@freescale.com \
--cc=tmorrison@empirix.com \
/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;
as well as URLs for NNTP newsgroup(s).