[alsa-devel] git trees

[Steve Calfee]

Hi Mark,

I am starting to look at a new codec driver. I have been looking at the
alsa-project wiki describing the various git trees. I am confused
because they seem to be lagging the linux releases (ie 2.6.38 is out,
not in the two trees I have tried.

The wiki proposed occasional developers use 3 trees - not clear what is
in each. ie:

git clone http://git.alsa-project.org/http/alsa-driver.git alsa-driver
git clone http://git.alsa-project.org/http/alsa-kmirror.git alsa-kmirror

if you like do only changes in code in alsa-kmirror, please, use
alsa-kernel repository

git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel

I really don't understand the sentence:
"if you like do only changes in code in alsa-kmirror, please, use
alsa-kernel repository"


When I built alsa-kernel, I kernel version 2.6.38-rc8+ - which built and
boots on my target.

I also cloned the kernel.org broonie/sound-2.6.git tree But when I look
at branches I see:
asoc$ git branch -r
  origin/ac97-runtime-pm
  origin/ads117x
  origin/asoc-regulator
  origin/asoc-v2-dev
  origin/bias-off
  origin/dapm
  origin/dapm-log
  origin/dev
  origin/ep93xx
  origin/for-2.6.29
  origin/for-2.6.30
  origin/for-2.6.31
  origin/for-2.6.32
  origin/for-2.6.33
  origin/for-2.6.34
  origin/for-2.6.35
  origin/for-2.6.36
  origin/for-2.6.37
  origin/for-2.6.38
  origin/for-2.6.39
  origin/for-2.6.40
  origin/for-next
  origin/init-card
  origin/new-maintainers
  origin/pending
  origin/pxa-ssp
  origin/refactoring
  origin/reg-cache
  origin/tegra-arch
  origin/twl4030-mfd
  origin/untested

So I checked out origin/for-2.6.39 when i built that I got a kernel
version 2.6.38-rc1 or something. (and it built but didn't boot)

What I need to know is which tree and which branch or tag I should use
to develop on and to submit alsa patches from.

Thanks for the help.

Regards, Steve