From: "Alan Casey" <alan.casey5@mail.dcu.ie>
To: linuxppc-embedded@ozlabs.org
Cc: alan.casey5@mail.dcu.ie
Subject: Linux issues on Xilinx XUPV2P board
Date: Thu, 3 Jul 2008 16:18:56 +0100 [thread overview]
Message-ID: <4858FDD100015AFE@hawk.dcu.ie> (raw)
Hi,
I have tried running the Linux 2.6.24 and Linux 2.6.26 kernels from
git.xilinx.com on the Xilinx XUPV2P board but have run into a few probl=
ems.
Cross-compiler i use to compile applications was built using Crosstools=
and
based on gcc 3.3.4. I use Xilinx EDK 7.1 for integrating hardware perip=
herals
onto the board.
The problems i've seen are:
(i) gettimeofday software function returns time of 0 all the time.
(ii) The Linux 2.6.24 kernel's Xilinx Framebuffer driver and/or the Xil=
inx
PLB TFT Controller IP block (plb_tft_cntlr_ref_v1_00_d) does not a=
ppear
to centre the display on a VGA screen properly(vertically offset).=
(iii) 64-bit write/read access to peripheral integrated onto the Xilinx=
Virtex-II Pro FPGA either causes a system crash or only lower par=
t
of 32-bit data to be written (i.e. lower part of 64-bit data appe=
ars
to be mirrored on the upper and lower 32-bits of the system bus).=
However, 32-bit write/read access to the peripheral passes as wel=
l
as 64-bit write/read access to the SDRAM memory address space.
Peripheral interface has been verified to be IBM PLB compliant
via IBM bus functional model simulations.
(iv) The Linux 2.6.26 Xilinx Framebuffer driver on the Xilinx XUPV2P b=
oard
does not appear to be working - nothing displayed to screen/conso=
le
not switching to framebuffer device on bootup.
Just wondering if anybody has seen these issues before and know how to=
resolve them?
Any info. appreciated,
Regards,
Alan.
next reply other threads:[~2008-07-03 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 15:18 Alan Casey [this message]
2008-08-15 8:43 ` Linux issues on Xilinx XUPV2P board wangyanlong
2008-08-15 9:59 ` Alan Casey
2008-08-15 11:35 ` wangyanlong
2008-08-15 12:34 ` Alan Casey
2008-08-15 14:30 ` John Linn
2008-08-15 14:36 ` Alan Casey
2008-08-15 14:53 ` John Linn
2008-08-15 15:08 ` Jon Loeliger
2008-08-15 14:31 ` wangyanlong
2008-08-15 14:50 ` Alan Casey
2008-08-31 15:58 ` wangyanlong
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=4858FDD100015AFE@hawk.dcu.ie \
--to=alan.casey5@mail.dcu.ie \
--cc=linuxppc-embedded@ozlabs.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).