linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Alan Casey" <alan.casey5@mail.dcu.ie>
To: "wangyanlong" <killyouatonce@gmail.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Linux issues on Xilinx XUPV2P board
Date: Fri, 15 Aug 2008 13:34:28 +0100	[thread overview]
Message-ID: <4891711700018E59@hawk.dcu.ie> (raw)
In-Reply-To: <18997255.post@talk.nabble.com>

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.

>-- Original Message --
>Date: Fri, 15 Aug 2008 04:35:01 -0700 (PDT)
>From: wangyanlong <killyouatonce@gmail.com>
>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=3Dsumm=
ary
"
>
>Merge ../../linux-2.6 into 2.6.26-merge  master  commit | commitdiff | t=
ree
>| snapshot
>  
>this version ,but it not work well,which version you downloaded?
>
>Many thanks
>yanlong
> 
>
>Alan Casey wrote:
>> 
>> 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.
>>   
>> 
>>>-- Original Message --
>>>Date: Fri, 15 Aug 2008 01:43:37 -0700 (PDT)
>>>From: wangyanlong <killyouatonce@gmail.com>
>>>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 not clear , hav=
e
>> you
>>>meet this?
>>>
>>>Alan Casey wrote:
>>>> 
>>>> Hi,
>>>> 
>>>>   I have tried running the Linux 2.6.24 and Linux 2.6.26 kernels fro=
m
>> 
>>> 
>>>>   git.xilinx.com on the Xilinx XUPV2P board but have run into a few
>>>> 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 for integrating hardware
>>>> peripherals
>>>>   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 th=
e
>>>> Xilinx
>>>> 
>>>>        PLB TFT Controller IP block (plb_tft_cntlr_ref_v1_00_d) does
not
>>>> appear
>>>> 
>>>>        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 lowe=
r
>> part
>>>> 
>>>>         of 32-bit data to be written (i.e. lower part of 64-bit data=

>>>> appears
>>>>         to be mirrored on the upper and lower 32-bits of the system
>>>> bus).
>>>>         However, 32-bit write/read access to the peripheral passes a=
s
>> well
>>>>         as 64-bit write/read access to the SDRAM memory address spac=
e.
>>>>         Peripheral interface has been verified to be IBM PLB complia=
nt
>>>
>>>>         via IBM bus functional model simulations. 
>>>> 
>>>>    (iv) The Linux 2.6.26 Xilinx Framebuffer driver on the Xilinx XUP=
V2P
>>>> 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 issues before and know h=
ow
>>>to
>>>>    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-tp18262250p189=
95644.html
>>>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-embedded
>> 
>> 
>
>-- 
>View this message in context: http://www.nabble.com/Linux-issues-on-Xili=
nx-XUPV2P-board-tp18262250p18997255.html
>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

  reply	other threads:[~2008-08-15 12:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 15:18 Linux issues on Xilinx XUPV2P board Alan Casey
2008-08-15  8:43 ` wangyanlong
2008-08-15  9:59   ` Alan Casey
2008-08-15 11:35     ` wangyanlong
2008-08-15 12:34       ` Alan Casey [this message]
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=4891711700018E59@hawk.dcu.ie \
    --to=alan.casey5@mail.dcu.ie \
    --cc=killyouatonce@gmail.com \
    --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).