Hi Lawrence,

Appreciate your quick reply and thanks for your help.

I've now got the git branch clone but the compilation is failing with this 
error:

arm-linux-gnueabihf-gcc: error: unrecognized command line option 
‘--min_array_alignment=4’
arm-linux-gnueabihf-gcc: error: unrecognized command line option 
‘--no_unaligned_access’
scripts/Makefile.build:302: recipe for target 
'arch/arm/mach-sunxi/pm/standby/super/common.o' failed
make[3]: *** [arch/arm/mach-sunxi/pm/standby/super/common.o] Error 1
arch/arm/mach-sunxi/pm/Makefile:72: recipe for target 
'arch/arm/mach-sunxi/pm/standby/super/resume/resume1.code' failed
make[2]: *** [arch/arm/mach-sunxi/pm/standby/super/resume/resume1.code] 
Error 2
scripts/Makefile.build:561: recipe for target 'arch/arm/mach-sunxi/pm' 
failed
make[1]: *** [arch/arm/mach-sunxi/pm] Error 2
Makefile:1016: recipe for target 'arch/arm/mach-sunxi' failed
make: *** [arch/arm/mach-sunxi] Error 2

I've used linaro toolchains 4.9, 6.3 and gcc 5.4 (default from the Ubuntu 
repo) and all failed with the same error.

Which toolchain you used please? Am I missing something?

Again, appreciate your help!

Thanks,

Ramesh


On Wednesday, 17 May 2017 16:53:54 UTC+1, Lawrence Yu wrote:
>
> Hi,
>
> I updated the instructions on the wiki to update the commit tag.  You 
> shouldn't need to switch branches if the commit tag is correct.  It looks 
> like the old commit tag disappeared.  I tested with the new commit tag on 
> sina-a33 and it appears to work. (make sure to use correct u-boot config 
> and dtb)  If this commit tag disappears, the patch should apply to anything 
> close to 4.12-rc1 in the sunxi-next branch.
>
> Hope that helps.
>
>
>
> On Tue, May 16, 2017 at 5:37 AM, Ramesh Nerella <[email protected] 
> <javascript:>> wrote:
>
>> Hello Lawrence,
>>
>> I've got the Sinlinx A33 dev board and trying to follow your instructions.
>>
>> Kernel compilation is failing:
>>
>> git clone https://github.com/linux-sunxi/linux-sunxi
>>
>> cd linux-sunxi
>>
>> git checkout cdb41f6bb3262b3c52e788fec9bb6f92a1cabb15
>>
>>
>> fatal: reference is not a tree: cdb41f6bb3262b3c52e788fec9bb6f92a1cabb15
>>
>> is it the right branch? You mentioned it is sunxi-next branch but you are 
>> cloning linux-sunxi (3.4) branch.
>>
>> Also, A33 is Cortex-A7 no?
>>
>> Could you please help?
>>
>> Thanks,
>>
>>
>> On Wednesday, 12 April 2017 16:42:51 UTC+1, Lawrence Yu wrote:
>>>
>>> I have been able to combine the A33 suspend to ram code from the 
>>> Allwinner 3.4 SDK into a recent mainline kernel and make suspend to ram 
>>> work if anyone would like to try it out.  I tested it on a A33 GA10H-v1.1 
>>> tablet and a Sinlinx SIN-A33 dev board.  The goal was to see if suspend to 
>>> ram would work (which it does), so the code is not clean enough for 
>>> submission to the kernel.  It uses the binary arisc firmware from Allwinner 
>>> which there is no source code for, and the DRAM parameters from the FEX 
>>> file have to be explicitly defined for the device in the dts file for the 
>>> arisc to use.
>>>
>>> The patch is too big to post to the mailing list (over 1.5MB) and the 
>>> build instructions are more complicated than building a normal mainline 
>>> kernel so I have written up instructions and posted them on the sunxi wiki 
>>> at https://linux-sunxi.org/A33_Suspend
>>>
>>> I don't foresee doing much more development on this, so my hope is that 
>>> this patch and instructions can help some effort in the future to get 
>>> suspend to ram into the mainline kernel.
>>>
>>>
>>>
>>>
>>> -- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/d/optout.

Reply via email to