From: Max Klein <mein_name@ist-einmalig.de>
To: raj raja <yuvaraj.addu@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa-driver cross compile problem - upgrading ALSA
Date: Mon, 02 Jul 2012 09:58:21 +0200 [thread overview]
Message-ID: <4FF1549D.5050206@ist-einmalig.de> (raw)
In-Reply-To: <CADgpFcpmf2LQzXYnfvUgZttAw0Ko71CdaTpAMJ+d3HpT0omTJA@mail.gmail.com>
What do you mean exactly? Am I missing any option? The other way around
would be to try integrating a newer ALSA driver version into my kernel
source (therefore updating the integrated ALSA driver before building
the kernel and afterwards directly build the Kernel with updated ALSA
version)?
> Better you compile with kernel
>
>
> Thanks
>
> Yuvi R
>
> On Fri, Jun 29, 2012 at 9:02 PM, Max Klein <mein_name@ist-einmalig.de>wrote:
>
>> I am running 2.6.27 kernel on arm board with ALSA driver version 1.0.17
>> (cat /proc/asound/version) and I would like to update ALSA driver version
>> to current 1.0.25.
>>
>> I am trying to build alsa-drivers with "./configure
>> --with-cross=arm-none-linux-gnueabi- --enable-dynamic-minors
>> --with-debug=full --with-isapnp=no --with-oss=no
>> --with-kernel=/data/src/kernel/linux-davinci
>> --with-build=/data/src/kernel/linux-davinci --with-sequencer=no"
>>
>> Afterwards I compile it via "make ARCH=arm" but this fails we the
>> following error:
>>
>> In file included from
>> /data/VRM/davinci33/alsa-1.0.25/alsa-driver-1.0.25/acore/hrtimer.c:1:
>> /data/VRM/davinci33/alsa-1.0.25/alsa-driver-1.0.25/include/adriver.h:753:
>> error: static declaration of 'jiffies_to_msecs' follows non-static
>> declaration
>> include/linux/jiffies.h:286: error: previous declaration of
>> 'jiffies_to_msecs' was here
>> /data/VRM/davinci33/alsa-1.0.25/alsa-driver-1.0.25/include/adriver.h:772:
>> error: static declaration of 'msecs_to_jiffies' follows non-static
>> declaration
>> include/linux/jiffies.h:288: error: previous declaration of
>> 'msecs_to_jiffies' was here
>>
>>
>> Can someone please help me how to get ALSA upgraded on my platform?
>> Obviously I am either doing something wrong when configuring or I am on the
>> absolutely wrong way?
>>
>> I am looking forward for any advice, thanks in advance!
next prev parent reply other threads:[~2012-07-02 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 15:32 alsa-driver cross compile problem - upgrading ALSA Max Klein
2012-07-02 4:06 ` raj raja
2012-07-02 7:58 ` Max Klein [this message]
2012-07-02 8:03 ` Rajeev kumar
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=4FF1549D.5050206@ist-einmalig.de \
--to=mein_name@ist-einmalig.de \
--cc=alsa-devel@alsa-project.org \
--cc=yuvaraj.addu@gmail.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