pvrxxx, linux code and modules

[usleepless at gmail.com]

Jim,

On 4/16/07, Jim Stapleton <stapleton.41 at gmail.com> wrote:
> > On 4/16/07, Jim Stapleton <stapleton.41 at gmail.com> wrote:
> > > First, I'd like to say this is an interesting topic, and I'd like it
> > > to stay public if possible.
> >
> > fine!
>
> Ok, since context doesn't pass well over text, I hope I didn't say
> that one in an offensive manner (is the '!' an exasperation or a
> enthusiasm?)

enthousiasm. sorry for the ambiguity.

> > > I'd like to be able to keep an eye on this, and see if there's any way
> > > I can help or suggest if possible. (For example, I would like a
> > > tuner/input selector device that I could cat/echo commands into).
> >
> > why?
>
> It'd be nice to have a trivial form of control that doesn't need me to
> run any unusual commands.

i'll be straight about it right away: i don't feel like adding yet
another interface. pvrxxx is partly about adding v4l(2) support. so
now we have a bktr, meteor and v4l(2) interface to the device. i don't
want to add another. i'd rather remove bktr and meteor.

btw, which applications are able to read from pvrxxx devices using
these interfaces?

> Right now, I user the pvr250[I hit tab here] command, but if I could
> simply do an echo/redirection, it would feel a lot more natural to me
> I guess (more UNIXy), and since it would be interfacing the device
> directly, I wouldn't get the obnoxious bktr warnings.

if there are problems with the pvr250-setchannel command, these need
to be addressed. what errors are you getting?

i will consider any patches received.

regards,

usleep

>
>
> Thanks,
>
> -Jim
>