From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@lazybastard.org>
Cc: Marco <marco.stornelli@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, Tim Bird <tim.bird@am.sony.com>,
Chris Simmonds <chris@2net.co.uk>, Arnd Bergmann <arnd@arndb.de>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 06/14] Pramfs: Include files
Date: Tue, 23 Jun 2009 22:15:42 +0100 [thread overview]
Message-ID: <1245791743.25547.3517.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090623192648.GB23119@logfs.org>
On Tue, 2009-06-23 at 21:26 +0200, Jörn Engel wrote:
> Endianness is a
> different case imo. dd may not work, but a jtag probe will happily get
> you the dump to your development machine.
And dd on /dev/mem would work, surely?
I'd definitely recommend making it fixed-endian. Not doing so for JFFS2
was a mistake I frequently regretted.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-06-23 21:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 13:21 [PATCH 06/14] Pramfs: Include files Marco
2009-06-13 14:04 ` Sam Ravnborg
2009-06-13 22:59 ` Arnd Bergmann
2009-06-14 7:15 ` Marco
2009-06-21 17:07 ` Marco
2009-06-21 20:22 ` Arnd Bergmann
2009-06-22 6:23 ` Marco Stornelli
2009-06-22 11:17 ` Arnd Bergmann
2009-06-22 18:05 ` Marco
2009-06-22 18:33 ` Arnd Bergmann
2009-06-22 19:31 ` Chris Simmonds
2009-06-22 20:30 ` Sam Ravnborg
2009-06-22 22:00 ` Tim Bird
2009-06-23 4:21 ` Sam Ravnborg
2009-06-23 17:38 ` Marco
2009-06-23 19:26 ` Jörn Engel
2009-06-23 21:15 ` David Woodhouse [this message]
2009-06-23 21:55 ` Arnd Bergmann
2009-06-24 6:32 ` Marco Stornelli
2009-06-24 15:30 ` Arnd Bergmann
2009-06-24 16:49 ` Marco
2009-06-22 21:41 ` Jörn Engel
2009-06-22 22:20 ` David Woodhouse
2009-06-23 5:57 ` Jörn Engel
2009-06-23 8:31 ` David Woodhouse
2009-06-22 23:07 ` Arnd Bergmann
2009-06-23 6:40 ` Marco Stornelli
2009-06-14 7:15 ` Marco
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=1245791743.25547.3517.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=arnd@arndb.de \
--cc=chris@2net.co.uk \
--cc=joern@lazybastard.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=sam@ravnborg.org \
--cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).