Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kevin Paul Herbert <kph@cisco.com>
To: Jun Sun <jsun@mvista.com>
Cc: Dimitri Torfs <dimitri@sonycom.com>,
	Pete Popov <ppopov@mvista.com>,
	Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Re: How stable is 2.6 on a SB1250 processor?
Date: 14 Jan 2004 11:09:21 -0800	[thread overview]
Message-ID: <1074107359.31877.14.camel@shakedown> (raw)
In-Reply-To: <20040113143137.N11733@mvista.com>

Thanks for the tips. I incorporated Dmitri's patches to uaccess.h and
the syscall handlers and got usermode to come up correctly.

I'm aware of the SB1250 PCI problems and will be addressing that after I
get a few more on-board peripherals working. I've got my own fairly
complex PCI subsystem to port from 2.4 (hotplug, many bridges,
hypertransport configuration) and the main thing that I need from the
core SB1250 support is the ability to generate configuration cycles.
Because of the way the hardware works, I have to program all the bridges
myself (the ROM firmware does not do this for me).

I'll be sure to send patches to the list for anything I fix in the core
SB1250 PCI support.

Thanks again for the tips,

Kevin


-- 
Kevin Paul Herbert <kph@cisco.com>
cisco Systems, Inc.

      parent reply	other threads:[~2004-01-14 19:09 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
2004-01-13 22:45       ` Ralf Baechle
2004-01-13 23:02         ` Jun Sun
2004-01-14 19:09       ` Kevin Paul Herbert [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=1074107359.31877.14.camel@shakedown \
    --to=kph@cisco.com \
    --cc=dimitri@sonycom.com \
    --cc=jsun@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox