> Which kernel version of the visor driver are you looking at?
> The most recent one does not call kmalloc in the write() call (well ok,
> the call is still there, but it never gets executed, as the urb transfer
> buffers all get set up in the visor_init() function. I should just
> remove it, but
Title: À̱¤°í¸ÞÀÏÀº´õÀÌ»ó¹ß¼ÛÇÏÁö¾Ê½À´Ï´Ù
ÀÌ ±¤°í ¸ÞÀÏÀº È«º¸¿ëÀ¸·Î
1ȸ ÀÌ»ó
¹ß¼ÛÇÏÁö ¾Ê½À´Ï´Ù ±¤°í
¸ÞÀÏÀÌ ºÒÄèÇϼ̴ٸé Á¤ÁßÈ÷ »ç°úµå¸³´Ï´Ù
¾È³çÇϼ¼¿ä±ÍÇÏÀÇ À̸ÞÀÏÀº °ø°³
À¥ »çÀÌÆ®¿¡¼ ¼öÁýÇÏ¿´À¸¸ç, °ø°³µÈ
À̸ÞÀÏ ¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö
¾Ê½À´Ï´Ù
On Fri, Dec 14, 2001 at 07:01:23PM +0530, V Ganesh wrote:
> hi,
> I've been developing a usb driver for the ipaq running wince. I ran
> into some trouble which, I think, potentially affects the visor driver as well.
> visor_write() calls kmalloc(..., GFP_KERNEL). I did the same thing and got
hi,
I've been developing a usb driver for the ipaq running wince. I ran
into some trouble which, I think, potentially affects the visor driver as well.
visor_write() calls kmalloc(..., GFP_KERNEL). I did the same thing and got
hit by a BUG() in kmem_cache_grow().
if (in_interrupt(
> > > manage dynamic loading of different overlaid firmware
> > > images at runtime
> >
> > Are there devices that really do that ?
>
> Yep. Right here in front of me ;-)
But are there are _products_ that do this and don't bother to
implement it as regular bank switching hardware? Last time
I
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
On Thu, 13 Dec 2001 [EMAIL PROTECTED] wrote:
> > Absolutely. But note, that is not the only problem: If the driver has to
> > manage dynamic loading of different overlaid firmware images at runtime
>
> Are there devices that really do that ?
Yep. Right here in front of me ;-)
Note that the Cypr
