From: Mark Lord <kernel@teksavvy.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-ide@vger.kernel.org, linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Single host/multiple hwifs vs. multiple hosts?
Date: Mon, 09 Apr 2012 21:24:59 -0400 [thread overview]
Message-ID: <4F838BEB.5090802@teksavvy.com> (raw)
In-Reply-To: <CAMuHMdXKUVU8WWVD_fd4XpB3-scsfrJjOVQ6D1D=jAMmi-qhsQ@mail.gmail.com>
On 12-04-08 05:12 AM, Geert Uytterhoeven wrote:
> On Sun, Mar 4, 2012 at 13:15, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> I'm wondering what are the differences between adding a single IDE host with
>> multiple hwifs vs. adding a separate IDE host for each hwif?
>> Do both ways work?
>
> Does no one know?
When I first wrote that code, the idea was that if a given chip
had multiple IDE ports (hardware interfaces, or hwifs for short),
then that's how it would be done. One controller, multiple hwifs.
This was before IDE had anything to do with the SCSI subsystem,
and allowed for things like controller chips which could operate
only a single hwif at any point in time (aka. "serialized").
Nowadays, the code's be hacked beyond recognition from its original form
and intent, so who knows! :)
next prev parent reply other threads:[~2012-04-10 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 12:15 Single host/multiple hwifs vs. multiple hosts? Geert Uytterhoeven
2012-04-08 9:12 ` Geert Uytterhoeven
2012-04-08 9:12 ` Geert Uytterhoeven
2012-04-10 1:24 ` Mark Lord [this message]
2012-04-10 1:24 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2012-03-04 12:15 Geert Uytterhoeven
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=4F838BEB.5090802@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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.