public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/4] sunxi: nand: Basic NAND driver for SPL
Date: Thu, 20 Aug 2015 15:42:56 +0200	[thread overview]
Message-ID: <55D5D960.5060706@redhat.com> (raw)
In-Reply-To: <55D5CA16.8070500@denx.de>

Hi,

On 08/20/2015 02:37 PM, Stefan Roese wrote:
> Hi,
>
> I've not done sunxi development for a while. So I need to ask you guys about some details. I hope you don't mind. Please see questions below.
>
> On 06.08.2015 09:55, Piotr Zierhoffer wrote:
>>>>>> I've merged patches 1 - 3 in my sunxi-wip branch,
>>>>>> and I'll include them in the next u-boot-sunxi pull-req.
>>>>>
>>>>>
>>>>> Shouldn't we at least wait for Scoot's approval?
>>>>
>>>>
>>>> Or Scott's. :-)
>>>>
>>>> ACK
>>>
>>>
>>> Thanks.
>
> Okay, this driver SPL NAND is now integrated in mainline. Great.
>
> But how about NAND support for the main U-Boot (load Linux from NAND etc.)? It seems to be missing. Is somebody working on this?

Yes, see:

https://github.com/NextThingCo/CHIP-u-boot
https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-nand-wip

 > Whats the current status here?

We want to use the Linux kernel code for the main U-Boot, which
is not fully upstream yet (and will likely not be for a while)
as it needs per partition config (ecc / scrambler) settings, as
well as merging of scrambler support into the upstream kernel first.

We will likely have a u-boot branch with this working soon-ish,
but getting this merged is a different story.

Regards,

Hans

  reply	other threads:[~2015-08-20 13:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 12:33 [U-Boot] [PATCH v3 0/4] sunxi: nand: Basic NAND driver for SPL Piotr Zierhoffer
2015-07-23 12:33 ` [U-Boot] [PATCH v3 1/4] sunxi: nand: Add pinmux and clock settings for NAND support Piotr Zierhoffer
2015-07-23 12:33 ` [U-Boot] [PATCH v3 2/4] sunxi: nand: Add basic sunxi NAND driver for SPL with DMA support Piotr Zierhoffer
2015-07-31  0:47   ` Scott Wood
2015-07-31  8:36     ` Hans de Goede
2015-07-31  9:24       ` Boris Brezillon
2015-07-31 14:25         ` Michal Suchanek
2015-07-31 14:27           ` Hans de Goede
2015-07-31 14:41           ` Boris Brezillon
2015-07-31 15:27             ` Michal Suchanek
2015-07-31 16:57             ` Scott Wood
2015-07-23 12:33 ` [U-Boot] [PATCH v3 3/4] sunxi: nand: Add board configuration options Piotr Zierhoffer
2015-07-23 12:33 ` [U-Boot] [PATCH v3 4/4] sunxi: nand: Add information to sunxi that it was run from NAND in SPL Piotr Zierhoffer
2015-07-23 14:04 ` [U-Boot] [PATCH v3 0/4] sunxi: nand: Basic NAND driver for SPL Marek Vasut
2015-07-23 14:59   ` Piotr Zierhoffer
2015-07-23 15:57     ` Marek Vasut
2015-08-01 12:15 ` Hans de Goede
2015-08-01 12:30   ` Boris Brezillon
2015-08-01 19:22     ` Scott Wood
2015-08-02 12:56       ` Hans de Goede
2015-08-06  7:55         ` Piotr Zierhoffer
2015-08-20 12:37           ` Stefan Roese
2015-08-20 13:42             ` Hans de Goede [this message]
2015-08-20 14:49               ` Stefan Roese
2015-08-27 10:06                 ` Stefan Roese
2015-08-27 10:10                   ` Stefan Roese

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=55D5D960.5060706@redhat.com \
    --to=hdegoede@redhat.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