From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PROPOSED] ata: Report 16/32bit PIO as best we can
Date: Thu, 09 Apr 2009 09:02:35 -0400 [thread overview]
Message-ID: <49DDF1EB.2060200@rtr.ca> (raw)
In-Reply-To: <20090409133221.18202.63779.stgit@t61.ukuu.org.uk>
Alan Cox wrote:
> Something like this then ?
>
>
> The legacy old IDE API for this is a bit primitive so we try and map stuff
> sensibly onto it.
>
> - Add flags2 as we ran out of flags
> - Set PIO over DMA devices to report 32bit
> - Add ability to change the PIO32 settings if the controller permits it
> - Add that functionality into the sff drivers
> - Add that functionality into the VLB legacy driver
> - Turn on the 32bit PIO on the ninja32 and add support there
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
..
By all means go ahead with something like this,
and thanks for doing it, Alan.
But.. these do look rather suspiciously like sysfs attrs to me.
We didn't have a sysfs in the IDE days (so Gadi added the klunky
procfs "settings" thing for there), but we do now.
I'm happy to update hdparm to check sysfs if that's where this
ends up, or to do almost nothing for it if we stick with the ioctls.
Thanks either way!
next prev parent reply other threads:[~2009-04-09 13:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:32 [PROPOSED] ata: Report 16/32bit PIO as best we can Alan Cox
2009-04-09 12:50 ` Jeff Garzik
2009-04-09 12:53 ` Alan Cox
2009-04-09 13:08 ` Jeff Garzik
2009-04-09 13:12 ` Alan Cox
2009-04-09 13:33 ` Jeff Garzik
2009-04-09 13:41 ` Alan Cox
2009-04-09 13:45 ` Jeff Garzik
2009-04-09 13:48 ` Tejun Heo
2009-04-09 13:49 ` Tejun Heo
2009-04-09 13:45 ` Tejun Heo
2009-04-09 13:58 ` Alan Cox
2009-04-09 14:02 ` Tejun Heo
2009-04-09 13:02 ` Mark Lord [this message]
2009-04-09 13:08 ` Alan Cox
2009-04-13 16:32 ` Jeff Garzik
2009-04-13 16:39 ` Alan Cox
2009-04-13 16:57 ` Jeff Garzik
2009-04-09 13:25 ` Jeff Garzik
2009-04-09 16:57 ` Mark Lord
2009-04-09 20:42 ` Jeff Garzik
2009-04-10 0:38 ` Douglas Gilbert
2009-04-10 0:47 ` 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=49DDF1EB.2060200@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.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 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).