From: camhirundo@gmail.com (Hirundo Cam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kirkwood: add dir-665 support
Date: Thu, 5 May 2011 08:23:34 +0800 [thread overview]
Message-ID: <BANLkTikNhcEWUYnBdajyVa6tMGRM=7QPRQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105040940410.24613@xanadu.home>
Hi Nicolas,
> I think that Kirkwood is actually a good case for device tree as the
> differences between boards is really simple as it usually boils down to
> different GPIO usage and MPP assignments. ?If someone would like to
> contribute to the DT effort on ARM then this would be a nice and easy
> target to convert over.
>
Do you have any idea of how the device tree should be implemented?
For example, how the data structure and probing process should be used?
Is there any discussing thread related to this topic?
Thanks
Regards,
Hirundo Cam
next prev parent reply other threads:[~2011-05-05 0:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 16:34 [PATCH] kirkwood: add dir-665 support Hirundo Cam
2011-04-27 23:52 ` Hirundo Cam
2011-05-03 15:55 ` Hirundo Cam
2011-05-03 20:51 ` mike at compulab.co.il
2011-05-04 2:36 ` Hirundo Cam
2011-05-04 2:54 ` Hirundo Cam
2011-05-04 3:00 ` Hirundo Cam
2011-05-04 6:32 ` Mike Rapoport
2011-05-04 8:09 ` Simon Guinot
2011-05-04 13:51 ` Nicolas Pitre
2011-05-05 0:23 ` Hirundo Cam [this message]
2011-05-05 15:06 ` Simon Guinot
2011-05-05 19:55 ` Nicolas Pitre
2011-05-06 15:41 ` Simon Guinot
2011-05-06 20:59 ` Nicolas Pitre
2011-05-04 3:30 ` Hirundo Cam
2011-05-04 6:31 ` Mike Rapoport
2011-05-03 21:14 ` Simon Guinot
[not found] ` <1304496346-13557-1-git-send-email-camhirundo@gmail.com>
2011-05-04 7:56 ` [PATCH v2] " Hirundo Cam
2011-05-04 8:16 ` Simon Guinot
2011-05-04 9:50 ` saeed bishara
2011-05-05 0:20 ` Hirundo Cam
2011-05-05 7:08 ` saeed bishara
2011-05-05 15:20 ` Hirundo Cam
2011-05-05 0:11 ` Hirundo Cam
2011-05-05 7:50 ` Simon Guinot
2011-05-04 9:23 ` [PATCH] " Jean-Christophe PLAGNIOL-VILLARD
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='BANLkTikNhcEWUYnBdajyVa6tMGRM=7QPRQ@mail.gmail.com' \
--to=camhirundo@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).