From: Michael Eager <eager@eagerm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] clk_setup decl missing in virtex_init
Date: Mon, 07 Nov 2011 14:46:47 -0800 [thread overview]
Message-ID: <4EB85FD7.2050004@eagerm.com> (raw)
The declaration of clk_setup is missing in
qemu/hw/virtex_ml507.c:
static void virtex_init(ram_addr_t ram_size,
const char *boot_device,
const char *kernel_filename,
const char *kernel_cmdline,
const char *initrd_filename, const char *cpu_model)
{
...
<no decl for clk_setup>
...
memset(clk_setup, 0, sizeof(clk_setup));
This SEGVs because clk_setup is an inline function defined in ppc.h.
(I presume that the linker generates an out-of-line copy.)
It isn't clear what the declaration should be. In ppc405_uc.c, there
is a decl:
clk_setup_t clk_setup[PPC405EP_CLK_NB];
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next reply other threads:[~2011-11-07 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 22:46 Michael Eager [this message]
2011-11-07 23:05 ` [Qemu-devel] clk_setup decl missing in virtex_init Edgar E. Iglesias
2011-11-07 23:25 ` Michael Eager
2011-11-08 21:01 ` Edgar E. Iglesias
2011-11-14 8:52 ` Fabien Chouteau
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=4EB85FD7.2050004@eagerm.com \
--to=eager@eagerm.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).