Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: > Alex, it's still hit and miss getting this card detected. I had to > insert/remove the card over 10 times with random driver load/unloads > until it created the device entries.. And for me it's still worse, no matter what I try with 2.6.20: speedy:~ # find /sys/devices | grep tifm /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3 /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/mmc_host:mmc0 /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/driver /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/bus /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/subsystem /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/power /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/power/wakeup /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/uevent speedy:~ # find /sys/block | grep mmc speedy:~ # -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Brad Campbell wrote: [EMAIL PROTECTED]:/sys/block/mmcblk0$ ls -laR .: total 0 drwxr-xr-x 6 root root0 2007-02-11 23:29 . drwxr-xr-x 13 root root0 2007-02-11 23:27 .. -r--r--r-- 1 root root 4096 2007-02-11 23:28 dev lrwxrwxrwx 1 root root0 2007-02-11 23:27 device -> ../../class/mmc_host/mmc0/mmc0:b368 Is this with CONFIG_SYSFS_DEPRECATED off? It should be pointing to the ../../devices tree. Rgds No, it's currently on. I'll recompile and do a dump with it off this evening. Either way, it's still broken and in 2.6.19 it wasn't. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: > [EMAIL PROTECTED]:/sys/block/mmcblk0$ ls -laR > .: > total 0 > drwxr-xr-x 6 root root0 2007-02-11 23:29 . > drwxr-xr-x 13 root root0 2007-02-11 23:27 .. > -r--r--r-- 1 root root 4096 2007-02-11 23:28 dev > lrwxrwxrwx 1 root root0 2007-02-11 23:27 device -> > ../../class/mmc_host/mmc0/mmc0:b368 Is this with CONFIG_SYSFS_DEPRECATED off? It should be pointing to the ../../devices tree. Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: [EMAIL PROTECTED]:/sys/block/mmcblk0$ ls -laR .: total 0 drwxr-xr-x 6 root root0 2007-02-11 23:29 . drwxr-xr-x 13 root root0 2007-02-11 23:27 .. -r--r--r-- 1 root root 4096 2007-02-11 23:28 dev lrwxrwxrwx 1 root root0 2007-02-11 23:27 device - ../../class/mmc_host/mmc0/mmc0:b368 Is this with CONFIG_SYSFS_DEPRECATED off? It should be pointing to the ../../devices tree. Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Brad Campbell wrote: [EMAIL PROTECTED]:/sys/block/mmcblk0$ ls -laR .: total 0 drwxr-xr-x 6 root root0 2007-02-11 23:29 . drwxr-xr-x 13 root root0 2007-02-11 23:27 .. -r--r--r-- 1 root root 4096 2007-02-11 23:28 dev lrwxrwxrwx 1 root root0 2007-02-11 23:27 device - ../../class/mmc_host/mmc0/mmc0:b368 Is this with CONFIG_SYSFS_DEPRECATED off? It should be pointing to the ../../devices tree. Rgds No, it's currently on. I'll recompile and do a dump with it off this evening. Either way, it's still broken and in 2.6.19 it wasn't. Brad -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: Alex, it's still hit and miss getting this card detected. I had to insert/remove the card over 10 times with random driver load/unloads until it created the device entries.. And for me it's still worse, no matter what I try with 2.6.20: speedy:~ # find /sys/devices | grep tifm /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3 /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/mmc_host:mmc0 /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/driver /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/bus /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/subsystem /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/power /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/power/wakeup /sys/devices/pci:00/:00:14.4/:03:09.3/tifm_sd0:3/uevent speedy:~ # find /sys/block | grep mmc speedy:~ # -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Brad Campbell wrote: [EMAIL PROTECTED]:/$ find sys/devices | grep mmc sys/devices/pci:00/:00:1e.0/:06:05.3/tifm_sd0:3/mmc_host:mmc0 This is strange. You should be getting more entries below that. I believe that should be the case.. /sys/block/mmcblk0/device [EMAIL PROTECTED]:/sys/block/mmcblk0$ ls -laR .: total 0 drwxr-xr-x 6 root root0 2007-02-11 23:29 . drwxr-xr-x 13 root root0 2007-02-11 23:27 .. -r--r--r-- 1 root root 4096 2007-02-11 23:28 dev lrwxrwxrwx 1 root root0 2007-02-11 23:27 device -> ../../class/mmc_host/mmc0/mmc0:b368 drwxr-xr-x 2 root root0 2007-02-11 23:27 holders drwxr-xr-x 3 root root0 2007-02-11 23:29 mmcblk0p1 drwxr-xr-x 3 root root0 2007-02-11 23:27 queue -r--r--r-- 1 root root 4096 2007-02-11 23:29 range -r--r--r-- 1 root root 4096 2007-02-11 23:27 removable -r--r--r-- 1 root root 4096 2007-02-11 23:29 size drwxr-xr-x 2 root root0 2007-02-11 23:27 slaves -r--r--r-- 1 root root 4096 2007-02-11 23:29 stat lrwxrwxrwx 1 root root0 2007-02-11 23:27 subsystem -> ../../block --w--- 1 root root 4096 2007-02-11 23:29 uevent ./holders: total 0 drwxr-xr-x 2 root root 0 2007-02-11 23:27 . drwxr-xr-x 6 root root 0 2007-02-11 23:29 .. ./mmcblk0p1: total 0 drwxr-xr-x 3 root root0 2007-02-11 23:29 . drwxr-xr-x 6 root root0 2007-02-11 23:29 .. -r--r--r-- 1 root root 4096 2007-02-11 23:29 dev drwxr-xr-x 2 root root0 2007-02-11 23:27 holders -r--r--r-- 1 root root 4096 2007-02-11 23:29 size -r--r--r-- 1 root root 4096 2007-02-11 23:29 start -r--r--r-- 1 root root 4096 2007-02-11 23:29 stat lrwxrwxrwx 1 root root0 2007-02-11 23:29 subsystem -> ../../../block --w--- 1 root root 4096 2007-02-11 23:29 uevent ./mmcblk0p1/holders: total 0 drwxr-xr-x 2 root root 0 2007-02-11 23:27 . drwxr-xr-x 3 root root 0 2007-02-11 23:29 .. ./queue: total 0 drwxr-xr-x 3 root root0 2007-02-11 23:27 . drwxr-xr-x 6 root root0 2007-02-11 23:29 .. drwxr-xr-x 2 root root0 2007-02-11 23:27 iosched -r--r--r-- 1 root root 4096 2007-02-11 23:29 max_hw_sectors_kb -rw-r--r-- 1 root root 4096 2007-02-11 23:29 max_sectors_kb -rw-r--r-- 1 root root 4096 2007-02-11 23:29 nr_requests -rw-r--r-- 1 root root 4096 2007-02-11 23:29 read_ahead_kb -rw-r--r-- 1 root root 4096 2007-02-11 23:29 scheduler ./queue/iosched: total 0 drwxr-xr-x 2 root root0 2007-02-11 23:27 . drwxr-xr-x 3 root root0 2007-02-11 23:29 .. -rw-r--r-- 1 root root 4096 2007-02-11 23:29 back_seek_max -rw-r--r-- 1 root root 4096 2007-02-11 23:29 back_seek_penalty -rw-r--r-- 1 root root 4096 2007-02-11 23:29 fifo_expire_async -rw-r--r-- 1 root root 4096 2007-02-11 23:29 fifo_expire_sync -rw-r--r-- 1 root root 4096 2007-02-11 23:29 quantum -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_async -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_async_rq -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_idle -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_sync ./slaves: total 0 drwxr-xr-x 2 root root 0 2007-02-11 23:27 . drwxr-xr-x 6 root root 0 2007-02-11 23:29 .. [EMAIL PROTECTED]:/sys/block/mmcblk0$ cd device [EMAIL PROTECTED]:/sys/block/mmcblk0/device$ ls -laR .: total 0 drwxr-xr-x 3 root root0 2007-02-11 23:30 . drwxr-xr-x 4 root root0 2007-02-11 23:27 .. lrwxrwxrwx 1 root root0 2007-02-11 23:30 block:mmcblk0 -> ../../../../block/mmcblk0 lrwxrwxrwx 1 root root0 2007-02-11 23:30 bus -> ../../../../bus/mmc -r--r--r-- 1 root root 4096 2007-02-11 23:30 cid -r--r--r-- 1 root root 4096 2007-02-11 23:30 csd -r--r--r-- 1 root root 4096 2007-02-11 23:30 date lrwxrwxrwx 1 root root0 2007-02-11 23:27 driver -> ../../../../bus/mmc/drivers/mmcblk -r--r--r-- 1 root root 4096 2007-02-11 23:30 fwrev -r--r--r-- 1 root root 4096 2007-02-11 23:30 hwrev -r--r--r-- 1 root root 4096 2007-02-11 23:30 manfid -r--r--r-- 1 root root 4096 2007-02-11 23:30 name -r--r--r-- 1 root root 4096 2007-02-11 23:30 oemid drwxr-xr-x 2 root root0 2007-02-11 23:27 power -r--r--r-- 1 root root 4096 2007-02-11 23:30 scr -r--r--r-- 1 root root 4096 2007-02-11 23:30 serial lrwxrwxrwx 1 root root0 2007-02-11 23:27 subsystem -> ../../../../bus/mmc --w--- 1 root root 4096 2007-02-11 23:30 uevent ./power: total 0 drwxr-xr-x 2 root root0 2007-02-11 23:27 . drwxr-xr-x 3 root root0 2007-02-11 23:30 .. -rw-r--r-- 1 root root 4096 2007-02-11 23:30 wakeup Alex, it's still hit and miss getting this card detected. I had to insert/remove the card over 10 times with random driver load/unloads until it created the device entries.. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: > > [EMAIL PROTECTED]:/$ find sys/devices | grep mmc > sys/devices/pci:00/:00:1e.0/:06:05.3/tifm_sd0:3/mmc_host:mmc0 > This is strange. You should be getting more entries below that. > /sys/block/mmcblk0/device Where does this point? Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Brad Campbell wrote: I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. Works fine here. The device tree is: /sys/devices/pnp0/00:02/mmc0/mmc0:0001/block:mmcblk0/mmcblk0p1/ Ok, following from that on my machine currently... [EMAIL PROTECTED]:/$ ls /dev/mmc* /dev/mmcblk0 /dev/mmcblk0p1 [EMAIL PROTECTED]:/$ find sys/devices | grep mmc sys/devices/pci:00/:00:1e.0/:06:05.3/tifm_sd0:3/mmc_host:mmc0 [EMAIL PROTECTED]:/$ find /sys/block/ | grep mmc /sys/block/mmcblk0 /sys/block/mmcblk0/queue /sys/block/mmcblk0/queue/iosched /sys/block/mmcblk0/queue/iosched/slice_idle /sys/block/mmcblk0/queue/iosched/slice_async_rq /sys/block/mmcblk0/queue/iosched/slice_async /sys/block/mmcblk0/queue/iosched/slice_sync /sys/block/mmcblk0/queue/iosched/back_seek_penalty /sys/block/mmcblk0/queue/iosched/back_seek_max /sys/block/mmcblk0/queue/iosched/fifo_expire_async /sys/block/mmcblk0/queue/iosched/fifo_expire_sync /sys/block/mmcblk0/queue/iosched/quantum /sys/block/mmcblk0/queue/scheduler /sys/block/mmcblk0/queue/max_sectors_kb /sys/block/mmcblk0/queue/max_hw_sectors_kb /sys/block/mmcblk0/queue/read_ahead_kb /sys/block/mmcblk0/queue/nr_requests /sys/block/mmcblk0/mmcblk0p1 /sys/block/mmcblk0/mmcblk0p1/holders /sys/block/mmcblk0/mmcblk0p1/subsystem /sys/block/mmcblk0/mmcblk0p1/stat /sys/block/mmcblk0/mmcblk0p1/size /sys/block/mmcblk0/mmcblk0p1/start /sys/block/mmcblk0/mmcblk0p1/dev /sys/block/mmcblk0/mmcblk0p1/uevent /sys/block/mmcblk0/slaves /sys/block/mmcblk0/holders /sys/block/mmcblk0/subsystem /sys/block/mmcblk0/device /sys/block/mmcblk0/stat /sys/block/mmcblk0/size /sys/block/mmcblk0/removable /sys/block/mmcblk0/range /sys/block/mmcblk0/dev /sys/block/mmcblk0/uevent [EMAIL PROTECTED]:~$ zcat /proc/config.gz | grep CONFIG_SYSFS_DEPRECATED CONFIG_SYSFS_DEPRECATED=y [EMAIL PROTECTED]:~$ uname -a Linux bklaptop2 2.6.20-git4-bkc1 #5 Sat Feb 10 23:49:52 GST 2007 i686 GNU/Linux Not sure if any of this is relevant info, but none the less, I'm not a sysfs or hal guru. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: > > I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail > the same way. > hald reports that the device has no parent and decides to ignore it. > Works fine here. The device tree is: /sys/devices/pnp0/00:02/mmc0/mmc0:0001/block:mmcblk0/mmcblk0p1/ and hal correctly shows the same structure. > I've also tested both combinations against hal from ubuntu 6.06LTS and a > more recent version > > [EMAIL PROTECTED]:~$ hald --version > HAL package version: 0.5.8.1 > I'm using 0.5.9 here, but CONFIG_SYSFS_DEPRECATED should make it work with any ancient version of hal. Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Hi. I can see this problem too. I have CONFIG_SYSFS_DEPRECATED set. It happens only with SD cards, with MMC everything is OK. Fabio On 2/11/07, Brad Campbell <[EMAIL PROTECTED]> wrote: Pierre Ossman wrote: > Alex Dubov wrote: >> One more problem (you may already know about it) - I was contacted by somebody from the hald >> project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card >> insertion. I can't see anything in my code so this may be a general mmc problem. >> The problem is described here: >> http://lists.freedesktop.org/archives/hal/2007-January/006960.html >> > > Odd. This might be the whole sysfs restructuring thing causing problems. Can you > check if that user has CONFIG_SYSFS_DEPRECATED on? I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. I've also tested both combinations against hal from ubuntu 6.06LTS and a more recent version [EMAIL PROTECTED]:~$ hald --version HAL package version: 0.5.8.1 Again with and without CONFIG_SYSFS_DEPRECATED and all combinations fail. Hal appears to go looking for /sys/block/mmcblk0/mmcblk0p1/range When it can't find it, it then looks for the parent of that to check what would be /sys/block/mmcblk0/range, Complains it can't find a parent for /sys/block/mmcblk0/mmcblk0p1 and just proceeds to ignore the event. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Hi. I can see this problem too. I have CONFIG_SYSFS_DEPRECATED set. It happens only with SD cards, with MMC everything is OK. Fabio On 2/11/07, Brad Campbell [EMAIL PROTECTED] wrote: Pierre Ossman wrote: Alex Dubov wrote: One more problem (you may already know about it) - I was contacted by somebody from the hald project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card insertion. I can't see anything in my code so this may be a general mmc problem. The problem is described here: http://lists.freedesktop.org/archives/hal/2007-January/006960.html Odd. This might be the whole sysfs restructuring thing causing problems. Can you check if that user has CONFIG_SYSFS_DEPRECATED on? I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. I've also tested both combinations against hal from ubuntu 6.06LTS and a more recent version [EMAIL PROTECTED]:~$ hald --version HAL package version: 0.5.8.1 Again with and without CONFIG_SYSFS_DEPRECATED and all combinations fail. Hal appears to go looking for /sys/block/mmcblk0/mmcblk0p1/range When it can't find it, it then looks for the parent of that to check what would be /sys/block/mmcblk0/range, Complains it can't find a parent for /sys/block/mmcblk0/mmcblk0p1 and just proceeds to ignore the event. Brad -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. Works fine here. The device tree is: /sys/devices/pnp0/00:02/mmc0/mmc0:0001/block:mmcblk0/mmcblk0p1/ and hal correctly shows the same structure. I've also tested both combinations against hal from ubuntu 6.06LTS and a more recent version [EMAIL PROTECTED]:~$ hald --version HAL package version: 0.5.8.1 I'm using 0.5.9 here, but CONFIG_SYSFS_DEPRECATED should make it work with any ancient version of hal. Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Brad Campbell wrote: I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. Works fine here. The device tree is: /sys/devices/pnp0/00:02/mmc0/mmc0:0001/block:mmcblk0/mmcblk0p1/ Ok, following from that on my machine currently... [EMAIL PROTECTED]:/$ ls /dev/mmc* /dev/mmcblk0 /dev/mmcblk0p1 [EMAIL PROTECTED]:/$ find sys/devices | grep mmc sys/devices/pci:00/:00:1e.0/:06:05.3/tifm_sd0:3/mmc_host:mmc0 [EMAIL PROTECTED]:/$ find /sys/block/ | grep mmc /sys/block/mmcblk0 /sys/block/mmcblk0/queue /sys/block/mmcblk0/queue/iosched /sys/block/mmcblk0/queue/iosched/slice_idle /sys/block/mmcblk0/queue/iosched/slice_async_rq /sys/block/mmcblk0/queue/iosched/slice_async /sys/block/mmcblk0/queue/iosched/slice_sync /sys/block/mmcblk0/queue/iosched/back_seek_penalty /sys/block/mmcblk0/queue/iosched/back_seek_max /sys/block/mmcblk0/queue/iosched/fifo_expire_async /sys/block/mmcblk0/queue/iosched/fifo_expire_sync /sys/block/mmcblk0/queue/iosched/quantum /sys/block/mmcblk0/queue/scheduler /sys/block/mmcblk0/queue/max_sectors_kb /sys/block/mmcblk0/queue/max_hw_sectors_kb /sys/block/mmcblk0/queue/read_ahead_kb /sys/block/mmcblk0/queue/nr_requests /sys/block/mmcblk0/mmcblk0p1 /sys/block/mmcblk0/mmcblk0p1/holders /sys/block/mmcblk0/mmcblk0p1/subsystem /sys/block/mmcblk0/mmcblk0p1/stat /sys/block/mmcblk0/mmcblk0p1/size /sys/block/mmcblk0/mmcblk0p1/start /sys/block/mmcblk0/mmcblk0p1/dev /sys/block/mmcblk0/mmcblk0p1/uevent /sys/block/mmcblk0/slaves /sys/block/mmcblk0/holders /sys/block/mmcblk0/subsystem /sys/block/mmcblk0/device /sys/block/mmcblk0/stat /sys/block/mmcblk0/size /sys/block/mmcblk0/removable /sys/block/mmcblk0/range /sys/block/mmcblk0/dev /sys/block/mmcblk0/uevent [EMAIL PROTECTED]:~$ zcat /proc/config.gz | grep CONFIG_SYSFS_DEPRECATED CONFIG_SYSFS_DEPRECATED=y [EMAIL PROTECTED]:~$ uname -a Linux bklaptop2 2.6.20-git4-bkc1 #5 Sat Feb 10 23:49:52 GST 2007 i686 GNU/Linux Not sure if any of this is relevant info, but none the less, I'm not a sysfs or hal guru. Brad -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Brad Campbell wrote: [EMAIL PROTECTED]:/$ find sys/devices | grep mmc sys/devices/pci:00/:00:1e.0/:06:05.3/tifm_sd0:3/mmc_host:mmc0 This is strange. You should be getting more entries below that. /sys/block/mmcblk0/device Where does this point? Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Brad Campbell wrote: [EMAIL PROTECTED]:/$ find sys/devices | grep mmc sys/devices/pci:00/:00:1e.0/:06:05.3/tifm_sd0:3/mmc_host:mmc0 This is strange. You should be getting more entries below that. I believe that should be the case.. /sys/block/mmcblk0/device [EMAIL PROTECTED]:/sys/block/mmcblk0$ ls -laR .: total 0 drwxr-xr-x 6 root root0 2007-02-11 23:29 . drwxr-xr-x 13 root root0 2007-02-11 23:27 .. -r--r--r-- 1 root root 4096 2007-02-11 23:28 dev lrwxrwxrwx 1 root root0 2007-02-11 23:27 device - ../../class/mmc_host/mmc0/mmc0:b368 drwxr-xr-x 2 root root0 2007-02-11 23:27 holders drwxr-xr-x 3 root root0 2007-02-11 23:29 mmcblk0p1 drwxr-xr-x 3 root root0 2007-02-11 23:27 queue -r--r--r-- 1 root root 4096 2007-02-11 23:29 range -r--r--r-- 1 root root 4096 2007-02-11 23:27 removable -r--r--r-- 1 root root 4096 2007-02-11 23:29 size drwxr-xr-x 2 root root0 2007-02-11 23:27 slaves -r--r--r-- 1 root root 4096 2007-02-11 23:29 stat lrwxrwxrwx 1 root root0 2007-02-11 23:27 subsystem - ../../block --w--- 1 root root 4096 2007-02-11 23:29 uevent ./holders: total 0 drwxr-xr-x 2 root root 0 2007-02-11 23:27 . drwxr-xr-x 6 root root 0 2007-02-11 23:29 .. ./mmcblk0p1: total 0 drwxr-xr-x 3 root root0 2007-02-11 23:29 . drwxr-xr-x 6 root root0 2007-02-11 23:29 .. -r--r--r-- 1 root root 4096 2007-02-11 23:29 dev drwxr-xr-x 2 root root0 2007-02-11 23:27 holders -r--r--r-- 1 root root 4096 2007-02-11 23:29 size -r--r--r-- 1 root root 4096 2007-02-11 23:29 start -r--r--r-- 1 root root 4096 2007-02-11 23:29 stat lrwxrwxrwx 1 root root0 2007-02-11 23:29 subsystem - ../../../block --w--- 1 root root 4096 2007-02-11 23:29 uevent ./mmcblk0p1/holders: total 0 drwxr-xr-x 2 root root 0 2007-02-11 23:27 . drwxr-xr-x 3 root root 0 2007-02-11 23:29 .. ./queue: total 0 drwxr-xr-x 3 root root0 2007-02-11 23:27 . drwxr-xr-x 6 root root0 2007-02-11 23:29 .. drwxr-xr-x 2 root root0 2007-02-11 23:27 iosched -r--r--r-- 1 root root 4096 2007-02-11 23:29 max_hw_sectors_kb -rw-r--r-- 1 root root 4096 2007-02-11 23:29 max_sectors_kb -rw-r--r-- 1 root root 4096 2007-02-11 23:29 nr_requests -rw-r--r-- 1 root root 4096 2007-02-11 23:29 read_ahead_kb -rw-r--r-- 1 root root 4096 2007-02-11 23:29 scheduler ./queue/iosched: total 0 drwxr-xr-x 2 root root0 2007-02-11 23:27 . drwxr-xr-x 3 root root0 2007-02-11 23:29 .. -rw-r--r-- 1 root root 4096 2007-02-11 23:29 back_seek_max -rw-r--r-- 1 root root 4096 2007-02-11 23:29 back_seek_penalty -rw-r--r-- 1 root root 4096 2007-02-11 23:29 fifo_expire_async -rw-r--r-- 1 root root 4096 2007-02-11 23:29 fifo_expire_sync -rw-r--r-- 1 root root 4096 2007-02-11 23:29 quantum -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_async -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_async_rq -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_idle -rw-r--r-- 1 root root 4096 2007-02-11 23:29 slice_sync ./slaves: total 0 drwxr-xr-x 2 root root 0 2007-02-11 23:27 . drwxr-xr-x 6 root root 0 2007-02-11 23:29 .. [EMAIL PROTECTED]:/sys/block/mmcblk0$ cd device [EMAIL PROTECTED]:/sys/block/mmcblk0/device$ ls -laR .: total 0 drwxr-xr-x 3 root root0 2007-02-11 23:30 . drwxr-xr-x 4 root root0 2007-02-11 23:27 .. lrwxrwxrwx 1 root root0 2007-02-11 23:30 block:mmcblk0 - ../../../../block/mmcblk0 lrwxrwxrwx 1 root root0 2007-02-11 23:30 bus - ../../../../bus/mmc -r--r--r-- 1 root root 4096 2007-02-11 23:30 cid -r--r--r-- 1 root root 4096 2007-02-11 23:30 csd -r--r--r-- 1 root root 4096 2007-02-11 23:30 date lrwxrwxrwx 1 root root0 2007-02-11 23:27 driver - ../../../../bus/mmc/drivers/mmcblk -r--r--r-- 1 root root 4096 2007-02-11 23:30 fwrev -r--r--r-- 1 root root 4096 2007-02-11 23:30 hwrev -r--r--r-- 1 root root 4096 2007-02-11 23:30 manfid -r--r--r-- 1 root root 4096 2007-02-11 23:30 name -r--r--r-- 1 root root 4096 2007-02-11 23:30 oemid drwxr-xr-x 2 root root0 2007-02-11 23:27 power -r--r--r-- 1 root root 4096 2007-02-11 23:30 scr -r--r--r-- 1 root root 4096 2007-02-11 23:30 serial lrwxrwxrwx 1 root root0 2007-02-11 23:27 subsystem - ../../../../bus/mmc --w--- 1 root root 4096 2007-02-11 23:30 uevent ./power: total 0 drwxr-xr-x 2 root root0 2007-02-11 23:27 . drwxr-xr-x 3 root root0 2007-02-11 23:30 .. -rw-r--r-- 1 root root 4096 2007-02-11 23:30 wakeup Alex, it's still hit and miss getting this card detected. I had to insert/remove the card over 10 times with random driver load/unloads until it created the device entries.. Brad -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Alex Dubov wrote: One more problem (you may already know about it) - I was contacted by somebody from the hald project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card insertion. I can't see anything in my code so this may be a general mmc problem. The problem is described here: http://lists.freedesktop.org/archives/hal/2007-January/006960.html Odd. This might be the whole sysfs restructuring thing causing problems. Can you check if that user has CONFIG_SYSFS_DEPRECATED on? I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. I've also tested both combinations against hal from ubuntu 6.06LTS and a more recent version [EMAIL PROTECTED]:~$ hald --version HAL package version: 0.5.8.1 Again with and without CONFIG_SYSFS_DEPRECATED and all combinations fail. Hal appears to go looking for /sys/block/mmcblk0/mmcblk0p1/range When it can't find it, it then looks for the parent of that to check what would be /sys/block/mmcblk0/range, Complains it can't find a parent for /sys/block/mmcblk0/mmcblk0p1 and just proceeds to ignore the event. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Alex Dubov wrote: > One more problem (you may already know about it) - I was contacted by > somebody from the hald > project and indeed I can confirm that on 2.6.20 kernel hald fails to take > action on card > insertion. I can't see anything in my code so this may be a general mmc > problem. > The problem is described here: > http://lists.freedesktop.org/archives/hal/2007-January/006960.html > Odd. This might be the whole sysfs restructuring thing causing problems. Can you check if that user has CONFIG_SYSFS_DEPRECATED on? Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
One more problem (you may already know about it) - I was contacted by somebody from the hald project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card insertion. I can't see anything in my code so this may be a general mmc problem. The problem is described here: http://lists.freedesktop.org/archives/hal/2007-January/006960.html Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q http://answers.yahoo.com/dir/?link=list=396545367 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Pierre Ossman wrote: Alex Dubov wrote: One more problem (you may already know about it) - I was contacted by somebody from the hald project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card insertion. I can't see anything in my code so this may be a general mmc problem. The problem is described here: http://lists.freedesktop.org/archives/hal/2007-January/006960.html Odd. This might be the whole sysfs restructuring thing causing problems. Can you check if that user has CONFIG_SYSFS_DEPRECATED on? I've tested both with and without CONFIG_SYSFS_DEPRECATED on, both fail the same way. hald reports that the device has no parent and decides to ignore it. I've also tested both combinations against hal from ubuntu 6.06LTS and a more recent version [EMAIL PROTECTED]:~$ hald --version HAL package version: 0.5.8.1 Again with and without CONFIG_SYSFS_DEPRECATED and all combinations fail. Hal appears to go looking for /sys/block/mmcblk0/mmcblk0p1/range When it can't find it, it then looks for the parent of that to check what would be /sys/block/mmcblk0/range, Complains it can't find a parent for /sys/block/mmcblk0/mmcblk0p1 and just proceeds to ignore the event. Brad -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
One more problem (you may already know about it) - I was contacted by somebody from the hald project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card insertion. I can't see anything in my code so this may be a general mmc problem. The problem is described here: http://lists.freedesktop.org/archives/hal/2007-January/006960.html Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Recent and not-so problems with tifm_sd driver - one more
Alex Dubov wrote: One more problem (you may already know about it) - I was contacted by somebody from the hald project and indeed I can confirm that on 2.6.20 kernel hald fails to take action on card insertion. I can't see anything in my code so this may be a general mmc problem. The problem is described here: http://lists.freedesktop.org/archives/hal/2007-January/006960.html Odd. This might be the whole sysfs restructuring thing causing problems. Can you check if that user has CONFIG_SYSFS_DEPRECATED on? Rgds -- -- Pierre Ossman Linux kernel, MMC maintainerhttp://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
