[8275] in linux-scsi channel archive
Re: Driver reading from a file
daemon@ATHENA.MIT.EDU (Alan Cox)
Tue Feb 29 19:53:36 2000
To: yiding_wang@agilent.com ("WANG,YIDING (HP-SanJose,ex1)")
Date: Tue, 29 Feb 2000 22:16:33 +0000 (GMT)
Cc: schaefer@alphanet.ch ('Marc SCHAEFER'),
linux-kernel@vger.rutgers.edu ('linux_kernel'),
linux-scsi@vger.rutgers.edu ('linux_scsi')
In-Reply-To: <D53173D574D6D211945500A0C9E95BEBEE16FE@xsj02.sj.hp.com> from "WANG,YIDING (HP-SanJose,ex1)" at Feb 29, 2000 01:20:24 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E12PuwV-0004Vv-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> set up persistent binding environment for Linux. This happens to Fibre
> Channel world when new device plugged into the loop or Fibric, the existing
> device address could change which leads to target id changes. The persisten
> binding is to preserve all existing device target id unchanged. This
> requires to put existing target id and the coresponding device world wide
> name pair somewhere in a file (or ROM), and be a refernece for the system
> next boot.
So the amount of data is quite small ?
> If Linux has some system calls to allow driver access from a file during the
> loading process, the solution will be obvious.
You have two cases then
1. You are the compiled in root file system driver. In which case only
boot up options from the command line (or lilo added) will work
since the rootfs cant be mounted until you are running
2. You pass the target id as a module parameter with insmod and use
the value in the driver.
Presumably an application would be needed after loading that queried the
driver to see if the target id changed ?
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
