public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Xpedite boards
Date: Thu, 11 May 2017 18:27:17 -0500	[thread overview]
Message-ID: <1494545237.21476.2.camel@xes-inc.com> (raw)
In-Reply-To: <CAPnjgZ2o7WC1WjYpVhMAT4o6nZWCLg6nkH38A6JGBhdQwUYSQQ@mail.gmail.com>

Hi Simon,

> 
> I am trying to help with the U-Boot conversion of CONFIG options to
> Kconfig. I notice that the Xpedite boards use a ds4510 driver which
> defines quite a few of these options. I could potentially convert it
> to Kconfig.

Thanks, and thanks for your work on U-Boot improvements in general over
the last few years!  I've been out of the development loop, but it's
neat to see the improvements you've been shepherding.

> However, many of the options in these boards define I2C addresses,
> which these days should be done with driver model / device tree.
> 
> I wonder if you have any interest in converting these boards as part
> of ongoing work?

I definitely have interest, but am iffy on the time:)  From what I
understand PowerPC has been pretty tardy on moving to the driver model
/ device tree, and no PowerPC board uses the device tree control at
this point.  To make sure I understand the end goal, you're asking
about defining CONFIG_OF_CONTROL for the XPedite boards?  This would
primarily entail getting CONFIG_OF_CONTROL working, at which point the
driver model should "just work"?  Let me know if I'm missing the high
level picture.

Regards,
Peter

  reply	other threads:[~2017-05-11 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 16:37 [U-Boot] Xpedite boards Simon Glass
2017-05-11 23:27 ` Peter Tyser [this message]
2017-05-13  1:11   ` Simon Glass

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=1494545237.21476.2.camel@xes-inc.com \
    --to=ptyser@xes-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox