All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aleš Nesrsta" <starous@volny.cz>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] USB Mass Storage CBI support
Date: Fri, 01 Oct 2010 17:06:35 +0200	[thread overview]
Message-ID: <1285945596.6460.14.camel@pracovna> (raw)
In-Reply-To: <4CA4FC38.8000308@gmail.com>

Vladimir 'φ-coder/phcoder' Serbinenko wrote: 
> On 09/26/2010 10:11 PM, Aleš Nesrsta wrote:
> > +  grub_uint8_t cbicb[GRUB_USBMS_CBI_CMD_SIZE] =
> > +    { 0x1d, 0x04, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff,
> > +      0xff, 0xff
> > +    };
> >   
> Could you deblob this?
> Other that this it can be merged into experimental. Be sure to push
> branches/cbi and then merge branches/cbi into experimental

Hi,

I am sorry, but I don't know what is "deblob", my English language
knowledge is unfortunately little bit limited (as you probably noticed
before...)...
(My dictionary says: "blob" is "small amount of a thick liquid"...)

I guess you probably want to explain what the code means and add related
comment (?)

It is CBI specific command "Command Block Reset" which should be used to
reset CBI protocol in "phase error" or similar fatal cases, i.e. it is
something like "Bulk Only Reset" control command.
There is difference between BO and CBI style of device communication
reset:
"Bulk Only Reset" is class-specific request for Bulk Only Mass Storage
devices.
CBI "Command Block Reset" is sent to device as a command block, i.e. as
DATA of CBI class-specific "universal" request ADSC.
(In both cases should be additionally cleared HALT feature on all EPs -
except control EP 0.)

In "USB Mass Storage Class Control/Bulk/Interrupt (CBI) Transport"
specification
(http://www.usb.org/developers/devclass_docs/usb_msc_cbi_1.1.pdf) you
can find "Command Block Reset" in chapter 2.2 Command Block Reset
Protocol, there is part of specification (citation):

"... To issue a Command Block Reset, the host shall use the Non-Data
Command Protocol to transport the command block:
1Dh 04h FFh FFh FFh FFh ...
The device may use the trailing FFh bytes to distinguish the Command
Block Reset from the legacy op 1Dh SEND DIAGNOSTIC command block.
..."

Regards
Ales 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel



  reply	other threads:[~2010-10-01 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 20:11 [PATCH] USB Mass Storage CBI support Aleš Nesrsta
2010-09-30 21:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-01 15:06   ` Aleš Nesrsta [this message]
2010-10-01 18:37     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-02 21:25       ` Aleš Nesrsta

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=1285945596.6460.14.camel@pracovna \
    --to=starous@volny.cz \
    --cc=grub-devel@gnu.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.