From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] add Phytec pcm030 board support
Date: Tue, 6 May 2008 10:08:11 +0200 [thread overview]
Message-ID: <20080506080811.GB4326@pengutronix.de> (raw)
In-Reply-To: <9e4733910805051022q7c2f868bw80173fd93e92b907@mail.gmail.com>
On Mon, May 05, 2008 at 01:22:40PM -0400, Jon Smirl wrote:
> On 5/5/08, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On Mon, May 5, 2008 at 11:01 AM, Jon Smirl <jonsmirl@gmail.com> wrote:
> > > Did this get fixed somehow? I used to need this to boot a pcm030.
> >
> >
> > I'm sorry; I'm at a lost as to context. Are you asking for this patch
> > to be applied? Or are you asking if this has been addressed in
> > another way?
>
> Sascha said the pcm030 was working with the simple dts. I always
> needed that patch to get a pcm030 to boot. Sasha's company wrote the
> patch. I'm just wondering how it got handled, do we still need the
> patch or did he come up with some other solution.
Yes, it is working with the simple dts except for the flash support. For
this we need the Flash description in the oftree.
> > >
> > > diff --git a/fs/jffs2/scan.c b/fs/jffs2/scan.c
> > > index 272872d..c982adc 100644
> > > --- a/fs/jffs2/scan.c
> > > +++ b/fs/jffs2/scan.c
> > > @@ -16,6 +16,7 @@
> > > #include <linux/pagemap.h>
> > > #include <linux/crc32.h>
> > > #include <linux/compiler.h>
> > > +#include <asm/io.h>
> > > #include "nodelist.h"
> > > #include "summary.h"
> > > #include "debug.h"
> > > @@ -505,7 +506,7 @@ static int jffs2_scan_eraseblock (struct
> > > jffs2_sb_info *c, struct jffs2_eraseblo
> > > sumptr = kmalloc(sumlen, GFP_KERNEL);
> > > if (!sumptr)
> > > return -ENOMEM;
> > > - memcpy(sumptr + sumlen -
> > > buf_len, buf + buf_size - buf_len, buf_len);
> > > + memcpy_fromio(sumptr + sumlen
> > > - buf_len, buf + buf_size - buf_len, buf_len);
> > > }
> > > if (buf_len < sumlen) {
> > > /* Need to read more so that
> > > the entire summary node is present */
> > > @@ -1035,7 +1036,7 @@ static int jffs2_scan_dirent_node(struct
> > > jffs2_sb_info *c, struct jffs2_eraseblo
> > > if (!fd) {
> > > return -ENOMEM;
> > > }
> > > - memcpy(&fd->name, rd->name, checkedlen);
> > > + memcpy_fromio(&fd->name, rd->name, checkedlen);
This patch is needed because memcpy uses unaligned accesses whereas
memcpy_fromio only uses aligned accesses on the io side. See this
thread: http://ozlabs.org/pipermail/linuxppc-embedded/2006-April/022544.html
--
Pengutronix e.K. - Linux Solutions for Science and Industry
-----------------------------------------------------------
Kontakt-Informationen finden Sie im Header dieser Mail oder
auf der Webseite -> http://www.pengutronix.de/impressum/ <-
next prev parent reply other threads:[~2008-05-06 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 13:48 [PATCH] add Phytec pcm030 board support Sascha Hauer
2008-05-05 1:16 ` David Gibson
2008-05-05 15:59 ` Grant Likely
2008-05-05 18:06 ` Segher Boessenkool
2008-05-05 19:38 ` Grant Likely
2008-05-06 4:06 ` Stephen Rothwell
2008-05-06 5:51 ` Segher Boessenkool
2008-05-06 7:20 ` Stephen Rothwell
2008-05-05 17:01 ` Jon Smirl
2008-05-05 17:08 ` Grant Likely
2008-05-05 17:22 ` Jon Smirl
2008-05-06 8:08 ` Sascha Hauer [this message]
2008-05-06 12:47 ` Jon Smirl
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=20080506080811.GB4326@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=jonsmirl@gmail.com \
--cc=linuxppc-dev@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).