From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alex Dubov <oakad@yahoo.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] MEMSTICK: Add driver for Ricoh R5C592 Card reader.
Date: Sat, 07 Aug 2010 23:22:45 +0300 [thread overview]
Message-ID: <1281212565.3300.20.camel@maxim-laptop> (raw)
In-Reply-To: <952321.94696.qm@web37608.mail.mud.yahoo.com>
Hi,
I have few more questions about memsticks.
First of all, I need an explanation of overwrite flag.
You already explained it to me once, but I still not sure about few
things.
#define MEMSTICK_OVERWRITE_UDST 0x10
This one I understand, thinking about xD again, I think it is very
handy.
My idea (from xD of course) is that copyonwrite is done this way:
1. read old sector
2. allocate new sector
2. write what was just read to new sector.
3. erase old sector.
Could you explain when I need to set and reset the
MEMSTICK_OVERWRITE_UDST?
#define MEMSTICK_OVERWRITE_PGST1 0x20
#define MEMSTICK_OVERWRITE_PGST0 0x40
I suppose these indicate that page(sector) contains incorrect data, just
like in xD there is page status?
Again, better explanation is welcome.
Also, should I touch that flag when I update sector?
#define MEMSTICK_OVERWRITE_BKST 0x80
This marks bad blocks?
Another question is about write of oob data.
When I write it, overwrite flag is updated, or I need to use
MEMSTICK_CP_OVERWRITE to update it?
I think former is true.
When I write a sector, I just write 0 to management flag, right?
And last question,
If I use MEMSTICK_CP_BLOCK, can I start reading a block from non-zero
page offset?
And surely last question, what is 'MS_CMD_BLOCK_END'
Thanks again for all help so far,
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-08-07 20:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 8:30 Alex Dubov
2010-08-05 11:20 ` Maxim Levitsky
2010-08-05 11:48 ` Alex Dubov
2010-08-05 12:30 ` Maxim Levitsky
2010-08-05 17:47 ` Maxim Levitsky
2010-08-06 7:43 ` Alex Dubov
2010-08-06 10:56 ` Maxim Levitsky
2010-08-07 13:15 ` Alex Dubov
2010-08-07 15:58 ` Maxim Levitsky
2010-08-08 13:31 ` Alex Dubov
2010-08-06 8:01 ` Alex Dubov
2010-08-05 12:46 ` Maxim Levitsky
2010-08-06 7:59 ` Alex Dubov
2010-08-06 10:59 ` Maxim Levitsky
2010-08-07 13:12 ` Alex Dubov
2010-08-07 16:03 ` Maxim Levitsky
2010-08-08 13:33 ` Alex Dubov
2010-08-07 20:22 ` Maxim Levitsky [this message]
2010-08-08 14:26 ` Alex Dubov
2010-08-08 15:07 ` Maxim Levitsky
2010-08-08 20:08 ` Maxim Levitsky
2010-08-09 6:31 ` Alex Dubov
2010-08-09 6:56 ` Maxim Levitsky
2010-08-09 15:30 ` Maxim Levitsky
2010-08-10 8:12 ` Alex Dubov
2010-08-10 9:47 ` Maxim Levitsky
2010-08-11 8:08 ` Alex Dubov
2010-08-11 8:32 ` Maxim Levitsky
2010-08-12 7:22 ` Alex Dubov
2010-08-12 7:58 ` Maxim Levitsky
2010-08-12 7:27 ` JMicron chipset update Alex Dubov
2010-08-09 19:19 ` [PATCH 2/2] MEMSTICK: Add driver for Ricoh R5C592 Card reader Maxim Levitsky
2010-08-10 7:53 ` Alex Dubov
2010-08-10 9:50 ` Maxim Levitsky
2010-08-11 8:16 ` Alex Dubov
-- strict thread matches above, loose matches on Subject: below --
2010-12-09 2:39 MEMSTICK: Add my 2 drivers Maxim Levitsky
2010-12-09 2:42 ` [PATCH 2/2] memstick: Add driver for Ricoh R5C592 card reader Maxim Levitsky
2010-08-03 14:53 [PATCH 0/2] Driver for Ricoh cardreader Maxim Levitsky
2010-08-03 14:53 ` [PATCH 2/2] MEMSTICK: Add driver for Ricoh R5C592 Card reader Maxim Levitsky
2010-08-04 7:57 ` Alex Dubov
2010-08-04 16:48 ` Maxim Levitsky
2010-08-04 19:31 ` Maxim Levitsky
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=1281212565.3300.20.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®