All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] video: treat signal like timeout as failure
Date: Tue, 10 Mar 2015 14:55:56 +0000	[thread overview]
Message-ID: <54FF05FC.5030704@ti.com> (raw)
In-Reply-To: <20150310144640.GM8656@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On 10/03/15 16:46, Russell King - ARM Linux wrote:

> In which case, let me propose that the exynos fbdev driver needs to be
> moved to drivers/staging, and stay there until this stuff gets fixed.
> drivers/staging is supposed to be for stuff which isn't up to the mark,
> and which is potentially unstable.  And that's what this driver exactly
> is.

There is drivers/gpu/drm/exynos/ which is getting a lot of updates. So...

I'd propose removing the exynos fbdev driver if the exynos drm driver
offers the same functionality. I don't know if that's the case. Does the
drm driver support all the devices the fbdev supports?

Also, I'm not sure if and how we can remove drivers. If exynos fbdev
driver is dropped, that would perhaps break boards that have exynos
fbdev in their .dts file. And if the drm driver doesn't offer the exact
same /dev/fbX interface, it would break the userspace.

So I don't know if that's possible. But that's what I'd like to do,
eventually, for all the fbdev drivers. Implement drm driver, remove the
fbdev one.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Nicholas Mc Guire <der.herr@hofr.at>
Cc: linux-fbdev@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	Donghwa Lee <dh09.lee@samsung.com>,
	Inki Dae <inki.dae@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Kukjin Kim <kgene@kernel.org>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	linux-arm-kernel@lists.infradead.org,
	Ajay Kumar <ajaykumar.rs@samsung.com>
Subject: Re: [PATCH] video: treat signal like timeout as failure
Date: Tue, 10 Mar 2015 16:55:56 +0200	[thread overview]
Message-ID: <54FF05FC.5030704@ti.com> (raw)
In-Reply-To: <20150310144640.GM8656@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On 10/03/15 16:46, Russell King - ARM Linux wrote:

> In which case, let me propose that the exynos fbdev driver needs to be
> moved to drivers/staging, and stay there until this stuff gets fixed.
> drivers/staging is supposed to be for stuff which isn't up to the mark,
> and which is potentially unstable.  And that's what this driver exactly
> is.

There is drivers/gpu/drm/exynos/ which is getting a lot of updates. So...

I'd propose removing the exynos fbdev driver if the exynos drm driver
offers the same functionality. I don't know if that's the case. Does the
drm driver support all the devices the fbdev supports?

Also, I'm not sure if and how we can remove drivers. If exynos fbdev
driver is dropped, that would perhaps break boards that have exynos
fbdev in their .dts file. And if the drm driver doesn't offer the exact
same /dev/fbX interface, it would break the userspace.

So I don't know if that's possible. But that's what I'd like to do,
eventually, for all the fbdev drivers. Implement drm driver, remove the
fbdev one.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: treat signal like timeout as failure
Date: Tue, 10 Mar 2015 16:55:56 +0200	[thread overview]
Message-ID: <54FF05FC.5030704@ti.com> (raw)
In-Reply-To: <20150310144640.GM8656@n2100.arm.linux.org.uk>

On 10/03/15 16:46, Russell King - ARM Linux wrote:

> In which case, let me propose that the exynos fbdev driver needs to be
> moved to drivers/staging, and stay there until this stuff gets fixed.
> drivers/staging is supposed to be for stuff which isn't up to the mark,
> and which is potentially unstable.  And that's what this driver exactly
> is.

There is drivers/gpu/drm/exynos/ which is getting a lot of updates. So...

I'd propose removing the exynos fbdev driver if the exynos drm driver
offers the same functionality. I don't know if that's the case. Does the
drm driver support all the devices the fbdev supports?

Also, I'm not sure if and how we can remove drivers. If exynos fbdev
driver is dropped, that would perhaps break boards that have exynos
fbdev in their .dts file. And if the drm driver doesn't offer the exact
same /dev/fbX interface, it would break the userspace.

So I don't know if that's possible. But that's what I'd like to do,
eventually, for all the fbdev drivers. Implement drm driver, remove the
fbdev one.

 Tomi


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150310/d88fe89e/attachment.sig>

  reply	other threads:[~2015-03-10 14:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20  5:23 [PATCH] video: treat signal like timeout as failure Nicholas Mc Guire
2015-01-20  5:23 ` Nicholas Mc Guire
2015-01-20  5:23 ` Nicholas Mc Guire
2015-01-26 12:50 ` Tomi Valkeinen
2015-01-26 12:50   ` Tomi Valkeinen
2015-01-26 12:50   ` Tomi Valkeinen
2015-01-26 12:59 ` Russell King - ARM Linux
2015-01-26 12:59   ` Russell King - ARM Linux
2015-01-26 12:59   ` Russell King - ARM Linux
2015-01-29  9:43   ` Nicholas Mc Guire
2015-01-29  9:43     ` Nicholas Mc Guire
2015-01-29  9:43     ` Nicholas Mc Guire
2015-03-10 12:43 ` Tomi Valkeinen
2015-03-10 12:43   ` Tomi Valkeinen
2015-03-10 12:43   ` Tomi Valkeinen
2015-03-10 12:51   ` Nicholas Mc Guire
2015-03-10 12:51     ` Nicholas Mc Guire
2015-03-10 12:51     ` Nicholas Mc Guire
2015-03-10 14:15     ` Russell King - ARM Linux
2015-03-10 14:15       ` Russell King - ARM Linux
2015-03-10 14:15       ` Russell King - ARM Linux
2015-03-10 14:39       ` Nicholas Mc Guire
2015-03-10 14:39         ` Nicholas Mc Guire
2015-03-10 14:39         ` Nicholas Mc Guire
2015-03-10 14:46         ` Russell King - ARM Linux
2015-03-10 14:46           ` Russell King - ARM Linux
2015-03-10 14:46           ` Russell King - ARM Linux
2015-03-10 14:55           ` Tomi Valkeinen [this message]
2015-03-10 14:55             ` Tomi Valkeinen
2015-03-10 14:55             ` Tomi Valkeinen
2015-03-10 15:26             ` Russell King - ARM Linux
2015-03-10 15:26               ` Russell King - ARM Linux
2015-03-10 15:26               ` Russell King - ARM Linux

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=54FF05FC.5030704@ti.com \
    --to=tomi.valkeinen@ti.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.