linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: shiyongsun <shiyongsun@sina.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: MPC8265 PCI driver
Date: Sat, 26 Apr 2003 16:04:32 +0800	[thread overview]
Message-ID: <20030426080432.2011.qmail@sina.com> (raw)


Hello,everybody
    Here is my application on MPC8260.The FCC1 was used as the UTOPIA16 and FCC2,FCC3 were used as Ethernet.Does anybody has the sharing code on the application? And is there any SAR code available?
    Thanks in advance!

                                         Jarry_sun
______________________________________

===================================================================

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-04-26  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-26  8:04 shiyongsun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-26  7:32 MPC8265 PCI driver shiyongsun

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=20030426080432.2011.qmail@sina.com \
    --to=shiyongsun@sina.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).