From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx_v6_v7_defconfig: Enable GPU support
Date: Tue, 22 Dec 2015 16:16:42 +0000 [thread overview]
Message-ID: <20151222161642.GO8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOMZO5CXqNNv7hv0kwyqQiQvo4d_X1jN8jf4QPmEJQvMogHzGA@mail.gmail.com>
Jon is busy at the moment, and I expect will reply in a few hours or
so.
On Tue, Dec 22, 2015 at 01:31:53PM -0200, Fabio Estevam wrote:
> It seems the information you got from Jon is not correct.
I suspect Jon is in a better position to comment about what works and
what doesn't, as he's doing the customer facing support for SolidRun,
and has to deal with people trying to run stock u-boot on SolidRun's
hardware.
_Especially_ when he gets regular reports from users trying to run
Fedora 23 on SolidRun platforms, which ships with mainline u-boot,
and it fails to work because mainline u-boot gets stuff wrong. The
telling thing for Jon is that when he gets users to switch to SR's
u-boot, the problems magically vanish.
> We do support several versions of Hummingboard and Cubox-i (at least
> for the board models I have access to) in mainline U-boot.
Maybe, rather than this "vendors are evil, we must write our own patches
which are independent of the vendor" attitude, maybe people ought to
work _with_ vendors? Jon is an open source guy, he was working on OLPC
before he switched to the SolidRun platforms, first as a hobby and later
as their kernel and uboot maintainer. He's not an evil vendor!
> The SDRAM is correctly setup depending on the board type:
> http://git.denx.de/?p=u-boot.git;a=history;f=board/solidrun/mx6cuboxi/mx6cuboxi.c;h=fc37f1eef06da5147e5403d4272d220836c9cfbc;hb=HEAD
>
> Like you said in the past only the old mx6d hummingboard was
> supported, but we are in better shape now and the old support has been
> removed.
Jon is aware of what's in mainline u-boot, and the memory timings there
are wrong. For a start, the highest DDR clock rate is 1066MHz, not
1600MHz that you have in mainline u-boot. So you're overclocking the
SDRAM.
I know that Jon has put a _lot_ of effort into getting the SDRAM setup
stable on SolidRun hardware to eliminate hangs and other problems, and
it seems the attitude is "we don't care about that, we're mainline, we
know better."
So, excuse me if I trust Jon's comments about uboot more than anyone
elses.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-12-22 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 18:44 [PATCH] ARM: imx_v6_v7_defconfig: Enable GPU support Fabio Estevam
2015-12-22 12:21 ` Shawn Guo
2015-12-22 12:30 ` Fabio Estevam
2015-12-22 12:47 ` Lucas Stach
2015-12-22 12:51 ` Fabio Estevam
2015-12-22 12:53 ` Russell King - ARM Linux
2015-12-22 15:02 ` Russell King - ARM Linux
2015-12-22 15:31 ` Fabio Estevam
2015-12-22 16:16 ` Russell King - ARM Linux [this message]
2015-12-22 16:38 ` Fabio Estevam
2015-12-22 17:34 ` Jon Nettleton
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=20151222161642.GO8644@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).