All of lore.kernel.org
 help / color / mirror / Atom feed
From: schardt <g.schardt@fz-juelich.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Newbie and linux on virtex-II ppc
Date: Mon, 27 Aug 2007 16:17:32 +0200	[thread overview]
Message-ID: <46D2DCFC.40401@fz-juelich.de> (raw)
In-Reply-To: <fa686aa40708270609x453092eye6eaf83b65ac2dee@mail.gmail.com>

Grant Likely wrote:
> On 8/27/07, schardt <g.schardt@fz-juelich.de> wrote:
>   
>> im a student from germany and i try to run linux on a virtex-II with
>> integrated powerpc.
>> i use the developer board DS-DB-2VP4/7-FG456 from Memec ( i think its
>> now avnet)
>>
>> what is running :
>>
>>   - Xilinx EDK project (standalone program running fine, and BSP files
>> are generated)
>>     the project has only one UARTLITE, 82MB SDRAM and a few kByte
>> blockram, and the systemace interface
>>
>>   - crosscompiler toolchain works
>>
>>   - after modified some defines in the xparameters.h i got a linux 2.4.
>> kernel (linuxppc) without compiler errors
>>     
>
> I strongly recommend trying to bring up a 2.6 kernel, it's much easier.
>   
okay, i'll try it :)
>   
>>     and yes, the uartlite driver is enabled :)
>>     
>
> Don't modify xparams by hand; it's not worth the trouble.  Go into
> software setting in your EDK project and select 'linux-2.6' as the OS.
>  Generate the libraries and copy the generated xparameters_ml40x.h
> into your kernel tree.
>
>   
i dont have this option. do i need a update  ?


G





-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
Forschungszentrum Jülich GmbH
52425 Jülich

Sitz der Gesellschaft: Jülich
Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe
Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv. 
Vorsitzender)
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------

  reply	other threads:[~2007-08-27 14:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 12:55 Newbie and linux on virtex-II ppc schardt
2007-08-27 13:09 ` Grant Likely
2007-08-27 14:17   ` schardt [this message]
2007-08-27 14:21     ` Grant Likely
2007-08-28  6:51   ` schardt
     [not found]   ` <46D2CFFB.6050602@fz-juelich.de>
     [not found]     ` <fa686aa40708270719s1fd230e9g188948ef02b3eda7@mail.gmail.com>
     [not found]       ` <46D41298.7060109@fz-juelich.de>
2007-08-28 13:06         ` Grant Likely
2007-08-28 13:24           ` schardt
2007-08-28 13:30             ` Grant Likely
2007-08-28 13:39               ` schardt
2007-08-28 13:55                 ` Grant Likely
2007-08-28 14:12                   ` schardt
2007-08-28 14:43                     ` Grant Likely
2007-08-28 14:44                       ` Grant Likely
2007-08-29  9:29                         ` schardt
2007-08-29 13:31                           ` schardt
2007-08-29 14:44                             ` Grant Likely
     [not found]                               ` <46DBA4F9.2010703@fz-juelich.de>
2007-09-03 13:41                                 ` Grant Likely
2007-08-27 13:54 ` Ming Liu

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=46D2DCFC.40401@fz-juelich.de \
    --to=g.schardt@fz-juelich.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.