linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: pata_it821x completely broken
Date: Tue, 22 Jul 2008 21:16:17 +0200	[thread overview]
Message-ID: <200807222116.19077.linux@rainbow-software.org> (raw)
In-Reply-To: <20080722191022.0417f45c@lxorguk.ukuu.org.uk>

On Tuesday 22 July 2008 20:10:22 Alan Cox wrote:
> > New patch below, this time with DMA forced on RAID volumes - as my
> > firmware does not identify the RAID arrays as DMA capable :(
>
> The underlying problem is that the newer libata rewrites the dev->id data
> in ways that we can't then patch up. I've actually been hacking on this a
> bit today. The existing it821x code was working fine and it does the
> needed patching, it just needs to do it in a different place, and that in
> turn needs a new ap->ops->read_id() method so it can be hooked.

I can test the code once it's done.
I just moved my / to the RAID1 provided by IT8212. The controller has a great 
feature that allows converting a drive between RAID1/standalone without data 
loss (haven't seen anything like this yet). Also the background rebuild is 
nice (as seen on much more expensive RAID controllers), it's running as I'm 
typing this.

>
> On the bright side that also allows us to implement a pata_mfm/rll
> driver at last.
>

I used to have an old drive that was something like that - 5.25" Seagate 40MB 
drive. I sold it including the controller a couple of years ago (it was still 
working) so no testing fun for me.

> Alan



-- 
Ondrej Zary

  reply	other threads:[~2008-07-22 19:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 19:53 pata_it821x completely broken Ondrej Zary
2008-07-04 20:22 ` Alan Cox
2008-07-04 21:39   ` Ondrej Zary
2008-07-04 21:46     ` Alan Cox
2008-07-05 10:41       ` Ondrej Zary
2008-07-05 15:49         ` Alan Cox
2008-07-06 21:03           ` Ondrej Zary
2008-07-06 20:51             ` Alan Cox
2008-07-06 21:46               ` Ondrej Zary
2008-07-06 19:37         ` Alan Cox
2008-07-06 21:50           ` Ondrej Zary
2008-07-06 23:01             ` Alan Cox
2008-07-07 18:07               ` Ondrej Zary
2008-07-10 20:35               ` Ondrej Zary
2008-07-11 18:43                 ` Ondrej Zary
2008-07-11 20:14                   ` Alan Cox
2008-07-12 21:42                     ` Ondrej Zary
2008-07-13 11:47                       ` Ondrej Zary
2008-07-13 11:35                         ` Alan Cox
2008-07-13 12:10                           ` Ondrej Zary
2008-07-13 14:08                             ` Alan Cox
2008-07-22 17:59                         ` Ondrej Zary
2008-07-22 18:10                           ` Alan Cox
2008-07-22 19:16                             ` Ondrej Zary [this message]
2008-07-22 19:35                               ` Rene Herman
2008-07-22 20:39                                 ` Alan Cox

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=200807222116.19077.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).