From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ide@vger.kernel.org
Subject: Re: [Bug 13882] Cannot read CD: "Logical unit communication CRC error"
Date: Sun, 02 Aug 2009 02:05:53 +0400 [thread overview]
Message-ID: <4A74BC41.4000203@ru.mvista.com> (raw)
In-Reply-To: <200908012130.n71LURC3026649@demeter.kernel.org>
--- Comment #15 from Alan <alan@lxorguk.ukuu.org.uk> 2009-08-01 21:30:26 ---
> I have complete documentation for them. They are set by the BIOS to indicate
> whether the cable is 40 or 80 wire. We cannot do drive side detect as there is
> no guarantee the boards support it.
>
I wonder how boards can support (or not) *drive side* cable detection...
next prev parent reply other threads:[~2009-08-01 22:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 22:44 [Bug 13882] New: Cannot read CD: "Logical unit communication CRC error" bugzilla-daemon
2009-07-30 22:53 ` [Bug 13882] " bugzilla-daemon
2009-07-31 2:39 ` bugzilla-daemon
2009-07-31 12:51 ` bugzilla-daemon
2009-07-31 13:16 ` bugzilla-daemon
2009-07-31 15:22 ` bugzilla-daemon
2009-07-31 18:40 ` bugzilla-daemon
2009-07-31 18:41 ` bugzilla-daemon
2009-07-31 18:42 ` bugzilla-daemon
2009-07-31 18:43 ` bugzilla-daemon
2009-07-31 18:44 ` bugzilla-daemon
2009-07-31 18:48 ` bugzilla-daemon
2009-07-31 18:49 ` bugzilla-daemon
2009-07-31 18:57 ` bugzilla-daemon
2009-07-31 18:57 ` bugzilla-daemon
2009-07-31 18:58 ` bugzilla-daemon
2009-07-31 20:07 ` bugzilla-daemon
2009-08-01 18:40 ` bugzilla-daemon
2009-08-01 21:30 ` bugzilla-daemon
2009-08-01 22:05 ` Sergei Shtylyov [this message]
2009-08-01 22:06 ` bugzilla-daemon
2009-08-02 10:53 ` bugzilla-daemon
2009-08-03 21:24 ` bugzilla-daemon
2009-08-03 21:49 ` bugzilla-daemon
2009-08-09 22:41 ` bugzilla-daemon
[not found] <bug-13882-11633@https.bugzilla.kernel.org/>
2012-06-13 14:31 ` bugzilla-daemon
2012-06-13 14:31 ` bugzilla-daemon
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=4A74BC41.4000203@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--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 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.