Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: devel

saa7115 devel

 

 

ivtv devel RSS feed   Index | Next | Previous | View Threaded


nufan_wfk at yahoo

Feb 7, 2003, 12:27 PM

Post #1 of 22 (5268 views)
Permalink
saa7115 devel

OK so i'm going through the i2c dumps.

Fill in the blanks (pvr250):
i2c addr = device

0x18 = Infrared
0x21 = saa7115
0x40 =
0x50 =
0x61 = tuner

i'm assuming the blanks are the audio chip the itvc
chip.

here's some questions for anyone familliar with i2c:

i see the following kinds of operations:
0xi2c_addr, read/write, register, data, data, ....

21,W,0A - write to a register with no data(?!)
21,r,88 - read the contents of a register
(byte?,word?)
21,W,0A,8E - write 0x83 to reg 0x0a
50,r,84,12,00,00 - read multiple data? explain?
40,W,12,00,13,0C,00 - write 4bytes to reg 0x12?

Are the data values shown in the dump (seems sometimes
yes, sometimes no) If someone could explain what's
going on in those (And other, if you want ;) examples,
i'd be very grateful.

-tmk








__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


linpvr at projectplasma

Feb 7, 2003, 1:04 PM

Post #2 of 22 (5148 views)
Permalink
Re: saa7115 devel [In reply to]

On Fri, 7 Feb 2003, kevin thayer wrote:

> OK so i'm going through the i2c dumps.
>
> Fill in the blanks (pvr250):
> i2c addr = device
>
> 0x18 = Infrared
> 0x21 = saa7115
> 0x40 =

msp34x5g/msp44x8g

> 0x50 =

Hauppauge eeprom. There are decoding functions and data in the bttv module.
It works :)

> 0x61 = tuner

pvr350 owners will also see:

0x44, saa712x, the video DAC(?)

> here's some questions for anyone familliar with i2c:
>
> i see the following kinds of operations:
> 0xi2c_addr, read/write, register, data, data, ....
>
> 21,W,0A - write to a register with no data(?!)
> 21,r,88 - read the contents of a register
> (byte?,word?)

You'll notice that these come in pairs. This is how reads work. The master
sends the address, the slave responds.

Some chips will send without being requested. Notice that 0x18 sends out a
byte roughly every 200ms.

> 21,W,0A,8E - write 0x83 to reg 0x0a

Yes. Hmm, that's kinda wonky. Typically reading and writing have two
separate register spaces.

> 50,r,84,12,00,00 - read multiple data? explain?

Register width is dependant on the chip, and which register or register set
it's writing to.

> 40,W,12,00,13,0C,00 - write 4bytes to reg 0x12?

Write 0x0c00 to register 0x0013 in set 12. -or-
Write 0x130c00 to register 0x00 in set 12.

> Are the data values shown in the dump (seems sometimes
> yes, sometimes no) If someone could explain what's
> going on in those (And other, if you want ;) examples,
> i'd be very grateful.

I highly suggest you concentrate on one chip at a time otherwise you're going
to get confused. There's a section in each datasheet that tells you how this
all works and this does vary from chip to chip and even between register sets.

The easiest one to understand is the tuner, so start with that one :)

John



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 7, 2003, 1:34 PM

Post #3 of 22 (5148 views)
Permalink
Re: saa7115 devel [In reply to]

> You'll notice that these come in pairs. This is how
> reads work. The master
> sends the address, the slave responds.

ok, so this is the driver reading the value of reg
0x9, and the card responding with "it's 0xc6":
845uS: 21 W 09
497uS: 21 r C6

> > 21,W,0A,8E - write 0x83 to reg 0x0a
>
> Yes. Hmm, that's kinda wonky. Typically reading
> and writing have two separate register spaces.

err that should be write 0x8e... this (is the only)
one i understand... i think :)

> I highly suggest you concentrate on one chip at a
> time otherwise you're going to get confused.

heh yeah. Don't worry.. Right now i'm only interested
in the saa7115. I've made some progress so far.

> > 50,r,84,12,00,00 - read multiple data? explain?
>
> Register width is dependant on the chip, and which
> register or register set it's writing to.

if i understand correctly, this is a response to a
read request, so it makes sense now.

> > 40,W,12,00,13,0C,00 - write 4bytes to reg 0x12?
>
> Write 0x0c00 to register 0x0013 in set 12. -or-
> Write 0x130c00 to register 0x00 in set 12.

What about write 0x00130c00 to register 0x12? that's
my hunch (who writes 24-bit values? :)

Anyhow, obersvations so far (using the saa7114 as a
loose reference)

0x87 (enable digitizer) seems to be left on (0x1)
except when making changes to 0x88, and possibly 0x08,
0x30, 0x31, 0x32, 0x34, 0x35, 0x36, 0x80 (not always
though) .. This is different than our driver currently
works... we leave it off and turn it on when we want
to capture.

and for register 0x02 (input select: tuner, composite,
svideo are options? maybe just tuner/composite and
svideo?)

Here's my interpretation (this is where he switches
from tuner to composite (i'm assuming his card is like
mine and has a svideo->composite adapter)

(previous value of 0x02 was 0x84)
160.621mS: 21 W 02 88 //set input to ?
873uS: 21 W 09 //request value of 0x09
497uS: 21 r 56 // value is 0x56
585uS: 21 W 09 C6 //set 0x09 to C6
1.010mS: 21 W 02 80 //switch input to direct-in
845uS: 21 W 09 //request value of 0x09
497uS: 21 r C6 // value is c6
562uS: 21 W 09 56 //set 0x09 to 56
2.220mS: 21 W 09 //request value of 0x09
499uS: 21 r 56 // value is 56

this sequence happens twice with about a second in
between.. Windows driver is wierd i suppose. Based on
the values in the saa7114 driver, 0x02 (low nibble) is
video source, and 0x09 is the chrominance trap bypass
(hi nibble).. These values are different than those of
the 7114 though.. appears 0x56 is the correct setting
for line-in and 0xc6 is correct for tuner.

Oh and john, thanks for the quick response. you be
rockin'
-tmk

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 7, 2003, 1:40 PM

Post #4 of 22 (5149 views)
Permalink
Re: saa7115 devel [In reply to]

> the 7114 though.. appears 0x56 is the correct
> setting for line-in and 0xc6 is correct for tuner.

