From: Steve Rossi <srossi@ccrl.mot.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: QSPAN II PCI?
Date: Wed, 08 Dec 1999 09:23:52 -0600 [thread overview]
Message-ID: <384E7808.5DC38E0A@ccrl.mot.com> (raw)
I'm beginning the design work on a custom 855T based board (an 860T
with only 1 SCC) on which I plan to run linux. I'm wondering if there
is support for the Tunda QSpan II PPC <-> PCI bridge in the kernel and
at what state is this driver is in? I know there at least appears to be
support
for the first rev QSPAN via qspan_pci.c. If it hasn't already been done,
what would it take to update it to support QSpan II?
Also - If anyone has any suggestions or would like to point out things
that
I should be aware of when designing a board to run linux - I would love
to
hear it!
Thanks!
Steve
--
-------------------------------------------------------
Steven K. Rossi srossi@ccrl.mot.com
Research Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-12-08 15:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=384E7808.5DC38E0A@ccrl.mot.com \
--to=srossi@ccrl.mot.com \
--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).