kernel source for r2 and working config please

[olimex]

definitly not! linux-sunxi have mailing list which all developers read and this is the best place to report bugs

[tlhingan]

I spoke with Dimitar few minutes ago and he says he check and Linux-Sunxi Kernel 3.4 have all patches which he did to kernel 3.3. to generate image2 already merged to Kernel 3.4 tree so he now will try to build new image for Debian, Ubuntu and Slack based on Linux-Sunxi Kernel 3.4

As soon these are available I will blog how to make them and update the wiki image links, but this will not happen tomorrow after the images are build we have to test them: I2C, HDMI etc all peripherial and this is slow process.

Do we have an update on this?

[olimex]

please read the post on the previous page!

[tlhingan]

https://github.com/hehopmajieh/OLinuXino-A20
in above repo are instructions how to build Kernel 3.3 (used in R2) and 3.4 which we use in the new image build we prepare

You mean this?

please stick to Linux-Sunxi community Kernel 3.4, which have everything working except the LCD touchscreen. We look into the TS issue to solve.

But what about this? We absolutely need the touchscreen working.
How is Olimex coming with the new images and/or patches to get the touchscreen working on Kernel 3.4?

[olimex]

touchscreen is fixed in Kernel 3.4

[tlhingan]

touchscreen is fixed in Kernel 3.4

Yaaaay!
Now I get to compile my own kernel.

[olimex]

we are preparing blog post with all settings

[Black_Wolf]

Hello, I have compiled it without problems, and put it on my R2 with modules and firmwares, but nothing happened. Card won't boot.
I have missed something ?

EDIT:
With Putty,

...
<5>Linux version 3.4.43+ (joachim@media-center) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu) ) #1 SMP PREEMPT Sun Sep 8 15:04:02 CEST 2013
CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

Error: unrecognized/unsupported machine ID (r1= 0x00000f35).


Error: unrecognized/unsupported machine ID (r1= 0x00000f35).

Available machine support:

ID(hex)         NAME
Available machine support:
ID(hex)         NAME
000010bb        sun7i
000010bb        sun7i
0000102a        sun5i
0000102a        sun51
00001008        sun4i
00001008        sun4i

Please check your kernel config and/or bootloader.

Please check your kernel config and/or bootloader.

So on compilation, it use my desktop information rather the "CONFIG_ARCH_SUN7I=y" on config file?

[pinnchus]

# setenv machid 10bb
# saveenv
# reset

[pinnchus]

Apparently, this occurs by a change in the file mach-types in the path linux-sunxi-sunxi-3.4/arch/arm/tools

...
sun7i                   MACH_SUN7I              SUN7I                   4283
...

sun7i  -> 4283 => 0x10BB

Regards,
Pinnchus

[tlhingan]

we are preparing blog post with all settings

I am very much looking forward to it!

[Black_Wolf]

Thanks Pinnchus, with the first post it run.
The second, I have test, but 0x10BB is only 4283 in hex.

I also see on the defconfig...
OK for IS NOT SET
OK for ...=y
but what is ...=m ? I don't find word for this M

[pinnchus]

M means yes but as a module

Regards,
Pinnchus

Thanks Pinnchus, with the first post it run.
The second, I have test, but 0x10BB is only 4283 in hex.

I also see on the defconfig...
OK for IS NOT SET
OK for ...=y
but what is ...=m ? I don't find word for this M

[olimex]

we are preparing blog post with all settings

I am very much looking forward to it!

patience just RTL8188CU works unreliable now, all other things are tested and work
apparently kernel 3.4 have no RTL8188CU support and Realtek drivers work with problems

[tlhingan]

patience just RTL8188CU works unreliable now, all other things are tested and work
apparently kernel 3.4 have no RTL8188CU support and Realtek drivers work with problems

Keep it coming!