public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] warp: Add a README file
Date: Mon, 02 Mar 2015 08:48:34 -0700	[thread overview]
Message-ID: <54F48652.700@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5DezbqCFt6wAyV6APs6rEdeKManKUvR606s2zgH2_nmhA@mail.gmail.com>

Hi Fabio,

On 03/02/2015 08:33 AM, Fabio Estevam wrote:
> Hi Otavio,
> 
> On Mon, Mar 2, 2015 at 11:52 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
> 
>>> +Required software on the host PC:
>>> +
>>> +- imx_loader: https://github.com/warpboard/imx_usb_loader
>>
>> I see no reason to link WaRP's fork. The Boundary Devices upstream
>> code offers a more up to date bases and I think we should give them
>> the credit for the tool. Mind to change it?
> 
> No problem for me to link Boundary Device's tree, but then we would
> need to create a mx6sl_usb_work.conf in this tree, so that the
> LOADADDR could be adapted for mx6sl. Then we also need to pass
> mx6sl_usb_work.conf
> in the imx_usb command line.
> 
> Eric,
> 
> What do you think?
> 
It's probably best to use ours, but we're okay either way.

I wasn't aware that Warp had forked imx_usb_loader, but a quick
read shows that it's behind by a couple of (minor) updates.

As for the mx6sl_usb_work.conf file, we'll certainly allow
the Warp-specific version to be stored in our repository
as long as it's named for the Warp

i.e.:
	mx6sl_usb_work-warp.conf

If somebody want to push a pull request, we'll be happy
to stash it there.

Regards,


Eric

  reply	other threads:[~2015-03-02 15:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 13:20 [U-Boot] [PATCH] warp: Add a README file Fabio Estevam
2015-03-02 14:52 ` Otavio Salvador
2015-03-02 15:33   ` Fabio Estevam
2015-03-02 15:48     ` Eric Nelson [this message]
2015-03-02 15:52       ` Fabio Estevam
2015-03-02 16:00         ` Eric Nelson

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=54F48652.700@boundarydevices.com \
    --to=eric.nelson@boundarydevices.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