All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/9] drivers/video: fsl-diu-fb: fix some ioctls
Date: Mon, 03 Oct 2011 17:24:05 +0000	[thread overview]
Message-ID: <4E89EFB5.1020200@freescale.com> (raw)
In-Reply-To: <1317244795-24671-1-git-send-email-timur@freescale.com>

Florian Tobias Schandinat wrote:
> On 09/28/2011 09:19 PM, Timur Tabi wrote:
>> Use the _IOx macros to define the ioctl commands, instead of hard-coded
>> numbers.  Unfortunately, the original definitions of MFB_SET_PIXFMT and
>> MFB_GET_PIXFMT used the wrong value for the size, so this will break
>> binary compatibility with older applications.
> 
> Don't break compatibility without the need to do so. Ask yourself whether using
> those macros is really worth it. If the answer is yes, at least give userspace a
> grace period, some kernel versions where both values work. For example you could
> rename the old numerical ones to MFB_SET_PIXFMT_OLD and then add a compatibility
> IOCTL, for example like this
> 
> case MFB_SET_PIXFMT_OLD:
> 	/* you could add a warning message here */
> case MFB_SET_PIXFMT:
> 	...

Ok, I can do that.

> Not much work and you could delete the compatibility stuff in a year or two but
> it would it make much easier for users to upgrade.
> 
> I don't know your driver, can int be only 32 bit on all plattforms where it can
> be used or is this another thing where compatibility can break?

We have 64-bit processors, but currently none of them have any multimedia
support.  That might change one day, and I'd rather the drivers be 64-bit clean
before we announce any such parts.  There are other places in the driver that
break on 64-bit, and I will fix those as well (just not today).

-- 
Timur Tabi
Linux kernel developer at Freescale


      parent reply	other threads:[~2011-10-03 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 21:19 [PATCH 1/9] drivers/video: fsl-diu-fb: fix some ioctls Timur Tabi
2011-10-03 16:17 ` Florian Tobias Schandinat
2011-10-03 17:24 ` Timur Tabi [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=4E89EFB5.1020200@freescale.com \
    --to=timur@freescale.com \
    --cc=linux-fbdev@vger.kernel.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.