| 11:42 | topi` | make -j10 zImage dtbs |
| 11:43 | topi` | I hpe the "dtbs" rule captures all relevant .dtb files? like the -v15-som.dtb? |
| 11:45 | topi` | jnettlet: are you aware that with the 3.14.60-sr kernel, the v15 som eMMC gets detected but fails with error -22? the reason probalby is "unrecognised EXT_CSD revision 8" |
| 12:12 | topi` | jnettlet: I can report that now after I cleanly compiled a freshly cloned 4.11-rc5 tree from linus, and applied the 4 patches, I can now see both mmc1 and mmc2 |
| 12:12 | topi` | the mmcblk2 has some funny partitions, like mmcblk2rpmb and mmcblk2boot0 |
| 12:18 | topi` | the eMMC is quite fast; I was able to dd 2 gigabytes off of it at 83.7 MB/s |
| 12:18 | topi` | I have a Kingston mSATA ssd that only does about 120MB/s |
| 12:20 | jnettlet | topi`, that sounds about right |
| 12:20 | jnettlet | emmc is slowly catching up |
| 12:21 | topi` | modprobe wl18xx did not bring anything to dmesg... |
| 12:21 | topi` | hmm, maybe I'm missing cfg80211 or other modules? |
| 12:22 | jnettlet | topi`, that should be automatically detected if the device-tree has the device enabled |
| 12:23 | topi` | ah! that might be it |
| 12:23 | topi` | since I just symlinked the imx6q .dtb to -som-v15.dtb |
| 12:24 | topi` | I'll check what dmesg has to say about the sdio devices |
| 12:51 | topi` | jnettlet: do you know how this "mmcblk2boot0" scheme affects how the imx6 BootROM code sees bytes off of the emmc? |
| 12:51 | topi` | I mean, does linux see the same bytes at offset 0x400 as the BootROM? |
| 12:52 | topi` | seems like this mmcblk2boot0 device is tailor-made for writing those SPL bytes |
| 13:06 | vpeter | On one other system I put whole u-boot there (there is no SPL for it). And before writing to it it needs to be put in rw mode. |
| 13:07 | topi` | jnettlet: do you know how this "mmcblk2boot0" scheme affects how the imx6 BootROM code sees bytes off of the emmc? |
| 13:07 | topi` | vpeter: was this a Hummingboard or any other i.mx6 device? |
| 13:11 | vpeter | no, it is some other device (not from solidrun). |
| 13:11 | topi` | this behaviour of loading the SPL from (device + 0x400) is particular to i.mx6 chips |
| 13:20 | topi` | I'm not entirely sure if I write the SPL and uboot to their offsets to mmcblk2, that the BootROM sees it the same way? |
| 13:20 | topi` | this is particularly problematic if we eFuse the virgin board to boot from eMMC after writing |
| 13:23 | vpeter | Little to much for me :) |
| 16:22 | topi` | is there any way to find out why wlan0 doesn't show up? and why modprobe wl18xx gives ntohing on dmesg? |
| 16:22 | topi` | I tried to look for hints in /sys/kernel/debug but found nothing... |