From: Greg Ungerer <gerg@snapgear.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: common RODATA in vmlinux.lds.h (2.5.59)
Date: Wed, 22 Jan 2003 13:25:44 +1000 [thread overview]
Message-ID: <3E2E0F38.7090506@snapgear.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301212045000.1577-100000@chaos.physics.uiowa.edu>
Hi Kai,
Kai Germaschewski wrote:
> First of all, asm-generic/vmlinux.lds.h is there to share common code
> where possible, so if it's not possible, you still have the option of
> having your own special code in arch/$(ARCH)/vmlinux.lds.S
And that is exactly what I have done as an immediate fix.
It would be nice if all architectures could use this
common code. Saves me having to specifically fix m68knommu
linker script when ever things inside RODATA change.
> Having said that, you could add
>
> #define TEXT_MEM > flash
>
> at the beginning of arch/m68knommu/vmlinux.lds.S
>
> and
>
> #ifndef TEXT_MEM
> #define TEXT_MEM
> #endif
>
> at the beginning of include/asm-generic/vmlinux.lds.h and then change
>
> .text : {
> *(.text)
> - }
> + } TEXT_MEM
>
> Would that work for you?
Yep, I would be happy with that.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Wizard EMAIL: gerg@snapgear.com
SnapGear Pty Ltd PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: www.SnapGear.com
next prev parent reply other threads:[~2003-01-22 3:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 2:05 common RODATA in vmlinux.lds.h (2.5.59) Greg Ungerer
2003-01-22 2:49 ` Kai Germaschewski
2003-01-22 3:25 ` Greg Ungerer [this message]
2003-01-22 4:32 ` Miles Bader
2003-01-22 4:47 ` Greg Ungerer
2003-01-22 5:42 ` Sam Ravnborg
2003-01-22 6:00 ` Miles Bader
2003-01-22 5:55 ` Kai Germaschewski
2003-01-22 6:23 ` Miles Bader
2003-01-22 16:32 ` Kai Germaschewski
2003-01-23 2:03 ` Miles Bader
2003-01-23 5:59 ` Greg Ungerer
2003-01-22 6:35 ` Greg Ungerer
2003-01-22 16:35 ` Kai Germaschewski
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=3E2E0F38.7090506@snapgear.com \
--to=gerg@snapgear.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@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