From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] Add support for DRM display subsystem
Date: Thu, 10 May 2012 20:16:21 +0200 [thread overview]
Message-ID: <4FAC05F5.1050506@gmail.com> (raw)
In-Reply-To: <037301cd2e90$529112e0$f7b338a0$%kim@samsung.com>
On 05/10/2012 11:36 AM, Kukjin Kim wrote:
> Note that I have a plan to replace board files with DT supporting in
> mach-exynos/ next time.
What is the purpose of one side decisions like this ? I find it really
annoying. We have been building those board files through multiple kernel
releases, it took much effort and time to create proper drivers and
extending frameworks, like video or media.
It is going to take some more effort to make those subsystems DT aware and
add proper support at the drivers. This is being worked on and touching
existing boards doesn't sound like an incentive to me. We have to deal
with multiple boards and breaking existing ones which are almost completed
just adds an effort for us of maintaining them internally. The mainline
kernel is going to always be a half-product, not properly tested and
validated.
We get new boards that need to be supported in the kernel quite frequently,
those boards share device IPs, so adapting the drivers to the DT is
already our goal, for getting new boards supported in the mainline.
I have no idea what that "replacing" is going to be about, but if you add
support for all devices present in those boards and they will all work
as before - I'll happily accept that. Although I'm afraid it is just going
to be one big breakage and regression, in the name of "everything must
migrate to the device tree".
I would really appreciate more common agreement, rather than putting
a spoke in somebody else's wheel.
Once all devices in current mach-exynos board files get proper DT support
we are going to remove the boards ourselves. I'm sure there is lots of
other things that need more attention than that.
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-05-10 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 10:39 [PATCHv2 0/3] Add support for DRM display subsystem Marek Szyprowski
2012-03-13 10:39 ` [PATCHv2 1/3] ARM: Exynos: add platform device for core DRM subsystem Marek Szyprowski
2012-03-13 10:39 ` [PATCHv2 2/3] ARM: Exynos: Add DRM core device support for Universal C210 board Marek Szyprowski
2012-03-13 10:39 ` [PATCHv2 3/3] ARM: Exynos: Add DRM core support for NURI board Marek Szyprowski
2012-05-10 9:36 ` [PATCHv2 0/3] Add support for DRM display subsystem Kukjin Kim
2012-05-10 9:53 ` Kyungmin Park
2012-05-10 13:48 ` Arnd Bergmann
2012-05-10 14:46 ` Kyungmin Park
2012-05-10 15:00 ` Sachin Kamat
2012-05-11 10:37 ` Kukjin Kim
2012-05-10 11:18 ` Marek Szyprowski
2012-05-10 18:16 ` Sylwester Nawrocki [this message]
2012-05-12 23:54 ` Kukjin Kim
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=4FAC05F5.1050506@gmail.com \
--to=sylvester.nawrocki@gmail.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 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).