From: Alan Cox <alan@redhat.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: Alan Cox <alan@redhat.com>, Samuel Flory <sflory@rackable.com>,
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: Sun, 8 Jun 2003 19:24:17 -0400 (EDT) [thread overview]
Message-ID: <200306082324.h58NOHI18294@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030608214504.GA5754@carfax.org.uk> from "Hugo Mills" at Meh 08, 2003 10:45:04
> > Its clearly clos in that it works in PIO although DMA is failing
>
> Given that there appear to be problems with DMA in the plain SiI
> driver, would it be worth my while waiting until those are sorted out
> before continuing?
I'll fold the patch in anyway, maybe set to pio by default
> What would be the next steps in getting this thing working? Should
> I try to obtain the board/chip specifications from Adaptec? Or start
> poking stuff into arbitrary registers? :)
Given it seems its an SI chip I suspect SI are the right people here
if we need to bug someone. I would be very suprised if this is anything
but an SI3112. Its expensive to fab a chip so you dont fab special ones
for people. You might print a different logo or change the PCI ID in
the external serial eeprom but no more.
prev parent reply other threads:[~2003-06-08 23:10 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
2003-06-08 21:45 ` Hugo Mills
2003-06-08 23:24 ` Alan Cox [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=200306082324.h58NOHI18294@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;
as well as URLs for NNTP newsgroup(s).