From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: Enabling mtd partitioning layout
Date: Tue, 22 Dec 2015 21:10:31 +0100 [thread overview]
Message-ID: <201512222110.31183.marex@denx.de> (raw)
In-Reply-To: <1450800042.1957.2.camel@altera.com>
On Tuesday, December 22, 2015 at 05:00:42 PM, Chin Liang See wrote:
> On Tue, 2015-12-22 at 16:53 +0100, Marek Vasut wrote:
> > On Tuesday, December 22, 2015 at 04:49:54 PM, Chin Liang See wrote:
> > > On Fri, 2015-12-18 at 14:10 +0100, Marek Vasut wrote:
> > > > On Friday, December 18, 2015 at 10:39:12 AM, Chin Liang See
> > >
> > > > wrote:
> > > [..]
> > >
> > > > > > I will send that patch out shortly, but I think there is
> > > > > > something
> > > > > > else
> > > > > > going on. I am starting to suspect something with the L3
> > > > > > interconnect.
> > > > > > Maybe some R/W reordering or something like that in NIC301 .
> > > > > >
> > > > > > Are you able to replicate my USB issue with mainline on
> > > > > > socfpga ?
> > > > > > What
> > > > > > happens if you run usb reset with a USB stick plugged in?
> > > > > > What
> > > > > > compiler
> > > > > > version do you use ?
> > > > >
> > > > > I tried that few weeks back and it works for me. FYI, I am
> > > > > using
> > > > > the
> > > > > mentor toolchain "arm-altera-eabi" that come with SOCEDS. Maybe
> > > > > I
> > > > > can
> > > > > try again with your toolchain.
> > > >
> > > > I am using the unreleased ELDK 5.8 (gcc 4.9.2) and debian gcc
> > > > 5.2.
> > > > Which gcc version is in the mentor toolchain?
> > >
> > > Mine is Sourcery CodeBench Lite 2015.05-11 (gcc 4.9.2 also)
> > >
> > > > Can you try it again with u-boot/master ? I'd be interested in
> > > > your
> > > > results.
> > > > Can you share the entire output of the U-Boot and run 'dcache'
> > > > command before
> > > > doing 'usb reset' ? I am seeing this issue with Sandisk Cruzer
> > > > USB
> > > > 2.0 sticks
> > > > now too.
> > >
> > > I can do that but git clone will take some time
> >
> > You can use git fetch in your current repo.
> >
> > I started wondering how you're testing the CV SoCDK, since I
> > discovered just
> > this morning that it doesn't even boot (I already sent patches to fix
> > that).
>
> I presume you are referring to SPL? FYI, I am still using the SPL from
> SOCEDS while using latest U-Boot from mainstream. That's why I didn't
> the issue noticed by Shengjiang and you.
Well, at least you're honest ... but *sigh*, it'd be nice if you tested
mainline only, really.
> But will make the switch soon once done with few in progress patches
> for U-Boot.
I will collect the remaining patches today and see how socdk fares.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-12-22 20:10 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
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 [this message]
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=201512222110.31183.marex@denx.de \
--to=marex@denx.de \
--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