Thanks for confirming William. Yeah it was working on 3.14 for me also. I had too many other problems with 3.14 (mainly SPI devices) and had to revert back to 3.8. Now I am seeing this oddity.
On Sunday, January 11, 2015 at 1:58:36 AM UTC-6, William Hermans wrote: > > And yeah, this is for 3.14.x, but I'd get the same result for 3.8.x as > well. . . > > On Sun, Jan 11, 2015 at 12:56 AM, William Hermans <yyr...@gmail.com > <javascript:>> wrote: > >> *Could someone at least confirm that I should be able to see device files >>> /dev/mmc0* and /dev/mmc1* for both the eMMC and an SD card assuming both >>> are present? It seems like the 3.8 kernel is playing hanky panky with >>> these mmc devices.* >>> >> >> root@beaglebone:~# lsblk >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>> mmcblk1boot0 179:16 0 1M 1 disk >>> mmcblk1boot1 179:24 0 1M 1 disk >>> mmcblk0 179:0 0 3.7G 0 disk >>> `-mmcblk0p1 179:1 0 1.7G 0 part / >>> mmcblk1 179:8 0 1.8G 0 disk >>> |-mmcblk1p1 179:9 0 70.6M 0 part >>> `-mmcblk1p2 179:10 0 1.7G 0 part >>> root@beaglebone:~# uname -a >>> Linux beaglebone 3.14.26-ti-r39 #1 SMP PREEMPT Mon Dec 8 04:56:09 UTC >>> 2014 armv7l GNU/Linux >>> >> >> So, it is /dev/mmcblkX not /dev/mmcX, anyway ls -l /sys/bus/mmc/devices >> works fine n this end, I'd say you have a problem. Exactly what ? No idea . >> . . >> >> On Sat, Jan 10, 2015 at 9:44 PM, Dallas Clement <dallas.a...@gmail.com >> <javascript:>> wrote: >> >>> Could someone at least confirm that I should be able to see device files >>> /dev/mmc0* and /dev/mmc1* for both the eMMC and an SD card assuming both >>> are present? It seems like the 3.8 kernel is playing hanky panky with >>> these mmc devices. >>> >>> On Wednesday, January 7, 2015 at 3:01:58 PM UTC-6, Dallas Clement wrote: >>>> >>>> I've got a beagle bone black which is booting a self built 3.8 kernel >>>> over TFTP / NFS. The kernel source is from (https://github.com/ >>>> beagleboard/linux.git). For some reason, I am not able to see a mmc >>>> block device assigned. The cape manager sees it and assigns it to a slot. >>>> >>>> But ls -l /sys/bus/mmc/devices does not show anything. >>>> >>>> However, if I insert a SD card, I am able to see a block mmc device >>>> assigned for it. I would like to be able to mount the eMMC device. >>>> >>>> Am I missing something? I was assuming that both the eMMC and the SD >>>> would have corresponding mmc block devices assigned by the driver. >>>> >>>> >>>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard...@googlegroups.com <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
