AMLogic 8726m3/Mali400 and Debian Linux/Xorg
#31
(2013-04-27, 23:06)j1nx Wrote: Oh ok.

Be aware we are upgrading the sources to 3.0.50

I've failed to follow, are you upgrading the m6 sources only or the m3 also ? (common kernel sources ?, no binary blobs ?)
Reply
#32
Hello everyone,
Indeed there have been new packages output at AMlogic I found the link on cnx-software.com
There was even the amlogoc alsa-utils !
http://openlinux.amlogic.com:8000/downlo...013-04-24/

I'll look at it tonight, and this new Kernel !
Reply
#33
Big thanks for this Sylvain, I will look at that closely also ! Smile
Let us know your findings !

wgetting all of it as we speak, I guess I found what to do with that week of free time ! Smile
Reply
#34
I've tried it some days ago. I beleive it's intended for android only. I might be missing something though...
It needs an ARC compiler also, which you can get from the openlinux page. But there doesn't seem to be support for mali DRM either
Reply
#35
As you look in the common:
The DRM will be added manually, this is not very complicated to do, there are just two build files to modify, and retrieve drivers DRM on this site : http://malideveloper.arm.com/develop-for...e-drivers/
Or even SUN4I, as did the author of Ubuntu version :
https://github.com/keenet/kernel_ubuntu_...rm/Kconfig
https://github.com/keenet/kernel_ubuntu_...m/Makefile
https://github.com/keenet/kernel_ubuntu_...u/drm/mali

The advantage to go on a V3 kernel is to guarantee the activation of DRM, but also have a newer DVB API and therefore compatible with the latest software.
Reply
#36
Kernel from http://openlinux.amlogic.com:8000/downlo...013-04-24/ is also 2.6.34 and has no drm support either.

For 3.x series try https://github.com/nspierbundel/amlogic-common/ but it's still not working as j1nx said some posts ago.
Reply
#37
We do not have the same result as on my side I'm reading :
Code:
VERSION = 3
PATCHLEVEL = 0
SUBLEVEL = 50
EXTRAVERSION =
NAME = Sneaky Weasel

I started work with the deposit that you mention, and apparently it was poorly prepared for missing files (eg the file scripts/Makefile.lib).
So I made my own repository you'll find here : https://github.com/SIP-Online/AMLogic-Ke...mon-3.0.50
Branch for "Meson3" will come later once I have corrected errors compilations.

For "DRM", you just need to enable it in defconf :
Code:
CONFIG_DRM=m
If you do this on version "2.6.34", reject that option, while on the "Kernel" he accepts this option !
And once manually put the "driver", you can activate it with this :
Code:
CONFIG_DRM_MALI=m

For the version of "Kernel", you will find it here : https://github.com/SIP-Online/Amlogic-Ke...r/Makefile
Reply
#38
I made ​​good progress, there are still things to see on the side of activation "MALI".
But before I will wish to correct a problem starting, I think fdff has had this kind of problem ?
Code:
NAND read: boot offset 0x0, size 0x800000
8388608 bytes read: OK
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-3.0.50
   Image Type:   ARM Linux Kernel Image (lzma compressed)
   Data Size:    3928808 Bytes = 3.7 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Then nothing Confused
Which can be changed a setting to "ttyS0" ?
Here are my patches for a compilation without errors with "drivers" and "codecs" enabled : http://speedy.sh/QBbHZ/Amlogic-Kernel-Co...eson-3.zip
Reply
#39
you probably have the framebuffer console enabled. Because of that I think the console is sent to the HDMI, which is not yet working.
Reply
#40
No, nothing happens, I even tried with "defconf" provides in the Kernel and always the same.
I have a doubt about the version of uboot, should also update ?
If I change two other file (m3ref.c-board, board-m3ref.h) to copy certain value present in the Kernel 2.6.34 (m3-reff16.c-board, board-m3-reff16.h).

I'll test suite with the master uboot "04.24.2013-git-1a38c20c95".

If this does not help, I will stop my research, and pass on another platform.
Reply
#41
Hi,
I`ve pushed the missing file to develop. https://github.com/nspierbundel/amlogic-...ee/develop

for the m3 box please checkout https://github.com/nspierbundel/amlogic-...ree/meson3 , vDorst has put a lot of effort in the m3 on kernel 3.0.8

at first we had simmilar errors like the starting kernel ...

enable low level debug and early printk in defconfig and it will spit out the errors why it wont boot, follow vDorst his commits to get it to work on 3.0.50 kernel.

for our m6 project a quick status update: it boots 3.0.50 kernel and has network, cardreader and a lot of bugs. It will also compile and boot using linaro gcc4.7 Big Grin

Daniel
Reply
#42
I responded to the filing of "Kernel 3.0.8" : http://forum.xbmc.org/showthread.php?tid...pid1407060

I wish I leave the M3 to move to MX, it will save more time, but I do not know if the "XBMC" included in the builroot work, have you had feedback on the compatibility of libamplayer-m3 and AML8726-MX ?

Thank you !
Reply
#43
are you adding console=ttyS0,115200n8 to the kernel boot parameters? is uart without core enabled in the kernel config?
Reply
#44
I don't know if lib amplayer will work.
I'm currently try to get nfs to work, should make it a lot easier to test rootfs.
A lot of changes must be made to buildroot.
Daniel

I'm not adding uart settings to the boot params, it works without. (or uboot manages this)
Daniel
Reply
#45
sorry I posted that for cSylvain without noticing there had been further replies.

nspierbundel, can you tell me which kernel you're using?

I can get some output by enabling CONFIG_DEBUG_LL in kernel configuration, but i get a "kernel oops" as soon as system starts booting kernel from https://github.com/nspierbundel/amlogic-...ree/meson3

<1>Unable to handle kernel NULL pointer dereference at virtual address 00000000
<1>pgd = c0004000
<1>[00000000] *pgd=00000000
<0>Internal error: Oops: 80000005 [#1] PREEMPT
Reply

Logout Mark Read Team Forum Stats Members Help
AMLogic 8726m3/Mali400 and Debian Linux/Xorg0