From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: Enabling mtd partitioning layout
Date: Tue, 15 Dec 2015 18:09:59 +0800 [thread overview]
Message-ID: <1450174199.2080.11.camel@altera.com> (raw)
In-Reply-To: <201512150215.00367.marex@denx.de>
On Tue, 2015-12-15 at 02:15 +0100, Marek Vasut wrote:
> On Tuesday, December 15, 2015 at 02:09:42 AM, Chin Liang See wrote:
> > On Tue, 2015-12-15 at 01:32 +0100, Marek Vasut wrote:
> > > On Monday, December 14, 2015 at 04:22:57 PM, Chin Liang See
> > > wrote:
> > > > On Mon, 2015-12-14 at 02:25 +0100, Marek Vasut wrote:
> > > > > On Monday, December 14, 2015 at 02:22:32 AM, Chin Liang See
> >
> > > > > wrote:
> > [...]
> >
> > > > Yeah, I can successfully mounted with ubifs :)
> > > >
> > > > Just that I still have the issue with U-Boot ubifsmount
> > > > although I
> > > > already applied the patch for cache ARMV7. I will take a look
> > > > into
> > > > ubi
> > > > code as I suspect its due to eraseblock size issue.
> > >
> > > Keep looking, good luck.
> >
> > Yup, will compare the UBI code with the Linux one.
> >
Yeah, I managed to get ubiufsmount work in U-Boot now. Need to disable
the 4K_SECTORS when enabling UBI at NOR flash.
> > > The armv7 cache issue is more serious than I thought, I am
> > > starting
> > > to suspect
> > > there is some problem with the L3 interconnect, but I cannot put
> > > my
> > > finger on
> > > it yet.
> >
> > Hmmm... I can try to help.
> >
> > FYI, I was trying to understand how the code error in cache-cp15
> > will
> > cause the misbehave. One thing I am suspecting it might due to
> > mismatch
> > of cache policy for the memory that store the page table and
> > translation page walk mechanism. But with your fix, it should be
> > good
> > as they are matching now.
>
> I would suggest to move this to the thread below the CPU_V7 patch.
Would you able to include me to the thread? Thanks in advance!
>
> btw. the L2 cache is not enabled on SoCFPGA at all :-( I have a patch
> to fix
> it, but this doesn't help us.
Hmmm... I saw the PL310 is defined. I might want to look further.
> I suspect there might be some synchronisation
> or timing issue with accesses through the L3 interconnect, which
> would point
> to NIC301 misconfiguration, but that's purely hypothetical.Do you
> have some
> hardware-level or RTL-level/simulation tool to debug such issues at
> Altera ?
I hardly use simulation except for in house pre-silicon validation. But
I use DS-5 a lot to troubleshoot an issue (by probing various registers
including cp15).
Thanks
Chin Liang
>
> Best regards,
> Marek Vasut
next prev parent reply other threads:[~2015-12-15 10:09 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 9:15 [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: Enabling mtd partitioning layout Chin Liang See
2015-12-11 9:15 ` [U-Boot] [PATCH 2/6] arm: socfpga: arria5-socdk: " Chin Liang See
2015-12-11 9:15 ` [U-Boot] [PATCH 3/6] arm: socfpga: de0-nano-soc: " Chin Liang See
2015-12-11 14:21 ` Marek Vasut
2015-12-11 15:43 ` Dinh Nguyen
2015-12-11 17:36 ` Marek Vasut
2015-12-12 0:01 ` Chin Liang See
2015-12-12 21:10 ` Pavel Machek
2015-12-12 21:45 ` Marek Vasut
2015-12-13 0:01 ` Chin Liang See
2015-12-13 0:04 ` Chin Liang See
2015-12-11 9:15 ` [U-Boot] [PATCH 4/6] arm: socfpga: mcvevk: " Chin Liang See
2015-12-11 14:21 ` Marek Vasut
2015-12-11 9:15 ` [U-Boot] [PATCH 5/6] arm: socfpga: sockit: " Chin Liang See
2015-12-11 14:23 ` Marek Vasut
2015-12-11 9:15 ` [U-Boot] [PATCH 6/6] arm: socfpga: socrates: " Chin Liang See
2015-12-11 14:23 ` Marek Vasut
2015-12-11 14:21 ` [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: " Marek Vasut
2015-12-11 23:59 ` Chin Liang See
2015-12-12 3:20 ` Marek Vasut
2015-12-12 6:30 ` Chin Liang See
2015-12-12 15:36 ` Marek Vasut
2015-12-12 23:59 ` Chin Liang See
2015-12-13 0:01 ` Marek Vasut
2015-12-13 0:49 ` Chin Liang See
2015-12-13 3:14 ` Marek Vasut
2015-12-13 13:03 ` Chin Liang See
2015-12-13 15:42 ` Marek Vasut
2015-12-14 0:11 ` Chin Liang See
2015-12-14 0:22 ` Marek Vasut
2015-12-14 0:43 ` Chin Liang See
2015-12-14 0:58 ` Marek Vasut
2015-12-14 1:22 ` Chin Liang See
2015-12-14 1:25 ` Marek Vasut
2015-12-14 15:22 ` Chin Liang See
2015-12-15 0:32 ` Marek Vasut
2015-12-15 1:09 ` Chin Liang See
2015-12-15 1:15 ` Marek Vasut
2015-12-15 10:09 ` Chin Liang See [this message]
2015-12-15 18:16 ` Marek Vasut
2015-12-18 9:39 ` Chin Liang See
2015-12-18 13:10 ` Marek Vasut
2015-12-22 15:49 ` Chin Liang See
2015-12-22 15:53 ` Marek Vasut
2015-12-22 16:00 ` Chin Liang See
2015-12-22 20:10 ` Marek Vasut
2015-12-23 0:24 ` Chin Liang See
2015-12-23 0:48 ` Marek Vasut
2015-12-23 1:38 ` Chin Liang See
2015-12-23 19:02 ` Pavel Machek
2015-12-23 22:57 ` Chin Liang See
2015-12-23 23:16 ` Marek Vasut
2015-12-23 23:36 ` Chin Liang See
2015-12-24 1:30 ` Marek Vasut
2015-12-28 8:51 ` Chin Liang See
2015-12-28 12:39 ` Marek Vasut
2015-12-29 21:06 ` Chin Liang See
2015-12-29 21:20 ` Marek Vasut
2015-12-23 23:18 ` Marek Vasut
2015-12-14 7:54 ` Pavel Machek
2015-12-14 11:09 ` Marek Vasut
2015-12-14 11:26 ` Pavel Machek
2015-12-14 11:31 ` Marek Vasut
2015-12-14 11:51 ` Pavel Machek
2015-12-14 12:20 ` Marek Vasut
2015-12-14 12:53 ` Pavel Machek
2015-12-14 13:34 ` Marek Vasut
2015-12-14 15:31 ` Chin Liang See
2015-12-13 0:49 ` Chin Liang See
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=1450174199.2080.11.camel@altera.com \
--to=clsee@altera.com \
--cc=u-boot@lists.denx.de \
/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