|To:||"J. Scott Kasten" <firstname.lastname@example.org>|
|Subject:||Re: implementation of software suspend on MIPS. (system log)|
|From:||"Hyon Lim" <email@example.com>|
|Date:||Thu, 1 Nov 2007 23:37:51 +0900|
|References:||<DDAE9570F73FC744918E843E20BE598B096E8E@server1.RightHand.righthandtech.com> <firstname.lastname@example.org> <Pine.SGI.email@example.com> <firstname.lastname@example.org> <Pine.LNX.email@example.com>|
Thank you for comments.
The remain work of my software suspend on MIPS project is resume procedure.
I already confirmed that suspend function was work. (See my post which contains system log).
In an i386 implementation, there are only few assembly code for suspend and resume procedure.
(You can refer : http://lxr.linux.no/source/arch/i386/power/swsusp.S?v=2.6.10)
So, my work will be similar with i386 implementation. Assembly code used in i386 implementation are several processor context related job
and copy saved page to memory. Instruction used in my MIPS implementation will be compatible to most of MIPS processor.
Because the instruction used in implementation is very basic (store and load and branch).
I agree your opinion related to maintainability and readability. So I implement my work with C and few assembly code.
Thank you for advice.
On 11/1/07, J. Scott Kasten <firstname.lastname@example.org> wrote:
Hyon Lim (임현)
Mobile. 010-8212-1240 (Intl' Call : +82-10-8212-1240)
Fax. 032-232-0578 (Intl' Available)
Homepage : http://www.alexlab.net
Blog : http://www.alexlab.net/blog
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: MIPS assembly directives in GCC, Thiemo Seufer|
|Next by Date:||Re: implementation of software suspend on MIPS. (system log), J. Scott Kasten|
|Previous by Thread:||Re: implementation of software suspend on MIPS. (system log), J. Scott Kasten|
|Next by Thread:||Re: implementation of software suspend on MIPS. (system log), J. Scott Kasten|
|Indexes:||[Date] [Thread] [Top] [All Lists]|