From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: Thiemo Seufer <ths@networkno.de>
Cc: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: linker script for non-4k page size
Date: Sun, 11 Dec 2005 19:46:19 +0800 [thread overview]
Message-ID: <439C118B.20402@ict.ac.cn> (raw)
In-Reply-To: <20060202110554.GA26789@networkno.de>
Thiemo Seufer 写道:
>
> AFAIR a 64k alignment between code and data segments was introduced
> in debian shortly before the sarge release, but no attempt to
> systematically rebuild with that toolchain was made (because debian
> sarge supports only 4k paged kernels). A rebuild of the respective
> sarge packages should be enough to work around the problem.
Rebuild is too much work:), I just wrote some scripts to convert all the
debian packages: extract the files, convert the binaries, and repack.
If anyone is interested, I can provide the scripts(and the resulting
16k-enable sarge mipsel isos), though he has to wait some days before I go
back to lab.
>
>
> Thiemo
>
>
>
prev parent reply other threads:[~2006-02-02 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 2:37 linker script for non-4k page size Fuxin Zhang
2005-12-11 2:56 ` Fuxin Zhang
2006-02-02 11:05 ` Thiemo Seufer
2005-12-11 11:46 ` Fuxin Zhang [this message]
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=439C118B.20402@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
/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