00:50 <bashintosh> mmmh.. got linux rfs on nand (/dev/mmcblk0p14) but the kernel (also on nand) seems to ignore the parameter file pointing at mmcblk0p14 for root - keeps on wanting to find the filesystem on mmcblk0p1 <_<

00:51 <bashintosh> mmcblk0p14 is ext4 and mountable (via miniroot)

01:21 <naobsd> bashintosh: kernel doesn't read parameter. loader read it and passes it to kernel

01:22 <naobsd> bashintosh: are you really sure cmdline in parameter and /proc/cmdline (or cmdline in dmesg) are different?

01:33 <bashintosh> naobsd: mmh I see - I will check that first then!

01:34 <bashintosh> cmdline in dmesg is visible just after the kernel starts right? If so cmdline there == to cmdline in parameter

01:37 <bashintosh> to be honest I have root=/dev/mmcblk0p14 (where the rfs is) but the actual partition offset (linuxroot) might not be right - how can I find the exact offset of a nand partition?

01:37 <bashintosh> I know the block size of such partition..

04:40 <steev> bashintosh: it's possible you're missing an option

04:41 <steev> iirc, most kernels default to 8 partitions max, and you have to enable something to show more than that

04:47 <bashintosh> steev: I thought about that and ended up modifying the partition layout so that the rfs lives in mmcblk0p3 - interesting enough the kernel during boot can see all partitions defined in the parameter (resource, kernel, boot, linuxroot) and their proper size. It hits the same error where it logs "rknand init:" next line "UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (1)"

04:49 <bashintosh> tried different options in the parameter (root=<args>) but the kernel still looks for mmcblk0p1 (which actually contains the kernel if mmcblk0p0 is resource)

04:49 <bashintosh> tried different bootloaders too... Same result. Curious really..

04:50 <bashintosh> the very same kernel boots fine when flashed on SD (with rfs also on SD)

05:00 <bashintosh> I am missing CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER in my config - although the kernel boot prints exactly what the parameter contains. Mmmmh..

05:03 <bashintosh> Nah that's not it - the DTS default bootargs are "bootargs = "androidboot.console=ttyFIQ0 initrd=0x02000000,0x00800000";" so the kernel is definitely getting more parameters than just that, including console parameters etc.

05:48 <naobsd> RK u-boot can modify dtb before passing it to kernel

05:51 <naobsd> if you're using initramfs as 1st root fs and initramfs does switch_root to actual root fs, then you need to check initramfs too

08:38 <Ava> Hi all!

08:51 <Avagetto> Hello again, to all. Anybody have experience in launching ap6xxx wifi module with chromium kernel 3.14?

13:37 <naobsd> hmm some arc emac patches are merged in linux-next

13:49 <naobsd> https://github.com/geekboxzone/mmallow_u-boot/blob/47b3fdb17f548fe1aa86bd8ad6e9790571df48e9/board/rockchip/common/platform/chipDepend.c#L344 no uart2usb for rk322x...???

13:53 <naobsd> https://github.com/geekboxzone/mmallow_kernel/blob/6916ea035be6666f1f48bc4b87f70d65908c62df/drivers/usb/dwc_otg_310/usbdev_rk322x.c#L184 hmm it should be supported in kernel...

14:45 <naobsd> hmmm I cannot access uart on my rk3229 board... :(

22:32 <bashintosh> naobsd: I assume you have tried different UART settings? i.e. baud rate, parity etc.

22:33 <bashintosh> You should only need GND,TX,RX - what kind of UART interface are you using? TTL?