Bill Dirks wrote:
> V4L2 has multiple opens per device, and it doesn't require passing
> file*s to drivers.
I've checked how v4l2 does it.
> That lets drivers remain decoupled from struct file
> (which they shouldn't care about anyway), and it lets file->private_data
> remain available for use by videodev.o.
Ah, that's why. I've wondered why it is done this way because right now
videodev2 does not use file->private_data itself but simply passes it down.
But this way it can be changed later without breaking the drivers. Ok,
I can see the point.
Gerd
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
- Grabbing frame off of capturing video Richard Eppes
- Re: Grabbing frame off of capturing video Gerd Knorr
- Re: Grabbing frame off of capturing video Alan Cox
- Re: Grabbing frame off of capturing video Gerd Knorr
- Re: Grabbing frame off of capturing video... scottrus
- Re: Grabbing frame off of capturing video Bill Dirks
- Why not use v4l2? (was: Grabbing fra... Gerd Knorr
- Why not use v4l2? (was: Grabbing frame of... Michael Hunold
- Re: Why not use v4l2? (was: Grabbing... Gerd Knorr
- Re: Why not use v4l2? (was: Grab... Michael Hunold
- Re: Why not use v4l2? (was: ... Gerd Knorr
- Re: Why not use v4l2? (was: ... Michael Schimek
- Re: Why not use v4l2? (was: ... Alan Cox
- Re: Why not use v4l2? (was: ... Gerd Knorr
- Re: Why not use v4l2? (was: ... Michael Schimek
- From the fellow that gave us... David VanHorn
- Re: Why not use v4l2? (was: ... Gerd Knorr
