headers
Stefan Roese | 1 Jul 2009 09:09
Picon
Picon
Favicon

PPC 44x DMA controller

Hi Dave,

On Tuesday 30 June 2009 18:41:52 Dave Cogley wrote:
> The old "ppc" architecture in Linux used to support several useful
> libraries that do not appear to have the functionality supported in the
> newer "powerpc" branch.
>
> I am looking for equivalent built in support of the PPC4xx DMA libraries
> that used to be supported under "ppc/syslib"; ppc4xx_dma.c and
> ppc_sgdma.c.

Ah, you're talking about those functions.

> The ELDK is currently using these libraries to support the
> OTG USB controller on the Canyonlands board. These libraries however are
> currently not built into the mainstream kernel as the should be.

Correct. Please note that this 4xx DMA support is not a real solution (one of 
the reasons that this USB driver was not pushed into kernel.org).

> I have already made the jump to mainstream Linux in my design and am
> running with 2.6.30. I was offering to port said libraries into a
> standard Linux format supporting the PPC4xx arch. In the interim I was
> able to compile the support directly into my device driver and
> everything appears to work with the exception of dma_alloc_coherant
> which is causing a kernel oops.

I'm not sure where the correct place for this 4xx DMA support would be. 
Perhaps drivers/dma or arch/powerpc/syslib? I suggest that you ask on 
linuxppc-dev.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthias Fuchs | 4 Jul 2009 11:56
Picon

Rebuilding python ELDT package

Hi,

I am trying to build - modify - build again the ELDT python RPM package.

I am using the latest tarball and spec file from the Denx git repositories.

The initial build as described on http://www.denx.de/wiki/view/DULG/ELDKRebuildingComponents
works fine. Good work.

But now I want to modify the python source and rebuild - but without doing the
complete rpmbuild. Because I am not an RPM expert I google'd and
found this recipe - still thinking this should be the same as "rpmbuild -ba"

1) Prepare the sources (unpack tarball etc.):
ppc_4xx-rpmbuild -bp python.spec

2) Modify sources (or not)

3) start at build stage
ppc_4xx-rpmbuild -bc --short-circuit python.spec

But now I get:

b.h: found (4, 5) in /opt/eldk_420/ppc_4xx/usr/include
db lib: using (4, 5) db-4.5
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for gcc... ppc-linux-gcc
checking for C compiler default output file name... a.out
(Continue reading)

Permalink | Reply | 3 comments |
headers
Diptopal Basu | 6 Jul 2009 09:48
Picon

need to use GDB/MI commands with gdb provided by ELDK4.1.

 I need to enable GDB/MI commands with ELDK 4.1 debigger for ARM , I am
doing remote debugging on an ARM board , and I have compiled a gdbserver
running on my target , right now I am not able to run the GDB/MI commands
because if I try to type some command GDB does not recognise it . I will
paste the error below.

[root at localhost Desktop]# arm-linux-gdb nick_arm
GNU gdb Red Hat Linux (6.3.0.0-1.21_3rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i386-redhat-linux --target=arm-linux".
The target architecture is set automatically (currently arm)
..
(gdb) set solib-absolute-prefix /home/dbasu/ELDKtoolchainforARM/arm/lib
(gdb) set solib-search-path /home/dbasu/ELDKtoolchainforARM/arm/lib
(gdb) target remote 10.99.105.29:12345
10.99.105.29:12345: Connection refused.
(gdb) target remote 10.99.105.126:12345
Remote debugging using 10.99.105.126:12345
[New Thread 376]
0x40000a80 in ?? ()
(gdb) -break-insert main
Undefined command: "-break-insert".  Try "help".

Regards
Diptopal
(Continue reading)

Permalink | Reply | 6 comments |
headers
Stefano Babic | 6 Jul 2009 10:14

need to use GDB/MI commands with gdb provided by ELDK4.1.

Diptopal Basu wrote:
>  I need to enable GDB/MI commands with ELDK 4.1 debigger for ARM , I am
> doing remote debugging on an ARM board , and I have compiled a gdbserver

gdbserver is provided with ELDK 4.1, too. You do not really to compile
it. Is there any difference if you tried with gdbserver supplied with ELDK ?

> (gdb) target remote 10.99.105.29:12345
> 10.99.105.29:12345: Connection refused.

There is no gdbserver running on this target and listening to this port.
Is there any errors when you start gdbserver on the target ?

Regards,
Stefano Babic

--

-- 
stefano <stefano.babic at babic.homelinux.org>
GPG Key: 0x55814DDE
Fingerprint 4E85 2A66 4CBA 497A 2A7B D3BF 5973 F216 5581 4DDE
Permalink | Reply | 2 comments |
headers
Diptopal Basu | 6 Jul 2009 10:33
Picon

need to use GDB/MI commands with gdb provided by ELDK4.1.

Hi Stefano ,

   No this error you pointed out is something else I actually forgot to
export the nfs file system , I fixed it afterwards., I could not locate the
gdb server in ELDK so compiled one of mine , I am able to do remote
debugging successfully , but unable to run the gdb-mi commands .

Regards
Diptopal

On Mon, Jul 6, 2009 at 1:44 PM, Stefano Babic <
stefano.babic at babic.homelinux.org> wrote:

> Diptopal Basu wrote:
> >  I need to enable GDB/MI commands with ELDK 4.1 debigger for ARM , I am
> > doing remote debugging on an ARM board , and I have compiled a gdbserver
>
> gdbserver is provided with ELDK 4.1, too. You do not really to compile
> it. Is there any difference if you tried with gdbserver supplied with ELDK
> ?
>
> > (gdb) target remote 10.99.105.29:12345
> > 10.99.105.29:12345: Connection refused.
>
> There is no gdbserver running on this target and listening to this port.
> Is there any errors when you start gdbserver on the target ?
>
> Regards,
> Stefano Babic
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Wolfgang Denk | 6 Jul 2009 10:43
Picon
Picon
Favicon

need to use GDB/MI commands with gdb provided by ELDK4.1.

Dear Diptopal Basu,

In message <bd97640b0907060048y551f0a82l3e17550f9ce5af61 at mail.gmail.com> you wrote:
>
>  I need to enable GDB/MI commands with ELDK 4.1 debigger for ARM , I am

Could you please explain what exactly you have in mind with using the
GDB/MI interface?

> [root at localhost Desktop]# arm-linux-gdb nick_arm
...
> (gdb) -break-insert main
> Undefined command: "-break-insert".  Try "help".

You are talking to GDB's  command  line  interface  here  (CLI,  also
called  console interpreter), which is the default interface for GDB.

