All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Wilkins" <chas@pcscs.com>
To: "Linux Kernel mailing list" <linux-kernel@vger.kernel.org>
Cc: <linux-raid@vger.kernel.org>
Subject: Fw: max number of ide controllers?
Date: Fri, 22 Dec 2000 14:30:46 -0500	[thread overview]
Message-ID: <007c01c06c4d$aef446e0$2b6e60cf@pcscs.com> (raw)



> > Charles Wilkins wrote:
> >
> > Is there a max number of ide controllers that linux-2.2.18 can
> > support?
>

Andrzej M. Krzysztofowicz says,

>"Linux supports up to 10 IDE channels, however channel numbers of PCI
controllers seem to be assigned first."

Warren Young says,
>"Kernel 2.2 is limited to 4 IDE controllers."

ok, so which is it kernel guys, 4 or 10 IDE controllers for the 2.2.x
kernel?

> I know 2.4 supports a maximum of 10 controllers, but each controller has
> to use a different I/O port.  The standard ones are 0x1F0 and 0x170.
> The mobo controllers you have probably are fixed to use the common I/O
> ports.  If the Promise controller can be set to use uncommon port
> values, you'll be able to use 4 controllers.

you didn't read the other posts . . .

> The Creative card is probably a loss, because it's probably fixed at I/O
> port 0x170 (second channel).

well, i know this SB32 card can operating on at least 3 different io ports .
. .


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-22 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-22 19:30 Charles Wilkins [this message]
2000-12-22 20:32 ` Fw: max number of ide controllers? Andreas Dilger
2000-12-22 20:40   ` Charles Wilkins
2000-12-22 21:26     ` Andreas Dilger
2000-12-22 22:24       ` Andrzej Krzysztofowicz
2000-12-23  4:04         ` Charles Wilkins

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='007c01c06c4d$aef446e0$2b6e60cf@pcscs.com' \
    --to=chas@pcscs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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.