public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: hugo-lkml@carfax.org.uk (Hugo Mills)
Cc: alan@redhat.com (Alan Cox), sflory@rackable.com (Samuel Flory),
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	andre@linux-ide.org
Subject: Re: [PATCH][RFC] Add support for Adaptec 1210SA (was: Re: SiI3112 (Adaptec 1210SA): no devices)
Date: Sat, 7 Jun 2003 14:02:34 -0400 (EDT)	[thread overview]
Message-ID: <200306071802.h57I2Yb07842@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030607175637.GA1266@carfax.org.uk> from "Hugo Mills" at Meh 07, 2003 06:56:37

>    Like the patch below?

Yep

>    I've assumed that it's exactly like a SiI3112 in making these
> changes. The kernel now recognises the device, and I can (e.g.) run
> cfdisk. However, any read or write on the disk causes huge delays, and
> these:

Its clearly clos in that it works in PIO although DMA is failing

>    I don't have the knowledge to determine whether this is similar to
> the SiI3112 problems people have been having elsewhere, or if it's a

It is

>  Model=ST3120026AS, FwRev=3.05, SerialNo=3JT059GT

According to the info I have that drive should be working ok


This is a very good starting point anyway

  reply	other threads:[~2003-06-07 17:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 19:35 SiI3112 (Adaptec 1210SA): no devices Hugo Mills
2003-06-05 20:13 ` Alan Cox
2003-06-05 21:04   ` Hugo Mills
2003-06-12  4:15   ` Andre Hedrick
2003-06-05 20:48 ` Samuel Flory
2003-06-05 21:15   ` Hugo Mills
2003-06-05 22:07     ` Alan Cox
2003-06-07 17:56       ` [PATCH][RFC] Add support for Adaptec 1210SA (was: Re: SiI3112 (Adaptec 1210SA): no devices) Hugo Mills
2003-06-07 18:02         ` Alan Cox [this message]
2003-06-08 21:45           ` Hugo Mills
2003-06-08 23:24             ` 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=200306071802.h57I2Yb07842@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=andre@linux-ide.org \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.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