From: Renaud Barbier <renaud.barbier@ge.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/3] DA923RC: enable UBIFS support to allow firmware flash booting
Date: Wed, 29 Jan 2014 11:06:49 +0000 [thread overview]
Message-ID: <1390993612-26246-1-git-send-email-renaud.barbier@ge.com> (raw)
UBI/UBIFS are enabled for the DA923RC board to load and boot images from
the NOR flash storage. As images may be loaded through a symlink, the
readlink entry point is implemented in the UBIFS driver support.
ppc bit operations header files are updated as they are in conflict with
main header files when UBIFS is enabled.
Renaud Barbier (3):
ppc: remove bit operation headers file conflict
UBIFS: implement readlink entry point
DA923RC: enable UBI/UBIFS configuration
arch/ppc/boards/geip-da923rc/env/bin/init | 12 +++++++
arch/ppc/configs/da923rc_defconfig | 6 ++++
arch/ppc/cpu-85xx/tlb.c | 2 +-
arch/ppc/include/asm/bitops.h | 46 +--------------------------
arch/ppc/mach-mpc85xx/fsl_law.c | 1 +
arch/ppc/mach-mpc85xx/include/mach/ffs64.h | 20 ++++++++++++
fs/ubifs/ubifs.c | 38 +++++++++++++++++++++++
7 files changed, 80 insertions(+), 45 deletions(-)
create mode 100644 arch/ppc/mach-mpc85xx/include/mach/ffs64.h
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-01-29 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 11:06 Renaud Barbier [this message]
2014-01-29 11:06 ` [PATCH 1/3] ppc: remove bit operation headers file conflict Renaud Barbier
2014-01-29 11:06 ` [PATCH 2/3] UBIFS: implement readlink entry point Renaud Barbier
2014-01-29 11:06 ` [PATCH 3/3] DA923RC: enable UBI/UBIFS configuration Renaud Barbier
2014-01-30 7:43 ` [PATCH 0/3] DA923RC: enable UBIFS support to allow firmware flash booting Sascha Hauer
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=1390993612-26246-1-git-send-email-renaud.barbier@ge.com \
--to=renaud.barbier@ge.com \
--cc=barebox@lists.infradead.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