public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Frederic TEMPORELLI <frederic.temporelli@bull.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: proc_name in sysfs
Date: Wed, 6 Apr 2005 11:36:14 -0700	[thread overview]
Message-ID: <20050406183614.GA25370@us.ibm.com> (raw)
In-Reply-To: <4253CA94.8000500@bull.net>

On Wed, Apr 06, 2005 at 01:40:04PM +0200, Frederic TEMPORELLI wrote:

> 2/ now, how can we get the adapter module name from sysfs ?

Why do you need it?

Anyway, try lsscsi, it walks the sysfs tree:

[elm3b79 patman]$ lsscsi  -H
[0]    qla1280
[1]    qla1280
[2]    qla2xxx
[3]    qla2xxx

Or, script it:

[elm3b79 tmp]$ more xx.sh
#! /bin/sh

hdir=/sys/class/scsi_host

for i in ${hdir}/host*
do
        host_dir=$(cd ${i}/device;/bin/pwd)
        driver_dir=$(cd ${host_dir}/../driver;/bin/pwd)
        module=$(basename ${driver_dir})
        # echo ${i} is in: ${host_dir}
        echo "${i} module (driver) is: ${module}"
done

[elm3b79 tmp]$ sh ./xx.sh
/sys/class/scsi_host/host0 module (driver) is: qla1280
/sys/class/scsi_host/host1 module (driver) is: qla1280
/sys/class/scsi_host/host2 module (driver) is: qla2300
/sys/class/scsi_host/host3 module (driver) is: qla2300

-- Patrick Mansfield

  reply	other threads:[~2005-04-06 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 11:40 proc_name in sysfs Frederic TEMPORELLI
2005-04-06 18:36 ` Patrick Mansfield [this message]
2005-04-07  1:06   ` Douglas Gilbert
2005-04-07  6:35     ` Frederic TEMPORELLI
2005-04-07  8:17       ` Douglas Gilbert
2005-04-08  0:02       ` Patrick Mansfield
2005-04-08  7:37         ` Frederic TEMPORELLI
2005-04-08  0:00     ` Patrick Mansfield
2005-04-08  6:46 ` Christoph Hellwig
2005-04-08  8:03   ` Douglas Gilbert
2005-04-11 11:52     ` Christoph Hellwig
2005-04-11 14:19       ` James Bottomley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050406183614.GA25370@us.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=frederic.temporelli@bull.net \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox