From: Richard Genoud <richard.genoud-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jean-Christophe PLAGNIOL-VILLARD
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Cc: linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Steffen Trumtrar
<s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Florian Tobias Schandinat
<FlorianSchandinat-Mmb7MZpHnFY@public.gmane.org>
Subject: Re: fb_monspecs and device tree
Date: Tue, 28 May 2013 13:37:45 +0200 [thread overview]
Message-ID: <CACQ1gAg-PyMkswKb3jz_ZMRXiRCU5WNoDv9U9_vf_xWK5SWkhA@mail.gmail.com> (raw)
In-Reply-To: <20130528104748.GL1952-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2013/5/28 Jean-Christophe PLAGNIOL-VILLARD <plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>:
> On 11:41 Tue 28 May , Richard Genoud wrote:
>> Hi !
>>
>> I've been using the display-timings device tree node (great job !) on
>> a sam9x5 soc.
>>
>> I was wondering if there's a planned support for struct fb_monspecs in
>> device tree, (or if it is irrelevant), if someone is already working
>> on that etc...
>
> I'm working on this but not on fbdev on DRI/KMS
> so we can have a full support of the overlay & co
> but I'm going to change complely the dt binding with the one present on
> github
>
> beawre the lcdc is already done on fbdev with display-timings
>
> but I'll be off the first week on June so wait a few for sam9x5
>
> Best Regards,
> J.
ok, that's good news !
thanks.
prev parent reply other threads:[~2013-05-28 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 9:41 fb_monspecs and device tree Richard Genoud
[not found] ` <CACQ1gAg=nyZrXMKk2g+cFvn5g7kHnRKMQ9R2G7ufAqs07dkYHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-28 10:47 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20130528104748.GL1952-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2013-05-28 11:37 ` Richard Genoud [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=CACQ1gAg-PyMkswKb3jz_ZMRXiRCU5WNoDv9U9_vf_xWK5SWkhA@mail.gmail.com \
--to=richard.genoud-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=FlorianSchandinat-Mmb7MZpHnFY@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org \
--cc=s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@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;
as well as URLs for NNTP newsgroup(s).