On 31/12/13 11:36, Hans de Goede wrote:
Hi,
On 12/31/2013 12:11 PM, Tim Fletcher wrote:
On 31/12/13 09:39, Hans de Goede wrote:
Hi,
On 12/30/2013 07:51 PM, Tim Fletcher wrote:
On 22/12/13 12:57, Hans de Goede wrote:
Hi,
On 12/22/2013 12:21 AM, Michal Suchanek wrote:
Actually sun7i smp conflicts badly with the sun6i smp .. so a stab at
a merge:
https://github.com/hramrach/linux-sunxi/commits/sunxi-next
Compile tested.
Actually the plan for A20 going forward is to have u-boot implement
PSCI and use that, the problem of the parent post is likely that he
does
not
have CONFIG_ARM_PSCI=y in his kernels .config. The reason for this is
that
this is necessary to properly enable HYP mode on the cpu-cores,
which we
want to be able to do hardware virtualization.
WRT I'm a bit surprised that Maxime does have SMP support for A31
in his
tree
to get merged upstream, as the A31 should be the same story, it has
Cortex
A7 cores which can do HYP mode too.
I've been testing this on my Cubietruck and your current devel tree
seems to be missing the dts changes from this commit.
https://github.com/hramrach/linux-sunxi/commit/8b5c1d5e7bbd71cf36535dc11578d9387af003b0
If I boot an rc5 kernel with a dtb from rc5 then I get usb but only 1
CPU (other fails to boot error -38), it I boot with a dtb from rc3 I
get both cpus but no USB.
If I apply the linked patch then I get both CPUs and USB.
Looking at you sunxi-next branch:
https://github.com/hramrach/linux-sunxi/commits/sunxi-next
You're not only adding "Add cpuconfig nodes in dts for smp configure."
but also
"Add smp support for Allwinner A20(sunxi 7i)."
This is the old way of doing smp on A20, we now have a u-boot with
PSCI, which is the preferred way of doing smp since it also give
us HYP mode, which many people want.
The proper way to get smp now is to use this u-boot:
https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next
Second try with coffee...
I am using your u-boot patched, with current sunxi-devel branch
kernel+dtb then only 1 CPU boots. If I apply just the changes I linked
to the dts file and rebuild it then both CPUs boot with the same
kernel binary.
I use your current u-boot and the rc5 kernel and just drop in the dtb
built from rc3 sunxi-next sources then both cpus boot but USB doesn't
work.
I have not applied any the kernel code changes, in fact all I did was
make dtbs, copy the new dtb file over and reboot.
Weird it works fine for me, and having that dtb change fix things makes
no sense since
if you did not apply the patch in question nothing in the kernel will be
responding
to that dtb blurb.
Are you sure you are booting the uImage you think you are booting?
These are the commands I'm using to build the kernel and dtb file
root@cubietruck:/usr/src/git/sunxi/linux-sunxi# git checkout
Your branch is up-to-date with 'origin/sunxi-devel'.
root@cubietruck:/usr/src/git/sunxi/linux-sunxi# LOADADDR=0x40008000 make
-j 3 uImage dtbs modules
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CHK kernel/config_data.h
CHK include/generated/uapi/linux/version.h
Building modules, stage 2.
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
Image arch/arm/boot/uImage is ready
MODPOST 2531 modules
root@cubietruck:/usr/src/git/sunxi/linux-sunxi# sha1sum
arch/arm/boot/uImage arch/arm/boot/dts/sun7i-a20-cubietruck.dtb
/boot/uImage-3.13.0-rc5+ /boot/sun7i-a20-cubietruck.dtb-3.13.0-rc5+
1a9e2e62aaa712ae66e9f23c28572d19e2e39177 arch/arm/boot/uImage
cf2a2b0ea3e3ca613f344097e23de966ba671cdf
arch/arm/boot/dts/sun7i-a20-cubietruck.dtb
1a9e2e62aaa712ae66e9f23c28572d19e2e39177 /boot/uImage-3.13.0-rc5+
cf2a2b0ea3e3ca613f344097e23de966ba671cdf
/boot/sun7i-a20-cubietruck.dtb-3.13.0-rc5+
--
Tim Fletcher <[email protected]>
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
