linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Lei Sun" <leisun124@gmail.com>
To: "Li Yang-r58472" <LeoLi@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: weird behavior for jffs2 on PQ2FADS-VR board
Date: Wed, 12 Jul 2006 10:38:18 -0400	[thread overview]
Message-ID: <f9a7e7a80607120738p4587f540wb320ab82a47bdb0d@mail.gmail.com> (raw)
In-Reply-To: <4879B0C6C249214CBE7AB04453F84E4D0300BA@zch01exm20.fsl.freescale.net>

Hi Dave and Liu:
   Thanks for your reply!
   I will give it a try tonight, I did figure out it's endianess issue
last night, I wrote a little test program writting to /dev/mtd3 and
read it back, they got swapped !

lei

      reply	other threads:[~2006-07-12 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  4:23 weird behavior for jffs2 on PQ2FADS-VR board Lei Sun
2006-07-12  4:56 ` Liu Dave-r63238
2006-07-12  5:41 ` Li Yang-r58472
2006-07-12 14:38   ` Lei Sun [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=f9a7e7a80607120738p4587f540wb320ab82a47bdb0d@mail.gmail.com \
    --to=leisun124@gmail.com \
    --cc=LeoLi@freescale.com \
    --cc=linuxppc-embedded@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).