From: In-Ki Dae <inki.dae@samsung.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Re: [PATCH 1/3] FB: Add some members for CPU Interface.
Date: Fri, 02 Jul 2010 07:50:53 +0000 [thread overview]
Message-ID: <25797910.38561278057053699.JavaMail.weblogic@epml17> (raw)
In-Reply-To: <AANLkTilgB3s8hy5Qg7IYpyBzwHCgK_GswVZqpxhryU5L@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 1602 bytes --]
Ok, I understood.
I think this issue incompatible with existing users is because userspace API didn't consider cpu mode before.
anyway, I will correct my patch as your comments and send it again.
Perhaps, cpu timing variables would be moved to platform file.
thank you.
------- Original Message -------
Sender : Russell King - ARM Linux<linux@arm.linux.org.uk>
Date : 2010-07-02 16:30 (GMT+09:00)
Title : Re: [PATCH 1/3] FB: Add some members for CPU Interface.
On Wed, Jun 30, 2010 at 08:02:31AM +0800, Jaya Kumar wrote:
> > diff --git a/include/linux/fb.h b/include/linux/fb.h
> > index 907ace3..73381c3 100644
> > --- a/include/linux/fb.h
> > +++ b/include/linux/fb.h
> > @@ -269,6 +269,12 @@ struct fb_var_screeninfo {
> > __u32 vmode; /* see FB_VMODE_* */
> > __u32 rotate; /* angle we rotate counter clockwise */
> > __u32 reserved[5]; /* Reserved for future compatibility */
> > +
> > + /* For cpu interface timing. */
> > + __u32 cs_setup;
> > + __u32 wr_setup;
> > + __u32 wr_act;
> > + __u32 wr_hold;
This changes the framebuffer userspace API, making it incompatible with
existing users. What this means is that stuff using the framebuffer API
in userspace has to be upgraded/downgraded in lock-step with this change
- which is not a good idea.
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±ýöÝzÿâØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+Ê+zf£¢·h§~Ûiÿÿïêÿêçz_è®\x0fæj:+v¨þ)ߣøm
WARNING: multiple messages have this Message-ID (diff)
From: inki.dae@samsung.com (In-Ki Dae)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] FB: Add some members for CPU Interface.
Date: Fri, 02 Jul 2010 07:50:53 +0000 (GMT) [thread overview]
Message-ID: <25797910.38561278057053699.JavaMail.weblogic@epml17> (raw)
Ok, I understood.
I think this issue incompatible with existing users is because userspace API didn't consider cpu mode before.
anyway, I will correct my patch as your comments and send it again.
Perhaps, cpu timing variables would be moved to platform file.
thank you.
------- Original Message -------
Sender : Russell King - ARM Linux<linux@arm.linux.org.uk>
Date : 2010-07-02 16:30 (GMT+09:00)
Title : Re: [PATCH 1/3] FB: Add some members for CPU Interface.
On Wed, Jun 30, 2010 at 08:02:31AM +0800, Jaya Kumar wrote:
> > diff --git a/include/linux/fb.h b/include/linux/fb.h
> > index 907ace3..73381c3 100644
> > --- a/include/linux/fb.h
> > +++ b/include/linux/fb.h
> > @@ -269,6 +269,12 @@ struct fb_var_screeninfo {
> > __u32 vmode; /* see FB_VMODE_* */
> > __u32 rotate; /* angle we rotate counter clockwise */
> > __u32 reserved[5]; /* Reserved for future compatibility */
> > +
> > + /* For cpu interface timing. */
> > + __u32 cs_setup;
> > + __u32 wr_setup;
> > + __u32 wr_act;
> > + __u32 wr_hold;
This changes the framebuffer userspace API, making it incompatible with
existing users. What this means is that stuff using the framebuffer API
in userspace has to be upgraded/downgraded in lock-step with this change
- which is not a good idea.
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-02 7:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 10:49 [PATCH 1/3] FB: Add some members for CPU Interface InKi Dae
2010-06-29 10:49 ` InKi Dae
2010-06-30 0:02 ` Jaya Kumar
2010-06-30 0:02 ` Jaya Kumar
2010-06-30 4:36 ` InKi Dae
2010-06-30 4:36 ` InKi Dae
2010-07-01 23:47 ` Jaya Kumar
2010-07-01 23:47 ` Jaya Kumar
2010-07-02 1:51 ` In-Ki Dae
2010-07-02 1:51 ` In-Ki Dae
2010-07-02 7:30 ` Russell King - ARM Linux
2010-07-02 7:30 ` Russell King - ARM Linux
2010-07-02 7:50 ` In-Ki Dae [this message]
2010-07-02 7:50 ` In-Ki Dae
2010-07-06 16:09 ` James Simmons
2010-07-06 16:09 ` James Simmons
2010-07-06 15:30 ` James Simmons
2010-07-06 15:33 ` James Simmons
2010-07-06 15:35 ` James Simmons
2010-07-06 20:23 ` Geert Uytterhoeven
2010-07-07 11:37 ` James Simmons
2010-07-08 0:52 ` In-Ki Dae
2010-07-05 8:42 ` Pawel Osciak
2010-07-05 8:42 ` Pawel Osciak
-- strict thread matches above, loose matches on Subject: below --
2010-07-02 1:21 In-Ki Dae
2010-07-02 2:35 In-Ki Dae
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=25797910.38561278057053699.JavaMail.weblogic@epml17 \
--to=inki.dae@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.