From: "Norman Diamond" <n0diamond@yahoo.co.jp>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Robert Hancock" <hancockrwd@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>,
"Jim Paris" <jim@jtan.com>,
"Sergei Shtylyov" <sshtylyov@ru.mvista.com>,
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
"Mark Lord" <liml@rtr.ca>
Subject: Re: Off-by-one in both LIBATA and IDE drivers
Date: Sat, 14 Mar 2009 18:34:23 +0900 [thread overview]
Message-ID: <078E30E4A81049A2847E24B3CF39BB5C@DIAMOND8600> (raw)
In-Reply-To: <20090314084827.2f2b05c2@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> [attribution stolen:]
>> ata_piix should definitely attach to 8086/7111 regardless of the
>> subsystem IDs. I can't really explain why it's not. You should at least
>> be seeing a message about the ata_piix version, if not then somehow the
>> driver probe function isn't even being called..
>
> Because on at least some kernels
> hda=noprobe ... etc
> does not stop the old IDE layer grabbing the PCI device and continuing to
> claim ownership (which means ATA cannot attach to it).
That could be part of the explanation. dmesg did include the usual
statements about PIIX4 not being 100% native and irqs would be probed later
(though of course they weren't probed later).
> Arguably this is correct behaviour as the IDE layer was asked to ignore
> the devices *NOT* to ignore the controller.
That doesn't explain why ide0=noprobe ide1=noprobe hda=none hdb=none
hdc=none hdd=none still didn't stop the old IDE layer from grabbing
something. ATA didn't report whether there was something it couldn't grab
onto, all it did was report loading and that was the end of it.
Alan Cox also wrote:
> [Norman Diamond:]
>> I think the PIIX4 devices of VMware server are well known. Besides
>> vendor 8086 and device 7111, VMware's subsystem is coded into LIBATA's
>> PIIX driver.
>
> That is a known working case so its something about your setup or build.
I doubt it. I think your other message explained part of the reason, though
something is still missing.
> You might want to try building with CONFIG_IDE=n and CONFIG_ATA + ATA_PIIX
> + AHCI = y to double check your config.
CONFIG_ATA + ATA_PIIX + AHCI were always y all along. An experiment
changing old IDE from y to m got PIIX4 working, but I'm still nervous about
lots of cases where I don't have machines with other old IDE chipsets to
test.
--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/
next prev parent reply other threads:[~2009-03-14 9:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 1:50 Norman Diamond
2009-03-11 3:03 ` Jim Paris
2009-03-11 3:28 ` Norman Diamond
[not found] ` <49B78859.5050807@ru.mvista.com>
2009-03-11 21:03 ` Norman Diamond
2009-03-12 11:20 ` Norman Diamond
2009-03-12 14:30 ` Mark Lord
2009-03-12 23:02 ` Norman Diamond
2009-03-13 7:41 ` Norman Diamond
2009-03-13 14:45 ` Robert Hancock
2009-03-14 2:05 ` Norman Diamond
2009-03-14 2:15 ` Robert Hancock
2009-03-14 8:48 ` Alan Cox
2009-03-14 9:34 ` Norman Diamond [this message]
2009-03-14 10:48 ` Alan Cox
2009-03-14 8:46 ` Alan Cox
2009-03-11 8:27 ` Alan Cox
2009-03-11 8:38 ` Norman Diamond
2009-03-12 0:10 ` Robert Hancock
2009-03-12 2:28 ` Norman Diamond
2009-03-12 4:26 ` Robert Hancock
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=078E30E4A81049A2847E24B3CF39BB5C@DIAMOND8600 \
--to=n0diamond@yahoo.co.jp \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=hancockrwd@gmail.com \
--cc=jim@jtan.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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
all inboxes | Powered by JetHome®