From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] - Relocating i386 Code - Permission to break orphan boards
Date: Sun, 30 Aug 2009 20:44:04 +1000 [thread overview]
Message-ID: <4A9A57F4.3070908@gmail.com> (raw)
Hi Wolfgang,
I have been playing around with gcc's -fpic and ld's -PIE and I think that
I can get 'proper' relocation happening on the i386 port. I've get the
basics down, and I've been looking at /lib_ppc/board.c for how the PPC
relocation scheme works and would like to replicate it (i.e. board_init_f,
board_init_r and relocate_code.
Unfortunately this leaves two options:
1) Tangle the i386 port up in a heap of #ifdefs, or;
2) Do a clean re-write for the eNET and break the other i386 boards
(sc520_cdp and sc520_spunk).
The other two i386 boards are OLD and i have my doubts as to if they ever
did work completely, and have really strong doubts as to them working now
I would really like to just throw all the old code out and do it all
cleanly, but not without strong support from the community.
What are your thoughts?
Regards,
G
next reply other threads:[~2009-08-30 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 10:44 Graeme Russ [this message]
2009-08-31 7:35 ` [U-Boot] [RFC] - Relocating i386 Code - Permission to break orphan boards 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=4A9A57F4.3070908@gmail.com \
--to=graeme.russ@gmail.com \
--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.