From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Bruce Link <Bruce@1045.ca>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
1063474@bugs.launchpad.net
Subject: Re: System fails to connect to iHOS-104 DVD drive with nvidia MCP61 chipset.
Date: Sun, 8 Sep 2013 08:25:49 -0400 [thread overview]
Message-ID: <20130908122549.GA30549@htj.dyndns.org> (raw)
In-Reply-To: <CADLC3L2uyJzz_4_q3tAUZ5+-wb2yqZ-r2LRzGCfPz6PN+1t8=g@mail.gmail.com>
Hello,
On Fri, Sep 06, 2013 at 07:53:49PM -0600, Robert Hancock wrote:
> > Is there any more information I can supply that would be helpful?
>
> I'm not quite sure what the next step would be. It's quite possible
> that the NVIDIA driver in Windows is doing some magic to work around
> the problem that we don't know about, but it's hard to say what that
> might be. The fact that the default drivers used in the WinPE boot
> don't seem to work would tend to point toward some kind of hardware
> incompatibility issue.
>
> Tejun, think you poked with some of this stuff before - any ideas?
It has been years since I looked at MCP quirks, of which there are too
many. It's likely another quirk on the controller side that nvidia
worked around somehow without telling anyone. Given the history and
that nvidia is out of chipset market, I think it's highly unlikely to
learn what the issue and workaround are without reverse engineering
it. So, um, no idea.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-09-08 12:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 22:36 System fails to connect to iHOS-104 DVD drive with nvidia MCP61 chipset Bruce Link
2013-08-14 6:17 ` Robert Hancock
2013-08-14 22:17 ` Bruce Link
2013-08-15 5:36 ` Robert Hancock
2013-08-16 2:47 ` Bruce Link
2013-08-17 17:32 ` Bruce Link
2013-08-18 7:05 ` Robert Hancock
2013-08-24 0:34 ` Bruce Link
[not found] ` <CADLC3L0wXmVDgHPOFEkeiXD9sDUBg3tZePcJ-gRfoRN5-fXE1w@mail.gmail.com>
[not found] ` <52180F76.3070803@1045.ca>
2013-08-24 3:11 ` Robert Hancock
2013-08-24 15:54 ` Bruce Link
[not found] ` <5218D74A.5020305@1045.ca>
2013-09-06 23:17 ` Bruce Link
2013-09-07 1:53 ` Robert Hancock
2013-09-08 12:25 ` Tejun Heo [this message]
2013-09-18 0:35 ` Bruce Link
2013-09-18 1:40 ` Robert Hancock
2013-09-18 22:27 ` Bruce Link
2013-10-19 0:04 ` Bruce Link
[not found] ` <5261CC95.1050903@1045.ca>
2013-10-22 1:17 ` Robert Hancock
2013-11-09 21:02 ` Bruce Link
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=20130908122549.GA30549@htj.dyndns.org \
--to=tj@kernel.org \
--cc=1063474@bugs.launchpad.net \
--cc=Bruce@1045.ca \
--cc=hancockrwd@gmail.com \
--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