From: Bret Indrelee <Bret.Indrelee@qlogic.com>
To: Jacky Lam <jackylam@astri.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: General porting question
Date: Wed, 8 Oct 2003 23:24:03 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0310082322160.17168-100000@spider.ancor.com> (raw)
In-Reply-To: <006e01c38e1b$5f72b500$2803050a@JackyLam>
On Thu, 9 Oct 2003, Jacky Lam wrote:
> Dear all,
>
> Could anyone give me some notes/idea what should be take care to port an
> x86 PCI card driver to powerpc walnut platform? I try several
> cards(ethernet, audio) which run well on my PC by cross-compiling the
> drivers. They can be recognized successfully, but none of them works. Walnut
> seems don't be able to receive any interrupt from the cards.
>
> I guess there must be something about PCI implementation in PPC
> different from x86. Is there any expert on PPC PCI can tell me what happen?
> Or any related documentation can help?
Best guess, the driver doesn't handle any of the endian issues.
PPC is a big-endian processor, x86 is little endian. Most likely you've
got data that needs to be byte swapped in order to work. Best way I know
of to find out if this is the case is using a PCI bus analyzer to
watch the PCI bus.
-Bret
--
Bret Indrelee QLogic Corporation
Bret.Indrelee@qlogic.com 6321 Bury Drive, St 13, Eden Prairie, MN 55346
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-09 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 4:11 General porting question Jacky Lam
2003-10-09 4:24 ` Bret Indrelee [this message]
2003-10-09 5:35 ` Matt Porter
2003-10-09 6:18 ` Jacky Lam
2003-10-09 13:38 ` Matt Porter
2003-10-09 15:36 ` Jacky Lam
2003-10-09 16:37 ` Matt Porter
2003-10-09 17:23 ` Jacky Lam
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=Pine.LNX.4.44.0310082322160.17168-100000@spider.ancor.com \
--to=bret.indrelee@qlogic.com \
--cc=jackylam@astri.org \
--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 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.