All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Bodo <rsb@ostel.com>
To: linux-kernel@vger.rutgers.edu
Subject: PLX 9050 chip
Date: Thu, 16 Sep 1999 18:02:11 -0700	[thread overview]
Message-ID: <37E19313.6090BE36@ostel.com> (raw)

Hi,

Does anyone on this list have experience with the PLX 9050 PCI bus
interface chip?  I am having this strange problem when reading from
registers in a xilinx across the local bus.  I can read pci config
registers, local config registers, and even the xilinx registes, until I
do a write to the xilinx.  After that, I can no longer read from
anywhere on the local bus.  I have implemented the PLX workarounds
mentioned in their FAQ and Errata.  Looking at a scope, I can see that I
am reading and writing to the local bus, but I get squat back from the
plx for reads.

I also want to make sure I am not re-inventing the wheel.  Grepping
through the kernel I found:

Some 9060 drivers
Lots of multi-port serial cards that use the 9050, are based on serial.c
and read their config from an eeprom. 

I am working on a card that will use a lot of the features of the 9050,
including burst mode across the local bus.  I also implement all the
workarounds in software and don't have an eeprom to work with, so I have
to do a little extra setup.  There is a neat PLX supplied tool called
PLXmon that I am able to run under FreeDOS to get and set register
values, I am thinking of writing a linux version.

-Rich

-- 
OST - the open source telecom corporation
Rich Bodo | rsb@ostel.com | 650-964-4-OST

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~1999-09-17  1:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-17  1:02 Rich Bodo [this message]
1999-09-17  2:34 ` PLX 9050 chip Benjamin LaHaise

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=37E19313.6090BE36@ostel.com \
    --to=rsb@ostel.com \
    --cc=linux-kernel@vger.rutgers.edu \
    /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.