St?phane VOLTZ wrote:
> got CVS login problems again (and still that have weird extra
> 'Password:'
> prompt). I'll commit your changes, and a few other tidbits as soon as
> possible. For now I'll do it in the experimental/genesys directory, we'll
> move it from here to sane-backends/ba
Hello,
got CVS login problems again (and still that have weird extra
'Password:'
prompt). I'll commit your changes, and a few other tidbits as soon as
possible. For now I'll do it in the experimental/genesys directory, we'll
move it from here to sane-backends/backend when the g
ed Aug 10 20:19:25 2005
Subject: [sane-devel] genesys gl841 patch
In-Reply-To: <42fa4c06.4040...@pirsoft.dnsalias.org>
References: <42f73ecc.6050...@pirsoft.dnsalias.org>
<20050810172153.ge12...@meier-geinitz.de>
<42fa4c06.4040...@pirsoft.dnsalias.org>
Me
Hi,
On Wed, Aug 10, 2005 at 07:08:24PM +0200, St?phane VOLTZ wrote:
> I have trouble applying your patch:
>
> ~/cvs/experimental/gl841>patch --verbose -p1 Hmm...patch unexpectedly ends in middle of line
> I can't seem to find a patch in there anywhere.
> patch: Only garbage was foun
Le Lundi 8 Ao?t 2005 13:15, Pierre Willenbrock a ?crit?:
> Hi,
>
> This is the newest and hopefully final version of my genesys_com patch.
>
> This patch makes the bulk transfer functions chip specific and completes
> the gl841 side with a gamma bulk transfer function. It also moves the
> last two
Le Lundi 8 Ao?t 2005 13:15, Pierre Willenbrock a ?crit?:
> Hi,
>
> This is the newest and hopefully final version of my genesys_com patch.
>
> This patch makes the bulk transfer functions chip specific and completes
> the gl841 side with a gamma bulk transfer function. It also moves the
> last two
Hi,
This is the newest and hopefully final version of my genesys_com patch.
This patch makes the bulk transfer functions chip specific and completes
the gl841 side with a gamma bulk transfer function. It also moves the
last two occurances of send_slope_table inside the chip specific init
function
Pierre Willenbrock schrieb:
> Bulk access differs in all cases between gl646 and gl841.
> genesys_com.diff.gz moves the bulk functions into the chip specific
> source files. I also moved the last two occurences of send_slope_table
> in genesys.c to genesys_gl646.c and genesys_gl841.c, since the gl8
St?phane VOLTZ schrieb:
> Le Mercredi 3 Ao?t 2005 16:35, Pierre Willenbrock a ?crit :
>>So i conclude that the gl646 expects the shortest pixeltime first, while
>>the gl841 wants the longest pixeltime first.
>>Is this correct or am i doing something wrong?
>
> GL646 behaves like GL841 in thi
Le Mercredi 3 Ao?t 2005 16:35, Pierre Willenbrock a ?crit?:
> Hi
>
> Yesterday i got gl841_slow_back_home to work correctly.
>
> I noticed that sanei_genesys_create_slope_tables generates a slope table
> which starts at about 100 and ends at 2100. This table is unusable (at
> least with my canon li
Hi
Yesterday i got gl841_slow_back_home to work correctly.
I noticed that sanei_genesys_create_slope_tables generates a slope table
which starts at about 100 and ends at 2100. This table is unusable (at
least with my canon lide 35). The windows driver sends a linear table
starting with a value of
I did some minimal work on the driver recently. My goal was to get the
scanner(canon lide35) to physically do something.
The gl841 does not understand the bulk register transfer used for gl646,
so i modified sanei_genesys_bulk_write_register to do single register
writes. After fixing gl841_init_reg
Hi,
it's really great work!
thanks a lot!
xue
At Mon, 27 Jun 2005 10:52:34 +0200,
Pierre wrote:
>
> Hi
>
> I am owner of a Canon LiDE 35. I created a program which is able to scan
> a whole page at 600dpi, 8bit color using libusb. It does calibration of
> led-timings and shading. I tried to u
Hi,
On Mon, 2005-06-27 at 10:52 +0200, Pierre wrote:
> Hi
>
> I am owner of a Canon LiDE 35. I created a program which is able to scan
> a whole page at 600dpi, 8bit color using libusb. It does calibration of
> led-timings and shading. I tried to use the minimal set of registers.
> The order of g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I made some scans with your tool and uploaded the results to Flickr:
http://flickr.com/photos/perldude/21875262/
http://flickr.com/photos/perldude/21876018/
http://flickr.com/photos/perldude/21876019/
Pierre wrote:
> Hi
>
> I am owner of a Can
hi!
> Your tool works fine with my Canon LiDE 50!
>
> Thanks s much for your work!
i can only agree - works find .. i guess that should be a start point
for further gl841 improvements ;)
thx a lot for that fine work ..
currently i'm trying to scan some test images as requested and will pos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Your tool works fine with my Canon LiDE 50!
Thanks s much for your work!
Jens
Pierre wrote:
> Hi
>
> I am owner of a Canon LiDE 35. I created a program which is able to scan
> a whole page at 600dpi, 8bit color using libusb. It does calibr
Hi
I am owner of a Canon LiDE 35. I created a program which is able to scan
a whole page at 600dpi, 8bit color using libusb. It does calibration of
led-timings and shading. I tried to use the minimal set of registers.
The order of gpio settings on initialization is important, the scanner
locks up/
Hello,
> If everyone is OK with this, I feel like doing it this week-end. For a
>start, gl841 functions would be a copy of gl646 functions.
>
I'm OK with this. Thanks for this.
Philipp
On Monday 02 May 2005 08:12, svo...@wanadoo.fr wrote:
> On Fri, Apr 29, 2005 at 08:51:29AM +0200, Gerhard Jaeger wrote:
> > On Wednesday 27 April 2005 20:50, Philipp Schmid wrote:
> > Hi Philipp,
> >
> > good work so far. My suggestion for making the genesys backend GL841
> > aware is to identifiy
On Fri, Apr 29, 2005 at 08:51:29AM +0200, Gerhard Jaeger wrote:
> On Wednesday 27 April 2005 20:50, Philipp Schmid wrote:
> Hi Philipp,
>
> good work so far. My suggestion for making the genesys backend GL841
> aware is to identifiy functions, which needs to be changed so that they
> will work wit
On Wednesday 27 April 2005 20:50, Philipp Schmid wrote:
> Hello,
>
> Stef, I think you are absolutely right with your diagnostic that the
> genesys driver (written for gl646) fails with gl841 because the
> registers of the gl841 are different to the regs from gl646.
>
> So I've shortly compared
This is a multi-part message in MIME format.
--010201010504090102010302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hello,
Stef, I think you are absolutely right with your diagnostic that the
genesys driver (written for gl646) fails wit
23 matches
Mail list logo
