From: "Andrey A. Porodko" <andrey.porodko@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jorge Luis Zapata Muga <jorgeluis.zapata@gmail.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Chaithrika U S <chaithrika@ti.com>,
Troy Kisky <troy.kisky@boundarydevices.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Kevin Hilman <khilman@deeprootsystems.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: Sound support for Neuros OSD2 Davinci based board.
Date: Mon, 30 Nov 2009 11:47:52 +0500 [thread overview]
Message-ID: <4B136A98.4010400@gmail.com> (raw)
In-Reply-To: <20091127164733.GC11913@rakim.wolfsonmicro.main>
Mark Brown wrote:
> On Thu, Nov 26, 2009 at 06:06:38PM +0500, A. Porodko wrote:
>
>> Hello,
>>
>> Here is a patch for Neuros OSD2 Davinci (DM6446) based board sound support.
>> Patch made against 2.6.32-rc6 kernel.
>>
>
> This doesn't apply against current ASoC. Could you please regenerate
> against this branch:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.33
>
>
Hi Mark,
Are you sure you have the latest davinci soc support in your tree?
Mine file davinci_evm.c is 7.5k size, in your
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git
repo your is 5.5k. Quick glance shows that in your repo davinci support
lacks of da830_evm support.
I'm confused which one is I have to use and apply patch to?
--
Best regards
Andrey A. Porodko
next prev parent reply other threads:[~2009-11-30 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 13:06 Sound support for Neuros OSD2 Davinci based board A. Porodko
2009-11-26 13:27 ` Chaithrika U S
2009-11-27 11:12 ` [alsa-devel] " Mark Brown
2009-11-27 13:14 ` A. Porodko
2009-11-27 13:28 ` Mark Brown
2009-11-27 16:47 ` Mark Brown
2009-11-28 15:07 ` Andrey A. Porodko
2009-11-30 6:47 ` Andrey A. Porodko [this message]
2009-11-30 6:52 ` Andrey A. Porodko
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=4B136A98.4010400@gmail.com \
--to=andrey.porodko@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=chaithrika@ti.com \
--cc=dbrownell@users.sourceforge.net \
--cc=jorgeluis.zapata@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=troy.kisky@boundarydevices.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