mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-28 18:51:56 -04:00
Merge branch 'for-linus2' of git://git.profusion.mobi/users/lucas/linux-2.6
* 'for-linus2' of git://git.profusion.mobi/users/lucas/linux-2.6: Fix common misspellings
This commit is contained in:
commit
42933bac11
2463 changed files with 4249 additions and 4249 deletions
|
|
@ -172,7 +172,7 @@ Source file list / functional overview:
|
|||
to provide a streaming API usable by a read() system call style of
|
||||
I/O. Right now this is the only layer on top of pvrusb2-io.[ch],
|
||||
however the underlying architecture here was intended to allow for
|
||||
other styles of I/O to be implemented with additonal modules, like
|
||||
other styles of I/O to be implemented with additional modules, like
|
||||
mmap()'ed buffers or something even more exotic.
|
||||
|
||||
pvrusb2-main.c - This is the top level of the driver. Module level
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ If you have trouble with some specific TV card, try to ask there
|
|||
instead of mailing me directly. The chance that someone with the
|
||||
same card listens there is much higher...
|
||||
|
||||
For problems with sound: There are alot of different systems used
|
||||
For problems with sound: There are a lot of different systems used
|
||||
for TV sound all over the world. And there are also different chips
|
||||
which decode the audio signal. Reports about sound problems ("stereo
|
||||
does'nt work") are pretty useless unless you include some details
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ state is stuck.
|
|||
|
||||
I've seen reports that bttv 0.7.x crashes whereas 0.8.x works rock solid
|
||||
for some people. Thus probably a small buglet left somewhere in bttv
|
||||
0.7.x. I have no idea where exactly, it works stable for me and alot of
|
||||
0.7.x. I have no idea where exactly, it works stable for me and a lot of
|
||||
other people. But in case you have problems with the 0.7.x versions you
|
||||
can give 0.8.x a try ...
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
bttv and sound mini howto
|
||||
=========================
|
||||
|
||||
There are alot of different bt848/849/878/879 based boards available.
|
||||
There are a lot of different bt848/849/878/879 based boards available.
|
||||
Making video work often is not a big deal, because this is handled
|
||||
completely by the bt8xx chip, which is common on all boards. But
|
||||
sound is handled in slightly different ways on each board.
|
||||
|
|
|
|||
|
|
@ -84,12 +84,12 @@ DMA usage
|
|||
transfer is not started. On "End Of Frame" interrupt, the irq handler
|
||||
starts the DMA chain.
|
||||
- capture of one videobuffer
|
||||
The DMA chain starts transfering data into videobuffer RAM pages.
|
||||
When all pages are transfered, the DMA irq is raised on "ENDINTR" status
|
||||
The DMA chain starts transferring data into videobuffer RAM pages.
|
||||
When all pages are transferred, the DMA irq is raised on "ENDINTR" status
|
||||
- finishing one videobuffer
|
||||
The DMA irq handler marks the videobuffer as "done", and removes it from
|
||||
the active running queue
|
||||
Meanwhile, the next videobuffer (if there is one), is transfered by DMA
|
||||
Meanwhile, the next videobuffer (if there is one), is transferred by DMA
|
||||
- finishing the last videobuffer
|
||||
On the DMA irq of the last videobuffer, the QCI is stopped.
|
||||
|
||||
|
|
@ -101,7 +101,7 @@ DMA usage
|
|||
|
||||
This structure is pointed by dma->sg_cpu.
|
||||
The descriptors are used as follows :
|
||||
- desc-sg[i]: i-th descriptor, transfering the i-th sg
|
||||
- desc-sg[i]: i-th descriptor, transferring the i-th sg
|
||||
element to the video buffer scatter gather
|
||||
- finisher: has ddadr=DADDR_STOP, dcmd=ENDIRQEN
|
||||
- linker: has ddadr= desc-sg[0] of next video buffer, dcmd=0
|
||||
|
|
|
|||
|
|
@ -343,7 +343,7 @@ ignored. If you want to check for errors use this:
|
|||
err = v4l2_device_call_until_err(v4l2_dev, 0, core, g_chip_ident, &chip);
|
||||
|
||||
Any error except -ENOIOCTLCMD will exit the loop with that error. If no
|
||||
errors (except -ENOIOCTLCMD) occured, then 0 is returned.
|
||||
errors (except -ENOIOCTLCMD) occurred, then 0 is returned.
|
||||
|
||||
The second argument to both calls is a group ID. If 0, then all subdevs are
|
||||
called. If non-zero, then only those whose group ID match that value will
|
||||
|
|
|
|||
Loading…
Reference in a new issue