From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc85xx, mpc86xx: device tree model
Date: Mon, 18 Mar 2019 09:59:09 +0100 [thread overview]
Message-ID: <c1b18fdd-3d88-56ea-2cf2-537a343fab7f@denx.de> (raw)
In-Reply-To: <20190317031608.GJ8732@bill-the-cat>
Hello Tom, rabhakar,
Am 17.03.2019 um 04:16 schrieb Tom Rini:
> On Sun, Mar 17, 2019 at 03:01:32AM +0000, Prabhakar Kushwaha wrote:
>>
>>> -----Original Message-----
>>> From: Tom Rini <trini@konsulko.com>
>>> Sent: Friday, March 15, 2019 9:36 PM
>>> To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
>>> Cc: u-boot at lists.denx.de; York Sun <york.sun@nxp.com>
>>> Subject: Re: mpc85xx, mpc86xx: device tree model
>>>
>>> On Fri, Mar 15, 2019 at 05:05:06AM +0000, Prabhakar Kushwaha wrote:
>>>
>>>> Hi Tom,
>>>>
>>>> I am seeing following type of build warnings for MMC.
>>>>
>>>> +===================== WARNING ====================== This board
>>> does
>>>> +not use CONFIG_DM_MMC. Please update the board to use
>>> CONFIG_DM_MMC
>>>> +before the v2019.04 release.
>>>> +Failure to update by the deadline may result in board removal.
>>>> +See doc/driver-model/MIGRATION.txt for more info.
>>>>
>>>> Considering "number" of powerpc platform are not migrated to deice
>>>> tree. They can not be migrated to CONFIG_DM_MMC withing v2019.04
>>>> time-frame (considering rc4 is on 18th march).
>>>> v2019.07 looks feasible for removing all warning which includes
>>>> CONFIG_DM_USB, CONFIG_DM_SCSI, CONFIG_DM_PCI,
>>> CONFIG_DM_SPI_FLASH and
>>>> CONFIG_DM_MMC.
>>>>
>>>> is there any plan of removing boards which don't have CONFIG_DM_MMC
>>>> for v2019.04?
>>>
>>> Good question. Where exactly are we with getting more of PowerPC brought up
>>> to date with these requirements?
>>
>> There are only 2 platforms which are on device tree model.
>>
>> Rest (65 targets) still need to be ported. Here 13 are non-NXP and 52 NXP.
>> I am working internally to get staffed for porting of NXP platform.
>> For non-NXP , I will reaching platform owners for migration.
>>
>> It will take some time.
>
> OK.
I may get time to dig into mpc85xx based socrates board.
Anyone tried if this board works anymore?
@York: Do you work on such an adaption? May we can share efforts?
bye,
Heikp
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52 Fax: +49-8142-66989-80 Email: hs at denx.de
next prev parent reply other threads:[~2019-03-18 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 5:05 [U-Boot] mpc85xx, mpc86xx: device tree model Prabhakar Kushwaha
2019-03-15 16:06 ` Tom Rini
2019-03-17 3:01 ` Prabhakar Kushwaha
2019-03-17 3:16 ` Tom Rini
2019-03-18 8:59 ` Heiko Schocher [this message]
2019-03-18 14:56 ` York Sun
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=c1b18fdd-3d88-56ea-2cf2-537a343fab7f@denx.de \
--to=hs@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