From: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 2/3] arm/davinci: spl - boot device selection
Date: Tue, 10 Jul 2012 00:10:30 +0400 [thread overview]
Message-ID: <20120710001030.4a42e48b@weasel.local> (raw)
In-Reply-To: <4FFB3A27.4020700@ti.com>
On Mon, 9 Jul 2012 13:08:07 -0700
Tom Rini <trini@ti.com> wrote:
> On 07/09/2012 12:57 PM, Mikhail Kshevetskiy wrote:
> > On Mon, 9 Jul 2012 12:41:06 -0700
> > Tom Rini <trini@ti.com> wrote:
> >
> >> On 07/09/2012 11:53 AM, Mikhail Kshevetskiy wrote:
> >>> This patch allow us to have a universal spl that detects a boot
> >>> device and select a corresponding boot algorithm for main u-boot part
> >>> (SOC_DA8XX only)
> >>>
> >>> This patch create copy copy of drivers/mtd/nand/nand_spl_load.c and
> >>> drivers/mtd/spi/spi_spl_load.c for the following reasons:
> >>> * avoid jump to main u-boot code just after its loading (required
> >>> for the next patch: spl - add compressed u-boot image support)
> >>> * makes a structure similar to omap3 sources
> >>>
> >>> Signed-off-by: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
> >>
> >> I guess I wasn't clear enough when I asked the series to be split. I
> >> want to see this portion turned into:
> >> a) Move omap-common spl bits to arch/arm/lib/
> >> b) davinci converted (and as needed, omap3/4/am33xx converted) to be
> >> able to use the same code.
> >>
> >> We shouldn't introduce a new spl_mmc.c for example, we should modify the
> >> davinci structure to be able to re-use the same spl_mmc.c code to
> >> load/verify and let the next step, as needed happen. I want to see
> >> "omap" be able to re-use SPI (since am33xx can do it too, and I've
> >> kludged the davinci stuff before) and potentially be able to re-use for
> >> example the gunzip support. This I think is the easy set of steps to
> >> being able to reuse this fairly common SPL logic outside of not just TI
> >> parts but anyone else that wants it.
> >
> > Ok, I'll take this task. Unfortunately I have no too much free time for this
> > job (summer, parents visit, new job and so on), so it may take a month or
> > so.
>
> OK, thanks.
>
> > What about other patches?
>
> The ddr/uart ones should make their way in soon and I've assigned the
> SPI ones to the custodian in patchwork.
>
> --
> Tom
Thanks!
Mikhail
next prev parent reply other threads:[~2012-07-09 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 18:53 [U-Boot] [PATCH V3 1/3] MMC: u-boot-spl may be compiled without partition support Mikhail Kshevetskiy
2012-07-09 18:53 ` [U-Boot] [PATCH V3 2/3] arm/davinci: spl - boot device selection Mikhail Kshevetskiy
2012-07-09 19:41 ` Tom Rini
2012-07-09 19:57 ` Mikhail Kshevetskiy
2012-07-09 20:08 ` Tom Rini
2012-07-09 20:10 ` Mikhail Kshevetskiy [this message]
2012-07-10 18:39 ` Sughosh Ganu
2012-07-10 19:20 ` Mikhail Kshevetskiy
2012-07-11 6:38 ` Sughosh Ganu
2012-07-11 8:19 ` Tom Rini
2012-07-11 10:40 ` Sughosh Ganu
2012-07-11 10:46 ` Tom Rini
2012-07-11 11:05 ` Sughosh Ganu
2012-07-11 11:43 ` Tom Rini
2012-07-11 12:08 ` Sughosh Ganu
2012-07-11 12:15 ` Tom Rini
2012-07-09 18:53 ` [U-Boot] [PATCH V3 3/3] arm/davinci: spl - add compressed u-boot image support Mikhail Kshevetskiy
2012-07-10 18:49 ` Sughosh Ganu
2012-07-10 19:29 ` Mikhail Kshevetskiy
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=20120710001030.4a42e48b@weasel.local \
--to=mikhail.kshevetskiy@gmail.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