From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 14:22:24 2006 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.ORG Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BC4D16A41F for ; Wed, 25 Jan 2006 14:22:24 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B10943D46 for ; Wed, 25 Jan 2006 14:22:23 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (srqxab@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k0PEMG2m081789 for ; Wed, 25 Jan 2006 15:22:21 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k0PEMGcA081788; Wed, 25 Jan 2006 15:22:16 +0100 (CET) (envelope-from olli) Date: Wed, 25 Jan 2006 15:22:16 +0100 (CET) Message-Id: <200601251422.k0PEMGcA081788@lurza.secnetix.de> From: Oliver Fromme To: freebsd-scsi@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-scsi User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 25 Jan 2006 15:22:21 +0100 (CET) Cc: Subject: Re: SCSI scanner, sym/ncr driver, pt(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-scsi@FreeBSD.ORG List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 14:22:24 -0000 Matthias Andree wrote: > Oliver Fromme writes: > > Hell, I do not even know if my "810" card is an "early NCR 810" which > > sym(4) keeps talking about. > > Why bother as long as it works :-) Well, there could have been the possibility that it might work better (faster, more stable, whatever) with the other driver. > > If you're just a user, the manpages fail to tell whether > > the sym(4) or ncr(4) driver is preferred for an 810 host > > adapter. > > Personally, I'd prefer sym(4). OK. Thanks für your recommendation. I'll keep sym, too. > > However, gimp and the xscanimage plugin use the full SANE > > scanner device string for identifying it and storing their > > configuration. > > AFAIR you can use xscan as GIMP plugin, too. Ah, you mean xsane? I've only tried xscanimage so far. Somehoe it didn't came to my mind that there could be other possibilities. :-) I just looked at the xsane homepage. The GUI looks quite good (better than xscanimage), so I think I'll give it a try tomorrow. Hopefully it supports manual specification of color correction values (xscanimage does), because I need to do that in order for colors to come out correctly with my scanner. Thanks for the hint! Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Python tricks" is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure . -- Tim Peters