I've been seeing a lot of complaints about aic7xxx in the 2.4.3 kernel. I
think that people are missing the crucial point: aic7xxx won't compile if
you patch up from 2.4.2, but if you download the complete 2.4.3 tarball,
it compiles fine.
So, I conclude that the patch was created incorrectly, or that something
changed between cutting the patch and the tarball.
-jwb
"Jeffrey W. Baker" wrote:
> So, I conclude that the patch was created incorrectly, or that something
> changed between cutting the patch and the tarball.
Compiled fine for me without the complete tarball, just patched. Now, I
went straight to ac2 (now ac3) without building the 2.4.3 stock kernel.
Have you tried a "make mrproper" on the tree?
John
>I've been seeing a lot of complaints about aic7xxx in the 2.4.3 kernel. I
>think that people are missing the crucial point: aic7xxx won't compile if
>you patch up from 2.4.2, but if you download the complete 2.4.3 tarball,
>it compiles fine.
>
>So, I conclude that the patch was created incorrectly, or that something
>changed between cutting the patch and the tarball.
>
>-jwb
Actually, the issue has to do with how the firmware is generated and
the dependencies between generated and source files. The tar file
touched all files whereas the patch touched only a few. This is why
the tar file worked and the patch did not.
Newer versions of the driver completely avoid this issue by only attempting
to re-build the firmware if you explicitly configure your kernel this way.
--
Justin