<karlp>
yeah, step3 is the bit that's missing all the useful information....
<Galland>
lol
<naobsd>
only few minutes I could spend for it ;)
<karlp>
Galland: seeng as you're here, I cloned your git@github.com:Galland/rk3x_kernel_3.0.36.git repo,
<karlp>
for a rk3066, is that still what's meant to work?
<naobsd>
I bought it few hours ago
<karlp>
it didn't compile for me, using hte arm-linux-gnueabihf-gcc (crosstool-NG linaro-1.13.1-4.8-2013.10 - Linaro GCC 2013.10) 4.8.2 20131014 (prerelease) at least
<Galland>
karlp: I think so, but I haven't tested the newer 3188 kernels (like Linux3188 in my github too) for rk3066
<karlp>
or should I be trying to use the rk3188 tree you have that suggests will work on both?
<Galland>
however they could/should work too, but without 3D and without video render acceleration
<Galland>
for my rk3066 stick I use the rk3x kernel though I haven't compiled it for a while
<Galland>
I see, try compiling without the mtk wifi driver
<Galland>
that driver has always been a pain
<Galland>
bbl
<naobsd>
updated
<karlp>
well, I was trying to compile yoru stock first :)
<karlp>
my de3vice has the rtl8188eus anyway
<naobsd>
it seems memo pad 8 uses emmc
<linuxium>
@naobsd, back on 12th Dec you wrote [23:32 <naobsd> well, "please try any "Linux for RK". what I wanted to say is, it's not only some specific product" this doesn't say please use "Linux for RK" with my ramdisk. ]
<linuxium>
I do not understand your meaning ... please can you explain again to help me understand your point?
<naobsd>
well
<naobsd>
there are some "Linux for some specific RK product"
<naobsd>
and some people think "Linux runs on *only* some specific RK product"
<naobsd>
I just said it's not correct
<naobsd>
sorry, I almost forgot what I talked on 12 Dec...
<naobsd>
later part is, well
<linuxium>
np, my fault for not asking earlier ... but what does "Linux for some specific RK product" mean?
<naobsd>
actually I never tried picuntu. I saw someone said like as "my device is not supported"
<linuxium>
ah, now I understand you ... many thanks for the clarification
<naobsd>
I was talked "my device is not supported" is not correct
<linuxium>
I agree that "my device is not supported" is not correct if you use the default Android kernel to boot a Linux RFS on that device
<naobsd>
stock kernel may gives wifi and/or something which is missed with kernel compiled from source...
<karlp>
linuxium: on that note, if you have a stock android kernel, you only need to adjust the kernel boot params to use a linux RFS right?
<karlp>
and that's something your multiboot thing helps with?
<naobsd>
easy 3 steps == I can't write more than 3 lines lol
<naobsd>
I want to try bootloader for memo pad 8 on RR or something with UART
<linuxium>
@karlp, my multiboot thing allows slightly more ... you can boot Android using an Android kernel and Linux using a Linux kernel ... you can boot either from SD card or NAND ... you can install from SD card to NAND and you can backup/dump your NAND to SD card ... an example might be that you can choose to boot Android from NAND or Ubuntu 12.04 LTS from NAND or Debian 7 from SD ... yep its meant to help with things
<naobsd>
btw there is binary file in kernel source for MeMO Pad 8...
<naobsd>
whats' NVT_Alg.nvto ;)
<Galland>
naobsd: is the kernel source for Memo Pad 8 available somewhere?
<naobsd>
it's on asus web site
<Galland>
can you be more specific? I can't seem to even find a reference to Memo Pad 8, just 7