On Mon, 2010-09-13 at 14:06 +0200, ext Hans Verkuil wrote: > On Monday, September 13, 2010 13:59:30 Matti J. Aaltonen wrote: > > On Mon, 2010-09-13 at 13:51 +0200, ext Hans Verkuil wrote: > > > On Monday, September 13, 2010 13:44:31 Matti J. Aaltonen wrote: > > > > On Mon, 2010-09-13 at 13:32 +0200, ext Hans Verkuil wrote: > > > > > > Anyway the difference between the "completely raw bits" and the "raw" > > > > > > blocks is small. And I doubt the usefulness of supporting the > > > > > > "completely raw" format. > > > > > > > > > > I don't intend to support it now. But we need to realize that it exists and > > > > > we have to plan for it. > > > > > > > > OK. So we can have RDS_RAW_READWRITE and also RDS_RAW_BLOCK_READWRITE > > > > (or something to the same effect)? > > > > > > In theory, yes. My proposed API additions allow for this to be added in the > > > future. Frankly, I don't think it is likely that it will be needed, but you > > > never know. > > > > Yes but I would like to add the RDS_RAW_BLOCK_READWRITE possibility > > right away because that's what the wl1273 driver does now... I guess > > that's OK? > > Well, yeah. That's what I proposed with the new tuner caps: OK, I didn't fully get that... sorry... > V4L2_TUNER_CAP_RDS_READWRITE 0x0100 Use read()/write() > V4L2_TUNER_CAP_RDS_CONTROLS 0x0200 Use RDS controls But now I see:-) We'll have: V4L2_TUNER_CAP_RDS_BLOCKS read()/write() V4L2_TUNER_CAP_RDS_CONTROLS RDS controls V4L2_TUNER_CAP_RDS_RAW also read()/write() B.R. Matti. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
