From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: bttv-driver: help required with new card
Date: 21 Aug 2002 08:39:45 GMT [thread overview]
Message-ID: <slrnam6keh.4m0.kraxel@bytesex.org> (raw)
In-Reply-To: 20020821075942.GF11372@finarfin.forwiss.uni-passau.de
> I have a framegrabber to work with linux (2.4.18). It's a BT878
> device and I have a lot of questions :(
>
> a) It does not use the muxsel-bits in BT848_IFORM but some bits in
> BT848_GPIO_DATA to select video-input---so seems to be a quite
> unusual device.
>
> Should I make switch(btv->type) statments in bt848_muxsel?
No. Pick the latest driver and use the muxsel_hook.
> b) several registers have to be initialised to other values then
> usual, to make the card work.
>
> At the moment I'm doing this in bt848_muxsel, but I would like to
> move to a place where it is not executed every time I switch input
> Is init_bt848 the right place?
No. Have you noticed the bttv-cards.c file? There is plenty of
card-specific initialization code. bttv_init_card2() likely is the
proper place.
> c) It does not identify with PCI_SUBSYSTEM_ID/PCI_SUBSYSTEM_VENDOR_ID
> (gives 0xffff). Any other way to autodetect it?
Sorry, no. Use the card=foo insmod option and flame the vendor of the
card.
> d) Who is the bttv-maintainer?!
/me.
How about reading documentation? Documentation/video4linux/bttv/ for
example?
Gerd
--
You can't please everybody. And usually if you _try_ to please
everybody, the end result is one big mess.
-- Linus Torvalds, 2002-04-20
prev parent reply other threads:[~2002-08-21 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 7:59 bttv-driver: help required with new card M G Berberich
2002-08-21 8:39 ` Gerd Knorr [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=slrnam6keh.4m0.kraxel@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.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