From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA-64 Linux TODO list
Date: Wed, 10 Jan 2001 21:51:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005018@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205896@msgid-missing>
All-
OK, I got the web page up with the TODO list on it. You can link
to it from `www.linuxia64.org' or go directly to the page at
`www.linuxia64.org/todo.html'. Check it out and let me know if
there are any changes or additions. Some obvious changes are we
need some volunteers for `EEPro100', `execve' and `gprof' - any
takers?
In addition to the web page I plan on sending out a text copy of
the list to this mailing list on a bi-weekly basis.
On Tue, Jan 09, 2001 at 11:23:23AM -0800, David Mosberger wrote:
> Since we're getting closer to a real release of various IA-64 Linux
> distros, I thought it would be a good idea to pass around my TODO
> list. I'd really appreciate if someone else could maintain this list
> and mail it out periodically (weekly?) as my bw is pretty limited
> right now. Here is what comes to mind:
>
> Kernel
> - enable kernel unaligned handler
> - verify that all on-board hardware is supported and working:
> - does cs4281 sound driver work reliably now?
> - what to do about eepro100? (currently hangs on > 180MB transfers?)
> - investigate and fix test suite failures reported by SCO (Who's the
> contact person at SCO for this? Please make available simple test
> cases that reproduce the problem so we can go about fixing them.)
> - consider clearing CPU state on an execve() to avoid leaking information
> to a new program; Alan Cox thinks it would be sufficient to do this
> when current->dumpable is zero
>
> Libraries
> - gprof support?
>
> Apps
> - gdb
> - NaT bits don't seem to work properly?
> - coredump support still broken?
> - strace
> - 'strace -f' hangs if the program forks a child;
> - verify that the new system calls have been added
>
> I'm planning to work on the kernel unaligned handler but if someone
> else is dying on doing that, let me know. ;-)
>
> If you can think of anything else, please let me know---I'll try keep
> the list uptodate for now.
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
next prev parent reply other threads:[~2001-01-10 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 19:23 [Linux-ia64] IA-64 Linux TODO list David Mosberger
2001-01-09 19:47 ` Don Dugger
2001-01-09 20:05 ` Uros Prestor
2001-01-09 20:32 ` Ahna, Christopher J
2001-01-09 21:25 ` Kevin Buettner
2001-01-09 21:44 ` David Mosberger
2001-01-10 21:51 ` Don Dugger [this message]
2001-01-11 17:29 ` Jes Sorensen
2001-01-25 0:19 ` Johannes Erdfelt
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-105590693005018@msgid-missing \
--to=n0ano@valinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.