linux-kernel - Re: [GIT PULL] Move device tree graph parsing helpers to drivers/of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 13 Mar 2014 11:35:28 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Philipp Zabel <p.zabel@...gutronix.de>
Cc:	Grant Likely <grant.likely@...aro.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	Tomi Valkeinen <tomi.valkeinen@...com>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	Rob Herring <robh+dt@...nel.org>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
	devicetree@...r.kernel.org,
	Sylwester Nawrocki <s.nawrocki@...sung.com>
Subject: Re: [GIT PULL] Move device tree graph parsing helpers to drivers/of

On Thu, Mar 13, 2014 at 12:08:16PM +0100, Philipp Zabel wrote:
> I'm not sure if maybe I misunderstood or missed a mail, but I haven't
> seen a proposal to resolve the situation without rewinds. Given that
> Mauro already reverted the media tree and applied conflicting changes,
> that's probably not going to happen?

Grant and myself have exchanged emails in private on this discussing what
should happen - essentially Grant's position is that he's happy to leave
this stuff queued provided a resolution to his concerns are forthcoming.

However, what I find incredibly unfair is that we're taking the rap for
these bad bindings.  From what I can see, these bad bindings were merged
into the V4L2 code with _zero_ review by DT maintainers.  It's quite
clear that DT maintainers would have objected to them had they seen them,
but they didn't.  And the lack of documentation of the bindings which
has been something that's been insisted on is also disgusting.

And now we're now taking the pain for that oversight.

So... frankly, I've walked away from this dysfunctional situation.  I
don't see imx-drm moving out of drivers/staging due to this debacle for
many months - possibly never now given that no one can agree on this
stuff.  This just goes to show what a fscking joke mainline kernels are,
and why people just give up and go to vendor kernels which offer /much/
better support all round.

As far as I can see, it's proved impossible to define a set of bindings
for display devices which satisfy everyone.  So, rather than doing
/something/ so we can move forward, we end up doing /nothing/.

It's times like this where I start believing that /board files/ were the
best solution for ARM, because DT just carries soo many thorny issues
(such as these) and is a continual blocker.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/