Messages in this thread | | | Date | Sun, 17 May 1998 21:10:20 -0400 (EDT) | From | "Albert D. Cahalan" <> | Subject | Re: some tiny and dumb questions |
| |
C. Scott Ananian writes:
> firmware should be linked directly into the module. > It's fairly simple to write a tool that translates an > arbitrary binary file into an equivalent C array declaration...
I've always wondered why we need to do that. Couldn't we just create a .o file directly? The base name of the input file would be a good choice for the symbol name.
Another thought: is there a way to keep all the symbol names with the kernel and make that data itself available? When I get some time, I'd like to put full symbol information in the kernel like most other modern unix systems do.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |