RE: Linux issues on Xilinx XUPV2P board
From: Alan Casey <hidden>
Date: 2008-08-15 14:36:25
Hi John, Im not having any problems using GIT. I can download 2.6.26 using git no problem - i think wangyanlong would like to use 2.6.24 or 2.6.26 and he has problems downloading it using git - hence i replied to him that he may find more info about how to download the current or previous version on git.xilinx.com. I think you misread my email. The Xilinx Framebuffer driver works fine in Linux 2.6.24 but there appears to be a problem with one of the Linux-2.6.26 versions which i posted about a few weeks/months ago. Alan.
-- Original Message -- Subject: RE: Linux issues on Xilinx XUPV2P board Date: Fri, 15 Aug 2008 08:30:25 -0600 From: John Linn <redacted> To: <redacted>, "wangyanlong" [off-list ref], [off-list ref] Hi Alan, I'm assuming you must not have Git installed from the question, otherwise you would be using git clone as the site shows. On the http://git.xilinx.com, it says the following, Users without Git installed may create a tar file by using the snapshot feature. Select the tree view of the repository (far right side) on this=
page, then select snapshot (near the top) and a gziped tar file will be created and downloaded. Is this what you're looking for? -- Johnquoted
-----Original Message----- From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs. org] On Behalf Of Alan Casey Sent: Friday, August 15, 2008 6:34 AM To: wangyanlong; linuxppc-embedded@ozlabs.org Subject: Re: Linux issues on Xilinx XUPV2P board Hi, I used version 2.6.24. Current version is 2.6.26+ but im not sure how to download previous versions from the git tree, there should be some info at http://git.xilinx.com about how to do this. Regards, Alan.quoted
-- Original Message -- Date: Fri, 15 Aug 2008 04:35:01 -0700 (PDT) From: wangyanlong <redacted> To: linuxppc-embedded@ozlabs.org Subject: Re: Linux issues on Xilinx XUPV2P board Hi Alan I dow load the kernel from " http://git.xilinx.com/cgi-bin/gitweb.cgi?p=3Dlinux-2.6-xlnx.git;a=3Dsummary "quoted
Merge ../../linux-2.6 into 2.6.26-merge master commit |commitdiff | treequoted
| snapshot this version ,but it not work well,which version you downloaded? Many thanks yanlong Alan Casey wrote:quoted
Hi, Yes i had a problem with using one of the Linux 2.6.26 kernel versions on the XUPV2P board where the VGA display has not driven correctly, not sure why. The Linux 2.6.24 kernel from git.xilinx.com works fine. Regards, Alan.quoted
-- Original Message -- Date: Fri, 15 Aug 2008 01:43:37 -0700 (PDT) From: wangyanlong <redacted> To: linuxppc-embedded@ozlabs.org Subject: Re: Linux issues on Xilinx XUPV2P board I meet the problem as yours . And my vga's display is notclear , havequoted
quoted
youquoted
meet this? Alan Casey wrote:quoted
Hi, I have tried running the Linux 2.6.24 and Linux 2.6.26kernels fromquoted
quoted
quoted
quoted
git.xilinx.com on the Xilinx XUPV2P board but have runinto a fewquoted
quoted
quoted
quoted
problems. Cross-compiler i use to compile applications was built using Crosstools and based on gcc 3.3.4. I use Xilinx EDK 7.1 forintegrating hardwarequoted
quoted
quoted
quoted
peripherals onto the board. The problems i've seen are: (i) gettimeofday software function returns time of 0all the time.quoted
quoted
quoted
quoted
(ii) The Linux 2.6.24 kernel's Xilinx Framebufferdriver and/or thequoted
quoted
quoted
quoted
Xilinx PLB TFT Controller IP block(plb_tft_cntlr_ref_v1_00_d) does notquoted
quoted
quoted
quoted
appear to centre the display on a VGA screen properly(vertically offset). (iii) 64-bit write/read access to peripheralintegrated onto thequoted
quoted
quoted
quoted
Xilinx Virtex-II Pro FPGA either causes a system crashor only lowerquoted
quoted
partquoted
quoted
of 32-bit data to be written (i.e. lower part of64-bit dataquoted
quoted
quoted
quoted
appears to be mirrored on the upper and lower 32-bits ofthe systemquoted
quoted
quoted
quoted
bus). However, 32-bit write/read access to theperipheral passes asquoted
quoted
wellquoted
quoted
as 64-bit write/read access to the SDRAM memoryaddress space.quoted
quoted
quoted
quoted
Peripheral interface has been verified to be IBMPLB compliantquoted
quoted
quoted
quoted
via IBM bus functional model simulations. (iv) The Linux 2.6.26 Xilinx Framebuffer driver onthe Xilinx XUPV2Pquoted
quoted
quoted
quoted
board does not appear to be working - nothing displayed to screen/console not switching to framebuffer device on bootup. Just wondering if anybody has seen these issuesbefore and know howquoted
quoted
quoted
toquoted
resolve them? Any info. appreciated, Regards, Alan. _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded-- View this message in context:http://www.nabble.com/Linux-issues-on-Xilinx-XUPV2P-board-tp18262250p18995644.htmlquoted
quoted
quoted
Sent from the linuxppc-embedded mailing list archive at Nabble.com.=
quoted
quoted
quoted
quoted
_______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded_______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded-- View this message in context:http://www.nabble.com/Linux-issues-on-Xilinx-XUPV2P-board-tp18 262250p18997255.htmlquoted
Sent from the linuxppc-embedded mailing list archive at Nabble.com. _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded_______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embeddedThis email and any attachments are intended for the sole use of the name=
d
recipient(s) and contain(s) confidential information that may be proprie=
tary,
privileged or copyrighted under applicable law. If you are not the inten=
ded
recipient, do not read, copy, or forward this email message or any attac=
hments.
Delete this email message and any attachments immediately.