From: Vojtech Pavlik <vojtech@suse.cz>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jens Altmann <jens.altmann@amd.com>,
Wolfgang Zuleger <wolfgang.zuleger@gmx.de>,
Alexander Kiausch <alex.kiausch@t-online.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: [RFH][PATCH] CS5535 driver
Date: Mon, 29 Aug 2005 18:32:27 +0200 [thread overview]
Message-ID: <20050829163227.GA29221@midnight.suse.cz> (raw)
In-Reply-To: <58cb370e0508290848457748dc@mail.gmail.com>
On Mon, Aug 29, 2005 at 05:48:26PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> Alan Cox has sent me this driver recently. It needs a little bit of
> work to become
> acceptable into mainline kernel and as I don't have neither the hardware nor the
> time to work on it now, I'm posting it to you and linux-ide ML with a remaining
> TODO list (original patch attached to the mail). :-)
>
> I hope that somebody will work on it so that it can be merged soon.
>
> * cs5535_tuneproc() needs to be fixed to not abuse ->tuneproc interface
> (which is exported to user-space), all DMA tuning should be done through
> ->speedproc interface only
> * cs5535_set_drive() needs to use ide_rate_filter() to limit values passed
> from the user-space
> * cs5535_set_drive() needs to set drive's speed unconditionally otherwise
> drive may not be setup correctly after resume
> * cs5535_set_drive() shouldn't change drive->current_speed
> * cable detection needs to be in separate function (for hotplug - later)
> * driver lacks device side cable detection [ see eighty_ninty_three() ]
That, as far as I know, only works on mainboards with a capacitor
installed. If there is host cable detection, it doesn't work reliably.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2005-08-29 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 15:48 [RFH][PATCH] CS5535 driver Bartlomiej Zolnierkiewicz
2005-08-29 16:32 ` Vojtech Pavlik [this message]
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=20050829163227.GA29221@midnight.suse.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alex.kiausch@t-online.de \
--cc=bzolnier@gmail.com \
--cc=jens.altmann@amd.com \
--cc=linux-ide@vger.kernel.org \
--cc=wolfgang.zuleger@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.