mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "John W. Ross" <programming@johnwross.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Increasing IDE Channels
Date: Thu, 8 Jul 2004 00:41:07 +0200	[thread overview]
Message-ID: <200407080041.07508.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <001801c46470$94116820$0a01a8c0@jwrdesktop>


[ next time please use/cc linux-ide ML ]

On Thursday 08 of July 2004 00:20, John W. Ross wrote:
> Greetings,

Hi,

> Changed ide.h:
>
> IDE_NR_PORTS  (10)
> to
> IDE_NR_PORTS  (12)

You've changed the wrong define.  Bump MAX_HWIFS in <asm/ide.h> instead.

> 1.) Could someone please explain why there is a limit of 10 interfaces (is
> this something that I shouldn't even try)?

- there are no more major numbers assigned for IDE
- for majority people of people it is enough
- IDE driver uses static data structures so higher number of interfaces
  means more memory wasted (if you don't use all of them of course)
- nobody cared

> 2.)What did I miss on moving to 12?

It should work with MAX_HWIFS corrected.

> 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?

What newer method are you talking about?

Regards,
Bartlomiej


  parent reply	other threads:[~2004-07-07 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07 22:20 John W. Ross
2004-07-07 22:37 ` Kernel 2.6.7 hangs Robert Horton
2004-07-08  1:35   ` Zwane Mwaikambo
2004-07-07 22:41 ` Bartlomiej Zolnierkiewicz [this message]
2004-07-07 22:56 Increasing IDE Channels 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=200407080041.07508.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=programming@johnwross.com \
    /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®