Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Matthew Hudson <mhudson@home.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: U2/Uturn stuff.
Date: Wed, 23 Aug 2000 09:06:51 -0700	[thread overview]
Message-ID: <200008231606.JAA11784@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 23 Aug 2000 10:39:07 PDT." <39A3F01B.E042265D@home.com>

Matthew Hudson wrote:
> Grant Grundler wrote:
> > Non-functional since U2/Uturn code is not ready yet (I'm working on it)
> > and not documented (let's not go there again right now). And even
> > if it were ready, I need to hack in some sort of an "I/O tree"
> > in order to support more than one U2/Uturn. K-class can have
> > multiple U2/Uturns.
> 
> I've looked over the ccio-dma.c code and nothing jumps out at me
> codewise. Can you point me to any information about the IOA
> chips?

Unfortunately not. If it's not clear from the code, point me
at the specific chunk of code you don't understand and I'll
add comments to make it clearer.

> Also, do you have an inkling of an idea where the problem
> might be? I'll take a crack at it and see if I can do anything,
> no promises. :-)

Bob Pflederer has it working and I committed his one line fix
to ccio-dma.c yesterday.  I haven't tested it as my C200 is being
shipped to someone else now.

Changes to lasi LAN (82596?) and cache flushing code are also
needed to make the system usable.

thanks,
grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

       reply	other threads:[~2000-08-23 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39A3F01B.E042265D@home.com>
2000-08-23 16:06 ` Grant Grundler [this message]
2000-08-24  8:55   ` U2/Uturn stuff Richard Hirst
2000-08-24 14:37     ` Matthew Hudson

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=200008231606.JAA11784@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=mhudson@home.com \
    --cc=parisc-linux@thepuffingroup.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