From: Gabriel C <nix.or.die@googlemail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: ata_piix broken in 2.6.22
Date: Fri, 20 Jul 2007 16:02:01 +0200 [thread overview]
Message-ID: <46A0C059.8090506@googlemail.com> (raw)
In-Reply-To: <20070720143510.6ce81c09@the-village.bc.nu>
Alan Cox wrote:
> O> ata_piix 0000:00:1f.2: version 2.11
>> ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
>> ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 16
>> ata_piix 0000:00:1f.2: 0x1F0 IDE port busy
>> ata_piix 0000:00:1f.2: 0x170 IDE port busy
>> ata_piix 0000:00:1f.2: no available legacy port
>
> You appear to have old IDE compiled in as well and finding the device
> first
Alan ,
But this is allowed now and for me, after removing CONFIG_SATA_INTEL_COMBINED option
some other options combos may be illegal and removing it broke a lot working setups.
On <2.6.22 you got on your SATA/PATA controller with CONFIG_IDE=y , ATA=y ( ATA_X=y and even BLK_DEV_X=y) the
SATA disk as SATA and PATA one as IDE now you get the SATA disk as 'IDE' too which gives you almost 3-4MB/s speed.
Is such a config legall for you for an SATA/IDE combo controller in >=2.6.22 ?
CONFIG_BLK_DEV_IDE_SATA=n
CONFIG_IDE=y
ATA=y
BLK_DEV_PIIX=y(or m doesn't matter )
ATA_PIIX=y
IMO after removing CONFIG_SATA_INTEL_COMBINED you guys introduced an real conflict with the IDE subsystem.
The only way to get libata working with such a config is to boot ideX=noprobe.
Regards,
Gabriel
next prev parent reply other threads:[~2007-07-20 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 13:26 ata_piix broken in 2.6.22 Felipe Contreras
2007-07-20 13:35 ` Alan Cox
2007-07-20 14:02 ` Gabriel C [this message]
2007-07-20 13:39 ` Gabriel C
2007-07-20 14:04 ` Felipe Contreras
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=46A0C059.8090506@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=felipe.contreras@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.