All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Trent Piepho <xyzzy@speakeasy.org>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: how to handle bt848 audio driver
Date: Fri, 26 Oct 2007 08:46:58 +0200	[thread overview]
Message-ID: <1193381218.13564.1217931615@webmail.messagingengine.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0710250407410.16052@shell4.speakeasy.net>

Trent Piepho wrote:
> I've made some more patches for the ALSA bt87x audio driver to support more
> features of the Osprey 440 card.
> 
> In order to support certain features, the ALSA driver needs access to the
> bt878's GPIO lines and I2C bus.  These are controlled by PCI function 0, which
> is driven by the V4L driver.  The bt878 DVB driver (which drives PCI function
> 1 just like the ALSA driver) needs to do the same thing and there is already
> some code to handle it.
> 
> So, the ALSA driver (snd-bt87x) needs to use functions from the V4L driver
> (bttv).  As it is now, the two drivers are completely separate and don't share
> any code and can be loaded individually.
> 
> The DVB driver in the same tree as bttv, so this isn't a problem.  But the
> snd-bt87x is in another tree, so it's somewhat harder, and I'm not sure what
> to do about it.

The part of the ALSA API used by snd-bt87x is apparently more stable
than the bttv functions to be used, so this seems to be a good
opportunity to move snd-bt87x into the V4L tree.


Regards,
Clemens

  reply	other threads:[~2007-10-26  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 16:31 how to handle bt848 audio driver Trent Piepho
2007-10-26  6:46 ` Clemens Ladisch [this message]
2007-10-30 19:26   ` Trent Piepho
2007-10-30 20:08     ` Mauro Carvalho Chehab

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=1193381218.13564.1217931615@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=mchehab@infradead.org \
    --cc=tiwai@suse.de \
    --cc=xyzzy@speakeasy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.