scratch that. looks like 09 = 0x53 is correct for
tuner

09 = 0xc6 is for whatever input 02 = 0x88 is

-tmk


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 7, 2003, 5:19 PM

Post #5 of 22 (5149 views)
Permalink
Re: saa7115 devel [In reply to]

Anyone know what "window settings" are in
saa711x-land?

I think i've got enough from the i2c captures to
modify the 7114 driver to do what I want..

or

i could build arrays of commands for the 7115 and just
have it compiled-in.. Not sure which i'd prefer.

opinions?


Here's the documentation i've written so far:
Initial observations:
This comes from the logs on the documentation page,
and also from the 7114 driver.

I am making the assumption that most of the init
defaults are for NTSC, and that
the person making the logs are in PAL-land..

Register 0x87 (enable digitizer - TV standard
independant)
==================================
seems to be left on (0x1) except when making changes
to 0x88, and possibly 0x08, 0x30, 0x31, 0x32, 0x34,
0x35, 0x36, 0x80 (not
always though)

0x88 (reset scaler - TV standard independant)
==================================(
High nibble "D" (0xd0) appears to reset the scaler,
high nibble
"F" (0xf0) seems to release the reset? (from 7114
driver).. Always called in pairs,
ie
W 88 D0
W 88 F0.

In non-init mode, always surrounded by digitizer
off/on calls:

21.138mS: 21 W 87 00
1.851mS: 21 W 88 D0
865uS: 21 W 88 F0
99.101mS: 21 W 87 01

0x02 (select input - TV standard dependant?)
0x09 (chrominance trap - follows 0x02)
==================================
tuner, composite, svideo are options?
maybe just tuner/composite and svideo?

Tuner:
0x02 = 0x84
0x09 = 0x53

composite/svideo
0x02 = 0x80
0x09 = 0x56

??
0x02 = 0x88
0x09 = 0xC6

0x30 to 0x36 (audio options - TV standard dependant)
==================================
Windows driver runs this seq when switching from
on->unused (ntsc?)
0x30 = 0xBC
0x31 = 0xDF
0x32 = 0x02
0x34 = 0xF2
0x35 = 0x00
0x36 = 0x2D

And before setting up a capture: (pal?)
0x30 = 0x00
0x31 = 0xC0
0x32 = 0x03
0x34 = 0xCE
0x35 = 0xFB
0x36 = 0x30

0x08 (HPLL according to 7114 driver - TV standard
independant?)
==================================
Claims "HPLL: free running in playback, locked in
capture"

0x08 = 68 - start init? (not capturing)
0x08 = 78 - end init? (not capturing)
0x08 = 28 - set for capture


There are a bunch of "window settings" which i suppose
are the
reolutions of the capture. pal/ntsc dependant of
course

init sequence/pre-sets. ??
==================================
562uS: 21 W 08 68 //start init HPLL?
891uS: 21 W 30 BC //audio settings.. ntsc?
803uS: 21 W 31 DF // "
814uS: 21 W 32 02 // "
807uS: 21 W 34 F2 // "
810uS: 21 W 35 00 // "
807uS: 21 W 36 2D // "
831uS: 21 W 80 00 //7114-drv says "X-port, I-port
and scaler"
855uS: 21 W 88 D0 //reset scaler
815uS: 21 W 91 40 //7114-drv says "task A
definition"
814uS: 21 W 93 80 // "
822uS: 21 W 98 0D //window-settings?
1.037mS: 21 W CA FD // "
820uS: 21 W CE FD // "
994uS: 21 W 91 48 //7114-drv says "task A
definition"
813uS: 21 W 93 84 // "
845uS: 21 W 88 F0 //un-reset scaler?
797uS: 21 W 30 CD //audio settings.. PAL?
805uS: 21 W 31 20 // "
806uS: 21 W 32 03 // "
815uS: 21 W 34 CE // "
813uS: 21 W 35 FB // "
808uS: 21 W 36 30 // "
805uS: 21 W 02 C6 // Set input to 0xc6 (??)
838uS: 21 W 98 05 //window-settings?
981uS: 21 W 90 80 //7114-drv says "task A
definition"
814uS: 21 W 30 BC //audio settings.. ntsc?
807uS: 21 W 31 DF // "
816uS: 21 W 32 02 // "
834uS: 21 W CA F0 //window-settings?
808uS: 21 W CE F0 // "
826uS: 21 W 80 30 //7114-drv says "X-port, I-port
and scaler"
811uS: 21 W 02 88 //Set input to 0x88?
916uS: 21 W 08 78 //end init HPLL?

sequence run just before capture (PAL?)
(edited out some redudant stuff)
==================================
648uS: 21 W C4 00 //window settings?
949uS: 21 W CA 20 // "
849uS: 21 W CB 01 // "
844uS: 21 W CE 20 // "
842uS: 21 W CF 01 // "
949uS: 21 W 94 00 // "
944uS: 21 W 98 0A // "
876uS: 21 W 9A 03 // "
871uS: 21 W 9C D0 // "
860uS: 21 W 9D 02 // "
76.710mS: 21 W 88 D0 //reset scaler
812uS: 21 W 91 48 //task a definition?
818uS: 21 W 93 84 //task a definition?
852uS: 21 W 88 F0 //end reset scaler
16.375mS: 21 W 98 05 //window settings?
820uS: 21 W 9A 02 // "
983uS: 21 W 90 00 //task a definition?
771uS: 21 W 9D 05 //window settings?
962uS: 21 W 9C A0 //window settings?
1.124mS: 21 W 88 00 //? to scaler
839uS: 21 W 88 F0 //end reset scaler
852uS: 21 W 30 00 //Audio setup (pal)
842uS: 21 W 31 C0 // "
834uS: 21 W 32 03 // "
847uS: 21 W 34 CE // "
838uS: 21 W 35 FB // "
857uS: 21 W 36 30 // "
21.138mS: 21 W 87 00 //disable digitizer
1.851mS: 21 W 88 D0 //reset scaler
865uS: 21 W 88 F0 //end reset scaler
99.101mS: 21 W 87 01 //enable digitizer
1.010mS: 21 W 02 80 //Set input to composite/svideo?
562uS: 21 W 09 56 //set chrominance trap for composite/svideo

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 7, 2003, 6:09 PM

Post #6 of 22 (5156 views)
Permalink
Re: saa7115 devel [In reply to]

update from 7114 driver:
can anyone define these better? (is width input width?
shouldn't that be autosensed? why 2 sets of seemingly
identical settings?)

(0x94) hoffset low
(0x95) hoffset high
(0x96) width low
(0x97) width high
(0x98) voffset low
(0x99) voffset high
(0x9a) height low
(0x9b) height high
(0x9c) out width low
(0x9d) out width high
(0x9e) out height low
(0x9f) out height high

(0xc4) hoffset low
(0xc5) hoffset high
(0xc6) width low
(0xc7) width high
(0xc8) voffset low
(0xc9) voffset high
(0xca) height low
(0xcb) height high
(0xcc) out width low
(0xcd) out width high
(0xce) out height low
(0xcf) out height high

the driver doesnt seem to set all of them. Any idea
why? here's a quick rundown:

sequence run just before capture (PAL?)
(edited out some redudant stuff)
==================================
648uS: 21 W C4 00 //hoffset low
949uS: 21 W CA 20 //height low
849uS: 21 W CB 01 //height high (height = 288)
844uS: 21 W CE 20 //out height low
842uS: 21 W CF 01 //out height high (height = 288)
949uS: 21 W 94 00 //hoffest low
944uS: 21 W 98 0A //voffset low
876uS: 21 W 9A 03 //height low
871uS: 21 W 9C D0 //out width low
860uS: 21 W 9D 02 //out width high (width = 720)
76.710mS: 21 W 88 D0 //reset scaler
812uS: 21 W 91 48 //task a definition?
818uS: 21 W 93 84 //task a definition?
852uS: 21 W 88 F0 //end reset scaler
16.375mS: 21 W 98 05 //voffset low
820uS: 21 W 9A 02 //height low
983uS: 21 W 90 00 //task a definition?
771uS: 21 W 9D 05 //out width high
962uS: 21 W 9C A0 //out width low (width = 1440)
1.124mS: 21 W 88 00 //? to scaler
839uS: 21 W 88 F0 //end reset scaler
852uS: 21 W 30 00 //Audio setup (pal)
842uS: 21 W 31 C0 // "
834uS: 21 W 32 03 // "
847uS: 21 W 34 CE // "
838uS: 21 W 35 FB // "
857uS: 21 W 36 30 // "
21.138mS: 21 W 87 00 //disable digitizer
1.851mS: 21 W 88 D0 //reset scaler
865uS: 21 W 88 F0 //end reset scaler
99.101mS: 21 W 87 01 //enable digitizer
1.010mS: 21 W 02 80 //Set input to composite/svideo?
562uS: 21 W 09 56 //set chrominance trap for
composite/svideo

-tmk

--- kevin thayer <nufan_wfk [at] yahoo> wrote:
> Anyone know what "window settings" are in
> saa711x-land?
>
> I think i've got enough from the i2c captures to
> modify the 7114 driver to do what I want..
>
> or
>
> i could build arrays of commands for the 7115 and
> just
> have it compiled-in.. Not sure which i'd prefer.
>
> opinions?
>
>
> Here's the documentation i've written so far:
> Initial observations:
> This comes from the logs on the documentation page,
> and also from the 7114 driver.
>
> I am making the assumption that most of the init
> defaults are for NTSC, and that
> the person making the logs are in PAL-land..
>
> Register 0x87 (enable digitizer - TV standard
> independant)
> ==================================
> seems to be left on (0x1) except when making changes
> to 0x88, and possibly 0x08, 0x30, 0x31, 0x32, 0x34,
> 0x35, 0x36, 0x80 (not
> always though)
>
> 0x88 (reset scaler - TV standard independant)
> ==================================(
> High nibble "D" (0xd0) appears to reset the scaler,
> high nibble
> "F" (0xf0) seems to release the reset? (from 7114
> driver).. Always called in pairs,
> ie
> W 88 D0
> W 88 F0.
>
> In non-init mode, always surrounded by digitizer
> off/on calls:
>
> 21.138mS: 21 W 87 00
> 1.851mS: 21 W 88 D0
> 865uS: 21 W 88 F0
> 99.101mS: 21 W 87 01
>
> 0x02 (select input - TV standard dependant?)
> 0x09 (chrominance trap - follows 0x02)
> ==================================
> tuner, composite, svideo are options?
> maybe just tuner/composite and svideo?
>
> Tuner:
> 0x02 = 0x84
> 0x09 = 0x53
>
> composite/svideo
> 0x02 = 0x80
> 0x09 = 0x56
>
> ??
> 0x02 = 0x88
> 0x09 = 0xC6
>
> 0x30 to 0x36 (audio options - TV standard dependant)
> ==================================
> Windows driver runs this seq when switching from
> on->unused (ntsc?)
> 0x30 = 0xBC
> 0x31 = 0xDF
> 0x32 = 0x02
> 0x34 = 0xF2
> 0x35 = 0x00
> 0x36 = 0x2D
>
> And before setting up a capture: (pal?)
> 0x30 = 0x00
> 0x31 = 0xC0
> 0x32 = 0x03
> 0x34 = 0xCE
> 0x35 = 0xFB
> 0x36 = 0x30
>
> 0x08 (HPLL according to 7114 driver - TV standard
> independant?)
> ==================================
> Claims "HPLL: free running in playback, locked in
> capture"
>
> 0x08 = 68 - start init? (not capturing)
> 0x08 = 78 - end init? (not capturing)
> 0x08 = 28 - set for capture
>
>
> There are a bunch of "window settings" which i
> suppose
> are the
> reolutions of the capture. pal/ntsc dependant of
> course
>
> init sequence/pre-sets. ??
> ==================================
> 562uS: 21 W 08 68 //start init HPLL?
> 891uS: 21 W 30 BC //audio settings.. ntsc?
> 803uS: 21 W 31 DF // "
> 814uS: 21 W 32 02 // "
> 807uS: 21 W 34 F2 // "
> 810uS: 21 W 35 00 // "
> 807uS: 21 W 36 2D // "
> 831uS: 21 W 80 00 //7114-drv says "X-port,
> I-port
> and scaler"
> 855uS: 21 W 88 D0 //reset scaler
> 815uS: 21 W 91 40 //7114-drv says "task A
> definition"
> 814uS: 21 W 93 80 // "
> 822uS: 21 W 98 0D //window-settings?
> 1.037mS: 21 W CA FD // "
> 820uS: 21 W CE FD // "
> 994uS: 21 W 91 48 //7114-drv says "task A
> definition"
> 813uS: 21 W 93 84 // "
> 845uS: 21 W 88 F0 //un-reset scaler?
> 797uS: 21 W 30 CD //audio settings.. PAL?
> 805uS: 21 W 31 20 // "
> 806uS: 21 W 32 03 // "
> 815uS: 21 W 34 CE // "
> 813uS: 21 W 35 FB // "
> 808uS: 21 W 36 30 // "
> 805uS: 21 W 02 C6 // Set input to 0xc6 (??)
> 838uS: 21 W 98 05 //window-settings?
> 981uS: 21 W 90 80 //7114-drv says "task A
> definition"
> 814uS: 21 W 30 BC //audio settings.. ntsc?
> 807uS: 21 W 31 DF // "
> 816uS: 21 W 32 02 // "
> 834uS: 21 W CA F0 //window-settings?
> 808uS: 21 W CE F0 // "
> 826uS: 21 W 80 30 //7114-drv says "X-port,
> I-port
> and scaler"
> 811uS: 21 W 02 88 //Set input to 0x88?
> 916uS: 21 W 08 78 //end init HPLL?
>
> sequence run just before capture (PAL?)
> (edited out some redudant stuff)
> ==================================
> 648uS: 21 W C4 00 //window settings?
> 949uS: 21 W CA 20 // "
> 849uS: 21 W CB 01 // "
> 844uS: 21 W CE 20 // "
> 842uS: 21 W CF 01 // "
> 949uS: 21 W 94 00 // "
> 944uS: 21 W 98 0A // "
> 876uS: 21 W 9A 03 // "
> 871uS: 21 W 9C D0 // "
> 860uS: 21 W 9D 02 // "
> 76.710mS: 21 W 88 D0 //reset scaler
> 812uS: 21 W 91 48 //task a definition?
> 818uS: 21 W 93 84 //task a definition?
> 852uS: 21 W 88 F0 //end reset scaler
> 16.375mS: 21 W 98 05 //window settings?
> 820uS: 21 W 9A 02 // "
> 983uS: 21 W 90 00 //task a definition?
> 771uS: 21 W 9D 05 //window settings?
> 962uS: 21 W 9C A0 //window settings?
> 1.124mS: 21 W 88 00 //? to scaler
> 839uS: 21 W 88 F0 //end reset scaler
> 852uS: 21 W 30 00 //Audio setup (pal)
> 842uS: 21 W 31 C0 // "
> 834uS: 21 W 32 03 // "
> 847uS: 21 W 34 CE // "
> 838uS: 21 W 35 FB // "
> 857uS: 21 W 36 30 // "
> 21.138mS: 21 W 87 00 //disable digitizer
> 1.851mS: 21 W 88 D0 //reset scaler
> 865uS: 21 W 88 F0 //end reset scaler
> 99.101mS: 21 W 87 01 //enable digitizer
> 1.010mS: 21 W 02 80 //Set input to
> composite/svideo?
> 562uS: 21 W 09 56 //set chrominance trap for
> composite/svideo
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up
> now.
> http://mailplus.yahoo.com
>
>
>
-------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =
> Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> ivtv-devel mailing list
>
=== message truncated ===


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 8, 2003, 12:08 PM

Post #7 of 22 (5144 views)
Permalink
Re: saa7115 devel [In reply to]

After further checking out the i2c logs, it looks like
there aren't any from driver-load.. So all the values
shown are just the app setting pre-capture. This will
be useful when we start doing v4l, but as far as
writing a driver for it goes, all the initialization
stuff is missing :<

Any ideas on where to go from here?

-tmk

--- kevin thayer <nufan_wfk [at] yahoo> wrote:
> update from 7114 driver:
> can anyone define these better? (is width input
> width?
> shouldn't that be autosensed? why 2 sets of
> seemingly
> identical settings?)
>
> (0x94) hoffset low
> (0x95) hoffset high
> (0x96) width low
> (0x97) width high
> (0x98) voffset low
> (0x99) voffset high
> (0x9a) height low
> (0x9b) height high
> (0x9c) out width low
> (0x9d) out width high
> (0x9e) out height low
> (0x9f) out height high
>
> (0xc4) hoffset low
> (0xc5) hoffset high
> (0xc6) width low
> (0xc7) width high
> (0xc8) voffset low
> (0xc9) voffset high
> (0xca) height low
> (0xcb) height high
> (0xcc) out width low
> (0xcd) out width high
> (0xce) out height low
> (0xcf) out height high
>
> the driver doesnt seem to set all of them. Any idea
> why? here's a quick rundown:
>
> sequence run just before capture (PAL?)
> (edited out some redudant stuff)
> ==================================
> 648uS: 21 W C4 00 //hoffset low
> 949uS: 21 W CA 20 //height low
> 849uS: 21 W CB 01 //height high (height = 288)
> 844uS: 21 W CE 20 //out height low
> 842uS: 21 W CF 01 //out height high (height =
> 288)
> 949uS: 21 W 94 00 //hoffest low
> 944uS: 21 W 98 0A //voffset low
> 876uS: 21 W 9A 03 //height low
> 871uS: 21 W 9C D0 //out width low
> 860uS: 21 W 9D 02 //out width high (width = 720)
> 76.710mS: 21 W 88 D0 //reset scaler
> 812uS: 21 W 91 48 //task a definition?
> 818uS: 21 W 93 84 //task a definition?
> 852uS: 21 W 88 F0 //end reset scaler
> 16.375mS: 21 W 98 05 //voffset low
> 820uS: 21 W 9A 02 //height low
> 983uS: 21 W 90 00 //task a definition?
> 771uS: 21 W 9D 05 //out width high
> 962uS: 21 W 9C A0 //out width low (width = 1440)
> 1.124mS: 21 W 88 00 //? to scaler
> 839uS: 21 W 88 F0 //end reset scaler
> 852uS: 21 W 30 00 //Audio setup (pal)
> 842uS: 21 W 31 C0 // "
> 834uS: 21 W 32 03 // "
> 847uS: 21 W 34 CE // "
> 838uS: 21 W 35 FB // "
> 857uS: 21 W 36 30 // "
> 21.138mS: 21 W 87 00 //disable digitizer
> 1.851mS: 21 W 88 D0 //reset scaler
> 865uS: 21 W 88 F0 //end reset scaler
> 99.101mS: 21 W 87 01 //enable digitizer
> 1.010mS: 21 W 02 80 //Set input to
> composite/svideo?
> 562uS: 21 W 09 56 //set chrominance trap for
> composite/svideo
>
> -tmk
>
> --- kevin thayer <nufan_wfk [at] yahoo> wrote:
> > Anyone know what "window settings" are in
> > saa711x-land?
> >
> > I think i've got enough from the i2c captures to
> > modify the 7114 driver to do what I want..
> >
> > or
> >
> > i could build arrays of commands for the 7115 and
> > just
> > have it compiled-in.. Not sure which i'd prefer.
> >
> > opinions?
> >
> >
> > Here's the documentation i've written so far:
> > Initial observations:
> > This comes from the logs on the documentation
> page,
> > and also from the 7114 driver.
> >
> > I am making the assumption that most of the init
> > defaults are for NTSC, and that
> > the person making the logs are in PAL-land..
> >
> > Register 0x87 (enable digitizer - TV standard
> > independant)
> > ==================================
> > seems to be left on (0x1) except when making
> changes
> > to 0x88, and possibly 0x08, 0x30, 0x31, 0x32,
> 0x34,
> > 0x35, 0x36, 0x80 (not
> > always though)
> >
> > 0x88 (reset scaler - TV standard independant)
> > ==================================(
> > High nibble "D" (0xd0) appears to reset the
> scaler,
> > high nibble
> > "F" (0xf0) seems to release the reset? (from 7114
> > driver).. Always called in pairs,
> > ie
> > W 88 D0
> > W 88 F0.
> >
> > In non-init mode, always surrounded by digitizer
> > off/on calls:
> >
> > 21.138mS: 21 W 87 00
> > 1.851mS: 21 W 88 D0
> > 865uS: 21 W 88 F0
> > 99.101mS: 21 W 87 01
> >
> > 0x02 (select input - TV standard dependant?)
> > 0x09 (chrominance trap - follows 0x02)
> > ==================================
> > tuner, composite, svideo are options?
> > maybe just tuner/composite and svideo?
> >
> > Tuner:
> > 0x02 = 0x84
> > 0x09 = 0x53
> >
> > composite/svideo
> > 0x02 = 0x80
> > 0x09 = 0x56
> >
> > ??
> > 0x02 = 0x88
> > 0x09 = 0xC6
> >
> > 0x30 to 0x36 (audio options - TV standard
> dependant)
> > ==================================
> > Windows driver runs this seq when switching from
> > on->unused (ntsc?)
> > 0x30 = 0xBC
> > 0x31 = 0xDF
> > 0x32 = 0x02
> > 0x34 = 0xF2
> > 0x35 = 0x00
> > 0x36 = 0x2D
> >
> > And before setting up a capture: (pal?)
> > 0x30 = 0x00
> > 0x31 = 0xC0
> > 0x32 = 0x03
> > 0x34 = 0xCE
> > 0x35 = 0xFB
> > 0x36 = 0x30
> >
> > 0x08 (HPLL according to 7114 driver - TV standard
> > independant?)
> > ==================================
> > Claims "HPLL: free running in playback, locked in
> > capture"
> >
> > 0x08 = 68 - start init? (not capturing)
> > 0x08 = 78 - end init? (not capturing)
> > 0x08 = 28 - set for capture
> >
> >
> > There are a bunch of "window settings" which i
> > suppose
> > are the
> > reolutions of the capture. pal/ntsc dependant of
> > course
> >
> > init sequence/pre-sets. ??
> > ==================================
> > 562uS: 21 W 08 68 //start init HPLL?
> > 891uS: 21 W 30 BC //audio settings.. ntsc?
> > 803uS: 21 W 31 DF // "
> > 814uS: 21 W 32 02 // "
> > 807uS: 21 W 34 F2 // "
> > 810uS: 21 W 35 00 // "
> > 807uS: 21 W 36 2D // "
> > 831uS: 21 W 80 00 //7114-drv says "X-port,
> > I-port
> > and scaler"
> > 855uS: 21 W 88 D0 //reset scaler
>
=== message truncated ===


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 8, 2003, 1:47 PM

Post #8 of 22 (5141 views)
Permalink
Re: saa7115 devel [In reply to]

OK some progress.

I've taken a bunch of the values from the i2c logs and
put them into an array that gets copied to the
saa7115. By itself, it doesn't work (not enough
commands i guess..) .. captures time out and it seems
as though the saa7115 isn't talking at all.

but

if one loads the 7114 driver *first*, lets it do its
init thing, then unload it (if you want.. i suppose
it's not necessary) and then run a capture, the
combination is enough to get a video stream from the
card. It's possible that you just need to run some
sort of "turn yourself on" command against the saa7115
and it'll have intelligent defaults. Remains to be
seen.

The video stream is horribly corrupted, but at least
it's something :)

Is there an i2c register dump program out there? I'm
confident i could make a working driver for the
saa7115 given a dump of the registers after
initialization (on ntsc and pal separately).. note i
don't want a dump of i2c communications, just of the
saa7115 regs.

If i had that, it'd be done in under an hour :)

If i get some more time later today i'll attempt to
tweak some settings to find out what creates valid
video.

-tmk

--- kevin thayer <nufan_wfk [at] yahoo> wrote:
> After further checking out the i2c logs, it looks
> like
> there aren't any from driver-load.. So all the
> values
> shown are just the app setting pre-capture. This
> will
> be useful when we start doing v4l, but as far as
> writing a driver for it goes, all the initialization
> stuff is missing :<
>
> Any ideas on where to go from here?
>
> -tmk

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


doug.stevens at insightbb

Feb 8, 2003, 1:55 PM

Post #9 of 22 (5146 views)
Permalink
Re: saa7115 devel [In reply to]

A quick google search later...

http://secure.netroedge.com/~lm78/i2ctools.html

Is this what you are looking for?

----- Original Message -----
From: "kevin thayer" <nufan_wfk [at] yahoo>
To: <ivtv-devel [at] lists>
Sent: Saturday, February 08, 2003 3:47 PM
Subject: Re: [ivtv-devel] saa7115 devel


> OK some progress.
>
> I've taken a bunch of the values from the i2c logs and
> put them into an array that gets copied to the
> saa7115. By itself, it doesn't work (not enough
> commands i guess..) .. captures time out and it seems
> as though the saa7115 isn't talking at all.
>
> but
>
> if one loads the 7114 driver *first*, lets it do its
> init thing, then unload it (if you want.. i suppose
> it's not necessary) and then run a capture, the
> combination is enough to get a video stream from the
> card. It's possible that you just need to run some
> sort of "turn yourself on" command against the saa7115
> and it'll have intelligent defaults. Remains to be
> seen.
>
> The video stream is horribly corrupted, but at least
> it's something :)
>
> Is there an i2c register dump program out there? I'm
> confident i could make a working driver for the
> saa7115 given a dump of the registers after
> initialization (on ntsc and pal separately).. note i
> don't want a dump of i2c communications, just of the
> saa7115 regs.
>
> If i had that, it'd be done in under an hour :)
>
> If i get some more time later today i'll attempt to
> tweak some settings to find out what creates valid
> video.
>
> -tmk
>
> --- kevin thayer <nufan_wfk [at] yahoo> wrote:
> > After further checking out the i2c logs, it looks
> > like
> > there aren't any from driver-load.. So all the
> > values
> > shown are just the app setting pre-capture. This
> > will
> > be useful when we start doing v4l, but as far as
> > writing a driver for it goes, all the initialization
> > stuff is missing :<
> >
> > Any ideas on where to go from here?
> >
> > -tmk
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 8, 2003, 2:01 PM

Post #10 of 22 (5139 views)
Permalink
Re: saa7115 devel [In reply to]

sort of, only for windows :)

I need a dump of the windows driver. I don't have
windows on my devel box, so someone else will have to
do it.

I wonder if there are legal issues with having john
send me a binary driver, then dumping regs on that..
Would that work?

Thoughts?

-tmk

--- Doug Stevens <doug.stevens [at] insightbb> wrote:
> A quick google search later...
>
> http://secure.netroedge.com/~lm78/i2ctools.html
>
> Is this what you are looking for?
>
> ----- Original Message -----
> From: "kevin thayer" <nufan_wfk [at] yahoo>
> To: <ivtv-devel [at] lists>
> Sent: Saturday, February 08, 2003 3:47 PM
> Subject: Re: [ivtv-devel] saa7115 devel
>
>
> > OK some progress.
> >
> > I've taken a bunch of the values from the i2c logs
> and
> > put them into an array that gets copied to the
> > saa7115. By itself, it doesn't work (not enough
> > commands i guess..) .. captures time out and it
> seems
> > as though the saa7115 isn't talking at all.
> >
> > but
> >
> > if one loads the 7114 driver *first*, lets it do
> its
> > init thing, then unload it (if you want.. i
> suppose
> > it's not necessary) and then run a capture, the
> > combination is enough to get a video stream from
> the
> > card. It's possible that you just need to run some
> > sort of "turn yourself on" command against the
> saa7115
> > and it'll have intelligent defaults. Remains to be
> > seen.
> >
> > The video stream is horribly corrupted, but at
> least
> > it's something :)
> >
> > Is there an i2c register dump program out there?
> I'm
> > confident i could make a working driver for the
> > saa7115 given a dump of the registers after
> > initialization (on ntsc and pal separately).. note
> i
> > don't want a dump of i2c communications, just of
> the
> > saa7115 regs.
> >
> > If i had that, it'd be done in under an hour :)
> >
> > If i get some more time later today i'll attempt
> to
> > tweak some settings to find out what creates valid
> > video.
> >
> > -tmk
> >
> > --- kevin thayer <nufan_wfk [at] yahoo> wrote:
> > > After further checking out the i2c logs, it
> looks
> > > like
> > > there aren't any from driver-load.. So all the
> > > values
> > > shown are just the app setting pre-capture. This
> > > will
> > > be useful when we start doing v4l, but as far as
> > > writing a driver for it goes, all the
> initialization
> > > stuff is missing :<
> > >
> > > Any ideas on where to go from here?
> > >
> > > -tmk
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up
> now.
> > http://mailplus.yahoo.com
> >
> >
> >
>
-------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld
> = Something 2 See!
> > http://www.vasoftware.com
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel [at] lists
> >
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>
>
>
-------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =
> Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


linpvr at projectplasma

Feb 8, 2003, 2:19 PM

Post #11 of 22 (5159 views)
Permalink
Re: saa7115 devel [In reply to]

On Sat, 8 Feb 2003, kevin thayer wrote:

> sort of, only for windows :)
>
> I need a dump of the windows driver. I don't have
> windows on my devel box, so someone else will have to
> do it.

