On Tue, May 22, 2007 at 12:46:16PM -0400, Jeff Garzik wrote:
> Karsten Keil wrote:
> >So what is the reason to do this now, does this block some changes in
> >other places ? I did not change this code for long time because I know
> >that this is a nightmare, the code was grown and grown (supporting
Karsten Keil wrote:
So what is the reason to do this now, does this block some changes in
other places ? I did not change this code for long time because I know
that this is a nightmare, the code was grown and grown (supporting more and
more cards/chipsets) and is really nothing which should be u
Hello Jeff,
thank you for this effort.
On Tue, May 22, 2007 at 08:44:58AM -0400, Jeff Garzik wrote:
>
> The follow is the first baby step towards moving the HiSax drivers to
> the new PCI API. The HiSax PCI initialization code is ass-backwards and
> an incredible pain, so this will take many st
The follow is the first baby step towards moving the HiSax drivers to
the new PCI API. The HiSax PCI initialization code is ass-backwards and
an incredible pain, so this will take many steps. If anybody is
motivated to assist, help is more than welcome!
The first step just moves some code into
4 matches
Mail list logo