You cannot use GDB/MI commands when talking to the CLI interface.  To
do  that,  you  must start GDB with the machine interface interpreter
(or  GDB/MI)  by  specifying  the  `-i'  or  `--interpreter'  startup
options. Please read the GDB manual for details.

Try something like

	arm-linux-gdb --interpreter mi nick_arm

Best regards,

Wolfgang Denk
(Continue reading)

Permalink | Reply | 2 comments |
headers
Wolfgang Denk | 6 Jul 2009 10:44
Picon
Picon
Favicon

need to use GDB/MI commands with gdb provided by ELDK4.1.

Dear Diptopal Basu,

In message <bd97640b0907060133s53faad15x46ae00a70bca3983 at mail.gmail.com> you wrote:
>
>    No this error you pointed out is something else I actually forgot to
> export the nfs file system , I fixed it afterwards., I could not locate the
> gdb server in ELDK so compiled one of mine , I am able to do remote
> debugging successfully , but unable to run the gdb-mi commands .

What do you mean by "could not locate it"? It's in /usr/bin/gdbserver
like on any other system. Hard to miss it there, it seems.

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
Imagination is more important than knowledge.      -- Albert Einstein
Permalink | Reply | 0 comments |
headers
Etienne Lorrain | 6 Jul 2009 10:41
Picon
Favicon

Glacier PPC460GT glacier.dts cache 2 problem in last linux git


Hi Stefan,

> De: Stefan Roese <sr at denx.de>
>...
> This looks wrong. Somehow we missed fixing these hex vs.
> decimal values in the Glacier dts file. Here the Canyonlands version:
> 
>         L2C0: l2c {
>...
>         };
> 
> You see the difference. Please give this one a try and let
> me know if it works.

Works prefectly, I can now see the line "256k L2-cache enabled" in Linux boot logs, thanks.

Best regards,
Etienne.
Permalink | Reply | 0 comments |
headers
Diptopal Basu | 6 Jul 2009 12:40
Picon

need to use GDB/MI commands with gdb provided by ELDK4.1.

I am trying to automate GDB debugging so that I can debug an application in
the lights out mode , the debug script will "test" the application using the
gdb and log the information I need.. This is in the concept stages , but
this is what I am planning to do .

     > Write some scripts may be in shell or otherwise ( I heard of a Tk
module called GDBMI ) which will be automatically able to communicate with
the gdb server running on the target and run commands . and capture data .

I will give an example below of how I need the set upto be automated , this
is assuming that the gdbserver on the target side is started with
application nick_arm and listening to port 12345

  $ arm-linux-gdb nick_arm

(gdb) set solib-absolute-prefix /home/dbasu/ELDK/arm/lib
(gdb) set solib-search-path /home/dbasu/ELDK/arm/lib
(gdb) target remote 10.99.104.56:12345

I need to have these set of commands automated , this will be my set up
script before I get into the actual automation , I thought GDB/MI interface
is easier to automate hence I thought  above commands need to be written in
MI equivalent of CLI, but I may be wrong here .

Please comment .

Regards
Diptopal

On Mon, Jul 6, 2009 at 2:13 PM, Wolfgang Denk <wd at denx.de> wrote:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Wolfgang Denk | 6 Jul 2009 20:22
Picon
Picon
Favicon

need to use GDB/MI commands with gdb provided by ELDK4.1.

Dear Diptopal Basu,

In message <bd97640b0907060340p63468cd6kaec28e2372b30eb5 at mail.gmail.com> you wrote:
>
> I am trying to automate GDB debugging so that I can debug an application in
> the lights out mode , the debug script will "test" the application using the
> gdb and log the information I need.. This is in the concept stages , but
> this is what I am planning to do .

I'm not sure that the MI commands will make scripting GDB much easier.
It is a _machine_ interface, and scripting is often more onvenient
when using the standard CLI.

Use standard tools like "expect" that were specifically created for
such purposes...

> I will give an example below of how I need the set upto be automated , this
> is assuming that the gdbserver on the target side is started with
> application nick_arm and listening to port 12345
> 
>   $ arm-linux-gdb nick_arm
> 
> (gdb) set solib-absolute-prefix /home/dbasu/ELDK/arm/lib
> (gdb) set solib-search-path /home/dbasu/ELDK/arm/lib
> (gdb) target remote 10.99.104.56:12345

How about simply using .gdbrc ?

> I need to have these set of commands automated , this will be my set up
> script before I get into the actual automation , I thought GDB/MI interface
(Continue reading)

Permalink | Reply | 0 comments |

Gmane