Unlike Linux, I don't think Windows has a common i2c interface. You'll need to
use whatever API the card's drivers provide. It's got one, haven't a clue how
to use it.

John



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 8, 2003, 3:23 PM

Post #12 of 22 (5144 views)
Permalink
Re: saa7115 devel [In reply to]

hmmm that sucks

do you think toth would be willing to make another
capture on request?

-tmk

--- PlasmaJohn <linpvr [at] projectplasma> wrote:
> On Sat, 8 Feb 2003, kevin thayer wrote:
>
> > sort of, only for windows :)
> >
> > I need a dump of the windows driver. I don't have
> > windows on my devel box, so someone else will have
> to
> > do it.
>
> Unlike Linux, I don't think Windows has a common i2c
> interface. You'll need to
> use whatever API the card's drivers provide. It's
> got one, haven't a clue how
> to use it.
>
> John
>
>
>
>
-------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =
> Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 8, 2003, 4:00 PM

Post #13 of 22 (5143 views)
Permalink
Re: saa7115 devel [In reply to]

hmmm that sucks

do you think toth would be willing to make another
capture on request?

-tmk

--- PlasmaJohn <linpvr [at] projectplasma> wrote:
> On Sat, 8 Feb 2003, kevin thayer wrote:
>
> > sort of, only for windows :)
> >
> > I need a dump of the windows driver. I don't have
> > windows on my devel box, so someone else will have
> to
> > do it.
>
> Unlike Linux, I don't think Windows has a common i2c
> interface. You'll need to
> use whatever API the card's drivers provide. It's
> got one, haven't a clue how
> to use it.
>
> John
>
>
>
>
-------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =
> Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


