public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Lee Revell <rlrevell@joe-job.com>,
	alsa devel <alsa-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Johannes Stezenbach <js@linuxtv.org>,
	Linux and Kernel Video <video4linux-list@redhat.com>,
	Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [RFC] Moving snd-bt87x and btaudio to drivers/media
Date: Wed, 18 Jan 2006 15:51:21 -0200	[thread overview]
Message-ID: <1137606681.28917.31.camel@localhost> (raw)
In-Reply-To: <s5h8xtdtsej.wl%tiwai@suse.de>

Em Qua, 2006-01-18 às 17:25 +0100, Takashi Iwai escreveu:
> At Wed, 18 Jan 2006 11:29:28 -0200,
> Mauro Carvalho Chehab wrote:
> > 

> Which directory do you suppose exactly?  drivers/media/tv (or
> something like that), or existing one like drivers/media/video?
	Better is to be at the same dir as other bttv modules. Currently, it
wil be under drivers/media/video. It seems to me that drivers/media
should be better organized, since lots of shared code between dvb and
v4l are emerging. IMHO, it seems to be a good idea to create a newer dir
to handle chipsets like:
 /drivers/media/chips/
	and include bttv, cx88, em28xx, saa7134 and others as separate dirs
under /chips. This way, it would be easier to detect code duplications
and similarities.
> 
> I personally have no big objection to move snd-bt87x location.
> although the external alsa-driver tarball would require a tune.
> It was there simply because the driver is basically independent from
> other layers but sound.
	True.
>   From the functionality viewpoint, it's better
> to gather all modules, of course.
> 
> One point I'm conerned is, however, the order of objects in the
> built-in kernel.  Recently we had a problem of initializations of
> saa7134-alsa and sound core stuff.  We should be careful about that.
	I've waited to the end of 2.6.16 window to start these discussions to
give us some time to fix compilation order and to realign all necessary
stuff. I think we will have some time until 2.6.17 to prioritize sound
core loading as Linus suggested. There's no rush for such changes.
> 
> Also, more intutive Kconfig would be nice to have.  For example, it'd
> be better to use a choice type for saa7134-alsa and -oss drivers.
> Also, to my eyes, it's better to select CONFIG_SND from saa7134-alsa
> instead of depending on it.
	Agreed. I have already a patch for it to use choice type. I'll work on
it to select CONFIG_SND and CONFIG_SND_PCM.
> 
> 
> Takashi
Cheers, 
Mauro.


  reply	other threads:[~2006-01-18 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 13:29 [RFC] Moving snd-bt87x and btaudio to drivers/media Mauro Carvalho Chehab
2006-01-18 16:25 ` Takashi Iwai
2006-01-18 17:51   ` Mauro Carvalho Chehab [this message]
2006-01-18 19:04   ` Manu Abraham
2006-01-18 19:41 ` Adrian Bunk
2006-01-18 19:53   ` 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=1137606681.28917.31.camel@localhost \
    --to=mchehab@infradead.org \
    --cc=abraham.manu@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=js@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=tiwai@suse.de \
    --cc=torvalds@osdl.org \
    --cc=video4linux-list@redhat.com \
    /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