From: Mark Lord <kernel@start.ca>
To: "Robert Hancock" <hancockrwd@gmail.com>,
"Pali Rohár" <pali.rohar@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, Robert Hancock <hancockr@shaw.ca>,
Tejun Heo <tj@kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux: sata_nv: adma support
Date: Tue, 25 Aug 2015 07:20:05 -0400 [thread overview]
Message-ID: <55DC4F65.70402@start.ca> (raw)
In-Reply-To: <CADLC3L01LMS4yTXBMj7Xke90aP=LK-HhUH9vM80_sMgLk+sg_w@mail.gmail.com>
On 15-08-01 09:45 PM, Robert Hancock wrote:
> On Sat, Aug 1, 2015 at 2:09 PM, Pali Rohár <pali.rohar@gmail.com> wrote:
>> On Thursday 25 December 2014 07:22:13 Robert Hancock wrote:
>>> On Tue, Dec 23, 2014 at 1:51 PM, Pali Rohár <pali.rohar@gmail.com>
>>> wrote:
>>>> Hello,
>>>>
>>>> I have nvidia nforce4 motherboard with nvidia sata controller:
..
>>> It looks like something is trying to issue a command to disable APM
>>> power management on the drive, and the command fails (likely because
>>> it doesn't support that command).
..
>> /sbin/hdparm -B254 $DRIVE
>>
>> And that -B254 cause above error message in dmesg log. Output from
>> hdparm is:
>>
>> /dev/sda:
>> setting Advanced Power Management level to 0xfe (254)
>> APM_level = not supported
..
>> $ sudo hdparm -I /dev/sda | grep -i power
>> * Power Management feature set
That's not the same as APM ("Advanced" Power Management).
> However, these NVIDIA SATAs are black boxes, and rather buggy ones at that,
> so it's possible there's an unknown issue there.
I wonder if NVIDIA simply bought out the IP from Pacific Digital
when they went bust? Pacific Digital invented the original "ADMA",
and the pdc_adma.c driver in the kernel knows all about it.
If the IP is pretty similar (identical?) then we could probably
improve things.
next prev parent reply other threads:[~2015-08-25 11:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201412232051.07067@pali>
[not found] ` <CADLC3L2N2TcO4FR1Bqt2n=g5G+i=dv_y_OhYHA9yXg79Bb6JPg@mail.gmail.com>
2015-08-01 20:09 ` Pali Rohár
2015-08-02 1:45 ` Robert Hancock
2015-08-02 9:08 ` Pali Rohár
2015-08-03 3:02 ` Robert Hancock
2015-08-04 18:06 ` Pali Rohár
2015-08-26 8:00 ` Pali Rohár
2015-09-25 11:40 ` Pali Rohár
2018-05-10 13:51 ` Pali Rohár
2018-08-09 11:48 ` Pali Rohár
2018-11-15 17:01 ` Pali Rohár
2019-12-25 18:31 ` Pali Rohár
2015-08-25 11:20 ` Mark Lord [this message]
2015-08-25 12:58 ` Pali Rohár
2015-08-26 4:01 ` Robert Hancock
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=55DC4F65.70402@start.ca \
--to=kernel@start.ca \
--cc=hancockr@shaw.ca \
--cc=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=tj@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
Powered by JetHome