public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "John Hahn" <jhahn@bcfsemi•com>
To: <linuxppc-embedded@ozlabs•org>
Subject: RE: SystemACE driver problem
Date: Sun, 21 Oct 2007 19:52:32 -0700	[thread overview]
Message-ID: <001a01c81456$985b6a90$c9123fb0$@com> (raw)
In-Reply-To: <fa686aa40710191120w209b62a0l4f71e528e5f1a1b3@mail.gmail.com>

Grant

Regarding your comment about the new xsysace.c driver vs. the old Xilinx
one, is that chosen at the kernel config time ? 

i.e.
cp arch/ppc/configs/ml403_defconfig
make ARCH=ppc CROSS_COMPILE=/opt/eldk4.1/usr/bin/ppc_4xx- oldconfig

...
Xilinx SystemACE support (XILINX_SYSACE) [N/m/y/?] (NEW) y
Xilinx SystemACE support (old driver) (XILINX_SYSACE_OLD) [N/m/y/?] (NEW) N

I am also about build and test with the 2.6.23-rc2 same source. Just wanted
to be sure I am choosing the right driver for the ml403 reference design
bits from Xilinx.

Thanks

John Hahn
BCF Semiconductor
---

P.S. Sorry for taking the thread off on a slight tangent ...

> From: Grant Likely
> Sent: Friday, October 19, 2007 11:21 AM
> 
... <snip>
>
> I don't know about the old xilinx supplied sysace driver, but the new
> xsysace.c driver is robust enough to work around missed interrupts.  I
> don't know of any other problems with the opb_sysace IP core.
> 
> Cheers,
> g.
> 
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab•ca
> (403) 399-0195
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2007-10-22  2:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  9:03 SystemACE driver problem aauer1
2007-10-19 14:04 ` Grant Likely
2007-10-19 18:13   ` aauer1
2007-10-19 18:20     ` Grant Likely
2007-10-22  2:52       ` John Hahn [this message]
2007-10-22  3:24         ` Grant Likely
2007-10-22 13:50       ` aauer1

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='001a01c81456$985b6a90$c9123fb0$@com' \
    --to=jhahn@bcfsemi$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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