From: Robert Hancock <hancockrwd@gmail.com>
To: Yuhong Bao <yuhongbao_386@hotmail.com>
Cc: david-b@pacbell.net, greg@kroah.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support
Date: Tue, 23 Feb 2010 18:26:29 -0600 [thread overview]
Message-ID: <51f3faa71002231626q1eb62adeo660c282418f0e01@mail.gmail.com> (raw)
In-Reply-To: <SNT125-W457447CBE941D2703E98D0C3420@phx.gbl>
On Tue, Feb 23, 2010 at 12:48 AM, Yuhong Bao <yuhongbao_386@hotmail.com> wrote:
>
>> According to one Microsoft page I saw, Windows XP did not implement
>> the 64-bit addressing feature in EHCI. I haven't found any information
>> on whether any newer Windows versions do or not.
> Windows 7 seems to support it, and it seems like they have to already do a workaround for broken NVIDIA chipsets:
> http://support.microsoft.com/?kbid=976972
> http://www.windows7tipsonline.com/USB_Problem.htm
> http://social.technet.microsoft.com/Forums/en-US/w7itprohardware/thread/3aae3b66-6a1a-47e8-ad1b-b20b68eaecf8#79ea3219-d76e-40bc-b910-c7d347002e66
> http://social.technet.microsoft.com/Forums/en-US/w7itprohardware/thread/38f25c1d-de67-4c74-8845-2cd3a15d8e41
That's good news actually.. it means they've apparently already
debugged the feature for us :-) I suppose the next step would be to
contact NVIDIA and see what they say (i.e. which particular chipsets
have the problem), but from my experience with them, requests of the
form "can you confirm X is a bug in your chipset" to those guys seem
to go into the bit bucket. Does anyone have any good contacts at
NVIDIA for USB or other chipset issues? I see there's some existing
NVIDIA-specific EHCI quirks so I'm assuming someone was in contact
with them before..
The fact that Windows 7 is now using the feature also means that there
aren't likely to be too many machines where the 64-bit addressing is
reported but doesn't work. Which means that aside from the NVIDIA
quirk, I think enabling 64-bit addressing should be relatively safe.
next prev parent reply other threads:[~2010-02-24 0:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 3:10 Robert Hancock
2010-02-18 4:26 ` Greg KH
2010-02-18 5:13 ` Robert Hancock
2010-02-18 5:22 ` Greg KH
2010-02-19 0:33 ` Robert Hancock
2010-02-19 0:47 ` Greg KH
2010-02-19 3:46 ` Robert Hancock
2010-02-19 3:54 ` Greg KH
2010-02-20 1:30 ` Robert Hancock
2010-02-20 4:26 ` Greg KH
2010-02-20 5:39 ` David Brownell
2010-02-20 7:15 ` Robert Hancock
2010-02-20 8:07 ` David Brownell
2010-02-20 18:13 ` Robert Hancock
2010-02-23 6:48 ` Yuhong Bao
2010-02-24 0:26 ` Robert Hancock [this message]
2010-02-25 2:28 ` Tejun Heo
2010-02-25 2:41 ` Yuhong Bao
2010-02-25 2:58 ` Tejun Heo
2010-02-25 3:15 ` Yuhong Bao
2010-02-25 3:29 ` Tejun Heo
2010-02-25 4:03 ` Oliver Neukum
2010-02-25 5:25 ` Tejun Heo
2010-02-25 16:14 ` Greg KH
2010-02-25 23:15 ` Robert Hancock
2010-02-25 23:25 ` Greg KH
2010-02-26 7:01 ` Oliver Neukum
2010-02-24 3:53 ` SB600 64-bit DMA BIOS misconfiguration (formerly RE: [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support) Yuhong Bao
2010-02-24 4:30 ` Robert Hancock
2010-02-24 4:33 ` Yuhong Bao
2010-02-24 13:30 ` Huang, Shane
2010-02-23 6:28 ` [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support Yuhong Bao
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=51f3faa71002231626q1eb62adeo660c282418f0e01@mail.gmail.com \
--to=hancockrwd@gmail.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yuhongbao_386@hotmail.com \
/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
all inboxes | Powered by JetHome®