Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] state of 2.5 merge
Date: Sat, 27 Jul 2002 22:00:53 -0700	[thread overview]
Message-ID: <20020728050053.GA1419@tausq.org> (raw)
In-Reply-To: <20020722034037.F12523@parcelfarce.linux.theplanet.co.uk>

> we're still a little short of attempting to link.  entry.S and head.S
> need to be massaged to work in the new O(1) scheduler world.  note that
> we're leaving preempt disabled until later.  once it does attempt to link,
> i suspect we'll find there're a lot of functions which need to be written
> (particularly mm-related ones) and probably some include cleanups to do.

In case people are wondering where this is at.... today we got a
somewhat working shell.....

kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Stand-alone shell (version 3.4)
> uname -a
Linux (none) 2.5.26-pa0 #106 Sat Jul 27 18:49:37 PDT 2002 parisc unknown unknown GNU/Linux

This is on a a500 (64-bit kernel). Richard has also had success with
b180 (iirc).

For the most part things are still quite broken (init, ls, etc don't 
work yet).  There are probably some changes related to the task_struct 
to thread_info transition that still needs to be worked out for 
syscalls to work correctly.... 

Richard Hirst worked out most of the bugs to get userspace working.
Thanks Richard! :-)

randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

      reply	other threads:[~2002-07-28  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22  2:40 [parisc-linux] state of 2.5 merge Matthew Wilcox
2002-07-28  5:00 ` Randolph Chung [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=20020728050053.GA1419@tausq.org \
    --to=randolph@tausq.org \
    --cc=parisc-linux@parisc-linux.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