From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] IMX6 DM_USB / DM_MMC requires OF_CONTROL?
Date: Tue, 19 Feb 2019 19:32:47 +0100 [thread overview]
Message-ID: <47c1484b-ab2c-da0d-d3f3-dbf1c81a4294@denx.de> (raw)
In-Reply-To: <CAJ+vNU3yD_YD=CQ=orYS5vfPMzcqRLygqeDRAY9nvYi=1qi3VA@mail.gmail.com>
Hi Tim,
On 19/02/19 19:24, Tim Harvey wrote:
> Greetings,
>
> I'm seeing that I need to switch my IMX6 board support
> (board/gateworks/gw_ventana) over to DM_USB and DM_MMC right away
> (v2019.04) and I notice enabling those fails building as it looks like
> these DM drivers expect OF_CONTROL (U-Boot running from a
> device-tree).
> Is that currently true or am I perhaps missing
> something?
You are completely correct : moving to DM requires to set a DT for the
board.
> I haven't pinned down what exactly is missing yet so I
> thought I would ask. It looks like only a couple of IMX6 boards have
> been converted over thus far.
Yes, that is true.
>
> What is the IMX6 status of DM_SCSI/DM_PCI/DM_VIDEO which are required
> by v2019.07?
>
> Best Regards,
>
Stefano
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2019-02-19 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 18:24 [U-Boot] IMX6 DM_USB / DM_MMC requires OF_CONTROL? Tim Harvey
2019-02-19 18:32 ` Stefano Babic [this message]
2019-02-21 14:48 ` Marcel Ziswiler
2019-02-22 17:14 ` Tim Harvey
2019-02-28 22:44 ` Lukasz Majewski
2019-02-19 18:37 ` Fabio Estevam
2019-02-19 19:11 ` Tim Harvey
2019-02-19 21:58 ` Adam Ford
2019-02-21 0:00 ` Fabio Estevam
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=47c1484b-ab2c-da0d-d3f3-dbf1c81a4294@denx.de \
--to=sbabic@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