linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Kuan Luo <kluo@nvidia.com>, Tejun Heo <htejun@gmail.com>,
	Zoltan Boszormenyi <zboszor@dunaweb.hu>,
	akpm@linux-foundation.org, linux-ide@vger.kernel.org,
	Peer Chen <pchen@nvidia.com>, Allen Martin <AMartin@nvidia.com>
Subject: Re: [patch 3/3] ata: SWNCQ should be enabled by default
Date: Fri, 04 Apr 2008 08:34:31 -0600	[thread overview]
Message-ID: <47F63C77.9010202@shaw.ca> (raw)
In-Reply-To: <47F5E271.10903@garzik.org>

Jeff Garzik wrote:
> Kuan Luo wrote:
>> Robert wrote:
>>> -Hotplug/hot-unplug fails to work properly, hotplug interrupts not 
>>> raised (seemingly only on certain boards/configurations as I can't 
>>> duplicate this problem). http://bugzilla.kernel.org/show_bug.cgi?id=8421
>>>
>> I occasionly encountered this problem in one port under certain system,
>> but didn't see this issue under other systems in the same mainboard.
>> After adding the operation of manually clearing the added/removed
>> interrupt bit in NV_INT_STATUS_CK804 register in nv_adma_interrupt 
>> function,  i saw some improvement. 
>> The key problem is that no one who knows this controller comes to help
>> to solve these issue.
>> Given this disadvantage, i think disabling it maybe is a good choice.
>> I don't know whether we need to continue to provide patch for adma after
>> disabling adma function.
> 
> Is there any hope of getting permission for me to (a) give the NV ADMA 
> documentation to Robert, or (b) posting the ADMA PDF on 
> http://gkernel.sourceforge.net/specs/ ?
> 
> I strongly encourage vendors -- especially with chips at or past 
> end-of-life -- to help customers and developers by permitting posting at 
> http://gkernel.sourceforge.net/specs/
> 
> Thanks,
> 
>     Jeff

I would second that call. It's been suggested that 3rd party IP was what 
inhibited this, I don't know if that is the case or not. But it would be 
a very nice gesture if NVIDIA would do what it takes to make this possible.

  reply	other threads:[~2008-04-04 14:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:33 [patch 3/3] ata: SWNCQ should be enabled by default akpm
2008-03-29 13:38 ` Tejun Heo
2008-03-29 18:22   ` Zoltan Boszormenyi
2008-03-30  0:11     ` Tejun Heo
2008-03-30  1:06       ` Robert Hancock
2008-03-30  1:17         ` Tejun Heo
2008-03-30  7:03           ` Zoltan Boszormenyi
2008-03-30 10:59             ` Tejun Heo
2008-03-31  2:58       ` Kuan Luo
2008-03-31  4:34         ` Tejun Heo
2008-04-01  3:14           ` Robert Hancock
2008-04-01  3:24             ` Robert Hancock
2008-04-01  5:24               ` Kuan Luo
2008-04-04  7:38                 ` Jeff Garzik
2008-04-04  8:10                 ` Jeff Garzik
2008-04-04 14:34                   ` Robert Hancock [this message]
2008-04-05  0:00                     ` Tejun Heo
2008-04-04  7:40 ` Jeff Garzik

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=47F63C77.9010202@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=AMartin@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kluo@nvidia.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=pchen@nvidia.com \
    --cc=zboszor@dunaweb.hu \
    /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).