From: Dan Malek <dan@mvista.com>
To: alex daniloff <alex_daniloff@mail.ru>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Qspan driver
Date: Mon, 23 Apr 2001 14:51:05 -0400 [thread overview]
Message-ID: <3AE47999.A0589002@mvista.com> (raw)
In-Reply-To: E14rbTK-000PMz-00@f5.mail.ru
alex daniloff wrote:
>
> I'm looking for embedded driver for Qspan.
There are a couple of different implementations of the Tundra
Qspan for MPC8xx in the Linux sources. You may have to adapt
them depending upon your design, as there are many possibilities.
> I've found only drivers for host or pc not for embedded OS.
Well, these aren't really "drivers", but rather the bridge
initialization and configuration space I/O functions.
> I tried to read from PMC PCI configuration space but I've got Machine Check.
Even for a properly configured Qspan you will get these for devices
that don't exist. You need to ensure (as Linux does) that you have
a continuation model machine check handler that can return errors to
the caller of this type of access.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-04-23 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 8:13 Qspan driver alex daniloff
2001-04-23 18:51 ` Dan Malek [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=3AE47999.A0589002@mvista.com \
--to=dan@mvista.com \
--cc=alex_daniloff@mail.ru \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).