> resolve is the internal processing of the data. All the other drivers
> allocate a big chunk of memory (1 megabyte), turn the hex data into a
Bletch
> binary format, then free the hex data. However, when I tried that here,
> my kmalloc failed. Should I be using vmalloc for this operation?
Yo
> > binary format, then free the hex data. However, when I tried that here,
> > my kmalloc failed. Should I be using vmalloc for this operation?
>
> You can't kmalloc > 128Kbytes
>
> However before you waste 1Mb of kernel memory on Linux (which is non paged)
> perhaps you should put the firmware
> Does the memory that you put into the transfer_buffer pointer in an URB
> need to be alloced with kmalloc
yes
> - or can it be alloced with vmalloc?
no ... it'd be bat to let it page out during I/O. :)
___
[EMAIL PROTECTED]
To unsubscrib
On Wed, Dec 19, 2001 at 03:56:22PM -0500, [EMAIL PROTECTED] wrote:
>
> The actual loading of the DSP code into the driver isn't the issue I'm
> trying to resolve right now - I'm hoping by the time I need to resolve
> it, you folks will have hammered out the details of this firmware
> loading thre
I'm writing a network driver for a USB ADSL modem. I previously wrote
the Mac OS9 and Mac OSX drivers for this modem. The modem has a DSP that
requires code to be uploaded from the host PC. The modem does not have
enough memory to contain the entire DSP code, so throughout its various
stages of op
