From: Stephan Gatzka <stephan@gatzka.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: linux-mtd@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: MPC5200b jffs2 memcpy alignment problem
Date: Mon, 02 Jul 2012 18:41:39 +0200 [thread overview]
Message-ID: <4FF1CF43.70707@gatzka.org> (raw)
In-Reply-To: <20120702122134.50340f5f@wker>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi!
> This problem has been discussed several times [1], [2], but wasn't
> resolved yet. The clean solution suggested was to implement a custom
> mapping driver [3].
Then I'll do that. It doesn't look terribly complicated.
It would be helpful if someone can test the first version if it's available.
Regards,
Stephan
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4931 bytes --]
prev parent reply other threads:[~2012-07-02 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 19:16 MPC5200b jffs2 memcpy alignment problem Stephan Gatzka
2012-06-30 20:09 ` Albrecht Dreß
2012-07-01 6:47 ` Stephan Gatzka
2012-07-01 13:50 ` William F.
2012-07-02 10:21 ` Anatolij Gustschin
2012-07-02 16:41 ` Stephan Gatzka [this message]
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=4FF1CF43.70707@gatzka.org \
--to=stephan@gatzka.org \
--cc=agust@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).