All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Dimitri Torfs <dimitri@sonycom.com>
Cc: Pete Popov <ppopov@mvista.com>,
	kph@cisco.com,
	Linux MIPS mailing list <linux-mips@linux-mips.org>,
	jsun@mvista.com
Subject: Re: How stable is 2.6 on a SB1250 processor?
Date: Tue, 13 Jan 2004 14:31:37 -0800	[thread overview]
Message-ID: <20040113143137.N11733@mvista.com> (raw)
In-Reply-To: <20040113214454.GA2737@sonycom.com>; from dimitri@sonycom.com on Tue, Jan 13, 2004 at 10:44:54PM +0100

On Tue, Jan 13, 2004 at 10:44:54PM +0100, Dimitri Torfs wrote:
> On Tue, Jan 13, 2004 at 01:09:25PM -0800, Pete Popov wrote:
> > 
> > I think userland is still broken. Ralf was working on the access_ok
> > problem the last time I talked to him.
> > 
> 
> Yes, if it's a 32-bit kernel then it's definitely broken. You might want
> to check out
> http://www.linux-mips.org/archives/linux-mips/2004-01/msg00000.html.
> 
> After that fix, user space stuff started to work for me.
> 

Yes, that is a temporary fix for the problem.

bcm1250 PCI still have issues though.  I have not looked into it.

What is troubling me most is either rockhopper nor malta works on 2.6.
With rockhopper I had to disable cache in order to run.  I
suspect there is something fundamental still not quite right, possibly
only affecting cache noncoherent systems.

More debugging fun ...

Jun

  reply	other threads:[~2004-01-13 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 21:03 How stable is 2.6 on a SB1250 processor? Kevin Paul Herbert
2004-01-13 21:09 ` Pete Popov
2004-01-13 21:44   ` Dimitri Torfs
2004-01-13 22:31     ` Jun Sun [this message]
2004-01-13 22:45       ` Ralf Baechle
2004-01-13 23:02         ` Jun Sun
2004-01-14 19:09       ` Kevin Paul Herbert

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=20040113143137.N11733@mvista.com \
    --to=jsun@mvista.com \
    --cc=dimitri@sonycom.com \
    --cc=kph@cisco.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@mvista.com \
    /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.