d18c7db at hotmail

Feb 12, 2003, 3:11 PM

Post #14 of 22 (5150 views)
Permalink
saa7115 devel [In reply to]

This is probably old news, but in the off chance that the SAA7115
datasheet is needed by anyone on the list...
a google search for "SAA7115 datasheet" produces a particular hit that
leads to a PDF of the actual datasheet
with big yellow "preliminary / NDA required" plastered on it. I've
"cached" a copy of it just in case :)

Cheers,

Alex


nufan_wfk at yahoo

Feb 12, 2003, 3:32 PM

Post #15 of 22 (5150 views)
Permalink
Re: saa7115 devel [In reply to]

Yeah i've seen that, but when i saw NDA req'd i
stopped looking. Trying to make sure this driver is
GPL'able

I've been meaning to call phillips (good luck to me
heh) and try to get their approval to use it for a
linux driver. If so, i think we'd be golden.

-tmk


--- d18c7db <d18c7db [at] hotmail> wrote:
> This is probably old news, but in the off chance
> that the SAA7115
> datasheet is needed by anyone on the list...
> a google search for "SAA7115 datasheet" produces a
> particular hit that
> leads to a PDF of the actual datasheet
> with big yellow "preliminary / NDA required"
> plastered on it. I've
> "cached" a copy of it just in case :)
>
> Cheers,
>
> Alex
>


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


