From: Arjan van de Ven <arjanv@redhat.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic7xxx strange code
Date: Thu, 1 Jan 2004 17:28:23 +0100 [thread overview]
Message-ID: <20040101162823.GC18742@devserv.devel.redhat.com> (raw)
In-Reply-To: <482322704.1072974098@aslan.scsiguy.com>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Thu, Jan 01, 2004 at 09:21:38AM -0700, Justin T. Gibbs wrote:
> >> Unfortunately, fixing 2.4 and 2.6 now doesn't help in supporting older
> >> kernels that are still in production. You can't change the past no
> >> matter how hard we'd like to try.
> >
> > But vendors will update those kernels.....
>
> Yes, but I can't remove support for these older kernels for quite
> some time.
2.6 seems to do the right thing at least so for your 2.6 drivers you can fix
it.
> Are you planning an audit of the other platforms to ensure API compliance?
This is the first time I've seen this bug (thanks again for reporting it)
and it's clearly an API violation of the ONE API in linux which is very well
documented so no other platform will have copied this bad bug... Adaptect
aic7xxx is not the only card which has the "ringbuffer needs to be in 32 bit
dma space" requirements and no other drivers have workarounds like this, a
sign that the bug isn't actually "common".
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-01 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 15:46 aic7xxx strange code Arjan van de Ven
2003-12-31 18:36 ` Justin T. Gibbs
2004-01-01 10:08 ` Arjan van de Ven
2004-01-01 16:16 ` Justin T. Gibbs
2004-01-01 16:17 ` Arjan van de Ven
2004-01-01 16:21 ` Justin T. Gibbs
2004-01-01 16:28 ` Arjan van de Ven [this message]
2004-01-01 22:31 ` Andi Kleen
2004-01-01 22:34 ` Arjan van de Ven
2004-01-01 23:14 ` Andi Kleen
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=20040101162823.GC18742@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@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