From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@redhat.com>
Cc: Andrew Hall <andrew.a.hall@gmail.com>, 'Mark Lord' <liml@rtr.ca>,
linux-ide@vger.kernel.org
Subject: Re: CF flash PATA on libata failure to attach
Date: Mon, 02 Jul 2007 19:58:49 +0900 [thread overview]
Message-ID: <4688DA69.60700@gmail.com> (raw)
In-Reply-To: <20070629101733.GB25064@devserv.devel.redhat.com>
Alan Cox wrote:
> On Fri, Jun 29, 2007 at 05:34:36PM +1000, Andrew Hall wrote:
>> Further to this the PATA to SATA bridge being used in this case is:
>>
>> http://www.jmicron.com/JM20330.html
>>
>> ..as you will see only PIO and UDMA modes are supported.
>
> In which case their microcontroller in the middle should be masking ident
> bits. Without a way to detect the presence of the device I don't see an
> easy way for us to handle it automatically at all
I'll ask JMicron about it.
--
tejun
next prev parent reply other threads:[~2007-07-02 11:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 10:02 CF flash IDE failure to attach with 2.6.20+ Andrew_hall
2007-06-18 11:26 ` Tejun Heo
2007-06-18 11:57 ` Alan Cox
2007-06-18 23:01 ` Andrew Hall
2007-06-19 5:00 ` Tejun Heo
2007-06-21 1:05 ` Andrew Hall
2007-06-21 3:02 ` Tejun Heo
2007-06-21 7:19 ` Andrew Hall
2007-06-21 14:45 ` Mark Lord
2007-06-21 15:09 ` Andrew Hall
2007-06-26 8:51 ` CF flash PATA on libata failure to attach Andrew Hall
2007-06-26 18:50 ` Mark Lord
2007-06-27 3:57 ` Andrew Hall
2007-06-27 14:08 ` Mark Lord
2007-06-27 23:49 ` Andrew Hall
2007-06-28 17:37 ` Mark Lord
2007-06-29 0:35 ` Andrew Hall
2007-06-29 1:10 ` Mark Lord
2007-06-29 1:36 ` Tejun Heo
2007-06-29 2:26 ` Mark Lord
2007-06-29 2:15 ` Andrew Hall
2007-06-29 2:28 ` Mark Lord
2007-06-29 3:24 ` Andrew Hall
2007-06-29 7:34 ` Andrew Hall
2007-06-29 10:17 ` Alan Cox
2007-07-02 10:58 ` Tejun Heo [this message]
2007-07-03 6:13 ` Albert Lee
2007-06-29 10:06 ` Alan Cox
2007-06-25 9:05 ` CF flash IDE failure to attach with 2.6.20+ Andrew Hall
2007-06-18 23:23 ` Andrew Hall
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=4688DA69.60700@gmail.com \
--to=htejun@gmail.com \
--cc=alan@redhat.com \
--cc=andrew.a.hall@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).