From: Yuri Tikhonov <yur@emcraft•com>
To: Andreas Schwab <schwab@suse•de>
Cc: wd@denx•de, dzu@denx•de, miltonm@bga•com,
linuxppc-dev@ozlabs•org, paulus@samba•org, yanok@emcraft•com
Subject: Re[2]: [PATCH][v2] powerpc 44x: support for 256KB PAGE_SIZE
Date: Sun, 21 Dec 2008 23:35:48 +0300 [thread overview]
Message-ID: <121213804.20081221233548@emcraft.com> (raw)
In-Reply-To: <jelju91e1q.fsf@sykes.suse.de>
=0D=0AOn Sunday, December 21, 2008 you wrote:
> Yuri Tikhonov <yur@emcraft•com> writes:
>> Thanks for pointing this. I guess, the -zmax-page-size option is new=20
>> to binutils 2.17.50.0.10. Right?
> It was added 2=BD years ago.
Yes, approximately: http://gcc.gnu.org/ml/gcc/2006-07/msg00361.html
"
Date: Sat, 15 Jul 2006 15:19:05 -0700
Subject: The Linux binutils 2.17.50.0.3 is released
Changes from binutils 2.17.50.0.2:
...
16. Add "-z max-page-size=3D" and "-z common-page-size=3D" to ELF linker.
"
>> I'll remove the STDBINUTILS config option from this patch then, and=20
>> correspondingly update the description.
I thought about this more, and I guess that we should keep the=20
dependency on the newly introduced by this patch STDBINUTILS option.=20
Perhaps, change it name to, say, STD_ELF_LINKING.
Because, in any case, either should we patch binutils, or should we=20
pass some non-default value to the linker: the resulted application=20
doesn't match the ELF standard, and the applications which match the=20
standard simply won't work with the 256K paged kernel - so, a user has=20
to be aware of it before turning the 256K on.
What do you think about this?
Regards, Yuri
next prev parent reply other threads:[~2008-12-21 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 11:46 [PATCH][v2] powerpc 44x: support for 256KB PAGE_SIZE Yuri Tikhonov
2008-12-21 17:07 ` Andreas Schwab
2008-12-21 20:00 ` Re[2]: " Yuri Tikhonov
2008-12-21 20:14 ` Andreas Schwab
2008-12-21 20:35 ` Yuri Tikhonov [this message]
2008-12-21 20:57 ` Andreas Schwab
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=121213804.20081221233548@emcraft.com \
--to=yur@emcraft$(echo .)com \
--cc=dzu@denx$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=miltonm@bga$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=schwab@suse$(echo .)de \
--cc=wd@denx$(echo .)de \
--cc=yanok@emcraft$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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