From: Steve Calfee <stevecalfee@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org
Subject: git trees
Date: Wed, 30 Mar 2011 17:19:30 -0700 [thread overview]
Message-ID: <4D93C892.6080602@gmail.com> (raw)
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
next reply other threads:[~2011-03-31 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 0:19 Steve Calfee [this message]
2011-03-31 0:33 ` git trees Mark Brown
2011-03-31 1:03 ` Steve Calfee
2011-03-31 21:39 ` Mark Brown
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=4D93C892.6080602@gmail.com \
--to=stevecalfee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).