From: "Dominic ES. Ijichi" <dom@ijichi.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-ide@vger.kernel.org, Frido Ferdinand <frido@zolder.org>
Subject: Re: PIIX libata ?
Date: Wed, 19 Apr 2006 10:48:26 +0100 (BST) [thread overview]
Message-ID: <31311506.91145440106542.JavaMail.root@willow.ijichi.org> (raw)
----- Randy.Dunlap <rdunlap@xenotime.net> wrote:
> On Tue, 18 Apr 2006 13:59:05 +0000 (UTC) Frido Ferdinand wrote:
>
> > Hi,
> >
> > How can i see that PIIX is either from libata or the usual IDE
> drivers. I have
> > both enabled in the kernel but not sure which takes presedence, will
> the drives
> > show up as /dev/sda ? disks used are non-sata/normal ide disks.
>
> If both are built into the kernel (=y and not modules), legacy
> IDE drivers take precedence since ide/ is ahead of scsi/ in
> drivers/Makefile (libata drivers are in scsi/).
>
> I have no idea about precedence if you are using initrd or initramfs.
>
> And if legacy ide and scsi are both modules, you won't boot...
> (without using initrd or initramfs).
if I have both ahci and ata_piix modules in initrd (as is the case in most distros), is there any way of passing a parameter to the kernel to tell it which one i want? ahci seems to take preference on my ICH6M but the ata_piix module works better.
dom
>
> ---
> ~Randy
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2006-04-19 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 9:48 Dominic ES. Ijichi [this message]
2006-04-19 19:34 ` PIIX libata ? Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 13:59 Frido Ferdinand
2006-04-19 2:32 ` Randy.Dunlap
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=31311506.91145440106542.JavaMail.root@willow.ijichi.org \
--to=dom@ijichi.org \
--cc=frido@zolder.org \
--cc=linux-ide@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.