From: lamikr <lamikr@cc.jyu.fi>
To: Komal Shah <komal_shah802003@yahoo.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: n770 alsa build broken
Date: Thu, 06 Apr 2006 02:18:04 +0300 [thread overview]
Message-ID: <4434502C.3050206@cc.jyu.fi> (raw)
In-Reply-To: <20060404161825.67622.qmail@web32901.mail.mud.yahoo.com>
Komal Shah wrote:
>Please supply the patch.
>
>#make n770_defconfig
>#make
>
>sound/arm/omap/omap-alsa-dma.c: In function `omap_sound_dma_link_lch':
>sound/arm/omap/omap-alsa-dma.c:143: error: `FN_IN' undeclared (first
>use in this function)
>
>
In which kernel version you got this? I tried to use your method instead
of opening xconfig but I could not reproduce this neither with
2.6.16-omap2 or
with the linux-omap-git head. With the code in head I the build stopped
however already earlier to some MMC build problems. The 2.6.16-omap2
compiled just fine.
One thing I noticed however. As 770 uses also alsa driver, it needs alsa
platform driver initialization stuff. For that I will send a patch in a
separate mail.
Mika
prev parent reply other threads:[~2006-04-05 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 16:18 n770 alsa build broken Komal Shah
2006-04-05 23:18 ` lamikr [this message]
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=4434502C.3050206@cc.jyu.fi \
--to=lamikr@cc.jyu.fi \
--cc=komal_shah802003@yahoo.com \
--cc=linux-omap-open-source@linux.omap.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