Hi Giuseppe, On Fri, Oct 28 2011, Giuseppe CAVALLARO wrote: > On 10/27/2011 4:19 PM, Sebastian Rasmussen wrote: >> Hi! >> >>> Before the patch the output from /sys/kernel/debug/mmc0/mmc0:0001/ext_csd >>> was a big number and I had many problems parsing it in real-time. >>> [...] >>> In any case, the patch wants to help to directly get the ext_csd in a >>> human format. >> >> Yes, I realize this. However I'm unsure whether this parsing should be >> done in kernelspace at all. If your patch is accepted then it is obvious >> that people think this belongs in kernelspace rather than in userspace. > > I've found really useful to have this kind of parsing in Kernel space > because, fortunately, we are also using the kernel to validate the HW on > our platforms.
sysfs has a strict one-value-per-file rule which this patch breaks, but I can see putting something like this in debugfs instead. I'm wary of committing to maintaining a parser for this information in the kernel, though -- does anyone have advice on where this ought to be done? I wonder if we should start an MMC userspace tools repository containing code for features like the cmd passthrough ioctl, secure erase/trim/discard requests, and debugging output of the type this patch provides. On the other hand, maybe existing similar tools should just be modified to learn about how to deal with MMC? Thanks, - Chris. -- Chris Ball <c...@laptop.org> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
