From: Alexander Aring <alex.aring@gmail.com>
To: Cristiano De Alti <cristiano_dealti@hotmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: i.MX21 ADS NAND flash bad blocks scan. Barebox vs Linux
Date: Tue, 18 Mar 2014 07:22:22 +0100 [thread overview]
Message-ID: <20140318062220.GA17105@omega> (raw)
In-Reply-To: <loom.20140317T232302-965@post.gmane.org>
On Mon, Mar 17, 2014 at 10:25:59PM +0000, Cristiano De Alti wrote:
> Alexander Aring <alex.aring@...> writes:
>
> >
> > Hi,
> >
> > just an idea... don't asking about why. But can you please disable
> >
> > ARM_OPTIMZED_STRING_FUNCTIONS
> >
> > and test it again? I will check something there...
> >
> > - Alex
> >
>
> I've disabled the above CONFIG in Barebox and I don't see any difference in
> the duration of the bad blocks scan. Should it take longer?
> What was the idea here?
> Thanks for your help. I didn't imagine supporting this board was still of
> some interest for someone ;)
>
mhh then sorry, I experienced a slow imx nand some time ago, too. The
config ARM_OPTIMZED_STRING_FUNCTIONS helped to improve the speedup. Was
just a try, I never looked deeper into the issue...
The issue was a slow tftp with a 'special' host ethernet card. I never
realize what the real problem was and I don't have this hardware anymore.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-03-18 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 20:44 i.MX21 ADS NAND flash bad blocks scan. Barebox vs Linux Cristiano De Alti
2014-03-17 6:31 ` Sascha Hauer
2014-03-17 22:09 ` Cristiano De Alti
2014-03-17 6:43 ` Alexander Aring
2014-03-17 22:25 ` Cristiano De Alti
2014-03-18 6:22 ` Alexander Aring [this message]
2014-03-22 16:08 ` Cristiano De Alti
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=20140318062220.GA17105@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=cristiano_dealti@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.