From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20pre7, aic7xxx-6.2.8: Panic: HOST_MSG_LOOP with invalid SCB 0
Date: Mon, 23 Sep 2002 11:35:01 -0600 [thread overview]
Message-ID: <2492970816.1032802501@aslan.btc.adaptec.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209231227330.922-100000@freak.distro.conectiva>
> Justin,
>
> I guess is the second or third report of problems with the new aic7xxx :(
This issue has already been resolved as a chipset issue requiring
I/O mapped register access to work around. The "old" aic7xxx driver
avoids these issues by issuing a register read after every register
write. This stops up your PCI bus with wasted cycles even if you have
a perfectly working chipset.
So, how would you like me to resolve this. We can do the same thing
as Adaptec's windows drivers and just always use the slower, less
efficient I/O mapped method for accessing registers. This will "fix"
the problems people have with broken VIA and Intel chipsets. I can
make this a compile and run-time option, but should we default to
I/O mapped or memory mapped?
Don't you just love broken PC hardware?
--
Justin
next prev parent reply other threads:[~2002-09-23 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 5:28 2.4.20pre7, aic7xxx-6.2.8: Panic: HOST_MSG_LOOP with invalid SCB 0 Ville Herva
2002-09-20 15:37 ` Justin T. Gibbs
2002-09-20 18:19 ` 2.4.19, 2.4.20pre7, problem with aic7xxx driver Stephan von Krawczynski
2002-09-20 19:48 ` Phil Brutsche
2002-09-20 19:56 ` Stephan von Krawczynski
2002-09-23 15:28 ` 2.4.20pre7, aic7xxx-6.2.8: Panic: HOST_MSG_LOOP with invalid SCB 0 Marcelo Tosatti
2002-09-23 17:35 ` Justin T. Gibbs [this message]
2002-09-23 16:54 ` Marcelo Tosatti
2002-09-23 6:35 ` Benjamin Herrenschmidt
2002-09-23 21:43 ` Justin T. Gibbs
2002-09-23 7:15 ` Benjamin Herrenschmidt
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=2492970816.1032802501@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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