From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>
Subject: Re: UFS utilities
Date: Wed, 29 Nov 2017 08:20:21 -0800 [thread overview]
Message-ID: <1511972421.3222.6.camel@HansenPartnership.com> (raw)
In-Reply-To: <e8aa9f0b9e854fe6bff7cb17dc08ce8c@SIWEX5A.sing.micron.com>
On Wed, 2017-11-29 at 15:39 +0000, Bean Huo (beanhuo) wrote:
> Thread-Topic: UFS utilities
> Thread-Index: AdNpKDYJWTPjczfxQHC/pD9WNnnl4w==
Could you fix your mail transfer agent? It's using these non standard
headers instead of the RFC mandated In-Reply-To: and References:
The problem is that this breaks threading on the public mailing lists
and means most of us can't tie this email back to the original thread.
> > On Mon, Nov 27, 2017 at 11:25:47AM +0000, Bean Huo (beanhuo) wrote:
> > >
> > > Hi, all
> > > Is there someone knows if exists one utilis dedicated to UFS
> > > device, rather than SCSI utils?
> > >
> > > I have tried sg3-utils, but it is not convenient for the embedded
> > > ARM-based system.
> > >
> > > And also it doesn't support several UFS special command.
> >
> > What specific UFS commands do you need to make to the device that
> > the current driver does not support?
>
>
> There are some UFS/vendor native commands. They are not SCSI based.
Can you list them? The reason for asking is that SCSI-3 is pretty
extensive in terms of management utilities, so any function you do with
vendor native commands that matches an sg3utils function could be done
by the latter instead via a SCSI translation layer.
James
next prev parent reply other threads:[~2017-11-29 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 15:39 UFS utilities Bean Huo (beanhuo)
2017-11-29 16:19 ` Greg KH
2017-11-29 16:20 ` James Bottomley [this message]
2017-12-04 2:47 ` Kyuho Choi
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 15:44 Bean Huo (beanhuo)
2017-12-05 15:49 ` gregkh
2017-11-27 11:25 Bean Huo (beanhuo)
2017-11-27 11:40 ` Greg KH
2017-11-27 19:35 ` Bart Van Assche
2017-12-04 15:20 ` [EXT] " Bean Huo (beanhuo)
2017-12-05 22:22 ` Bart Van Assche
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=1511972421.3222.6.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=beanhuo@micron.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vinholikatti@gmail.com \
/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.