From: Alex Dubov <oakad@yahoo.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Legacy memstick support + FTL questions
Date: Tue, 23 Feb 2010 01:01:40 -0800 (PST) [thread overview]
Message-ID: <75802.83415.qm@web37603.mail.mud.yahoo.com> (raw)
In-Reply-To: <1266880283.32669.8.camel@maxim-laptop>
> > > Alex, could you explain how a single TPC is
> performed?
> > >
> > > I currently first send MS_TPC_SET_RW_REG_ADRS,
> and then
> > > MS_TPC_READ_REG
> > >
> > > When I send the TPC I specify both the tpc number
> and its
> > > len. Is the
> > > len transmitted?
> >
> > Of course, it is. How otherwise media would know how
> many bits to sample
> > in?
> By watching the #BS?
> Every clock cycle media reads 1 or 4 bits, when #BS goes
> low it stops
> reading...
> Why otherwise one would need the #BS line?
It is so and not so.
It appears, length is not transmitted as part of actual TPC payload.
However, number of data payload bytes is always determined by the media
register values. If this condition is not maintained all sorts of bad
things may happen.
__________________________________________________________________________________
Yahoo!7: Catch-up on your favourite Channel 7 TV shows easily, legally, and for free at PLUS7. www.tv.yahoo.com.au/plus7
next prev parent reply other threads:[~2010-02-23 9:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1266091737.30330.16.camel@maxim-laptop>
2010-02-14 15:06 ` Legacy memstick support + FTL questions Alex Dubov
2010-02-14 19:03 ` Maxim Levitsky
2010-02-16 14:15 ` Alex Dubov
2010-02-16 23:49 ` Maxim Levitsky
2010-02-17 2:26 ` Alex Dubov
2010-02-17 23:39 ` Maxim Levitsky
2010-02-21 22:42 ` Maxim Levitsky
2010-02-22 14:04 ` Alex Dubov
2010-02-22 23:11 ` Maxim Levitsky
2010-02-23 9:01 ` Alex Dubov [this message]
2010-02-24 1:10 ` Maxim Levitsky
2010-02-24 2:20 ` Alex Dubov
2010-01-26 21:43 Maxim Levitsky
2010-01-27 2:16 ` Alex Dubov
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=75802.83415.qm@web37603.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@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.