From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "Will Kritikos" <will.kritikos@gmail.com>,
<linuxppc-embedded@ozlabs.org>
Subject: RE: xilinx_hwicap driver problems
Date: Wed, 14 May 2008 11:37:29 -0700 [thread overview]
Message-ID: <20080514183731.04FE920053@mail163-sin.bigfish.com> (raw)
In-Reply-To: <3ee6f9e50805140903o381346f5kddbce29a3d06ba1f@mail.gmail.com>
I bet you're using ARCH ppc...
It looks like in arch/ppc/syslib/virtex_devices.c:
#define XPAR_HWICAP(num) { \
.name =3D "xilinx_icap", \
Should probably be:
#define XPAR_HWICAP(num) { \
.name =3D "icap", \
now.
Can you make this change locally and verify that it solves the problem?
Steve
> -----Original Message-----
> From: linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org
[mailto:linuxppc-embedded-
> bounces+stephen=3Dneuendorffer.name@ozlabs.org] On Behalf Of Will
Kritikos
> Sent: Wednesday, May 14, 2008 9:03 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: xilinx_hwicap driver problems
>=20
> I am having some trouble using the xilinx_hwicap driver in Linux.
> I am using version 2.6.24-rc8-xlnx of the Linux kernel from the Xilinx
> GIT repository.
> The xilinx_hwicap driver is statically compiled in - not a loadable
module.
> I am using the opb_hwicap device on a V4FX60 FPGA, Linux running on
the PPC405.
>=20
> The driver successfully is initialized on boot - I added a printk to
> the init function to verify this. However, as far as I can tell, the
> probe function is never called. There is nothing in dmesg from the
> icap driver.
>=20
> After boot, the following files exist in /sys
>=20
> /sys/bus/platform/xilinx_icap.0
> /sys/bus/platform/drivers/icap/bind
> /sys/bus/platform/drivers/icap/uevent
> /sys/bus/platform/drivers/icap/unbind
> /sys/devices/platform/xilinx_icap.0
>=20
> I can make a device node /dev/icap, major number 259 minor number 0,
> and copy partial bitstreams to it, but again nothing happens, and no
> output in dmesg.
>=20
> Any help is appreciated. I am probably overlooking something simple.
>=20
> Thanks,
> Will Kritikos
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
This email and any attachments are intended for the sole use of the named=
recipient(s) and contain(s) confidential information that may be=
proprietary, privileged or copyrighted under applicable law. If you are=
not the intended recipient, do not read, copy, or forward this email=
message or any attachments. Delete this email message and any attachments=
immediately.
next prev parent reply other threads:[~2008-05-14 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 16:03 xilinx_hwicap driver problems Will Kritikos
2008-05-14 18:37 ` Stephen Neuendorffer [this message]
2008-05-14 19:20 ` Will Kritikos
2008-05-14 20:09 ` Stephen Neuendorffer
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=20080514183731.04FE920053@mail163-sin.bigfish.com \
--to=stephen.neuendorffer@xilinx.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=will.kritikos@gmail.com \
/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).