From: roger blofeld <blofeldus@yahoo.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Yenta + sata_sil + 2.6.30.8 fails because dma_ops==NULL
Date: Wed, 14 Oct 2009 20:56:53 -0700 (PDT) [thread overview]
Message-ID: <71202.24923.qm@web53511.mail.re2.yahoo.com> (raw)
Hi
I have a powerbook G4 which has drives connected via a cardbus sata_sil. It is running fedora 11. It boots fine with 2.6.27.35-170.2.94.fc10.ppc, but with 2.6.30.8-64.fc11.ppc because of an error in the probe function of sata_sil.
I have traced the problem to be the line in sata_sil.c function sil_init_one
rc = pci_set_dma_mask(pdev, ATA_DMA_MASK);
which returns -5 (-EIO) because
get_dma_ops(&pdev->dev);
returns NULL.
I looked at the diffs to sata_sil.c between these kernel revs and didn't see the problem. Seems to be something at a higher level changed.
Any ideas where I should look or how to find the real cause?
Thanks
-roger
P.S., on the working kernel lspci gives:
0001:11:00.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
reply other threads:[~2009-10-15 3:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=71202.24923.qm@web53511.mail.re2.yahoo.com \
--to=blofeldus@yahoo.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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