linpvr at projectplasma

Feb 12, 2003, 5:23 PM

Post #16 of 22 (5152 views)
Permalink
Re: saa7115 devel [In reply to]

On Wed, 12 Feb 2003, kevin thayer wrote:

> Yeah i've seen that, but when i saw NDA req'd i
> stopped looking. Trying to make sure this driver is
> GPL'able
>
> I've been meaning to call phillips (good luck to me
> heh) and try to get their approval to use it for a
> linux driver. If so, i think we'd be golden.
>
> -tmk

Well....

You're not the one that broke NDA. Once it's been outed, it's more or less
"fair game" although the documents do retain copyright. OTOH, IANAL ;)

John



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 12, 2003, 5:54 PM

Post #17 of 22 (5143 views)
Permalink
Re: saa7115 devel [In reply to]

even better, one just says "prelim" and "company
confidential"

I'm quite tempted to use that. I did call philips
though, i was referred to a field office. Got
voicemail.. Will call back from time to time and bug
them:)

-tmk

--- PlasmaJohn <linpvr [at] projectplasma> wrote:
> On Wed, 12 Feb 2003, kevin thayer wrote:
>
> > Yeah i've seen that, but when i saw NDA req'd i
> > stopped looking. Trying to make sure this driver
> is
> > GPL'able
> >
> > I've been meaning to call phillips (good luck to
> me
> > heh) and try to get their approval to use it for a
> > linux driver. If so, i think we'd be golden.
> >
> > -tmk
>
> Well....
>
> You're not the one that broke NDA. Once it's been
> outed, it's more or less
> "fair game" although the documents do retain
> copyright. OTOH, IANAL ;)
>
> John
>
>
>
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


