mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Raphaël Poggi" <poggi.raph@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: at91: device tree
Date: Mon, 28 Jul 2014 14:37:48 +0200	[thread overview]
Message-ID: <20140728123748.GB23235@pengutronix.de> (raw)
In-Reply-To: <CACqcpZDdPLs3LRpg7X9u2E_z+824+vDC=c9vS6NRundiJUmTOA@mail.gmail.com>

Hi Raphaël,

On Sun, Jul 27, 2014 at 12:18:07PM +0200, Raphaël Poggi wrote:
> Hi all !
> 
> In barebox, atmel AT91 boards don't have device tree support(neither
> atmel drivers like: atmel_nand).
> I am currently working on adding device tree support especially on
> at91sam9m10g45ek board (the only atmel board, I have for testing) and
> corresponding drivers (i2c, nand, spi, etc...).
> 
> I wonder if barebox community is interested to add device tree support
> for atmel or if there is already somebody who works on it.

I'm not aware of anyone working on device tree support for AT91.
Jean-Christophe sometimes mentioned that this is on his todo list, but
AFAIK he hasn't started yet.

Having device tree support for AT91 would be great, this would open the
door for quite some cleanups in the AT91 port.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2014-07-28 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 10:18 Raphaël Poggi
2014-07-28 12:37 ` Sascha Hauer [this message]

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=20140728123748.GB23235@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=poggi.raph@gmail.com \
    /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