Is the DAC960 driver broken? I note that the maintainer is no longer active,
and it does not compile.
Is there patches to fix this problem?
Regards,
David McIlwraith mailto:[email protected]
On Wednesday 02 October 2002 01:08, David McIlwraith wrote:
> Is the DAC960 driver broken? I note that the maintainer is no longer active,
> and it does not compile.
>
> Is there patches to fix this problem?
Dave Olien has a functional patch. Look for his posts on this list.
--
Daniel
Patch for 2.5.38 works, albeit if you copy DAC960.[ch] from 2.5.38 to
drivers/block. The patch is broken in 2.5.40.
----- Original Message -----
From: "Daniel Phillips" <[email protected]>
To: "David McIlwraith" <[email protected]>;
<[email protected]>
Sent: Wednesday, October 02, 2002 9:19 AM
Subject: Re: [2.5.40] DAC960 broken?
> On Wednesday 02 October 2002 01:08, David McIlwraith wrote:
> > Is the DAC960 driver broken? I note that the maintainer is no longer
active,
> > and it does not compile.
> >
> > Is there patches to fix this problem?
>
> Dave Olien has a functional patch. Look for his posts on this list.
>
> --
> Daniel
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Somewhat premature.
----- Original Message -----
From: "David McIlwraith" <[email protected]>
To: "Daniel Phillips" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, October 02, 2002 10:04 AM
Subject: Re: [2.5.40] DAC960 broken?
> Patch for 2.5.38 works, albeit if you copy DAC960.[ch] from 2.5.38 to
> drivers/block. The patch is broken in 2.5.40.
>
> ----- Original Message -----
> From: "Daniel Phillips" <[email protected]>
> To: "David McIlwraith" <[email protected]>;
> <[email protected]>
> Sent: Wednesday, October 02, 2002 9:19 AM
> Subject: Re: [2.5.40] DAC960 broken?
>
>
> > On Wednesday 02 October 2002 01:08, David McIlwraith wrote:
> > > Is the DAC960 driver broken? I note that the maintainer is no longer
> active,
> > > and it does not compile.
> > >
> > > Is there patches to fix this problem?
> >
> > Dave Olien has a functional patch. Look for his posts on this list.
> >
> > --
> > Daniel
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
On compiling the driver w/ Dave Olein's patches:
gcc -Wp,-MD,./.DAC960.o.d -D__KERNEL__ -I/usr/src/linux-2.5.40/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-ali
asing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -I/usr/src/
linux-2.5.40/arch/i386/mach-generic -nostdinc -iwithprefix
lude -DKBUILD_BASENAME=DAC960 -c -o DAC960.o DAC960.c
drivers/block/DAC960.c: In function `DAC960_RegisterBlockDevice':
drivers/block/DAC960.c:2112: structure has no member named `major_name'
drivers/block/DAC960.c: In function `DAC960_UnregisterBlockDevice':
drivers/block/DAC960.c:2137: structure has no member named `major_name'
drivers/block/DAC960.c:2150: warning: implicit declaration of function
`blk_clear'
drivers/block/DAC960.c: In function `DAC960_Initialize':
drivers/block/DAC960.c:2766: too many arguments to function `register_disk'
drivers/block/DAC960.c: In function `DAC960_Open':
drivers/block/DAC960.c:5316: too many arguments to function `register_disk'
ld -m elf_i386 -r -o built-in.o elevator.o ll_rw_blk.o blkpg.o genhd.o
block_ioctl.o deadline-iosched.o floppy.o DAC960.o
ld: cannot open DAC960.o: No such file or directory
make[2]: *** [built-in.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.5.40/drivers/block'
make[1]: *** [block] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.40/drivers'
make: *** [drivers] Error 2
Anyone have any ideas?
Thanks in advance,
David McIlwraith mailto:[email protected]
I'm looking at it. I'll try post a patch tomorrow for 2.5.40.
On Wed, Oct 02, 2002 at 10:15:57AM +1000, David McIlwraith wrote:
> On compiling the driver w/ Dave Olein's patches:
>
>
>
> gcc -Wp,-MD,./.DAC960.o.d -D__KERNEL__ -I/usr/src/linux-2.5.40/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-ali
> asing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -I/usr/src/
> linux-2.5.40/arch/i386/mach-generic -nostdinc -iwithprefix
> lude -DKBUILD_BASENAME=DAC960 -c -o DAC960.o DAC960.c
> drivers/block/DAC960.c: In function `DAC960_RegisterBlockDevice':
> drivers/block/DAC960.c:2112: structure has no member named `major_name'
> drivers/block/DAC960.c: In function `DAC960_UnregisterBlockDevice':
> drivers/block/DAC960.c:2137: structure has no member named `major_name'
> drivers/block/DAC960.c:2150: warning: implicit declaration of function
> `blk_clear'
> drivers/block/DAC960.c: In function `DAC960_Initialize':
> drivers/block/DAC960.c:2766: too many arguments to function `register_disk'
> drivers/block/DAC960.c: In function `DAC960_Open':
> drivers/block/DAC960.c:5316: too many arguments to function `register_disk'
> ld -m elf_i386 -r -o built-in.o elevator.o ll_rw_blk.o blkpg.o genhd.o
> block_ioctl.o deadline-iosched.o floppy.o DAC960.o
> ld: cannot open DAC960.o: No such file or directory
> make[2]: *** [built-in.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.5.40/drivers/block'
> make[1]: *** [block] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.5.40/drivers'
> make: *** [drivers] Error 2
>
> Anyone have any ideas?
>
> Thanks in advance,
> David McIlwraith mailto:[email protected]
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/