All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: linux-kernel@vger.kernel.org
Subject: common RODATA in vmlinux.lds.h (2.5.59)
Date: Wed, 22 Jan 2003 12:05:44 +1000	[thread overview]
Message-ID: <3E2DFC78.1040402@snapgear.com> (raw)

Hi All,

The new common definition of RODATA for linker scripts
(in include/asm-generic/vmlinux.lds.h) is causing me some
amount of pain, at least on the m68knommu architecture.

The problem is that on the m68knommu arch linker script
it fundamentaly groups everything into 2 memory regions,
one for flash and one for ram. Each section is then
directed to the appropriate memory region, eg:

         .text : {
             *(.text)
         } > flash

With the way the RODATA define is setup I cannot do this.
It contains definitions for a number of complete sections.

Anyone got any ideas on the best way to fix this?

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Wizard        EMAIL:  gerg@snapgear.com
Snapgear Pty Ltd                               PHONE:    +61 7 3279 1822
825 Stanley St,                                  FAX:    +61 7 3279 1820
Woolloongabba, QLD, 4102, Australia              WEB:   www.SnapGear.com






             reply	other threads:[~2003-01-22  1:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  2:05 Greg Ungerer [this message]
2003-01-22  2:49 ` common RODATA in vmlinux.lds.h (2.5.59) Kai Germaschewski
2003-01-22  3:25   ` Greg Ungerer
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=3E2DFC78.1040402@snapgear.com \
    --to=gerg@snapgear.com \
    --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 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.