[lkml]   [1996]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Accessing copy_to_user() from interrupt handler?

> > holding 8k Pixels and it sends an interrupt when it is half full. I
> > have tried to wake up the process in the interrupt handler, but this
> > wasn't reliable under high load (sometimes the wakeup took to long and
> > the FIFO overflowed). Now I would like to try reading half a FIFO
> You probably want to buffer the data in the kernel, then the mlock isnt
> a problem (its up to the user).
> > worth of data from the card and copy it to the mlock()'d user buffer
> > directly in the interrupt handler. Is this possible at all, or do I
> Its 'entertaining'. The ATM folks have played with this a bit. Another
> approach is to make the device mmap()able and map the kernel CCD buffer
> into user space.
> Alan

These are the methods used by the Matrox Meteor driver. It allocates
space in the kernel using Matt Welsh's bigphysarea patch (any hope
of getting this functionallity in 2.1.x?) and then makes that memory
mmap'able by the user process.

In this case the bigphysarea patch was needed instead of just vmalloc
because of DMA requirements.


 \ /
  Last update: 2005-03-22 13:38    [W:0.100 / U:0.720 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site