From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/2] cmd64x: set IDE_HFLAG_SERIALIZE explictly for CMD646
Date: Thu, 30 Oct 2008 00:42:29 +0100 [thread overview]
Message-ID: <200810300042.29405.bzolnier@gmail.com> (raw)
In-Reply-To: <4908F240.2020606@ru.mvista.com>
On Thursday 30 October 2008, Sergei Shtylyov wrote:
> Hello.
>
> Bartlomiej Zolnierkiewicz wrote:
>
> >>>>>>> * Set IDE_HFLAG_SERIALIZE explictly for CMD646.
> >>>>>>>
> >>>>>>>
> >>>>>> Was that some kernel.org bug that this is fixing?
> >>>>>>
> >>>>>>
> >>>>> Nope (AFAIK).
> >>>>>
> >>>>>
> >>>> User report then?
> >>>>
> >>>>
> >>> Nope as far as my inbox tells me.
> >>>
> >>>
> >> Then whar's the reason? :-)
> >>
> >
> > From the patch description:
> >
> > * Set IDE_HFLAG_SERIALIZE explictly for CMD646.
> >
> > * Remove no longer needed ide_cmd646 chipset type (which has
> > a nice side-effect of fixing handling of unexpected IRQs).
> >
> > The latter is possible because of the former
> > (see ide-probe.c::init_irq() for details).
> >
>
> Ah, got it at last. But I doubt that 646 *really* needs serialization...
I remember getting bugreport which supposedly was fixed by commit
deffca117b90dadec395c0cf3ee816de27dfe2fd (but it could also be that
it was something else in reality or that it just hide some other
bug that we fixed in the meantime).
We would need somebody with the hardware to verify it.
next prev parent reply other threads:[~2008-10-29 23:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 19:58 [PATCH 2/2] cmd64x: set IDE_HFLAG_SERIALIZE explictly for CMD646 Bartlomiej Zolnierkiewicz
2008-10-27 23:22 ` Sergei Shtylyov
2008-10-29 19:26 ` Bartlomiej Zolnierkiewicz
2008-10-29 20:34 ` Sergei Shtylyov
2008-10-29 21:42 ` Bartlomiej Zolnierkiewicz
2008-10-29 22:59 ` Sergei Shtylyov
2008-10-29 23:10 ` Bartlomiej Zolnierkiewicz
2008-10-29 23:31 ` Sergei Shtylyov
2008-10-29 23:42 ` Bartlomiej Zolnierkiewicz [this message]
2008-10-31 14:36 ` Mark Lord
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=200810300042.29405.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@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).