From: Tom Rini <trini@konsulko.com>
To: Oleksandr G Zhadan <oleks@arcturusnetworks.com>
Cc: sjg@chromium.org, u-boot-request@lists.denx.de,
u-boot@lists.denx.de,
"arcsupport@ArcturusNetworks.com"
<arcsupport@ArcturusNetworks.com>
Subject: Re: U-Boot Digest, Vol 158, Issue 63
Date: Wed, 28 Jul 2021 12:43:05 -0400 [thread overview]
Message-ID: <20210728164305.GP9379@bill-the-cat> (raw)
In-Reply-To: <0735982b-277d-9f3d-3ed3-5fc0368c2cac@arcturusnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 4289 bytes --]
On Wed, Jul 28, 2021 at 12:22:57PM -0400, Oleksandr G Zhadan wrote:
> Hello,
>
> Please see inline.
>
> On 7/26/21 9:40 AM, u-boot-request@lists.denx.de wrote:
> > Message: 13
> > Date: Mon, 26 Jul 2021 07:34:06 -0600
> > From: Simon Glass<sjg@chromium.org>
> > To: U-Boot Mailing List<u-boot@lists.denx.de>
> > Cc: Tom Rini<trini@konsulko.com>, Simon Glass<sjg@chromium.org>,
> > Albert Aribaud<albert.u.boot@aribaud.net>, Andy Fleming
> > <afleming@gmail.com>, Joe Hershberger<joe.hershberger@ni.com>, Marek
> > Vasut<marex@denx.de>, Mario Six<mario.six@gdsys.cc>, Oleksandr
> > Zhadan and Michael Durrant<arcsupport@arcturusnetworks.com>, Pavel
> > Herrmann<morpheus.ibis@gmail.com>, Priyanka Jain
> > <priyanka.jain@nxp.com>, Rob Herring<rob.herring@calxeda.com>, Stefan
> > Roese<sr@denx.de>, Stefano Babic<sbabic@denx.de>, Wolfgang Denk
> > <wd@denx.de>
> > Subject: [PATCH 00/33] pci: Drop all pre-driver model code
> > Message-ID:<20210726133440.634682-1-sjg@chromium.org>
> >
> > The hard work to actually enable DM_PCI everywhere was done recently. This
> > series attempts to drop most of the code that it no-longer needed now that
> > PCI has been converted to driver model.
>
> > It also drops the UCP1020 board since it has various unique build issues.
>
> What issues are we talking about?Please name it.
>
> Today's u-boot clone builds and runs fine in our module without any warnings
> except:
>
> > git clone https://source.denx.de/u-boot/u-boot.git u-boot-20210728
>
> > cd u-boot-20210728
>
> > make UCP1020_defconfig
>
> > CROSS_COMPILE=powerpc-linux- make 2>222
>
> > cat 222
> ===================== WARNING ======================
> This board does not use CONFIG_DM. CONFIG_DM will be
> compulsory starting with the v2020.01 release.
> Failure to update may result in board removal.
> See doc/driver-model/migration.rst for more info.
> ====================================================
> ===================== WARNING ======================
> This board does not use CONFIG_DM_ETH (Driver Model
> for Ethernet drivers). Please update the board to use
> CONFIG_DM_ETH before the v2020.07 release. Failure to
> update by the deadline may result in board removal.
> See doc/driver-model/migration.rst for more info.
> ===================================================
>
> > It doesn't even support driver model so it seems reasonable to just remove
> > it.
> 1. Sure it's my fault that I didn't notice the warnings that CONFIG_DM is
> the only choice to build and run u-boot.
>
> 2. Why is CONFIG_DM still present in `make menuconfig` options?
>
> 3. We only use u-boot as the first stage bootloader to start the kernel. We
> need minimal device controllers support. We don't need anything like PCI,
> USB, etc.
>
> 4. At least you need to add doc/driver-model/migration.rst to the source
> tree from https://source.denx.de/u-boot/u-boot.git if you point to it in
> your warnings.
>
> And
>
> 5. I have seen NO reason to remove ANY support board without REAL reasons to
> do so.
So, unfortunately this was the only board that was not triggering the
PCI migration warning as well because of how it was using the legacy PCI
subsystem. For today, if you want to continue to be in mainline, just
removing the PCI and other options that you don't use, and submitting
that patch is sufficient.
> SUMMARY:
>
> 1. UCP1020_defconfig does not have any compiler warnings on build (at least
> 2021.07.28 clone).
>
> 2. If now the only choice is CONFIG_DM, then it should be removed as an
> option from "make menuconfig", and we will definitely fix the related
> warnings/errors.
>
> 3. IMPO board support can be removed if it breaks when built and/or breaks
> any other builds.
Note that CONFIG_DM is still an option because it won't be until after
the v2022.01 window (when that migration warning you noted above) will
have been present for about 3 years. It's still an option as we're down
to 15 boards (UCP included) that need migration still. Having just
counted that, I'm quite likely to fire off a separate email now and see
if there's interest in these boards being updated or not, now that we're
down to so few boards.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-07-28 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1076.1627306815.660.u-boot@lists.denx.de>
2021-07-28 16:22 ` U-Boot Digest, Vol 158, Issue 63 Oleksandr G Zhadan
2021-07-28 16:43 ` Tom Rini [this message]
2021-08-03 13:21 ` Oleksandr G Zhadan
2021-08-05 20:31 ` Tom Rini
2021-09-08 14:25 ` 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=20210728164305.GP9379@bill-the-cat \
--to=trini@konsulko.com \
--cc=arcsupport@ArcturusNetworks.com \
--cc=oleks@arcturusnetworks.com \
--cc=sjg@chromium.org \
--cc=u-boot-request@lists.denx.de \
--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