Hello,
I appologize if it's not the right place to ask, as the sun6i is not yet
supported on linux-sunxi, but I can't see another place where I could ask
this kind of question.
So I compiled a 3.3 kernel for a A31 based tablet but once I boot it (in
TWRP), it can't detect the sunxi-mmc.2. As this tablet use a eMMC as
internal storage (I'm talking about moviNAND, or eNAND), I just can't do
anything but using tmpfs without it being recognized.
On the other side, the external SD card is recognized just fine by
sunxi-mmc.0.
Here is the folder /sys/dev/block, using the stock tablet kernel in TWRP:
#/>ll /sys/dev/block
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:0 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:1 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p1
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:10 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
mmcblk0p10/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:11 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
mmcblk0p11/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:12 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
mmcblk0p12/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:13 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
mmcblk0p13/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:16 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
mmcblk0boot0/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:2 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p2
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:3 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p3
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:32 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/
mmcblk0boot1/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:48 -> ../../
devices/platform/sunxi-mmc.0/mmc_host/mmc1/mmc1:21cb/block/mmcblk1/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:49 -> ../../
devices/platform/sunxi-mmc.0/mmc_host/mmc1/mmc1:21cb/block/mmcblk1/mmcblk1p1
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:5 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p5
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:6 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p6
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:7 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p7
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:8 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 179:9 -> ../../
devices/platform/sunxi-mmc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p9
/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:0 -> ../../devices/
virtual/block/loop0/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:1 -> ../../devices/
virtual/block/loop1/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:2 -> ../../devices/
virtual/block/loop2/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:3 -> ../../devices/
virtual/block/loop3/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:4 -> ../../devices/
virtual/block/loop4/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:5 -> ../../devices/
virtual/block/loop5/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:6 -> ../../devices/
virtual/block/loop6/
lrwxrwxrwx 1 root root 0 Dec 31 14:15 7:7 -> ../../devices/
virtual/block/loop7/
And the same one, using the kernel I compiled (note that the external sd is
showing up and is named mmcblk0):
sh-3.2# ls -lF --color=auto /sys/dev/block
lrwxrwxrwx 1 root root 0 Dec 31 14:31 179:0 -> ../../
devices/platform/sunxi-mmc.0/mmc_host/mmc1/mmc1:21cb/block/mmcblk0/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 179:1 -> ../../
devices/platform/sunxi-mmc.0/mmc_host/mmc1/mmc1:21cb/block/mmcblk0/mmcblk0p1
/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:0 -> ../../
devices/virtual/block/loop0/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:1 -> ../../
devices/virtual/block/loop1/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:2 -> ../../
devices/virtual/block/loop2/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:3 -> ../../
devices/virtual/block/loop3/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:4 -> ../../
devices/virtual/block/loop4/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:5 -> ../../
devices/virtual/block/loop5/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:6 -> ../../
devices/virtual/block/loop6/
lrwxrwxrwx 1 root root 0 Dec 31 14:31 7:7 -> ../../
devices/virtual/block/loop7/
And the mounted partitions:
sh-3.2# mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000
,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,errors=
continue)
/dev/block/mmcblk0p1 on /and-sec type vfat (rw,relatime,fmask=0000,dmask=
0000,allow_utime=0022,codepage=cp437,iocharset=ascii,shortname=mixed,errors=
continue)
Currently, I'm using the kernel source found in the
a31_v4.5_hummingbird_kfb_ok SDK, but I've already tried too with the kernel
of rhombus-tech (same failure) and the Maxime Ripard one but couldn't make
it boot.
The tablet I'm using is the p78HD which has the KLM8G1WEMB-B031 eNAND
storage.
I haven't found a serial connection, but I still have to check every test
points of the board to see if I can find it there.
So is it because this type of internal storage isn't supported ? Or because
I've overlooked some important things ?
(This is the first time I compile a kernel for something different than
x86_64)
--
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.
