From: Martin Dalecki <dalecki@evision-ventures.com>
To: Stephen Samuel <samuel@bcgreen.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: More than 10 IDE interfaces
Date: Wed, 17 Apr 2002 12:21:27 +0200 [thread overview]
Message-ID: <3CBD4CA7.6090003@evision-ventures.com> (raw)
In-Reply-To: <20020411040845.GE14801@dark.x.dtu.dk> <3CB53D70.5070100@evision-ventures.com> <3CBC0FA1.8070907@bcgreen.com>
Stephen Samuel wrote:
> It might be trowing bad money after good to do it, but why
> not just put together a simple translation table.
>
> rather than
> drivenum=(driveletter - 'a')
> and
> driveletter=(drivenum+'a')
>
> have translation tables, so that
> drivenum= chartodrivenum[driveletter]
> and
> driveletter= drivenumtoletter[drivenum]
> If you're willing to map (almost) all of the printable
> characters, you could get 46 controllers and 92 drives
> (I'd refuse to map ', ", \ or space)
>
>
> You'd still be limited to one character, but it would, at least
> make it easy to have 26 controllers and 52 drives (and that's
> just using upper and lower case characters!)
Hmm this propasal is not without reaons but the main obstacle
is currently just the option parsing code in ide. At some
point in time I just intend to rewrite it and to support
namings along the way of /dev/hdXX, where XX are simply digits.
The old names will be preserved as "backwards compatibility".
OK?
If you wish you could of course look in to this yourself, since
it's not *that* difficult. I would be really glad if someone did this.
prev parent reply other threads:[~2002-04-17 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 4:08 More than 10 IDE interfaces Baldur Norddahl
2002-04-11 7:38 ` Martin Dalecki
2002-04-11 13:09 ` Bill Davidsen
2002-04-11 12:22 ` Martin Dalecki
2002-04-12 13:39 ` Martin Dalecki
2002-04-16 11:48 ` Stephen Samuel
2002-04-17 10:21 ` Martin Dalecki [this message]
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=3CBD4CA7.6090003@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel@bcgreen.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