From: "Sam Duan" <sam_duan@ovt.com.cn>
To: linux-omap@vger.kernel.org
Subject: prcm_34xx.c--compiler error
Date: Tue, 25 Nov 2008 12:22:54 +0800 [thread overview]
Message-ID: <003e01c94eb5$7df5fd10$79e1f730$@com.cn> (raw)
Hi All,
I am new here, pardon me if this mail is not suitable and please point out
to me.
When CONFIG_OMAP3_PM was enabled with omapkernel2.6.27 for omapzoom
board(configured with "omap_ldp_pm_defconfig"), I got errors: "initializer
element is not constant" from line 66 to line 467 in prcm_34xx.c. All errors
relates to initialization for dom_reg[].regdef[].reg_addr,
dpll_reg[].regdef[].reg_addr, clksel_reg[].reg_addr..if we missed some
initialization in prcm-regs.h(line 40) for "typedef struct { volatile u32
offset[4096]; } __regbase32;"? I am not clear how the initialization
working.
The kernel can be built OK with "omap_ldp_defconfig" following steps in
"Getting Started with Linux OMAP Kernel".
I googled this error but couldn't find any information useful for this
issue. Did anybody meet the same problem?
Appreciate for your attention.
Sam Duan
reply other threads:[~2008-11-25 4:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='003e01c94eb5$7df5fd10$79e1f730$@com.cn' \
--to=sam_duan@ovt.com.cn \
--cc=linux-omap@vger.kernel.org \
/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