From: John T Copeland <johnc@neto.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linuxkernel <linux-kernel@vger.kernel.org>
Subject: siimage driver
Date: Thu, 12 Jun 2003 18:04:42 -0500 [thread overview]
Message-ID: <3EE9070A.4040403@neto.com> (raw)
Alan,
A couple of questions if you please.
1) When I compile the siimage driver into the kernel, the ide buses are
scanned in the following order:
IDE0 - SATA primary - hda, hdb
IDE1 - SATA secondary - hdc, hdd
IDE2 - ATA tertiary - hde, hdf
IDE3 - ATA quandrary hdg, hdh
I want the ATA to be IDE0/1 and SATA to be IDE2/3. I have noticed from
some of the posts about the siimage driver on the ASUS nforce2 mobo this
is the apparent order scanned. My mobo is an Abit NF7-S nforce2. Is
there someway of controlling the order of scannin the IDE buses? I
tried append="ide=reverse" to no avail.
2) To try and get the nforce2 IDE buses scanned first, I compiled
siimage as a module, but when I did an "insmod siimage" I get an
unresolved external, "noautodma", in siimage.
I'd appreciate any help you can offer.
Thanks,
John Copeland
next reply other threads:[~2003-06-12 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 23:04 John T Copeland [this message]
2003-06-12 23:20 ` siimage driver Andre Hedrick
2003-06-13 14:25 ` John T Copeland
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=3EE9070A.4040403@neto.com \
--to=johnc@neto.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox