-On [20000124 00:00], Joachim Jäckel ([EMAIL PROTECTED]) wrote:
>
>Here´s some information to the card I'd like to support:
>
>It's a Miro DC10+ Video Grabber Card for Non-Linear Video-Editing.
>It uses a Siemens SAA7110, a Zoran 36060+36067 and a ADV???? chip to en-
>and decode the video-information. I got the specifications for the chips
>from Siemens and Zoran's Web-Sites and a first driver-skeleton was
>generated through the /usr/share/examples/drivers/make_pci... script for
>me.

Did you contact Miro?

And /usr/share/examples/drivers/make_pci is pre 4.0.

>Currently I get a boot-message from my kernel, that he has found the
>card.(I read the pci_id and send a text-message :-)

That's a good start.

>Additionally I found a linux-driver for this card (an early one...) but
>it is not fully compatible with the documentation, I got.

It can make certain things clear.

>Maybe you would allow me one question? (To get a little faster to the
>information than browsing through the source.)

Asking questions is free. =)

>But how get's the zoran36067_regs structure the information from the
>chip?

If you were using newbus (on FreeBSD 4.0) I'd say bus_space_read_#() to
get the info in the registers our of your chip.

>If I change the content of the structure, which function would change
>the registers on the chip accordingly? (Or is it done through the call
>of pci_map_mem? And is everything I change to the structure
>automatically changed on the card?)

I have to show my lack of 2.2.x and 3.x driver programming.  I am
spoiled due to 4.x.  I think someone else needs to answer this.  Juergen
appears to know 3.x driver programming.

>Sorry, if these questions are real dumb ones!

Not at all.

-- 
Jeroen Ruigrok vd W/Asmodai         asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/B-rated Coder BSD: Technical excellence at its best  
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
How the gods kill...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to