From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Daniel Drake <dsd@gentoo.org>, CaT <cat@zip.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: IT8212/ITE RAID
Date: Mon, 22 Aug 2005 11:28:31 +0200 [thread overview]
Message-ID: <58cb370e0508220228770415f7@mail.gmail.com> (raw)
In-Reply-To: <58cb370e050814142013db4ba1@mail.gmail.com>
Any news about URLs? It shouldn't be too hard find them unless they
never existed in the first place. I will work on the issues immediately.
Bartlomiej
On 8/14/05, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> On 8/14/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Sul, 2005-08-14 at 17:56 +0200, Bartlomiej Zolnierkiewicz wrote:
> > > * your stuff was accepted after all (and some stuff like ide-cd
> > > fixes was never splitted from the -ac patchset and submitted)
> >
> > They were.
>
> I remember discussion about end-of-media ide-cd fixes but the patch
> was never submitted. If you have *URL* to the patch I'll work on the patch.
>
> > > * you've never provided any technical details on "the stuff I broke"
> >
> > I did, several times. I had some detailed locking discussions with
> > Manfred and others on it as a result. The locking in the base IDE is
> > still broken, in fact its become worse - the random locking around
> > timing changes now causes some PIIX users to see double spinlock debug
> > with the base kernel as an example.
>
> Huh? *WHICH* my patch causes this?
>
> I don't remember this discussion et all, care to give some pointers?
>
> > > > Would make sense, but I thought I had the right bits masked. Will take a
> > >
> > > WIN_RESTORE is send unconditionally (as it always was),
> > >
> > > This is not the right thing, somebody should go over all ATA/ATAPI
> > > drafts and come with the correct strategy of handling WIN_RESTORE.
> >
> > Ok that would make sense. Matthew Garrett also reported some problems in
> > that area with suspend/resume (BIOS restoring its idea of things...)
>
> Quite likely, WIN_RESTORE is not sent on resume etc.
>
next prev parent reply other threads:[~2005-08-22 22:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 5:30 IT8212/ITE RAID CaT
2005-08-14 11:08 ` Daniel Drake
2005-08-14 11:47 ` CaT
2005-08-14 12:44 ` Daniel Drake
2005-08-14 13:33 ` Alan Cox
2005-08-14 15:01 ` Bartlomiej Zolnierkiewicz
2005-08-14 15:52 ` Alan Cox
2005-08-14 15:56 ` Bartlomiej Zolnierkiewicz
2005-08-14 21:13 ` Alan Cox
2005-08-14 21:20 ` Bartlomiej Zolnierkiewicz
2005-08-22 9:28 ` Bartlomiej Zolnierkiewicz [this message]
2005-08-22 10:33 ` Alan Cox
2005-08-22 10:21 ` Bartlomiej Zolnierkiewicz
2005-08-22 23:48 ` Andre Hedrick
2005-08-14 23:59 ` CaT
2005-08-16 22:41 ` CaT
2005-08-14 21:09 ` James Tabor
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=58cb370e0508220228770415f7@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cat@zip.com.au \
--cc=dsd@gentoo.org \
--cc=linux-kernel@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