Linux

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • v4l2 porting of a USB device driver

    0 answers - 917 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    >The bug is around VIDIC_QBUF (FIF buffer queuing)/VIDIC_DQBUF (FIF
    >buffer dequeuing).
    >I don't know when to change the state of frames (frame->grabstate), and
    >usbvision->curFrameNum too, and I think this is what breaks the code.
    >I did not touch the decompression algorithm so this may not the problem.
    >For the controls, I send the request to the I2C clients directly without
    >controling the range.

    I did confirm that the decompression is running when a device is used. So I think your right about
    VIDIC_QBUF needs some love.

    >I have no such error messages and I have a saa7113 decoder. Fortunately
    >the saa7115 configures the decoder with default values. Another bug to
    >find

    Looks like it's just the range and values of the controls. Not a big issue.
    Dwaine

Re: v4l2 porting of a USB device driver


max 4000 letters.
Your nickname that display:
In order to stop the spam: 4 + 3 =
QUESTION ON "Linux"

EMSDN.COM