From: Robert Hancock <hancockr@shaw.ca>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ide: Fix ata_id_has_dword_io to return DWORD I/O support properly
Date: Fri, 19 Dec 2008 19:58:03 -0600 [thread overview]
Message-ID: <494C512B.6090304@shaw.ca> (raw)
In-Reply-To: <20081218181015.2e160d5c@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> This seems like a risky assumption...
>
> Its wrong on various counts
>
> - ata_id_major_version can't tell early ATA versions apart
> - on anything later than the early ISA IDE paddles (the ones that
> basically were just bus decoders) its invisible to the drive
>
> Except for legacy ISA bus controllers (and even there it is questionable)
> I would favour simply ignoring it.
32-bit IO wouldn't work on any ISA controller, would it? What happens if
you do 32-bit IO port access on something on the ISA bus?
WARNING: multiple messages have this Message-ID (diff)
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ide: Fix ata_id_has_dword_io to return DWORD I/O support properly
Date: Fri, 19 Dec 2008 19:58:03 -0600 [thread overview]
Message-ID: <494C512B.6090304@shaw.ca> (raw)
In-Reply-To: <20081218181015.2e160d5c@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> This seems like a risky assumption...
>
> Its wrong on various counts
>
> - ata_id_major_version can't tell early ATA versions apart
> - on anything later than the early ISA IDE paddles (the ones that
> basically were just bus decoders) its invisible to the drive
>
> Except for legacy ISA bus controllers (and even there it is questionable)
> I would favour simply ignoring it.
32-bit IO wouldn't work on any ISA controller, would it? What happens if
you do 32-bit IO port access on something on the ISA bus?
next prev parent reply other threads:[~2008-12-20 1:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 14:18 [PATCH] ide: Fix ata_id_has_dword_io to return DWORD I/O support properly Mario Schwalbe
2008-12-18 17:08 ` Jeff Garzik
2008-12-18 17:24 ` Sergei Shtylyov
2008-12-18 20:42 ` Bartlomiej Zolnierkiewicz
2008-12-18 22:40 ` Alan Cox
2008-12-18 23:13 ` Bartlomiej Zolnierkiewicz
2008-12-19 10:50 ` Alan Cox
2008-12-19 19:30 ` Bartlomiej Zolnierkiewicz
2008-12-20 0:10 ` Alan Cox
2008-12-19 11:31 ` Sergei Shtylyov
2008-12-19 11:34 ` Sergei Shtylyov
2008-12-18 18:10 ` Alan Cox
2008-12-20 1:58 ` Robert Hancock [this message]
2008-12-20 1:58 ` Robert Hancock
2008-12-20 13:25 ` Sergei Shtylyov
2008-12-22 20:16 ` Sergei Shtylyov
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=494C512B.6090304@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--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 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.