From: "Simone" <cjb.sw.nospam@gmail.com>
To: "'Daiane Angolini'" <daiane.list@gmail.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: Imx53 sd card read write timing
Date: Thu, 31 Oct 2013 16:20:21 +0100 [thread overview]
Message-ID: <013001ced64c$b846a860$28d3f920$@gmail.com> (raw)
In-Reply-To: <CA+jg_OUnOKGQV5e=3jk1hUMrfyWgnqa4b2Y1hM48A9BKDZ79zQ@mail.gmail.com>
Hello Daiane,
you are my lifeline...
My kernel is the linux-fsl (linux-2.6.35.3) with some changes made for
configure the GPIOs and UARTs in our board (in mx53_loco.c)
The bootloader I'm using is U-Boot 2013.10-rc3
Really I don’t know if the L2 cache is enabled or not.
How I can check this?
Regards
Simone
-----Messaggio originale-----
Da: Daiane Angolini [mailto:daiane.list@gmail.com]
Inviato: giovedì 31 ottobre 2013 15:40
A: Simone
Cc: meta-freescale@yoctoproject.org
Oggetto: Re: [meta-freescale] R: Imx53 sd card read write timing
On Thu, Oct 31, 2013 at 12:35 PM, Simone <cjb.sw.nospam@gmail.com> wrote:
> Nobody can help me?
>
I don´t know your kernel. And I´m not sure which u-boot you´re using.
It may be anything!
But, the only thing that came to my mind is L2 cache enabled or not.
Do you know if you have enabled L2 cache?
Daiane
> Simone
>
>
> -----Messaggio originale-----
> Da: Simone [mailto:cjb.sw.nospam@gmail.com]
> Inviato: mercoledì 30 ottobre 2013 20:22
> A: <meta-freescale@yoctoproject.org>
> Oggetto: Imx53 sd card read write timing
>
> Dear all,
> I've finished today to port our changes from the old FSL kernel we
> used
> (2011 version, v11.05) for our board based on imx53qsb.
>
> Everything is working fine now, using the FSL kernel from Master
> branch, except one thing.
> Compared to the previous (very old) version of the kernel, we noted
> that the uSD card read/write timings are a lot more slower than before
> (also the system kernel loading, seems two times than before)
>
> Now i really don't know where to point my finger first.
> Maybe something inserted in the sdhc driver? Or the journaled filesystem?
>
> Really i don't know.
>
> Does someone have faced a similar problem in the past?
>
> Thank you so much
> My best regards
> Simone
>
>
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
next prev parent reply other threads:[~2013-10-31 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 19:21 Imx53 sd card read write timing Simone
2013-10-31 14:35 ` Simone
2013-10-31 14:40 ` Daiane Angolini
2013-10-31 15:20 ` Simone [this message]
2013-10-31 16:11 ` Daiane Angolini
2013-10-31 16:21 ` Otavio Salvador
2013-10-31 16:35 ` Daiane Angolini
2013-10-31 16:37 ` Otavio Salvador
2013-10-31 16:49 ` Fabio Estevam
2013-10-31 16:56 ` Otavio Salvador
2013-10-31 16:57 ` Simone
2013-10-31 17:13 ` Simone
2013-10-31 17:18 ` Otavio Salvador
2013-10-31 18:08 ` Simone
2013-10-31 18:09 ` Otavio Salvador
2013-10-31 18:14 ` Fabio Estevam
2013-11-01 13:05 ` Daiane Angolini
2013-11-01 12:58 ` Simone
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='013001ced64c$b846a860$28d3f920$@gmail.com' \
--to=cjb.sw.nospam@gmail.com \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.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 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.