[lkml]   [2003]   [Jan]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: common RODATA in (2.5.59)
Hi Kai,

Kai Germaschewski wrote:
> Yes, I saw it, but on the other hand I'd like to avoid introducing
> complexity which isn't really needed. So the important question is: Is
> there a reason that v850 does things differently, or could it just as well
> live with separate .text and .rodata sections (Note that sections
> like .rodata1 will be discarded when empty).

The reason we tend to group all these things together is that logically
that is the way they are layed out between flash and ram (and running
the kernel code in flash is really the case that is interresting here).
Where you have the text and rodata parts resident in flash (and this is
where they stay), and the data and bss in ram (but they start in flash
and are copied on start up to ram). So 2 very different memory regions
involved, not just one contiguous blob like on most VM architectures.

So to build a flash image most people just objcopy out the
text and the data (and init really too) sections and cat them
together and that is the binary image that you program into
your flash. If you have lots of sections this makes this
extraction and concatentation process just plain ugly. And when
you add new sections your flash building needs to know about
them and handle them.


Greg Ungerer -- Chief Software Wizard EMAIL:
SnapGear Pty Ltd PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB:

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.131 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site