From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 23 11:02:53 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 6730216A423 for ; Mon, 23 Jan 2006 11:02:52 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D175343D7D for ; Mon, 23 Jan 2006 11:02:40 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0NB2ex3086379 for ; Mon, 23 Jan 2006 11:02:40 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0NB2dtY086373 for freebsd-scsi@freebsd.org; Mon, 23 Jan 2006 11:02:39 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 23 Jan 2006 11:02:39 GMT Message-Id: <200601231102.k0NB2dtY086373@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 11:02:53 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi [sym] SCSI subsystem hangs under heavy lo o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug o [2003/05/24] kern/52638 scsi [panic] SCSI U320 on SMP server won't run s [2003/09/30] kern/57398 scsi [mly] Current fails to install on mly(4) o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with o [2003/12/27] kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C81 s [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/12/02] kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5 o [2005/06/04] kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceP o [2005/12/12] kern/90282 scsi [sym] SCSI bus resets cause loss of ch de 12 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57469 scsi [scsi] [patch] Quirk for Conner CP3500 o [2005/01/12] kern/76178 scsi [ahd] Problem with ahd and large SCSI Rai 6 problems total. From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 08:51:32 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 6FE4B16A41F for ; Wed, 25 Jan 2006 08:51:32 +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 72CCE43D45 for ; Wed, 25 Jan 2006 08:51:31 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (jividq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k0P8pNR2065464 for ; Wed, 25 Jan 2006 09:51:29 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k0P8pNeQ065463; Wed, 25 Jan 2006 09:51:23 +0100 (CET) (envelope-from olli) Date: Wed, 25 Jan 2006 09:51:23 +0100 (CET) Message-Id: <200601250851.k0P8pNeQ065463@lurza.secnetix.de> From: Oliver Fromme To: freebsd-scsi@FreeBSD.ORG X-Newsgroups: list.freebsd-scsi User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 25 Jan 2006 09:51:29 +0100 (CET) Cc: Subject: 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 08:51:32 -0000 Hi, I'm running FreeBSD 6-stable. Recently I have connected an old SCSI scanner (EPSON GT-9000 a.k.a. ES-1200C) to an even older NCR810 host adapter. It works fine with SANE from the ports collection, after tweaking the config a little bit. However, I have a few questions. First I noticed that the NCR810 host adapter seems to be supported both by ncr(4) and sym(4). I was unable to find any documentation about the advantages of each. The man pages don't mention when to prefer one over the other. I tried sym(4) first because it seems to be newer, and it works fine. But I wonder if the ncr(4) driver offered any advantages. I mean, there must be a reason it is still in the source tree and not declared obsolete. By the way, these are the sym(4) probe messages: sym0: <810> port 0xec00-0xecff mem 0xe6403000-0xe64030ff irq 11 at device 20.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: [GIANT-LOCKED] I assume that ncr(4) is also giant-locked, right? The second question is probably a SANE issue, not a FreeBSD one, but I'll mention it to the experts here anyway. :-) The scanner is probed and attached to the pt(4) driver: pt0 at sym0 bus 0 target 4 lun 0 pt0: Fixed Processor SCSI-CCS device pt0: 3.300MB/s transfers However, the SANE back-end driver (man pages sane-epson(5) and sane-sscsi(5)) doesn't want to use /dev/pt0. When I try to access it, I get "invalid argument". The device node does exist, of course. But when I tell SANE to use the pass device, it works. The problem with that is that the number of the pass device is not always the same. It can be /dev/pass0 or /dev/pass1, depending on whether the scanner was on during boot, or switched on later and detected by re- scanning the SCSI bus. That's somewhat annoying, because I have to change the device setting all the time. My guess is that accessing the scanner through the pt0 device requires special API support in the SANE driver, while using the pass device does not. Is that right? Thanks in advance for any hints and insights! Best regards Oliver PS: No need for Cc, I read the freebsd-scsi list. -- 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. "C++ is the only current language making COBOL look good." -- Bertrand Meyer From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 09:15:16 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 712FD16A41F for ; Wed, 25 Jan 2006 09:15:16 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 95FD243D45 for ; Wed, 25 Jan 2006 09:15:15 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 25 Jan 2006 09:15:13 -0000 Received: from p50911ED7.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.30.215] by mail.gmx.net (mp032) with SMTP; 25 Jan 2006 10:15:13 +0100 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 96BCC200510 for ; Wed, 25 Jan 2006 10:15:07 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17013-11 for ; Wed, 25 Jan 2006 10:15:05 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 0AB65201109; Wed, 25 Jan 2006 10:15:05 +0100 (CET) From: Matthias Andree To: freebsd-scsi@FreeBSD.ORG In-Reply-To: <200601250851.k0P8pNeQ065463@lurza.secnetix.de> (Oliver Fromme's message of "Wed, 25 Jan 2006 09:51:23 +0100 (CET)") References: <200601250851.k0P8pNeQ065463@lurza.secnetix.de> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Wed, 25 Jan 2006 10:15:04 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Cc: Subject: Re: SCSI scanner, sym/ncr driver, pt(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 09:15:16 -0000 Oliver Fromme writes: > Hi, > > I'm running FreeBSD 6-stable. Recently I have connected > an old SCSI scanner (EPSON GT-9000 a.k.a. ES-1200C) to > an even older NCR810 host adapter. It works fine with > SANE from the ports collection, after tweaking the config > a little bit. However, I have a few questions. > > First I noticed that the NCR810 host adapter seems to be > supported both by ncr(4) and sym(4). I was unable to find > any documentation about the advantages of each. Try reading the man pages carefully. The differences have melted down somewhat in the past. There was a time when sym(4) didn't support the more efficient LOAD/STORE uncapable 810, 815, 825 chips (the A variants, where they exist, support LOAD/STORE). sym(4) has learned to use MEMMOVE on these, however. ncr(4) has never used LOAD/STORE, and lacks support for the 897 chip and the 1010 family. > The man pages don't mention when to prefer one over the other. I > tried sym(4) first because it seems to be newer, and it works fine. So stick with it. > But I wonder if the ncr(4) driver offered any advantages. It doesn't. There used to be a time when it worked with the old 810 and sym(4) didn't, but this no longer holds. > pt0 at sym0 bus 0 target 4 lun 0 > pt0: Fixed Processor SCSI-CCS device > pt0: 3.300MB/s transfers > > However, the SANE back-end driver (man pages sane-epson(5) > and sane-sscsi(5)) doesn't want to use /dev/pt0. When I > try to access it, I get "invalid argument". The device > node does exist, of course. But when I tell SANE to use > the pass device, it works. Sane now accesses devices through more generic access schemes, libusb for USB scanners, and pass for SCSI scanners. It was found that adding scanner drivers to the kernel is unnecessary bloat. > The problem with that is that the number of the pass > device is not always the same. It can be /dev/pass0 or > /dev/pass1, depending on whether the scanner was on > during boot, or switched on later and detected by re- > scanning the SCSI bus. That's somewhat annoying, because > I have to change the device setting all the time. Does it work if you list both devices (pass0 and pass1) in the SANE configuration (sane.d/epson.conf), or if you don't list explicit devices at all? USB scanners don't have a constant device number either and are identified by vendor/device ID (though libusb) rather than device number. I don't have a SCSI scanner though, so you're free to ignore me on the last two paragraphs. -- Matthias Andree From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 10:00:10 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 0E9BF16A420 for ; Wed, 25 Jan 2006 10:00:10 +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 3ED4043D48 for ; Wed, 25 Jan 2006 10:00:08 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ipknwl@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k0PA029I070582 for ; Wed, 25 Jan 2006 11:00:07 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k0PA02CY070581; Wed, 25 Jan 2006 11:00:02 +0100 (CET) (envelope-from olli) Date: Wed, 25 Jan 2006 11:00:02 +0100 (CET) Message-Id: <200601251000.k0PA02CY070581@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)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 25 Jan 2006 11:00:08 +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 10:00:10 -0000 Matthias Andree wrote: > Oliver Fromme writes: > > First I noticed that the NCR810 host adapter seems to be > > supported both by ncr(4) and sym(4). I was unable to find > > any documentation about the advantages of each. > > Try reading the man pages carefully. > > The differences have melted down somewhat in the past. > > There was a time when sym(4) didn't support the more efficient > LOAD/STORE uncapable 810, 815, 825 chips (the A variants, where they > exist, support LOAD/STORE). sym(4) has learned to use MEMMOVE on these, > however. > > ncr(4) has never used LOAD/STORE, and lacks support for the 897 chip and > the 1010 family. I've read about that LOAD/STORE and MEMMOVE stuff in the manpage, but I'm not a SCSI expert, so that's really only gibberish to me, I'm afraid. Hell, I do not even know if my "810" card is an "early NCR 810" which sym(4) keeps talking about. 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. > > The man pages don't mention when to prefer one over the other. I > > tried sym(4) first because it seems to be newer, and it works fine. > > So stick with it. I will. Thanks for the advice and explanation. > > But I wonder if the ncr(4) driver offered any advantages. > > It doesn't. There used to be a time when it worked with the old 810 and > sym(4) didn't, but this no longer holds. OK, so the ncr(4) should be regarded obsolete, right? In that case, the manpage should say so, at least. The sym(4) manpage explains in great length how to configure a preference between stm(4) and ncr(4), so that differnt chip types are attached to different drivers (using the SYM_SETUP_LP_PROBE_MAP setting). That made me think that there must be a reason why you would want to use the ncr(4) driver for certain chips. I think that all of that is pretty confusing. Anyway, thanks for the clarification, Matthias. > > pt0 at sym0 bus 0 target 4 lun 0 > > pt0: Fixed Processor SCSI-CCS device > > pt0: 3.300MB/s transfers > > > > However, the SANE back-end driver (man pages sane-epson(5) > > and sane-sscsi(5)) doesn't want to use /dev/pt0. When I > > try to access it, I get "invalid argument". The device > > node does exist, of course. But when I tell SANE to use > > the pass device, it works. > > Sane now accesses devices through more generic access schemes, libusb > for USB scanners, and pass for SCSI scanners. It was found that adding > scanner drivers to the kernel is unnecessary bloat. I certainly agree with that. But pt(4) is not a scanner driver, but a generic SCSI processing target driver, right? Do you know if there's a reason why SANE doesn't want to use it? I mean, what _purpose_ does pt(4) serve? Sorry if that's a dumb question. :-) So I assume I can remove "device pt" from my kernel, and SANE would still work. > > The problem with that is that the number of the pass > > device is not always the same. It can be /dev/pass0 or > > /dev/pass1, depending on whether the scanner was on > > during boot, or switched on later and detected by re- > > scanning the SCSI bus. That's somewhat annoying, because > > I have to change the device setting all the time. > > Does it work if you list both devices (pass0 and pass1) in the SANE > configuration (sane.d/epson.conf), or if you don't list explicit devices > at all? In fact, I don't list them. My epson.conf just contains this line: scsi "EPSON SC" so the scanner is identified by the vendor string. That works fine. scanimage(1) reports that it finds the scanner "epson:/dev/pass0" or "epson:/dev/pass1". However, gimp and the xscanimage plugin use the full SANE scanner device string for identifying it and storing their configuration. From the view point of gimp/xscanimage, I have two scanners. When I change the configuration of my pass0 scanner (e.g. resolution, color correction, whatever), it doesn't affect the "other" scanner, and vice versa. That's annoying. Hm. I've just got an idea. Is it possible to use devd(8) to create a symlink /dev/scanner whenever the scanner is detected, pointing to either pass0 or pass1? Then I could tell SANE to always use /dev/scanner. I've never fiddled with /etc/devd.conf, but it seems to be what I need. I guess I need to read a few more manpages. :-) 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. "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 10:26:26 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 056FE16A41F for ; Wed, 25 Jan 2006 10:26:26 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id D572443D58 for ; Wed, 25 Jan 2006 10:26:24 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 25 Jan 2006 10:26:23 -0000 Received: from p50911ED7.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.30.215] by mail.gmx.net (mp039) with SMTP; 25 Jan 2006 11:26:23 +0100 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 20EE62005D4 for ; Wed, 25 Jan 2006 11:26:22 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18589-09 for ; Wed, 25 Jan 2006 11:26:19 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 8D49B200F66; Wed, 25 Jan 2006 11:26:19 +0100 (CET) From: Matthias Andree To: freebsd-scsi@FreeBSD.ORG In-Reply-To: <200601251000.k0PA02CY070581@lurza.secnetix.de> (Oliver Fromme's message of "Wed, 25 Jan 2006 11:00:02 +0100 (CET)") References: <200601251000.k0PA02CY070581@lurza.secnetix.de> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Wed, 25 Jan 2006 11:26:19 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Cc: Subject: Re: SCSI scanner, sym/ncr driver, pt(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 10:26:26 -0000 Oliver Fromme writes: > Matthias Andree wrote: > > Oliver Fromme writes: > > > First I noticed that the NCR810 host adapter seems to be > > > supported both by ncr(4) and sym(4). I was unable to find > > > any documentation about the advantages of each. > > > > Try reading the man pages carefully. > > > > The differences have melted down somewhat in the past. > > > > There was a time when sym(4) didn't support the more efficient > > LOAD/STORE uncapable 810, 815, 825 chips (the A variants, where they > > exist, support LOAD/STORE). sym(4) has learned to use MEMMOVE on these, > > however. > > > > ncr(4) has never used LOAD/STORE, and lacks support for the 897 chip and > > the 1010 family. > > I've read about that LOAD/STORE and MEMMOVE stuff in the > manpage, but I'm not a SCSI expert, so that's really only > gibberish to me, I'm afraid. The driver downloads a program to the SCSI chip that handles the protocol, and the commands that these programs ("SCRIPTS") can use depend on the chip. > 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 :-) > 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). > I certainly agree with that. But pt(4) is not a scanner > driver, but a generic SCSI processing target driver, right? Never used it or even looked at the docs. > 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. -- Matthias Andree From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 12:40:09 2006 Return-Path: X-Original-To: freebsd-scsi@hub.freebsd.org Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 900B116A420; Wed, 25 Jan 2006 12:40:09 +0000 (GMT) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 360BC43D48; Wed, 25 Jan 2006 12:40:09 +0000 (GMT) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (flz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0PCe8Jx004042; Wed, 25 Jan 2006 12:40:09 GMT (envelope-from flz@freefall.freebsd.org) Received: (from flz@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0PCe8uE004031; Wed, 25 Jan 2006 12:40:08 GMT (envelope-from flz) Date: Wed, 25 Jan 2006 12:40:08 GMT From: Florent Thoumie Message-Id: <200601251240.k0PCe8uE004031@freefall.freebsd.org> To: walter@pelissero.de, flz@FreeBSD.org, freebsd-scsi@FreeBSD.org Cc: Subject: Re: kern/57469: [scsi] [patch] Quirk for Conner CP3500 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 12:40:09 -0000 Synopsis: [scsi] [patch] Quirk for Conner CP3500 State-Changed-From-To: open->closed State-Changed-By: flz State-Changed-When: Wed Jan 25 12:40:07 UTC 2006 State-Changed-Why: Committed some time ago. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=57469 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 From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 26 00:37:35 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 9C70516A420 for ; Thu, 26 Jan 2006 00:37:35 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id AD56E43D46 for ; Thu, 26 Jan 2006 00:37:34 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 26 Jan 2006 00:37:33 -0000 Received: from p50911ED7.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.30.215] by mail.gmx.net (mp037) with SMTP; 26 Jan 2006 01:37:33 +0100 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 7C3CA201B5A for ; Thu, 26 Jan 2006 01:37:32 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12577-06 for ; Thu, 26 Jan 2006 01:37:30 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 7061A201B5C; Thu, 26 Jan 2006 01:37:30 +0100 (CET) From: Matthias Andree To: freebsd-scsi@FreeBSD.ORG In-Reply-To: <200601251422.k0PEMGcA081788@lurza.secnetix.de> (Oliver Fromme's message of "Wed, 25 Jan 2006 15:22:16 +0100 (CET)") References: <200601251422.k0PEMGcA081788@lurza.secnetix.de> Mail-Followup-To: matthias.andree@gmx.de X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Thu, 26 Jan 2006 01:37:30 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 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: matthias.andree@gmx.de List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2006 00:37:35 -0000 Oliver Fromme writes: > > AFAIR you can use xscan as GIMP plugin, too. > > Ah, you mean xsane? Yes, I do. Sorry for mistyping it. > 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. It does. The default screen will only allow global correction but there's a switch underneath the sliders to allow setting these (contrast, brightness, gamma) per individual color channel (RGB). I'm setting Reply-To: to my personal mail address to take the discussion of the list. xsane color correction questions are perhaps better asked on Usenet in de.rec.fotografie or other relevant groups. -- Matthias Andree From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 27 10:49:10 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 2CF2716A420; Fri, 27 Jan 2006 10:49:10 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E2B143D45; Fri, 27 Jan 2006 10:49:08 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 29A7C84420; Fri, 27 Jan 2006 11:49:07 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 80196-01; Fri, 27 Jan 2006 11:49:01 +0100 (CET) Received: from [172.16.164.75] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 3D4CF8441E; Fri, 27 Jan 2006 11:49:01 +0100 (CET) Message-ID: <43D9FAA1.70105@fsn.hu> Date: Fri, 27 Jan 2006 11:49:05 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-scsi@freebsd.org Subject: Not so deep and not so correct benchmark for SCSI target mode X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2006 10:49:10 -0000 Hello, I've tried to do a quick benchmark of FreeBSD's target mode on Fibre Channel. The graphs are here: http://people.fsn.hu/~bra/freebsd/tmode-bench/ -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/