All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Adrian May <Adrian_May@Jabil.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SES firmward download to SAS expander
Date: Mon, 16 Mar 2009 23:49:07 -0400	[thread overview]
Message-ID: <49BF1DB3.7090705@interlog.com> (raw)
In-Reply-To: <CCC151398C6F2B41AD8ACC06C28A779106775B32@penmsg10.corp.jabil.org>

Adrian May wrote:
> Hi all,
> 
> Some folks are asking me to advise about downloading firmware to some
> SAS expander. They had this conversation with the box:
> 
> #sg_ses -s /dev/sg5
> ...
> Download microcode (SES-2) [0xe]
> ...
> #sg_ses --control --page=0xe --data=- /dev/sg5 < image.bin
>   PMCSIERA  SXP 36x6Gsec      RevB

Looks like an interesting device: a 36 port 6Gbps SAS
expander that talks SES (as well as SMP I assume)?

>     enclosure services device
> Setting SES control page 0xe not supported yet
> 
> What I'm trying to figure out is WHO doesn't support it: the driver or
> the hardware?

ME, the guy who wrote sg_ses. That utility is 5 years old
and this is the first time anyone has asked me about
firmware download capability.

  Is everything done by the generic linux driver or is there
> some vendor-specific driver somewhere in the picture?

The SCSI generic driver is there for devices that don't
already have a "class" driver. To date there has been
no class driver for SES devices but I think one is
being added. As for a vendor specific driver you might
ask PMC Sierra.

  And why would this
> diag page be listed if it doesn't work?

Would it be better if sg_ses said something like
"not implemented, feel free to send code"?

> Huge thanks in advance for any assistance,

What is the size of the firmware file? If it is
approaching 1 MB or more then that may be too big
for a single SCSI command. That would require the
firmware to be broken up into more digestible blobs.

If you look at ses2r20.pdf section 6.1.18 (and 6.1.19)
then you might agree with me that firmware download
is relatively complex.

Doug Gilbert

      reply	other threads:[~2009-03-17  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  1:49 SES firmward download to SAS expander Adrian May
2009-03-17  3:49 ` Douglas Gilbert [this message]

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=49BF1DB3.7090705@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=Adrian_May@Jabil.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.