From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] Documentation: devicetree: add description for generic bus properties
Date: Fri, 29 Nov 2013 09:57:03 +0000 [thread overview]
Message-ID: <20131129095703.GV16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131129093713.GC22771@ulmo.nvidia.com>
On Fri, Nov 29, 2013 at 10:37:14AM +0100, Thierry Reding wrote:
> There's a large gap between how fast new SoCs are supposed to tape out
> and the rate at which new code can be merged upstream. Perhaps some of
> that could be mitigated by putting more of the complexity into firmware
> and that's already happening to some degree for ARMv8. But I suspect
> there's a limit to what you can hide away in firmware while at the same
> time giving the kernel enough information to do the right thing.
One of the bigger issues which stands in the way of companies caring
about mainstream support is closed source IPs like VPUs and GPUs.
If you have one of those on your chip, even if the kernel side code
is already under the GPL, normally that code is not "mainline worthy".
Also, as the userspace code may not be open source, some people object
to having the open source part in the kernel.
So for customers to be able to get the performance out of the chip,
they have to stick with having non-mainline kernel.
At that point, why bother spending too much time getting mainline
support for the device. It's never going to be fully functional in
mainline. It doesn't make sense for these SoC companies.
next prev parent reply other threads:[~2013-11-29 9:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 17:28 [RFC PATCH] Documentation: devicetree: add description for generic bus properties Dave Martin
2013-11-27 23:06 ` Greg KH
2013-11-28 10:28 ` Will Deacon
2013-11-28 17:33 ` Dave Martin
2013-11-28 19:13 ` Greg KH
2013-11-28 19:39 ` Dave Martin
2013-11-28 21:25 ` Greg KH
2013-11-29 11:44 ` Will Deacon
2013-11-29 17:37 ` Greg KH
2013-11-29 18:01 ` Will Deacon
2013-11-29 18:11 ` Greg KH
2013-11-29 18:15 ` Will Deacon
2013-11-28 19:10 ` Greg KH
2013-11-28 20:33 ` Thierry Reding
2013-11-28 21:10 ` Jason Gunthorpe
2013-11-28 22:22 ` Thierry Reding
2013-11-28 23:31 ` Jason Gunthorpe
2013-11-29 2:35 ` Greg KH
2013-11-29 9:37 ` Thierry Reding
2013-11-29 9:57 ` Russell King - ARM Linux [this message]
2013-11-29 10:43 ` Thierry Reding
2013-11-29 13:13 ` Dave Martin
2013-11-29 13:29 ` Russell King - ARM Linux
2013-11-29 17:43 ` Greg KH
2013-11-29 17:42 ` Greg KH
2013-11-29 19:45 ` Thierry Reding
2013-12-04 18:43 ` Mark Brown
2013-12-04 19:03 ` Greg KH
2013-12-04 20:27 ` Mark Brown
2013-11-29 9:57 ` Thierry Reding
2013-11-29 14:13 ` Dave Martin
2013-11-29 11:58 ` Dave Martin
2013-11-29 18:43 ` Jason Gunthorpe
2013-12-02 20:25 ` Dave Martin
2013-12-03 0:07 ` Jason Gunthorpe
2013-12-03 11:45 ` Dave Martin
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=20131129095703.GV16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).