Re: [PATCH] aic7xxx bouncing over 4G

Doug Ledford (dledford@redhat.com)
Sat, 28 Dec 2002 14:42:14 -0500


On Sat, Dec 28, 2002 at 12:13:38PM -0700, Justin T. Gibbs wrote:
>
> Unfortunately, the versions of the aic7xxx driver that are in the main
> trees (both nearly a year out of date) don't have this test and, like the
> "old" driver, they default to memory mapped I/O. One of the reasons I've
> been pushing so hard for this new driver to go into the tree is that 90%
> of the complaints about the new driver would go away if it were updated
> to a sane revision.

Actually, no, you need to check 2.5.53 Justin. Your latest stuff (6.2.24
or thereabouts I think) has been sucked in and several of the "It breaks
in 2.5.53" reports that have floated through linux-scsi in the last week
are in fact about that specific version of the driver. From the Changelog
of 2.5.53:

<gibbs@overdrive.btc.adaptec.com>
Update to aic7xxx 6.2.22 and aic79xx 1.3.0_ALPHA2

<gibbs@overdrive.btc.adaptec.com>
Remove generated file.

<gibbs@overdrive.btc.adaptec.com>
Enable highmem_io.

<gibbs@overdrive.btc.adaptec.com>
o Kill host template files.
o Move readme files into the Documentation SCSI directory
o Enable highmem_io
o Split out Kconfig files for aic7xxx and aic79xx

Host template and large disk changes provided or inspired by:
Christoph Hellwig <hch@sgi.com>

<gibbs@overdrive.btc.adaptec.com>
Complete the upgrade to aic7xxx 6.2.23 and aic79xx 1.3.0_ALPHA3.

<gibbs@overdrive.btc.adaptec.com>
Update to aic7xxx version 6.2.24 and aic79xx version 1.3.0_ALPHA5.

So, in short, your going to have to change your autoresponse to 2.5
kernels now because Linus bit the bullet and grabbed your tree.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/