> e ksymoops to figure out where your code is oopsing. See > Documentation/oops-tracing.txt for more info on doing this.
Thanks for that info ... this is my first dive into kernel debugging. > But again, I don't see why you have to allocate these large amounts of > memory. If you already have the data in memory, just copy it in small > chunks, like the usb-serial drivers do. Trust me, for now I need to do this. A short explanation attempt .... we have a hex/text format of DSP memory. However, the DSP obviously wants us to send him memory blocks in a binary format. So, the first thing we do is we create a virtual picture of the DSP's entire memory by allocating a large chunk of memory and creating the binary form from the hex form (the hex/text code is actually Motorolla S-record format). We then setup arrays of structures that define the various blocks of DSP memory in the big chunk. These represent our memory map of our copy of the DSP memory. That way when the DSP says "send me swap page 28", we know where it is in the big chunk, and how big it is. -Chris _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
