Re: [linux-usb-devel] Memory error

2001-12-20 Thread chris . edgington
FYI, regarding my queries about the "unable to handle kernel paging request" error - turns out the code in question, while it has been used on multiple platforms - those platforms are all big-endian. There are some endian issues in the conversion of the motorolla data that need addressed when runn

Re: [linux-usb-devel] Memory error

2001-12-20 Thread Greg KH
On Thu, Dec 20, 2001 at 11:04:40AM -0500, [EMAIL PROTECTED] wrote: > > t do all of that processing beforehand, and create a large > > binary image in a .h file of your memory map. Then you have a static > > variable that is your memory map. So when the DSP asks for "swap page > > 'Cause the man

Re: [linux-usb-devel] Memory error

2001-12-20 Thread chris . edgington
> t do all of that processing beforehand, and create a large > binary image in a .h file of your memory map. Then you have a static > variable that is your memory map. So when the DSP asks for "swap page 'Cause the manufacturer of this modem wants to provide DSP firmware upgrades by delivering

Re: [linux-usb-devel] Memory error

2001-12-20 Thread Greg KH
On Thu, Dec 20, 2001 at 10:40:36AM -0500, [EMAIL PROTECTED] wrote: > > 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 t

Re: [linux-usb-devel] Memory error

2001-12-20 Thread chris . edgington
> 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

Re: [linux-usb-devel] Memory error

2001-12-20 Thread Greg KH
On Thu, Dec 20, 2001 at 09:25:07AM -0500, [EMAIL PROTECTED] wrote: > Ok, I changed my code to use vmalloc instead of kmalloc, which allowed > the code to proceed. My memory alloc sequence looks like this: > > alloc 0x10 bytes > alloc 0x000140 bytes > alloc 0x30 bytes > > The last alloc,

[linux-usb-devel] Memory error

2001-12-20 Thread chris . edgington
Ok, I changed my code to use vmalloc instead of kmalloc, which allowed the code to proceed. My memory alloc sequence looks like this: alloc 0x10 bytes alloc 0x000140 bytes alloc 0x30 bytes The last alloc, for 0x30 bytes, happens 39 times. Somewhere along the line, I get the following