From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic7xxx woes in 2.5
Date: Mon, 16 Dec 2002 12:26:27 -0700 [thread overview]
Message-ID: <54180000.1040066787@aslan.btc.adaptec.com> (raw)
In-Reply-To: <3DFE24BE.A8E3755F@digeo.com>
>> Since you are running 2.5.X, the ahc_unlock never occurs.
>> In 2.4.X, ahd_midlayer_entrypoint_lock() saves the cpu flags
>> for us, so the variable is never uninitialized in the case
>> where it actually is compiled in.
>
> In 2.5.52 uniprocessor a
>
> make drivers/scsi/aic7xxx/aic7xxx_linux.i
>
> gives:
>
> static __inline void
> ahc_unlock(struct ahc_softc *ahc, unsigned long *flags)
> {
> do { do { (void)( &ahc->platform_data->spin_lock ); } while(0)
> ; __asm__ __volatile__("pushl %0 ; popfl": :"g" ( *flags ):"memory",
> "cc") ; do { } while (0) ; } while (0) ; }
>
> Which is loading *flags into the CPU's interrupt status register.
Since I wrote the routine, I'm well aware of how it operates.
> And it is being called from ahc_linux_queue_recovery_cmd:
>
> if (wait) {
> struct timer_list timer;
> int ret;
>
> ahc_unlock(ahc, &s);
> init_timer(&timer);
You must have botched the integration of the latest driver from here:
http://people.FreeBSD.org/~gibbs/linux/SRC.
I just downloaded it again (both the archive from the 10th and the 13th)
and neither use ahc_unlock under 2.5.X in ahc_linux_queue_recovery_cmd().
What are the $Id$ strings at the top of the file?
--
Justin
prev parent reply other threads:[~2002-12-16 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 4:31 aic7xxx woes in 2.5 Andrew Morton
2002-12-15 6:06 ` Ishikawa
2002-12-15 6:48 ` Andrew Morton
2002-12-15 13:48 ` Ishikawa
2002-12-15 20:17 ` Justin T. Gibbs
2002-12-15 20:09 ` Justin T. Gibbs
2002-12-16 9:40 ` Andrew Morton
2002-12-16 18:52 ` Justin T. Gibbs
2002-12-16 19:03 ` Christoph Hellwig
2002-12-16 19:08 ` Andrew Morton
2002-12-16 19:26 ` Justin T. Gibbs [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=54180000.1040066787@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=akpm@digeo.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