Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: "Bryan W. Headley" <bheadley@interaccess.com>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: C110 question
Date: Thu, 4 Oct 2001 17:27:02 +0200	[thread overview]
Message-ID: <20011004172702.B5324@solo.franken.de> (raw)
In-Reply-To: <200110021733.LAA07820@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Tue, Oct 02, 2001 at 11:33:05AM -0600

On Tue, Oct 02, 2001 at 11:33:05AM -0600, Grant Grundler wrote:
> > The drives are hanging off of a FWSCSI controller. I'm right in thinking 
> > that the support for that is still not there, right?
> 
> In general the SCSI driver for Zalon works. The problem is with
> IO MMU support for devices below anything other than the first IO MMU.

I don't know how close a C110 is compared to a C100, but we had massive
filesystem corruptions on a C100 (and a C160) during the weekend in Oldenburg. 
It looked like the problems I had with my C200, which seem to be fixed
(I've compiled XFree and mozialla on that machine). I'll recheck on
my C100, when I get home again.

> XF86 is mostly working for B180 and 712's from reports on p-l mailing list.
> If you have Vis-EG (normal built-in) graphics, it might work for
> C110 as well since it's not using IO MMU (afaik).

it should work. To use stifb you need to remove the check for Artist
only (search for HACK:).

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                 [ Alexander Viro on linux-kernel ]

      reply	other threads:[~2001-10-04 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BB9D453.3050308@interaccess.com>
2001-10-02 17:33 ` [parisc-linux] Re: C110 question Grant Grundler
2001-10-04 15:27   ` Thomas Bogendoerfer [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=20011004172702.B5324@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bheadley@interaccess.com \
    --cc=grundler@puffin.external.hp.com \
    --cc=parisc-linux@lists.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