[ELDK] how to use u-boot command to diagnose pci dma
linuxdemo
linuxdemo at 126.com
Thu Jan 8 01:46:11 CET 2009
I made a pci card for a board based on ppc405ep,and I want to test the card's dma function, so which u-boot command can be used to diagnose DMA function of the pci card ?
thanks.
在2009-01-07，eldk-request at lists.denx.de 写道：
>Send eldk mailing list submissions to
> eldk at lists.denx.de
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.denx.de/mailman/listinfo/eldk
>or, via email, send a message with subject or body 'help' to
> eldk-request at lists.denx.de
>
>You can reach the person managing the list at
> eldk-owner at lists.denx.de
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of eldk digest..."
>
>
>Today's Topics:
>
> 1. Re: Building tcpdump package in eldk 4.1 (Wolfgang Denk)
> 2. Rebuilding the crosstool rpm on SL5 (Dach Miroslaw)
> 3. Re: Rebuilding the crosstool rpm on SL5 (Wolfgang Denk)
> 4. Building Target packages in eldk 4.1 (Matheos Worku)
> 5. Re: Building tcpdump package in eldk 4.1 (Matheos Worku)
> 6. Re: Building Target packages in eldk 4.1 (Wolfgang Denk)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 06 Jan 2009 15:36:24 +0100
>From: Wolfgang Denk <wd at denx.de>
>Subject: Re: [ELDK] Building tcpdump package in eldk 4.1
>To: Matheos Worku <Matheos.Worku at Sun.COM>
>Cc: eldk at lists.denx.de
>Message-ID: <20090106143624.AA0F28387CDB at gemini.denx.de>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Dear Matheos,
>
>In message <4962B816.2030005 at sun.com> you wrote:
>>
>> I am trying to build tcpdump package for ppc/powerpc architecture. The
>> library (libpcap) and the tcpdump src come in non rpm package. I was
>> wondering if there is a good way of building the src in
>> ".configure/make" build scheme in cross compile environment in eldk 4.1?
>
>If you just need something for immediate use, then the fastest way is
>always to build the library and the tool on the target - it is one of
>the big advanages of LDK over other embedded distros that ELDK
>includes a complete native build environment.
>
>Best regards,
>
>Wolfgang Denk
>
>--
>DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
>HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
>To be a winner, all you need to give is all you have.
>
>
>------------------------------
>
>Message: 2
>Date: Tue, 6 Jan 2009 15:33:05 +0100
>From: "Dach Miroslaw" <miroslaw.dach at psi.ch>
>Subject: [ELDK] Rebuilding the crosstool rpm on SL5
>To: <eldk at lists.denx.de>
>Message-ID:
> <1B4F8000449511488D1A640DD6DECA35029130D2 at MAILBOX0A.psi.ch>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Dear Sirs,
>
>I have the Scientific Linux 5 (SL5) distribution based system on my PC. I wanted to rebuild the crosstools source RPM (which is part of ELDK 4.2) on my host SL5 for ppc_4xx and ppc_4xxFP target architectures.
>To do so I have dowloaded the the crosstool-0.43-1.src.rpm from:
>http://ftp.denx.de/pub/eldk/4.2/ppc-linux-x86/sources/SRPMS/crosstool-0.43-1.src.rpm
>
>Next I have read the documentation about rebuilding the rpm sources. I understood that to rebuild the rpm package like
>crosstool-0.43-1.src.rpm from sources I need first to install the whole ELDK 4.2 and use commands like ppc_4xx-rpmbuild ?
>
>I have tried however to use native SL5 rpm and rpmbuild programs.
>
>unfortunately rpmbuild -ba crosstool.spec did not work:
>
>error: parse error in expression
>error: /home/devl/Work/RedHat-RPMS/redhat/SPECS/crosstool.spec_org:35: parseExpressionBoolean returns -1
>error: Package has no %description: crosstool
>
>I have added the definition to the crosstool.spec at the beginning of the file:
>%define _targetarch ppc
>
>The rpm build process was sucessful. I have got 3 rpms:
>crosstool-0.43-1.i386.rpm
>crosstool-powerpc-devel-0.43-1.i386.rpm
>crosstool-targetcomponents-0.43-1.i386.rpm
>
>It seems to be that only one contains files: crosstool-powerpc-devel-0.43-1.i386.rpm
>Two other files do not contain files.
>
>The cross ggc compiler is loacated under: /usr/bin/powerpc-linux-gcc
>
>In the past when I was dealing with ELDK 4.1 I have had in addition to real files also the
>symbolic links like ppc_4xx-gcc -> powerpc-linux-gcc.
>
>Is it sufficient to define CROSS_COMPILE variable to deal either with ppc_4xx or ppc_4xxFP architectures?
>
>I however do not see crosscompiled libraries (shared libraries) for ppc_4xx or/and ppc_4xxFP?
>
>I will be very much grateful for help on that subject.
>
>Best Regards
>
>Mirek
>
>
>------------------------------
>
>Message: 3
>Date: Tue, 06 Jan 2009 16:18:27 +0100
>From: Wolfgang Denk <wd at denx.de>
>Subject: Re: [ELDK] Rebuilding the crosstool rpm on SL5
>To: "Dach Miroslaw" <miroslaw.dach at psi.ch>
>Cc: eldk at lists.denx.de
>Message-ID: <20090106151827.7CB4D8387CDB at gemini.denx.de>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Dear Miroslaw,
>
>In message <1B4F8000449511488D1A640DD6DECA35029130D2 at MAILBOX0A.psi.ch> you wrote:
>>
>> I have the Scientific Linux 5 (SL5) distribution based system on my PC. I wanted to rebuild the crosstools source RPM (which is part of ELDK 4.2) on my host SL5 for ppc_4xx and ppc_4xxFP target architectures.
>
>May I ask why you want to do this? If it works, the result should be
>the same as thebinaries included with the ELDK release...
>
>> To do so I have dowloaded the the crosstool-0.43-1.src.rpm from:
>> http://ftp.denx.de/pub/eldk/4.2/ppc-linux-x86/sources/SRPMS/crosstool-0.43-1.src.rpm
>
>OK.
>
>> Next I have read the documentation about rebuilding the rpm sources. I understood that to rebuild the rpm package like
>> crosstool-0.43-1.src.rpm from sources I need first to install the whole ELDK 4.2 and use commands like ppc_4xx-rpmbuild ?
>
>Yes.
>
>> I have tried however to use native SL5 rpm and rpmbuild programs.
>
>This is bound to fail. Please proceed exactly as documented.
>
>> I however do not see crosscompiled libraries (shared libraries) for ppc_4xx or/and ppc_4xxFP?
>
>Libraries is another issue.
>
>> I will be very much grateful for help on that subject.
>
>Maybe it would help if you explained what exactly you are trying to
>acchieve. Just rebuilding is probably not your only intention?
>
>Best regards,
>
>Wolfgang Denk
>
>--
>DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
>HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
>: 1. What is the possibility of this being added in the future?
>In the near future, the probability is close to zero. In the distant
>future, I'll be dead, and posterity can do whatever they like... :-)
> - lwall
>
>
>------------------------------
>
>Message: 4
>Date: Tue, 06 Jan 2009 18:48:24 -0800
>From: Matheos Worku <Matheos.Worku at Sun.COM>
>Subject: [ELDK] Building Target packages in eldk 4.1
>To: eldk at lists.denx.de
>Message-ID: <496417F8.1030407 at sun.com>
>Content-Type: text/plain; format=flowed; charset=ISO-8859-1
>
>Hi,
>
>
>How do I find and install some of the target packages from the section
>(List of Target Packages). I went through the installation process per
>documentation but the whole /usr/local/bin was missing. For example, I
>need perl and libraries and it is not installed (not even in the RPM list).
>
>Regards
>Matheos
>
>
>
>------------------------------
>
>Message: 5
>Date: Tue, 06 Jan 2009 18:48:10 -0800
>From: Matheos Worku <Matheos.Worku at Sun.COM>
>Subject: Re: [ELDK] Building tcpdump package in eldk 4.1
>To: Wolfgang Denk <wd at denx.de>
>Cc: eldk at lists.denx.de
>Message-ID: <496417EA.3010505 at sun.com>
>Content-Type: text/plain; format=flowed; charset=ISO-8859-1
>
>Wolfgang Denk wrote:
>
>>Dear Matheos,
>>
>>In message <4962B816.2030005 at sun.com> you wrote:
>>
>>
>>>I am trying to build tcpdump package for ppc/powerpc architecture. The
>>>library (libpcap) and the tcpdump src come in non rpm package. I was
>>>wondering if there is a good way of building the src in
>>>".configure/make" build scheme in cross compile environment in eldk 4.1?
>>>
>>>
>>
>>If you just need something for immediate use, then the fastest way is
>>always to build the library and the tool on the target - it is one of
>>the big advanages of LDK over other embedded distros that ELDK
>>includes a complete native build environment.
>>
>>Best regards,
>>
>>Wolfgang Denk
>>
>>
>>
>Thanks a lot. I will give it a try.
>Regards
>Matheos
>
>
>
>------------------------------
>
>Message: 6
>Date: Wed, 07 Jan 2009 09:40:04 +0100
>From: Wolfgang Denk <wd at denx.de>
>Subject: Re: [ELDK] Building Target packages in eldk 4.1
>To: Matheos Worku <Matheos.Worku at Sun.COM>
>Cc: eldk at lists.denx.de
>Message-ID: <20090107084004.C7DAF8387CDB at gemini.denx.de>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Dear Matheos,
>
>In message <496417F8.1030407 at sun.com> you wrote:
>>
>> How do I find and install some of the target packages from the section
>> (List of Target Packages). I went through the installation process per
>> documentation but the whole /usr/local/bin was missing. For example, I
>
>This is not a surprise - /usr/local ist supposed to be stuff locally
>added, i. e. the standard distributions will use it (at least Fedora -
>which is the base for ELDK - doesn't).
>
>> need perl and libraries and it is not installed (not even in the RPM list).
>
>You should use ELDK release 4.2 which already includes Perl (but of
>course in the standard location, i. e. in /usr/bin, not /usr/local).
>
>Best regards,
>
>Wolfgang Denk
>
>--
>DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
>HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
>In C we had to code our own bugs, in C++ we can inherit them.
>
>
>------------------------------
>
>_______________________________________________
>eldk mailing list
>eldk at lists.denx.de
>http://lists.denx.de/mailman/listinfo/eldk
>
>
>End of eldk Digest, Vol 15, Issue 3
>***********************************
More information about the eldk
mailing list