All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/11] dm: Removal of some boards due to DM_MMC deadline
Date: Sun, 12 May 2019 14:08:14 -0600	[thread overview]
Message-ID: <CAPnjgZ3JNdc_2QcrNw0wPm4P+eCofP95wv22v-LB6vwU-dYSkw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ0e3XFQBFkeFgbWJqqjTTiKq62uO9jtwbis8Hhs=Q+W+Q@mail.gmail.com>

Hi Tom,

On Sun, 12 May 2019 at 13:03, Simon Glass <sjg@chromium.org> wrote:
>
> Hi Tom,
>
> On Sat, 11 May 2019 at 13:36, Tom Rini <trini@konsulko.com> wrote:
> >
> > + Peng, the new MMC maintainer
> >
> > On Sat, May 11, 2019 at 01:23:45PM -0600, Simon Glass wrote:
> >
> > > This series starts the process of removing boards which have not been
> > > converted to driver model for MMC.
> >
> > I'm sorry, no.  Like I've been saying in the SPI thread, and I thought I
> > had made clear elsewhere:
> > - This release we move the drivers to depend on BROKEN.  Jagan has a
> >   patch right now that makes BROKEN make another warning happen, but I'm
> >   not 100% sure I like this, but also haven't had a chance to try my
> >   idea of just removing the driver from the build and seeing if the
> >   boards link, or how hard making them link again is.
> > - Next release we can remove the _drivers_ that depend on BROKEN.
>
> Sorry I must have missed this, have had very little time in the past
> few months. I did see mention of BROKEN elsewhere but had somehow not
> made the connection.
>
> Could we get a note added to MIGRATION.txt perhaps?
>
> >
> > Yes, this will result in a bunch of boards that aren't nearly so
> > functional as they would be expected to be.  This in turn might lead to:
> > - Someone stepping up as they care about the hardware
> > - Removing of the boards down the line when it's clear no one has been
> >   using them as there's a big window where generally key drivers aren't
> >   there anymore.
>
> Sounds like a great plan, and much better and easier than removal
> (which is a real pain to create patches for).

I've hit a snag though. s32v234evb doesn't even support
CONFIG_OF_CONTROL. What should we do in that case?

Regards,
Simon

  reply	other threads:[~2019-05-12 20:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-11 19:23 [U-Boot] [PATCH 00/11] dm: Removal of some boards due to DM_MMC deadline Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 01/11] patman: Update cros_subprocess to use bytearray Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 02/11] Add a simple script to remove boards Simon Glass
2019-05-11 19:44   ` Tom Rini
2019-05-12 19:03     ` Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 03/11] solidrun: Fix soldrun typo Simon Glass
2019-05-12 10:00   ` Stefan Roese
2019-05-11 19:23 ` [U-Boot] [PATCH 04/11] atmel: gurnard: Complete DM migration Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 05/11] bubblegum_96: " Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 06/11] arm: Remove s32v234evb board Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 07/11] arm: Remove ls1088ardb_sdcard_qspi_SECURE_BOOT board Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 08/11] arm: Remove ls1046ardb_sdcard_SECURE_BOOT board Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 09/11] arm: Remove ls1043ardb_sdcard_SECURE_BOOT board Simon Glass
2019-05-11 19:23 ` [U-Boot] [PATCH 10/11] evb-ast2500: Enable CONFIG_DM_MMC Simon Glass
2019-05-13 16:39   ` Maxim Sloyko
2019-05-11 19:23 ` [U-Boot] [PATCH 11/11] vf610twr/_nand: " Simon Glass
2019-05-11 19:36 ` [U-Boot] [PATCH 00/11] dm: Removal of some boards due to DM_MMC deadline Tom Rini
2019-05-12 19:03   ` Simon Glass
2019-05-12 20:08     ` Simon Glass [this message]
2019-05-14 14:08       ` Tom Rini
2019-05-14 14:11     ` Tom Rini

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=CAPnjgZ3JNdc_2QcrNw0wPm4P+eCofP95wv22v-LB6vwU-dYSkw@mail.gmail.com \
    --to=sjg@chromium.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.