d18c7db at hotmail

Feb 12, 2003, 6:14 PM

Post #18 of 22 (5144 views)
Permalink
RE: saa7115 devel [In reply to]

Is there any leaked doco on the iTVC15/CX23415 ?

Incidentally the PTV250 card I got uses the CX23416 which I gather is
the encode only cheapie version.
Got some pics at http://axl.freeyellow.com/PVR250/ sorry my digital
camera is broken so these were captured off my camcoder.

The tuner is a FI1236 mk2 IIRC, popped the cover off and the only chips
I see is the TDA9800 plus a M1875 which I haven't researched yet but
there should definitely be another chip (perhaps on the other side of
the board) with the I2C interface. In the past I've played with the
FI1216 tuner (got a few in my draw still).

Alex

PS: try not to slip up and append the word "images" to the url above ;)

-----Original Message-----
From: ivtv-devel-admin [at] lists
[mailto:ivtv-devel-admin [at] lists] On Behalf Of kevin
thayer
Sent: Thursday, 13 February 2003 1:54 p.m.
To: ivtv-devel [at] lists
Subject: Re: [ivtv-devel] saa7115 devel


even better, one just says "prelim" and "company
confidential"

I'm quite tempted to use that. I did call philips
though, i was referred to a field office. Got
voicemail.. Will call back from time to time and bug
them:)

