plustek: Driver doesn't work on >= 2.4.0-test8


Previous by date: 17 Oct 2000 21:25:32 -0000 Re: Driver doesn't work on >= 2.4.0-test8, Jaeger, Gerhard
Next by date: 17 Oct 2000 21:25:32 -0000 insmod pt_drv failed, Haiko Appel
Previous in thread: 17 Oct 2000 21:25:32 -0000 Re: Driver doesn't work on >= 2.4.0-test8, Jaeger, Gerhard
Next in thread: 17 Oct 2000 21:25:32 -0000 Re: Driver doesn't work on >= 2.4.0-test8, G. Jaeger

Subject: Re: Driver doesn't work on >= 2.4.0-test8
From: Jorge Nerin ####@####.####
Date: 17 Oct 2000 21:25:32 -0000
Message-Id: <39EC33D2.66244244@zaralinux.com>

Mark Bialkowski wrote:
> 
> Hey Gerhard:
> 
> Looks like a no-go on the sysdep-2.1.h update you sent.  The problem seems
> to be that the kernel simply doesn't recognize the get_user_ret and
> put_user_ret symbols, since they were completely dropped from uaccess.h, so
> it won't load the module even if you define the functions back into the
> driver.  A grep of the test9 source shows absolutely no sign of either
> put_user_ret or get_user_ret.
> 
> It looks as if the equivalent to put_user_ret(a,b,return) in test8/9/beyond
> is
> 
>         if (put_user(a,b))
>                 return value;
> 
> Yeah.  It's that ugly.  A couple examples I dug out from the kernel source:
> 
[SNIP]
> ------
> 
> You get the idea.
> 
> Hope this helps you come up with a solution, and I'll hope for some magical
> inspiration at this end.
> -Mark

Well, I have tried the driver in 2.4.0-test10-pre3+reiserfs-3.6.18, with
no luck, compiled with DEBUG uncommented:

kernel: *********************************************
kernel: pt_drv: init_module()
kernel: pt_drv : driver version = 0.36-36
kernel: ptdrvInit(0)
kernel: Init settings done
kernel: ScanData = 0xc4140000
kernel: Requested port at 0x378
kernel: Requested port (0x378) found
kernel: Port mode reported: (0x0047)
kernel: Port for device 0 registered
kernel: ptdrvOpen(port=0x378)
kernel: Try to claim the parport
kernel: Using EPP-mode
kernel: Starting Scanner-Autodetection
kernel: ************ DETECTP48xx ************
kernel: ModelSet4800()
kernel: modelInitPageSettings()
kernel: A4 set
kernel: ModelSet4800() done.
kernel: P48xxInitAsic()
kernel: DacInitialize()
kernel: ImageInitialize()
kernel: IOInitialize()
kernel: MotorInitialize()
kernel: Dataport = 0x0378
kernel: Ctrlport = 0x037a
kernel: Test 0x55
kernel: Test 0xAA
kernel: Compare data=0x7e and status=0x7e, port=0x378
kernel: detectScannerConnection() returns -9021.
kernel: ************ DETECTP9636 ************
kernel: ModelSet9636()
kernel: ModelSet9360()
kernel: modelInitPageSettings()
kernel: A4 set
kernel: ModelSet9630() done.
kernel: modelInitPageSettings()
kernel: A4 set
kernel: ModelSet9636() done.
kernel: P9636InitAsic()
kernel: DacInitialize()
kernel: ImageInitialize()
kernel: IOInitialize()
kernel: MotorInitialize()
kernel: AsicID = 0x77
kernel: ptdrvClose()
kernel: MiscRestorePort()
kernel: - no need to restore portmode !
kernel: Releasing parport
kernel: ptdrvShutdown()
kernel: cleanup device 0
kernel: Lamp-Timer stopped !
kernel: Try to claim the parport
kernel: Releasing parport
kernel: Port unregistered
kernel: pt_drv: init failed - ret = -9020
kernel: ---------------------------------------------

As seen the driver begins to load, but later it fails. This time there
is no dependencies problem.

I happen to own a Primax Colorado Direct 9600 scaner, which I hope its
supported by this driver.

Please CC me as you have done, because I'm not subscribed to the list,
thank you.

-- 
Jorge Nerin
####@####.####

Previous by date: 17 Oct 2000 21:25:32 -0000 Re: Driver doesn't work on >= 2.4.0-test8, Jaeger, Gerhard
Next by date: 17 Oct 2000 21:25:32 -0000 insmod pt_drv failed, Haiko Appel
Previous in thread: 17 Oct 2000 21:25:32 -0000 Re: Driver doesn't work on >= 2.4.0-test8, Jaeger, Gerhard
Next in thread: 17 Oct 2000 21:25:32 -0000 Re: Driver doesn't work on >= 2.4.0-test8, G. Jaeger


Powered by ezmlm-browse 0.20.