From: Christoph Hellwig <hch@infradead.org>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
greg@kroah.com, mochel@osdl.org, "Moore,
Eric Dean" <Eric.Moore@lsil.com>,
"Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>,
Luben Tuikov <luben_tuikov@adaptec.com>
Subject: Re: 2.6: how do I this in sysfs?
Date: Thu, 25 Aug 2005 20:09:51 +0100 [thread overview]
Message-ID: <20050825190951.GA20812@infradead.org> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF10AB38B33@cceexc23.americas.cpqcorp.net>
> > typedef struct _CSMI_SAS_IDENTIFY {
> > __u8 bDeviceType;
> > __u8 bRestricted;
> > __u8 bInitiatorPortProtocol;
> > __u8 bTargetPortProtocol;
> > __u8 bRestricted2[8];
> > __u8 bSASAddress[8];
> > __u8 bPhyIdentifier;
> > __u8 bSignalClass;
> > __u8 bReserved[6];
> > } CSMI_SAS_IDENTIFY,
> > *PCSMI_SAS_IDENTIFY;
please compare this with struct sas_identify in
include/linux/scsi_transport_sas.h and look at
drivers/scsi/scsi_transport_sas.c om how it's exposed.
> > typedef struct _CSMI_SAS_PHY_ENTITY {
> > CSMI_SAS_IDENTIFY Identify;
> > __u8 bPortIdentifier;
> > __u8 bNegotiatedLinkRate;
> > __u8 bMinimumLinkRate;
> > __u8 bMaximumLinkRate;
> > __u8 bPhyChangeCount;
> > __u8 bAutoDiscover;
> > __u8 bReserved[2];
> > CSMI_SAS_IDENTIFY Attached;
> > } CSMI_SAS_PHY_ENTITY,
> > *PCSMI_SAS_PHY_ENTITY;
and this one to struct sas_port_attrs.
This is after my minimal sas transport class, please also read the
thread about it on linux-scsi
next prev parent reply other threads:[~2005-08-25 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 18:52 2.6: how do I this in sysfs? Miller, Mike (OS Dev)
2005-08-25 19:02 ` Andrew Patterson
2005-08-25 19:09 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-29 17:24 Miller, Mike (OS Dev)
2005-08-29 22:32 ` Greg KH
2005-08-29 23:17 ` gcoady
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=20050825190951.GA20812@infradead.org \
--to=hch@infradead.org \
--cc=Eric.Moore@lsil.com \
--cc=Mike.Miller@hp.com \
--cc=andrew.patterson@hp.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=mochel@osdl.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