-tmk

--- PlasmaJohn <linpvr [at] projectplasma> wrote:
> On Wed, 12 Feb 2003, kevin thayer wrote:
>
> > Yeah i've seen that, but when i saw NDA req'd i
> > stopped looking. Trying to make sure this driver
> is
> > GPL'able
> >
> > I've been meaning to call phillips (good luck to
> me
> > heh) and try to get their approval to use it for a
> > linux driver. If so, i think we'd be golden.
> >
> > -tmk
>
> Well....
>
> You're not the one that broke NDA. Once it's been
> outed, it's more or less
> "fair game" although the documents do retain
> copyright. OTOH, IANAL ;)
>
> John
>
>
>
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 12, 2003, 6:19 PM

Post #19 of 22 (5143 views)
Permalink
RE: saa7115 devel [In reply to]

I think the i2c is internal to the itvc15.. could be
wrong tho.

The docs we have are handled by john, there was a
leaked ref driver which supposedly had API docs, but
i'm just going by what john's posted.

"clean room" technique or whatever

-tmk

--- d18c7db <d18c7db [at] hotmail> wrote:
> Is there any leaked doco on the iTVC15/CX23415 ?
>
> Incidentally the PTV250 card I got uses the CX23416
> which I gather is
> the encode only cheapie version.
> Got some pics at http://axl.freeyellow.com/PVR250/
> sorry my digital
> camera is broken so these were captured off my
> camcoder.
>
> The tuner is a FI1236 mk2 IIRC, popped the cover off
> and the only chips
> I see is the TDA9800 plus a M1875 which I haven't
> researched yet but
> there should definitely be another chip (perhaps on
> the other side of
> the board) with the I2C interface. In the past I've
> played with the
> FI1216 tuner (got a few in my draw still).
>
> Alex
>
> PS: try not to slip up and append the word "images"
> to the url above ;)
>
> -----Original Message-----
> From: ivtv-devel-admin [at] lists
> [mailto:ivtv-devel-admin [at] lists] On
> Behalf Of kevin
> thayer
> Sent: Thursday, 13 February 2003 1:54 p.m.
> To: ivtv-devel [at] lists
> Subject: Re: [ivtv-devel] saa7115 devel
>
>
> even better, one just says "prelim" and "company
> confidential"
>
> I'm quite tempted to use that. I did call philips
> though, i was referred to a field office. Got
> voicemail.. Will call back from time to time and bug
> them :)
>
> -tmk
>
> --- PlasmaJohn <linpvr [at] projectplasma> wrote:
> > On Wed, 12 Feb 2003, kevin thayer wrote:
> >
> > > Yeah i've seen that, but when i saw NDA req'd i
> > > stopped looking. Trying to make sure this driver
> > is
> > > GPL'able
> > >
> > > I've been meaning to call phillips (good luck to
> > me
> > > heh) and try to get their approval to use it for
> a
> > > linux driver. If so, i think we'd be golden.
> > >
> > > -tmk
> >
> > Well....
> >
> > You're not the one that broke NDA. Once it's been
> > outed, it's more or less
> > "fair game" although the documents do retain
> > copyright. OTOH, IANAL ;)
> >
> > John
> >
> >
> >
> >
>
-------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel [at] lists
> >
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Shopping - Send Flowers for Valentine's Day
> http://shopping.yahoo.com
>
>
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>
>
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


