public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot 2017.07 not working on Raspberry Pi
Date: Thu, 3 Aug 2017 13:42:49 -0400	[thread overview]
Message-ID: <20170803174249.GI29197@bill-the-cat> (raw)
In-Reply-To: <f2b07d26-3dba-baf5-b02b-9f0731792e4d@wwwdotorg.org>

On Thu, Aug 03, 2017 at 09:42:13AM -0600, Stephen Warren wrote:
> On 08/03/2017 07:45 AM, Simon Glass wrote:
> ...
> >I'm not sure if we have a Raspberry Pi in a test farm anywhere. I
> >should be able to look next week if no one can figure these out
> >beforehand.
> 
> I thought that Tom had some Pis in his test farm?

I have an RPi 3, but we don't have Linux boot tests atm.  I'm talking
with Kevin Hilman about how I might setup kernelci to test a few things
in my lab, which might catch this kind of problem sooner rather than
later.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170803/1f379654/attachment.sig>

  reply	other threads:[~2017-08-03 17:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 12:13 [U-Boot] U-boot 2017.07 not working on Raspberry Pi Paul Barker
2017-08-03  9:02 ` Jonathan Gray
2017-08-03  9:37   ` Mark Kettenis
2017-08-03 13:45     ` Simon Glass
2017-08-03 15:42       ` Stephen Warren
2017-08-03 17:42         ` Tom Rini [this message]
2017-08-21  2:59           ` Simon Glass
2017-08-25  1:46             ` Simon Glass
2017-08-25  9:46               ` Paul Barker
2017-08-25 12:25                 ` Jonathan Gray
2017-08-25 16:01                 ` Stephen Warren
2017-08-21  5:06           ` Heiko Schocher
2017-08-04 12:58       ` Paul Barker
2017-08-04 13:18         ` Mark Kettenis

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=20170803174249.GI29197@bill-the-cat \
    --to=trini@konsulko.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