From: John Williams <john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
To: John Linn <John.Linn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: David DeBonis <ddeboni-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Stephen Neuendorffer
<stephenn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Linux Kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michal Simek
<michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Re: Xilinx SYSACE driver and 8-bit attachment
Date: Thu, 8 Oct 2009 09:46:36 +1000 [thread overview]
Message-ID: <1d3f23370910071646la1ac12ds7c2805f1569cd9e6@mail.gmail.com> (raw)
In-Reply-To: <7a2a686d-ddf4-4a42-8c73-c933cebf22a4-+Ck8Kgl/v09Eus+KprP3J7jjLBE8jN/0@public.gmane.org>
Hi John,
On Thu, Oct 8, 2009 at 9:44 AM, John Linn <John.Linn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org> wrote:
> I fixed the device tree generator and checked into git-dev, I'll push it out soon after a little more test time.
I think we should be careful about adding special per-device handing
in the DTS generator. Where ever possible I would encourage generic
handling. Most Xilinx devices are "green fields" with respect to the
device tree binding and these params, SystemACE is a little different
because it's been in mainline longer and has users outside the DTS
generator flow.
John
--
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663
next prev parent reply other threads:[~2009-10-07 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1d3f23370910070013u6307bc42hf7ab243b52d007df@mail.gmail.com>
[not found] ` <1d3f23370910070013u6307bc42hf7ab243b52d007df-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 13:34 ` Xilinx SYSACE driver and 8-bit attachment Grant Likely
2009-10-07 14:24 ` John Linn
[not found] ` <838c3c32-27d9-4a0a-a197-c7227b911942-+Ck8Kgl/v0/UuUXyfqFqSbjjLBE8jN/0@public.gmane.org>
2009-10-07 23:41 ` John Williams
[not found] ` <1d3f23370910071641s75b2d217h71a839b1a0b4013c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 23:44 ` John Linn
[not found] ` <7a2a686d-ddf4-4a42-8c73-c933cebf22a4-+Ck8Kgl/v09Eus+KprP3J7jjLBE8jN/0@public.gmane.org>
2009-10-07 23:46 ` John Williams [this message]
2009-10-07 14:42 ` John Linn
[not found] ` <192797ad-5dd4-4ebe-8db3-d381bb949e1e-+Ck8Kgl/v09YkiQOvaGFS7jjLBE8jN/0@public.gmane.org>
2009-10-07 14:52 ` Grant Likely
2009-10-07 16:18 ` Stephen Neuendorffer
[not found] ` <fa686aa40910070634r4a8dcf74qdcbfb3bde3413109-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 23:44 ` John Williams
[not found] ` <1d3f23370910071644y5877cf9v879967340a463f19-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 23:47 ` John Linn
2009-10-07 23:48 ` Stephen Neuendorffer
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=1d3f23370910071646la1ac12ds7c2805f1569cd9e6@mail.gmail.com \
--to=john.williams-g5w7nranp4bdpfhejli6iq@public.gmane.org \
--cc=John.Linn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=ddeboni-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=stephenn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.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