linpvr at projectplasma

Feb 12, 2003, 6:43 PM

Post #20 of 22 (5145 views)
Permalink
RE: saa7115 devel [In reply to]

On Thu, 13 Feb 2003, d18c7db wrote:

> Is there any leaked doco on the iTVC15/CX23415 ?

Nothing distributable. All known copies have been removed from public access
at the request of the current copyright holder.

> Incidentally the PTV250 card I got uses the CX23416 which I gather is
> the encode only cheapie version.

"Man and I thought *I* had a hell of a birthmark" ...

I was afraid of that. I believe that they are compatible, but there may be
some differences. You'll definitely need to extract your own firmware. There
may even be some API differences.

> The tuner is a FI1236 mk2 IIRC, popped the cover off and the only chips
> I see is the TDA9800 plus a M1875 which I haven't researched yet but
> there should definitely be another chip (perhaps on the other side of
> the board) with the I2C interface. In the past I've played with the
> FI1216 tuner (got a few in my draw still).

The TDA part is inside the tuner? Then that's the one that has the i2c bus.
Regardless, the linux tuner.o module handles the FI1236 (a fairly common
part).

What would be more interesting would be part numbers of the two squarish
QFP's, the one to the right of the can and the one directly below the can.
The TSOP to the left of the '16 is the encode RAM. The small smt dip in the
upper right is a PIC processor? That would be the IR part. Nicely supported
by the LIRC project if you can get the i2c bus attached. The curious one is
the small one in the center. An A/D converter?

Thanks,
John




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


d18c7db at hotmail

Feb 12, 2003, 7:18 PM

Post #21 of 22 (5148 views)
Permalink
RE: saa7115 devel [In reply to]

John, try clicking on the main picture, you get enlargements of the
chips you mention :)

URL for reference again http://axl.freeyellow.com/PVR250 Apologies for
the pop-under advertising, I have no control of that (freebie site).

A

-----Original Message-----
From: ivtv-devel-admin [at] lists
[mailto:ivtv-devel-admin [at] lists] On Behalf Of PlasmaJohn
Sent: Thursday, 13 February 2003 2:43 p.m.
To: ivtv-devel [at] lists
Subject: RE: [ivtv-devel] saa7115 devel


On Thu, 13 Feb 2003, d18c7db wrote:

> Is there any leaked doco on the iTVC15/CX23415 ?

Nothing distributable. All known copies have been removed from public
access at the request of the current copyright holder.

> Incidentally the PTV250 card I got uses the CX23416 which I gather is
> the encode only cheapie version.

"Man and I thought *I* had a hell of a birthmark" ...

I was afraid of that. I believe that they are compatible, but there may
be some differences. You'll definitely need to extract your own
firmware. There may even be some API differences.

> The tuner is a FI1236 mk2 IIRC, popped the cover off and the only
> chips I see is the TDA9800 plus a M1875 which I haven't researched yet

> but there should definitely be another chip (perhaps on the other side

> of the board) with the I2C interface. In the past I've played with the

> FI1216 tuner (got a few in my draw still).

The TDA part is inside the tuner? Then that's the one that has the i2c
bus. Regardless, the linux tuner.o module handles the FI1236 (a fairly
common part).

What would be more interesting would be part numbers of the two squarish
QFP's, the one to the right of the can and the one directly below the
can. The TSOP to the left of the '16 is the encode RAM. The small smt
dip in the upper right is a PIC processor? That would be the IR part.
Nicely supported by the LIRC project if you can get the i2c bus
attached. The curious one is the small one in the center. An A/D
converter?

Thanks,
John




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


linpvr at projectplasma

Feb 12, 2003, 8:21 PM

Post #22 of 22 (5152 views)
Permalink
RE: saa7115 devel [In reply to]

On Thu, 13 Feb 2003, d18c7db wrote:

> John, try clicking on the main picture, you get enlargements of the
> chips you mention :)

D'oh! I was wondering why it had the "active" border. Gee and you even
metion "Click on the rectangle areas to enlarge...".

Ok,
msp3435g (audio processor)
saa7115hl (digitizer)
pic16c54c (ir)

hmm, not sure what the one in the upper right is. Possibly an op-amp.
I think the one next to the PIC, the 24lc028 is your eeprom.

> URL for reference again http://axl.freeyellow.com/PVR250 Apologies for
> the pop-under advertising, I have no control of that (freebie site).

Heh. I've got Mozilla set up to not allow anybody to muck with the z-index.
Better yet, I've added accumail.com and webmarket.com to my junkbuster config,
and I don't even get the popup, heck, I don't get any of the ads. Boy, it's
been a long time since I've added somebody...

> A



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.