From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Fix QSPI doesn't work on socdk board
Date: Mon, 21 Dec 2015 11:41:24 +0100 [thread overview]
Message-ID: <20151221104124.GC18741@amd> (raw)
In-Reply-To: <201512211112.29190.marex@denx.de>
On Mon 2015-12-21 11:12:29, Marek Vasut wrote:
> On Monday, December 21, 2015 at 10:37:23 AM, Pavel Machek wrote:
> > On Mon 2015-12-21 07:33:34, ?? ? wrote:
> > > Hi Marek Vasut,
> > >
> > >
> > > On Dec 18, 2015, at 04:50 AM, Marek Vasut <marex@denx.de> wrote:
> > >
> > > On Friday, December 18, 2015 at 08:57:22 AM, ?? ? wrote:
> > > Hi Chin,
> > >
> > > The PLL settings are copied from previous version
> > > http://git.rocketboards.org/u-boot-socfpga.git,
> > >
> > > This stuff should be generated by quartus, so why are you copying it from
> > > some random version of u-boot somewhere ?
> > >
> > > Thank you for your comment, if this configuration
> > > is automatically generated by Quartus without manually modification,
> > > then I would like to withdraw this patch.
> >
> > No, please don't. socdk should work out of the box.
>
> SoCDK works out of the box last time I checked (2016.01rc1), did you test it
> recently and do you observe problems ?
Did you test QSPI? Because that is what subject claims does not work.
> > I should not need
> > quartus to build a working u-boot spl for the board.
>
> You DO need quartus to generate the header files (that go into board/nnn/qts)
> to build working U-Boot SPL for any board. I fail to understand your comment,
> sorry.
Ok, lets talk about this personally or over phone.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-12-21 10:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 7:33 [U-Boot] [PATCH] arm: socfpga: Fix QSPI doesn't work on socdk board 圣江 吴
2015-12-21 9:37 ` Pavel Machek
2015-12-21 9:56 ` Chin Liang See
2015-12-21 10:12 ` Marek Vasut
2015-12-21 10:12 ` Marek Vasut
2015-12-21 10:41 ` Pavel Machek [this message]
2015-12-21 14:49 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2015-12-23 2:26 圣江 吴
2015-12-23 2:27 ` Marek Vasut
2015-12-23 2:29 ` Chin Liang See
2015-12-23 2:38 ` Chin Liang See
2015-12-23 3:04 ` Marek Vasut
[not found] <18c117d0-3bdb-4cf8-972a-35711ec3eacf@me.com>
2015-12-23 1:26 ` Marek Vasut
2015-12-23 1:22 圣江 吴
2015-12-23 1:24 ` Marek Vasut
2015-12-23 2:02 ` ShengjiangWu
2015-12-23 2:07 ` Marek Vasut
2015-12-23 2:27 ` Chin Liang See
2015-12-22 9:18 shengjiangwu
2015-12-22 9:36 ` Chin Liang See
2015-12-22 20:19 ` Marek Vasut
2015-12-22 20:33 ` Marek Vasut
2015-12-18 7:57 圣江 吴
2015-12-18 12:37 ` Marek Vasut
2015-12-18 7:21 shengjiangwu
2015-12-18 7:44 ` 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=20151221104124.GC18741@amd \
--to=pavel@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