On Tue, 2014-12-02 at 15:17 +0900, Heesub Shin wrote:
> Hello Simons,
>
> On 12/01/2014 09:59 PM, Sjoerd Simons wrote:
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > +*/
> > +
> > +/dts-v1/;
> > +#include "exynos5800.dtsi"
>
> Looking at exynos5800.dtsi, it derives from exynos5420.dtsi and seems
> having differences on clock and mfc. Is it proper to include
> exynos5800.dtsi here, instead of exynos5420.dtsi? It's just my curiosity
> as I am not in a position to know detailed things on the soc. Only
> semiconductor guys could answer this.
I would love to get a conclusive answer on this one as the exynos 5422
vs. exynos 5800 question seems to keep coming up (both on this list and
the u-boot one where XU3 support is being added as well).
As far as i understand things the Exynos 5800 is a "variant" of the
Exynos 5422 for chromebooks[0]. I suspect things are just being called
5800 in the kernel and u-boot as the chromebooks were the first boards
based on this SoC to reach mainline...
Which led to interesting things like:
#define EXYNOS5800_SOC_ID 0xE5422000
Iotw, the identifier for the 5800 is 0x5422, which doesn't really make
things more clear.
I'm working on the assumption that this SoC variation doesn't expose
differences to the OS. I did not yet test the MFC, but should get round
to that later this week, which should help in verifying the MFC side of
things at least.. I haven't yet seen any issues caused due to the
differences in clock setup between samsung,exynos5800-clock and
samsung,exynos5420-clock
> > +
> > +/ {
> > + model = "Hardkernel Odroid XU3";
> > + compatible = "hardkernel,odroid-xu3", "samsung,exynos5800", "samsung,exynos5";
> > +
> > + memory {
> > + reg = <0x20000000 0x80000000>;
> > + };
>
> Start address above should be 0x40000000, not 0x20000000.
Indeed, the Hardkernel DTS also starts at 0x40000000, I missed that.
Looking at the other exynos5800/5420 based boards in the kernel they all
have their start offset at 0x20000000, is this different for the XU3
because it runs with secure firmware or is there some other reason
behind this?
> One more thing, having bootargs which specifies 'console=xxx' would be
> better.
Hrm, i've got a dislike for chosen/bootargs as they typically seem
rather random/inconsistent (not sure who they're meant for). However, I
should indeed specify chosen/stdout-path to point to the serial console.
Thanks for your review!
0: See table at the bottom of
http://www.samsung.com/global/business/semiconductor/minisite/Exynos/w/solution.html#?v=octa_5422
--
Sjoerd Simons <sjoerd.simons@xxxxxxxxxxxxxxx>
Collabora Ltd.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
