From: Jun Nakajima <jun@sco.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] TODO list
Date: Fri, 09 Feb 2001 19:14:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005128@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005124@msgid-missing>
Do we want to support epc-based system calls? I know some other IA-64 OS
uses that mechanism. I'm not sure how much perfermance gain we can get
by that in Linux, though.
Don Dugger wrote:
>
> All-
>
> As promised, here is the Linux IA64 To-Do list, current
> as of 2/9/01. The pretty printed HTML version is always
> available at `http://www.linuxia64.org/todo.html/'. Note
> that there are a few things that no one has signed up to
> do yet. If you are interested in taking responsibility for:
>
> EEPro100
> Hot plug SCSI
> GLIBC unwind API
> setjmp cleanup
>
> just let me know (here is your chance for fame and fortune :-)
>
> Linux IA64 To-Do List
> Februrary 9, 2001
>
> Kernel
>
> Task
> Owner
> Details
>
> Unaligned handler
> David Mosberger - DONE
> Works for user procs, need support for kernel
>
>
> CS4281 Sound
> Thomas Woller
> Should be OK, requires updated MPG128 and/or XMMS
>
>
> EEPro100
> ?
> Hangs on >180MB xfers
>
>
> Hot plug SCSI
> ?
> Hotplugging doesn't crash the kernel but the
> kernel doesn't detect the change.
>
>
> Other HW Support
>
>
> UNIX98 test suite
> Doug Beattie
> Fix test suite failures, need simple test cases
>
>
> CPU state on execve
> David Mosberger
> Clear CPU state to avoid info leak to new program.
> Alan Cox thinks it would be sufficient to do this when
> current->dumpable is zero
>
> AGP Support
> Chris Ahna
>
>
> DRI support
> Chris Ahna
> Need DRI module for ATI Rage128
>
>
> llseek
> Erich Focht - DONE
> Need llseek for fs/proc/base.c:proc_mem operations.
> Patch submitted.
>
>
> Libraries
>
> Task
> Owner
> Details
>
>
> gprof support
> Jes Sorensen
> Most of the GLIBC bits should be there,
> hope to get the M4 autoconf done soon.
>
>
> GLIBC unwind API
> ?
> Define API that works with signal handling, probably
> starting from the kernel unwinder.
> Implement this API
> Contact David Mosberger for details.
>
>
>
> setjmp cleanup
> ?
> Bring setjmp into compliance with SW conventions
> (flushrs must be done on a setjmp)
> Remove extraneous loadrs in __longjmp.
> Contact David Mosberger for details.
>
>
>
> Applications
>
> Task Owner Details
>
>
> gdb
> Kevin Buettner
> NaT bits fail
> pthread support
> coredump support broken
> inferior function calls fail
> HW watchpoints fail
>
>
> strace
> Don Dugger
> new system calls added
> strace -f hangs on a fork
> --
> Don Dugger
> "Censeo Toto nos in Kansa esse decisse." - D. Gale
> n0ano@valinux.com
> Ph: 303/938-9838
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Jun U Nakajima
Core OS Development
SCO/Murray Hill, NJ
Email: jun@sco.com, Phone: 908-790-2352 Fax: 908-790-2426
next prev parent reply other threads:[~2001-02-09 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 17:58 [Linux-ia64] TODO list Don Dugger
2001-02-09 19:14 ` Jun Nakajima [this message]
2001-02-09 19:42 ` David Mosberger
2001-02-09 20:01 ` Don Dugger
2001-02-09 20:04 ` David Mosberger
2001-02-16 19:29 ` Dragan Stancevic
2001-02-16 21:37 ` Don Dugger
2001-02-16 23:30 ` Michael Madore
2001-02-17 2:14 ` Dragan Stancevic
2001-02-17 2:54 ` Don Dugger
2001-02-17 19:44 ` Dragan Stancevic
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=marc-linux-ia64-105590693005128@msgid-missing \
--to=jun@sco.com \
--cc=linux-ia64@vger.kernel.org \
/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