From: "John W. Ross" <programming@johnwross.com>
To: <linux-kernel@vger.kernel.org>
Subject: Increasing IDE Channels
Date: Wed, 7 Jul 2004 15:20:15 -0700 [thread overview]
Message-ID: <001801c46470$94116820$0a01a8c0@jwrdesktop> (raw)
Greetings,
I've spent several days working to increase the number of IDE channels above
the 10 allowed in the kernel. Ideally I would like to raise the limit to
14. (to accomidate the 2 interfaces on the motherboard and 6 cheap dual
channel ide cards) Although I've found some references to others who would
like to do this, I can find noone who has actually both accomplished the
task and mentioned their success. I decided to start small and try to get
up to 12. To do this I:
Changed ide.h:
IDE_NR_PORTS (10)
to
IDE_NR_PORTS (12)
In major.h I added:
#define IDE10_MAJOR 240
#define IDE11_MAJOR 241
in ide.c I changed
static const u8 ide_hwif_to_major[] = { IDE0_MAJOR, IDE1_MAJOR,
IDE2_MAJOR, IDE3_MAJOR,
IDE4_MAJOR, IDE5_MAJOR,
IDE6_MAJOR, IDE7_MAJOR,
IDE8_MAJOR, IDE9_MAJOR };
to :
static const u8 ide_hwif_to_major[] = { IDE0_MAJOR, IDE1_MAJOR,
IDE2_MAJOR, IDE3_MAJOR,
IDE4_MAJOR, IDE5_MAJOR,
IDE6_MAJOR, IDE7_MAJOR,
IDE8_MAJOR, IDE9_MAJOR,
IDE10_MAJOR, IDE11_MAJOR)
This was on a clean 2.6.7 kernel download. I then ran menuconfig and the
only change I made was to select the processor as AMD Athlon. After
compiling I still get the "too many ide interfaces, no room in table".
I'm certianly no kernel hacker at heart, so I may be trying to do the
impossible/impractical.
1.) Could someone please explain why there is a limit of 10 interfaces (is
this something that I shouldn't even try)?
2.)What did I miss on moving to 12?
3.) I could understand a limit of 12, as hda, hdb, hdc... hdw, hdx, would
only allow a possible 13th interface, but at 14 you would totally exhaust
the alphabet, but is that still relevant with the newer method of
enumerating partitions?
4.) Is there a kernel patch available already that I'm ignorant of?
5.) Are there references that I should review elsewhere?
6.) I generally use Mandrake but if there is another distribution patched to
allow additional interfaces pray tell.
Thank you for you time reading this, and for any help you may be able to
provide.
John
To respond, just click reply. The spammers will get the address regardless
of anything I do to prevent it!
next reply other threads:[~2004-07-07 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 22:20 John W. Ross [this message]
2004-07-07 22:37 ` Kernel 2.6.7 hangs Robert Horton
2004-07-08 1:35 ` Zwane Mwaikambo
2004-07-07 22:41 ` Increasing IDE Channels Bartlomiej Zolnierkiewicz
2004-07-07 22:56 Kronos
2004-07-08 15:58 ` Timothy Miller
2004-07-08 18:26 ` Kronos
2004-07-08 19:03 ` Timothy Miller
2004-07-08 19:28 ` Kronos
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='001801c46470$94116820$0a01a8c0@jwrdesktop' \
--to=programming@johnwross.com \
--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
all inboxes | Powered by JetHome®