All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Hershberger <joe.hershberger@ni.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-Custodians] RFC: Migration target date for DM_ETH
Date: Thu, 15 Aug 2019 02:57:33 +0000	[thread overview]
Message-ID: <CANr=Z=Y+GnnzGDM-mtpo8JBMwM_oZfpg_hGNj8arZ51mZn1yEg@mail.gmail.com> (raw)
In-Reply-To: <2fe7b590-6f02-391f-eeca-67ebbb29f575@gmx.de>

Hi Heinrich,

On Fri, Aug 9, 2019 at 4:41 PM Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
> On 8/9/19 7:02 PM, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Fri, 9 Aug 2019 at 00:31, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >>
> >> Currently dozens of boards still do not use the driver model for the
> >> network devices. This makes integration between devices in the UEFI
> >> sub-system with the U-Boot devices complicated.
> >>
> >> See: https://travis-ci.org/xypron2/u-boot/builds/569675547
> >>
> >> In doc/driver-model/migration.rst I am missing a migration target day
> >> for DM_ETH. Shouldn't we define one? 2020-07 should be realistic.
> >
> > Yes, good idea.
> >
> > Also we need to convert the Ethernet PHYs to DM.
>
> In drivers/net/phy/ there isn't even a uclass. It makes sense to convert
> this class of drivers too. But I guess it can be handles as a separate task.

Yes, for sure. I think Simon is just sending a reminder to me. ;)

>
> Best regards
>
> Heinrich
> _______________________________________________
> U-Boot-Custodians mailing list
> U-Boot-Custodians at lists.denx.de
> https://lists.denx.de/listinfo/u-boot-custodians

  reply	other threads:[~2019-08-15  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  6:30 [U-Boot] RFC: Migration target date for DM_ETH Heinrich Schuchardt
2019-08-09 17:02 ` Simon Glass
2019-08-09 21:41   ` Heinrich Schuchardt
2019-08-15  2:57     ` Joe Hershberger [this message]
2020-02-26 18:58 ` [U-Boot-Custodians] " Christophe Leroy
2020-02-26 19:07   ` Heinrich Schuchardt

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='CANr=Z=Y+GnnzGDM-mtpo8JBMwM_oZfpg_hGNj8arZ51mZn1yEg@mail.gmail.com' \
    --to=joe.hershberger@ni.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 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.