From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Nelson Date: Mon, 02 Mar 2015 08:48:34 -0700 Subject: [U-Boot] [PATCH] warp: Add a README file In-Reply-To: References: <1425302449-14301-1-git-send-email-fabio.estevam@freescale.com> Message-ID: <54F48652.700@boundarydevices.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 > 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