Hi Mathieu,
Mathieu Desnoyers wrote:
Is there any particular reason why m68knommu does not use the RODATA
linker script macro defined in asm-generic/vmlinux.lds.h ? It makes it
rather inconvenient to add new RO sections to the kernel.
This is going back some way, but this was the original commit message:
# --------------------------------------------
# 03/02/18 [email protected] 1.984
# [PATCH] use local RODATA setup for m68knommu linker script
#
# This patch removes the use of the common RODATA define in the m68knommu
# architecture. It cannot be used the same way for the m68knommu target.
# For starters just inserting it here is syntactically wrong. All the read
# only parts are grouped into a single "text" segment, and this is the root
# cause of the problem. So for the m68knommu arch it makes sense to not
# use the generic RODATA setup, but to list them locally.
The problem looks to be the same today.
The current vmlinux.lds.S for m68knommu directs sections out to ROM
or RAM depending on whether we are building to be run from some type
of read only memory (ROM, FLASH, etc) or RAM. The RODATA macro as it
stands doesn't allow that.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: [email protected]
Secure Computing Corporation PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
