Problems with cpia-0.2.3

[Peter Pregler]

On 21-Oct-99 Bas Rijniersce wrote:
> Hi,
> 
> I finally had the time to try the Peter's latest driver. I run into some
> trouble when compiling the driver. First the system:
> Dual celeron, 128 Mb, RedHat 6.0, Linux 2.2.12
> 
> Insmod'ing parport and parport_pc:
> parport0: PC-style at 0x378 [SPP,ECP,ECPEPP,ECPPS2]

Here the dma-port should be listed. In my setup things look like

Oct 21 09:14:08 lugburz kernel: parport0: PC-style at 0x378, dma 3
[SPP,ECP,ECPEPP,ECPPS2]. DMA is available only iff you load the parport_*
as given below, i.e. DMA is not autoprobed.

> No problems with the compile. But insmod'ing ppcuscpia.o gives a whole
> list off unresolved symbol's:
> ppcuscpia.o: unresolved symbol schedule_timeout
> ppcuscpia.o: unresolved symbol __wake_up
> ppcuscpia.o: unresolved symbol parport_unregister_device
> ..
> ppcuscpia.o: unresolved symbol jiffies
> ppcuscpia.o: unresolved symbol printk
> ppcuscpia.o: unresolved symbol __generic_copy_to_user

That's strange. I have no idea why all those standard kernel functions are
not found. Are you sure that the include-path for the kernel-headers does
match the current running kernel?

> ? Checking parport_unregister_device, used in interface_pp.c, wich
> include's linux/parport.h where parport_unregister_device is defined. 
> 
> Peter, in README.DMA you say "load the parport_pc module with parameter
> dma=N". Is N something like 0x378?

No, that is the dma-channel and not the io-port. In intel-land this is
something between 0-7 which you normally set in the bios (or a jumper for
old boards ;). As for alpha I have no idea where the association
dma-channel/parport is defined.

-Peter


-------------------------------
Email: Peter.Pregler@risc.uni-linz.ac.at
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
-----------------------------------------------------------------------------
To unsubscribe from this mailinglist, send the line "unsubscribe vision-webcam" in the
body of a message to "majordomo@errors.no".