All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Alex deVries <adevries@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] PCI bus walking!
Date: Sun, 03 Oct 1999 14:57:02 -0700	[thread overview]
Message-ID: <199910032157.OAA14770@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Sun, 03 Oct 1999 02:54:47 PDT." <37F6FDB7.54FEEE9F@thepuffingroup.com>

Alex deVries wrote:
> 
> The kernel tree in CVS now has PCI code sort of working, so it can scan
> the PCI bus on a Dino and find devices.  It's still broken in several
> ways: it doesn't support multiple dino's, it can't handle interrupts yet,
> and is basically doing things in the wrong order, but does work.

Alex,
This is awesome! Kudos!

I can fix all of those things. Can you tell me:
o what's broken about multi-Dino support
o What you think is wrong with interrupts?
  (I assume registration isn't working as dino_interrupt() is simple)
o What's the order you are seeing and what order shoulds it be.

Kudos again!
grant

ps. Kudos to Philipp too for yesterdays code drop!

      reply	other threads:[~1999-10-03 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-03  6:54 [parisc-linux] PCI bus walking! Alex deVries
1999-10-03 21:57 ` Grant Grundler [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=199910032157.OAA14770@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=adevries@thepuffingroup.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 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.