From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] x86: Force the lib_sysinfo structure to be in the .data section
Date: Sun, 8 Jan 2012 00:19:48 -0500 [thread overview]
Message-ID: <201201080019.49987.vapier@gentoo.org> (raw)
In-Reply-To: <1322633275-10542-4-git-send-email-gabeblack@chromium.org>
On Wednesday 30 November 2011 01:07:54 Gabe Black wrote:
> +struct sysinfo_t lib_sysinfo __attribute__((section(".data")));
seems like it should be .data.lib_sysinfo
or maybe pick a field you always init and set it to something non-zero.
struct sysinfo_t lib_sysinfo = {
/* force into .data */
.cpu_khz = 1,
};
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120108/ab4a754a/attachment.pgp>
next prev parent reply other threads:[~2012-01-08 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 6:07 [U-Boot] [PATCH 0/4] Add code to read in the coreboot tables and fill in memory info Gabe Black
2011-11-30 6:07 ` [U-Boot] [PATCH 1/4] x86: Import code from coreboot's libpayload to parse the coreboot table Gabe Black
2011-12-02 12:06 ` Graeme Russ
2011-11-30 6:07 ` [U-Boot] [PATCH 2/4] x86: Determine the ram size using the coreboot tables Gabe Black
2011-11-30 6:07 ` [U-Boot] [PATCH 3/4] x86: Force the lib_sysinfo structure to be in the .data section Gabe Black
2011-12-02 21:10 ` Graeme Russ
2011-12-02 21:16 ` Gabe Black
2011-12-02 21:22 ` Graeme Russ
2011-12-02 21:27 ` Gabe Black
2012-01-08 5:19 ` Mike Frysinger [this message]
2011-11-30 6:07 ` [U-Boot] [PATCH 4/4] x86: Add infrastructure to extract an e820 table from the coreboot tables Gabe Black
2011-12-02 21:14 ` Graeme Russ
2011-12-02 21:24 ` Gabe Black
2011-12-02 21:36 ` Graeme Russ
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=201201080019.49987.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.