linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler <pml@dtbb.net>
To: linux-ide@vger.kernel.org
Subject: Increasing max supported ide drives to more than 26
Date: Sun, 24 Apr 2005 06:15:57 -0700	[thread overview]
Message-ID: <426B9C0D.9010209@dtbb.net> (raw)

I would like to modify my kernel to be able to support more than the 
maximum of 26 IDE drives.

Its not that it won't support that many now, but when you have more than 
26 drives currently, they start being named things like /dev/hd{ 
/dev/hd; etc.. instead of like the scsi system where after they roll 
past /dev/sdz, they go to /dev/sdaa /dev/sdab, etc.

I've already configured my kernel to allow 20 IDE controllers (2 ports 
each), using the MAX_HWIFS in the include/asm-i386/ide.h file.  This 
allows all my controllers to be detected/used when linux starts, but the 
system doesn't letter the drives properly past /dev/hdz.

The system consists of  2 x onboard channels (4 drives), 4 x highpoint 
hpt374 chipset raid cards (not using built-in raid option) which gives 
16 ports (32 drives), and optionally, there's also a built-in promise 
pdc 20378 (currently unused and disabled in bios, and no drivers in kernel).

The driver that is included in the kernel (2.6.11.7) doesn't use scsi 
emulation.. it uses /dev/hdX lettering scheme (is there  a way to tell 
it to use scsi emulation / drive lettering), only the driver you 
download from highpoint uses scsi emulation and drive lettering.  I 
would prefer to have the option of using either the tainted proprietary 
driver, or the included kernel driver, and only the drive lettering is 
holding me back.. thanks

Tyler.

                 reply	other threads:[~2005-04-24 13:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=426B9C0D.9010209@dtbb.net \
    --to=pml@dtbb.net \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).