public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: mvebu: Add SolidRun ClearFog Armada 38x initial support
Date: Mon, 14 Dec 2015 07:36:02 +0100	[thread overview]
Message-ID: <566E6352.3080600@denx.de> (raw)
In-Reply-To: <000001519d5e2119-9135a42a-f79d-4fbe-b861-6bfc8243819c-000000@email.amazonses.com>

Hi Dennis, Hi Luka,

On 13.12.2015 23:02, Luka Perkov wrote:
> On Sun, Dec 13, 2015 at 11:33:46AM -0600, Dennis Gilmore wrote:
>> Trying to test this  I have hit an error with CONFIG_PHY_ADDR not defined.
>>
>> I am guessing that I am missing some other sets of patches. digging through
>> patchwork I am not able to figure it out.  there is a bunch of patches in
>> patchwork that say they are in NEW state however they are in the tree so not
>> labeled correctly.  Any clues as to which patch sets this depends on are
>> appreciated.
>
> I've asked Stefan to put the patches up on some git repo for easier
> review and pull on my side. I'm also very eager to test this patchset!

Right. And I've not done so until now, since the basis for the SPL DM
support for MVEBU has not accepted by Simon yet. But it seems that we
may have an acceptable solution now after a longer discussion.

I have a few new patches in the queue as well and will post them
later today (or in the next days). And will also publish a git
branch with all the pending MVEBU patches. Including the ClearFog
support.

I'll keep you informed on this...

Thanks,
Stefan

      reply	other threads:[~2015-12-14  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 15:15 [U-Boot] [PATCH] arm: mvebu: Move some defines to common include file Stefan Roese
2015-11-27 15:15 ` [U-Boot] [PATCH] arm: mvebu: Add SolidRun ClearFog Armada 38x initial support Stefan Roese
2015-12-13 17:33   ` Dennis Gilmore
2015-12-13 22:02     ` Luka Perkov
2015-12-14  6:36       ` Stefan Roese [this message]

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=566E6352.3080600@denx.de \
    --to=sr@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