On 3/4/12 2:15 PM, Felix Fietkau wrote:
> On 2012-03-04 10:00 PM, Philip Prindeville wrote:
>> I'm trying to write some scripts to help out with debugging kernel traces, 
>> etc. for people who aren't used to doing such, trying to automate everything 
>> as much as possible.
>>
>> I've identified a need to use modinfo, but just selecting 
>> CONFIG_BUSYBOX_CONFIG_MODINFO=y doesn't do it since we don't build and 
>> install modules.dep in the kernel.
>>
>> root@OpenWrt:/# modinfo crc_ccitt
>> modinfo: can't open '/lib/modules/3.2.2/modules.dep': No such file or 
>> directory
>> root@OpenWrt:/#
>>
>> For, at most 100 modules or so, the file size shouldn't be too 
>> objectionable, and as a text file with a lot of repetition it should 
>> compress down well on the squashfs.
>>
>> Can we add support for this? It's a matter of building an external kernel 
>> target, right? modpost or whatever?
> What would you even need modinfo for? I've never needed it for debugging
> traces in kernel modules, nor do I think it should be enabled by default.
>
> - Felix

See the Alix thread about generating a "add-symbol-file ..." script 
automatically from modinfo + /proc/modules + sed...

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to