summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@infradead.org>2007-09-19 01:44:18 -0400
committerMauro Carvalho Chehab <mchehab@infradead.org>2007-09-19 01:44:18 -0400
commit8df59213e66592abbfeba4cdc595aac994dfce7a (patch)
tree79ea79458e4a779026e3f7ee22a860c77ce9b2c7 /COPYING
parent845d1d0003ba257568ca49628085f11463c5b8db (diff)
downloadmediapointer-dvb-s2-8df59213e66592abbfeba4cdc595aac994dfce7a.tar.gz
mediapointer-dvb-s2-8df59213e66592abbfeba4cdc595aac994dfce7a.tar.bz2
cafe_ccic: default to allocating DMA buffers at probe time
From: Andres Salomon <dilinger@queued.net> By default, we allocate DMA buffers when actually reading from the video capture device. On a system with 128MB or 256MB of ram, it's very easy for that memory to quickly become fragmented. We've had users report having 30+MB of memory free, but the cafe_ccic driver is still unable to allocate DMA buffers. Our workaround has been to make use of the 'alloc_bufs_at_load' parameter to allocate DMA buffers during device probing. This patch makes DMA buffer allocation happen during device probe by default, and changes the parameter to 'alloc_bufs_at_read'. The camera hardware is there, if the cafe_ccic driver is enabled/loaded it should do its best to ensure that the camera is actually usable; delaying DMA buffer allocation saves an insignicant amount of memory, and causes the driver to be much less useful. Signed-off-by: Andres Salomon <dilinger@debian.org> Acked-by: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions