From: Tim Bird <tim.bird@am.sony.com>
To: � <barrioskmc@gmail.com>
Cc: "'Thiemo Seufer'" <ths@networkno.de>, linux-mips@linux-mips.org
Subject: Re: MIPS processors gain GNU/Linux binary prelinker
Date: Wed, 08 Nov 2006 09:18:31 -0800 [thread overview]
Message-ID: <45521167.9010603@am.sony.com> (raw)
In-Reply-To: <000801c702fb$c96e89e0$0202fea9@swcenter.sec.samsung.co.kr>
� wrote:
> Who know anymore about prelink for mips architecture?
> Let me know prelink for mips detaily.
> Thanks in advance.
There's a white paper available. See the linuxdevices article
for a link to it:
http://www.linuxdevices.com/news/NS6220941326.html
>
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org [mailto:linux-mips-bounce@linux-mips.
> org] On Behalf Of Thiemo Seufer
> Sent: Tuesday, November 07, 2006 11:05 PM
> To: Tim Bird
> Cc: CE Linux Developers List; linux-mips@linux-mips.org
> Subject: Re: MIPS processors gain GNU/Linux binary prelinker
>
> Tim Bird wrote:
>> FYI - For those interested in bootup time improvements on MIPS
>> processors, here is some information about the recently
>> developed MIPS prelinking feature, done by CodeSourcery
>> and MIPS Technologies.
>
> The patches are showing up piecemeal now on the various mailing lists,
> I also dumped a debian-styleish patchset at
> ftp://ftp.linux-mips.org/pub/linux/mips/people/ths/mips-prelinker-patches-
> debian/
>
>
> Thiemo
>
>
--
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
prev parent reply other threads:[~2006-11-08 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 22:47 MIPS processors gain GNU/Linux binary prelinker Tim Bird
2006-11-07 14:04 ` Thiemo Seufer
2006-11-08 6:04 ` 김민찬
2006-11-08 6:04 ` 김민찬
2006-11-08 8:41 ` Fu, He Wei PSE NKG
2006-11-08 8:41 ` Fu, He Wei PSE NKG
2006-11-08 17:18 ` Tim Bird [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=45521167.9010603@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=barrioskmc@gmail.com \
--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