All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Palash Bandyopadhyay <Palash.Bandyopadhyay@conexant.com>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Question about adding support for new audio codecs from Conexant
Date: Thu, 02 Jun 2011 08:40:59 +0200	[thread overview]
Message-ID: <4DE7307B.7080505@perex.cz> (raw)
In-Reply-To: <34B38BE41EDBA046A4AFBB591FA311320501B9BD3A@NBMBX01.bbnet.ad>

Date 2.6.2011 07:04, Palash Bandyopadhyay wrote:
> Dear Jaroslav,
> 
>  
> 
>   I am a group lead and a developer for Conexant Systems
> (www.conexant.com <http://www.conexant.com>). Over the years, we have
> been developing quite a range of audio devices. We have also written
> ALSA drivers for a few of our I2S/PCM codecs that work with SoCs such as
> NVidia’s Tegra, Samsung’s V210, Freescale’s iMx series.
> 
>  
> 
>   The question that I have is, what is the procedure of adding these
> drivers to the main ALSA repository so that users can have access to
> this directly rather than to have to contact us? Any suggestions/help in
> this direction will be very helpful. Going through the wiki site, I see
> that main stream developers might need write access to the git
> repository. If that is true, what is the process that needs to be
> followed in order to get write access to the repository?

Hello,

	basically, send your patches (try to split changes to small pieces) to
the alsa-devel mailing list. We review them and apply to our repository.
If you have many patches available, it would be better to create your
own kernel GIT tree with these patches and send a summary with the GIT
URL to the alsa-devel mailing list. We pull your patches after review.

>   BTW, I am also a developer for the V4L/LinuxTV community as we
> (Conexant) also make capture chips for PCTV and Surveillance.

Nice to know.

				Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

           reply	other threads:[~2011-06-02  6:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <34B38BE41EDBA046A4AFBB591FA311320501B9BD3A@NBMBX01.bbnet.ad>]

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=4DE7307B.7080505@perex.cz \
    --to=perex@perex.cz \
    --cc=Palash.Bandyopadhyay@conexant.com \
    --cc=alsa-devel@alsa-project.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.