Werner Almesberger schrieb: > Nils Faerber wrote: >> I do not know what the aboive mdebus call fully does but it causes the >> card to be "ejected", which is in general fine. >> >> But the eth0 interface still remains to exist, which causes all kinds of >> nasty things to happen, e.g. > > Hmm, that's odd indeed. What's the HEAD of the kernel you're using ?
I am up-to-date on andy-tracking, if this is what you need to know. > Also, if someone could find out what that mdbus call does, that would > be useful. I am working on the mdebus part right now - I am not a Python neither a dbus expert so reading the code is pretty tough to me ;) I think it does something like echo "s3c2440-sdi" > /sys/bus/platform/drivers/s3c2440-sdi/bind for enabling and echo "s3c2440-sdi" > /sys/bus/platform/drivers/s3c2440-sdi/unbind for disabling. Very interesting! > - Werner Cheers nils faerber -- kernel concepts GbR Tel: +49-271-771091-12 Sieghuetter Hauptweg 48 Fax: +49-271-771091-19 D-57072 Siegen Mob: +49-176-21024535 http://www.kernelconcepts.de
