From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] ide: add IDE_HFLAG_NO_DSC host flag
Date: Sun, 30 Dec 2007 18:17:40 +0100 [thread overview]
Message-ID: <200712301817.40456.bzolnier@gmail.com> (raw)
In-Reply-To: <477652A3.2020900@ru.mvista.com>
On Saturday 29 December 2007, Sergei Shtylyov wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > * Add IDE_HFLAG_NO_DSC host flag for hosts that doesn't support DSC overlap.
>
> > * Set it in aec62xx (for ATP850UF only) and hpt34x host drivers.
>
> > * Convert ide-tape device driver to check for IDE_HFLAG_NO_DSC flag.
>
> > Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
>
> Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>
> > Index: b/include/linux/ide.h
> > ===================================================================
> > --- a/include/linux/ide.h
> > +++ b/include/linux/ide.h
> > @@ -1098,6 +1098,8 @@ enum {
> > IDE_HFLAG_CY82C693 = (1 << 27),
> > /* force host out of "simplex" mode */
> > IDE_HFLAG_CLEAR_SIMPLEX = (1 << 28),
> > + /* DSC overlap is unsupported */
> > + IDE_HFLAG_NO_DSC = (1 << 29),
> > };
>
> Too many flags -- you'll run out of sizeof(unsigned) soon. :-)
Actually I'm already one bit short for WIP patches.... :)
I can compensate for it by using the same bit for IDE_HFLAG_CS5520
and IDE_HFLAG_VDMA for now (they are set only by cs5520 host driver)
but long-term we should get rid of some flags (IDE_HFLAG_ABUSE*,
especially IDE_HFLAG_ABUSE_DMA_MODES, sound like a good candidates
for extermination) or make flags field u64 (eeew)...
Bart
prev parent reply other threads:[~2007-12-30 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 17:38 [PATCH 3/3] ide: add IDE_HFLAG_NO_DSC host flag Bartlomiej Zolnierkiewicz
2007-12-29 13:58 ` Sergei Shtylyov
2007-12-30 17:17 ` Bartlomiej Zolnierkiewicz [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=200712301817.40456.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).