From: Rod <Rod@Rods.id.au>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [Fwd: Change wording of DIFF file please]
Date: Fri, 09 May 2008 00:26:38 +1000 [thread overview]
Message-ID: <48230D9E.3010104@Rods.id.au> (raw)
In-Reply-To: <d9def9db0805071624j62836409jb7a24a3153c1df9e@mail.gmail.com>
Markus Rechberger wrote:
> Hey,
>
> On 5/8/08, Rod <Rod@rods.id.au> wrote:
>
>> Repost as I think I fell off the list ;o(
>>
>>
>
> this stuff was generated against my v4l-dvb-experimental repository it seems.
>
> + }
> + break;
> + case TUNER_XCEIVE_XC3028:
> + dprintk(KERN_INFO "saa7134_tuner_callback TUNER_XCEIVE_XC3028
> command %d\n", command);
> + switch(command) {
> + case TUNER_RESET1:
> + case TUNER_RESET2:
> + /* this seems to be to correct bit */
> + saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x00008000, 0x00000000);
> + saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x00008000, 0x00008000);
> + break;
> +
> + case TUNER_RESET3:
> + break;
>
> this also needs a change to work with the linuxtv repository, that way
> the patch is not compatible with the linuxtv.org repository it was
> generated against my v4l-dvb-experimental repository.
>
> You already have the xceive reset line bit. Look how other xc3028
> reset callbacks are implemented into the linuxtv.org repository and
> change this according to the other callbacks.
>
> Markus
>
Would I be able to get a little help with this please?
I know I may be asking a bit much, but I'm trying to learn this
stuff at the same time ;o)
Does the code already work in 2.6.25? or its only in V4L repos
building before submission into the linux tree?
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-05-08 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 22:35 [linux-dvb] [Fwd: Change wording of DIFF file please] Rod
2008-05-07 23:24 ` Markus Rechberger
2008-05-08 14:26 ` Rod [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48230D9E.3010104@Rods.id.au \
--to=rod@rods.id.au \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox