public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Siarhei Siamashka <siarhei.siamashka@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-sunxi.git/master
Date: Fri, 18 Jul 2014 22:45:23 +0300	[thread overview]
Message-ID: <20140718224523.599252a4@i7> (raw)
In-Reply-To: <1405710851.26270.12.camel@hastur.hellion.org.uk>

On Fri, 18 Jul 2014 20:14:11 +0100
Ian Campbell <ijc@hellion.org.uk> wrote:

> Hi Albert,
> 
> Welcome back!
> 
> The following changes since commit 23f23f23d509e8e873797884456070c8a47d72b2:
> 
>   socfpga: Relocate arch common functions away from board (2014-07-05 10:14:46 +0200)
> 
> are available in the git repository at:
> 
>   git://git.denx.de/u-boot-sunxi.git master
> 
> for you to fetch changes up to 7c48b015100eeff0e1bbb766394f7beca23afb48:
> 
>   sunxi: use setbits_le32 to enable the DMA clock (2014-07-18 19:42:25 +0100)
> 
> ----------------------------------------------------------------
> Chen-Yu Tsai (1):
>       sunxi: Add support for using MII phy-s with the GMAC nic
> 
> Hans de Goede (12):
>       sunxi: mksunxiboot: Fix loading of files with a size which is not a multiple of 4
>       sunxi: Fix u-boot-spl.lds to refer to .vectors
>       sunxi: Remove mmc DMA support
>       sunxi: Implement reset_cpu
>       sunxi: Add sun4i support
>       sunxi: Add sun5i support

Can we avoid pushing the sun4i and sun5i patches? They cause clean
sunxi dram code rework more difficult.

Just to give an example. Here is what we have now in u-boot for the
sunxi dram code (a very schematic example):

    #ifdef SUN7I
      do_thing_a
      do_thing_b
    #endif
      do_thing_c

Here is what is done by the patches from Hans:

    #ifdef SUN4I
      do_thing_b
      do_thing_a
    #endif
    #if defined(SUN5I) || defined(SUN7I)
      do_thing_a
      do_thing_b
    #endif
      do_thing_c

And here is what we actually want in the end to support all these SoC
variants (with some tweaks and bugfixes for each of these steps):

      do_thing_a
      do_thing_b
      do_thing_c

The reordering of the 'do_thing_a' and 'do_thing_b' operations is
superfluous. And the fugly resulting ifdef hell does not look like a
great improvement, even though the code kinda does the job.

Basically, if these patches are pushed, we have a bigger mess to clean
compared to what we have now. Also if we have a messy support for sun4,
sun5i and sun7i added first, then any future dram code rework needs to
keep the dram functional on all of these SoC variant after every patch.
This is rather inconvenient.

That's why I'm trying to first focus on the sun7i support alone
with the patches:
    http://lists.denx.de/pipermail/u-boot/2014-July/183981.html
And add the support for the other SoC variants only after the initial
sun7i cleanup is done.

Is anyone really in a hurry to get this stuff pushed out of the
u-boot-sunxi tree to upstream right now? Can't we get a 'testing'
branch in the sunxi repository and have everything reviewed first?

-- 
Best regards,
Siarhei Siamashka

  reply	other threads:[~2014-07-18 19:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 19:14 [U-Boot] Please pull u-boot-sunxi.git/master Ian Campbell
2014-07-18 19:45 ` Siarhei Siamashka [this message]
2014-07-18 20:05   ` Ian Campbell
2014-07-28  8:53 ` Albert ARIBAUD
  -- strict thread matches above, loose matches on Subject: below --
2014-07-30  8:37 Hans de Goede
2014-07-31  4:30 ` Masahiro Yamada
2014-07-31  7:54   ` Ian Campbell
2014-07-31  8:09     ` Hans de Goede
2014-07-31  8:23     ` Masahiro Yamada
2014-07-31 14:25       ` Hans de Goede
2014-07-31 14:30 Hans de Goede
2014-08-01  1:54 ` Masahiro Yamada
2014-08-09 13:41   ` Albert ARIBAUD
2014-08-09 16:42 ` Albert ARIBAUD
2014-08-12  8:36 Hans de Goede
2014-08-29 17:48 ` Tom Rini
2014-08-28 21:17 Hans de Goede
2014-09-05 13:23 Ian Campbell
2014-09-09  7:58 ` Albert ARIBAUD
2014-09-09  8:27   ` Ian Campbell

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=20140718224523.599252a4@i7 \
    --to=siarhei.siamashka@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