[PATCH 1/1] eldk-map.dat: Add armv7a-hf to known targets

This is required to make it possible to switch to armv7a-hf

Also remove some trailing whitespace.

Signed-off-by: Thomas Lange <thomas@...>
---
 eldk-map.dat |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/eldk-map.dat b/eldk-map.dat
index 23eff6e..4468b2d 100644
--- a/eldk-map.dat
+++ b/eldk-map.dat
 <at>  <at>  -75,7 +75,7  <at>  <at>  amigaone-xe-g4	MPC7455

 # Dave
 ppchameleon	PPC405EP
- 
+
 # Dave/Denx
 aria		MPC5121e
 qong		IMX31
 <at>  <at>  -464,6 +464,7  <at>  <at>  armv4t		arm
 armv5te		arm
 armv6		arm
 armv7a		arm
+armv7a-hf	arm
 powerpc		powerpc
 powerpc-softfloat	powerpc
 powerpc-4xx		powerpc

eldk-5.3

hi,
i just installed eldk-5.3 for powerpc and started working with it.
I am using a mpx8349 board with linux-3.5.0 booted via tftp and using 
/opt/eldk-5.3/powerpc/rootfs-lsb-sdk via nfs.
this is working so far.

Then i tried to mount another directory from my development-machine with the 
command
mount -t nfs 192.168.69.57:/home/dorwig /mnt/net
this does not work like it did before with eldk-4.0
after stracing it shows up that the mount systemcall returns EINVAL.

what can i do ?

Then i went on and tried to compile an application which is using pam.
the pam_appl.h used to be in usr/include/security .
now there is no such directory in 
/opt/eldk-5.3/powerpc/sysroots/powerpc-linux/usr/include

i found the file in /opt/eldk-5.3/powerpc/rootfs-lsb-sdk/usr/include/security, 
but this is not the place where the crosscompiler expects it.

after copying these files to /opt/eldk-5.3/powerpc/sysroots/powerpc-
linux/usr/include/security the compilation succeded until linking

the linker was missing libpam and libcrypto
there is /opt/eldk-5.3/powerpc/sysroots/powerpc-linux/lib/libcrypto.so.1.0.0
i had to make a symbolic link libcrypto.so -> libcrypto.so.1.0.0

is this normal ?

ligcov missing?

Hi.

I'm running eldk-5.2.1 and noticed that libgcov seems to be missing. Is
there any reason as to why or am I running this the wrong way?

Logs from my attempt:
user <at> machine:~/gcov$
/opt/eldk-5.2.1/powerpc-4xx/sysroots/i686-eldk-linux/usr/bin/ppc440e-linux/powerpc-4xx-gcc
-Wall --coverage main.c
/opt/eldk-5.2.1/powerpc-4xx/sysroots/i686-eldk-linux/usr/libexec/ppc440e-linux/gcc/powerpc-linux/4.6.4/ld:
cannot find -lgcov
collect2: ld returned 1 exit status

Best regards,
Tobias

_______________________________________________
eldk mailing list
eldk@...
http://lists.denx.de/mailman/listinfo/eldk

Diamond blade Supply与您共享了相册。

Dear Sir,

We noticed that you are in the line of Diamond tools if there is chance we  
can cooperate with each other.

We can offer best cheap price while the quality is as good as required.  
Like 100mm/4" sintered blade for Concrete/Granite or other cutting material  
of premium quality costs only $0.8USD.And our 350mm/14" Laser welded blade  
for general purpose of premium quality costs only $24USD.

And glad to inform you that we have a promotion for the segmented blade in  
300mm and 350mm,please check the following:

And  Upon receipt of your reply with your need specification in  
details(diameter,segment size,cutting material). We will send our very  
competitive price to support you.We can make sure at the same price our  
quality is the best and stable.

Looking forward to seeing your soon reply.Thanks for your time.

Best Regards!

Cain Huang

TOOLS CO.,LTD
Add:  Fengxian,Shanghai,China

https://picasaweb.google.com/lh/sredir?uname=104603799815496377009&target=ALBUM&id=5848049099082183281&authkey=Gv1sRgCLvlwJu32vufLw&invite=CKLWtA4&feat=email

Removing X11 and GTK libraries from qte rootfs images in eldk 5.3

Hello all,

In new ELDK 5.3 the pulseaudio package enables x11 and gtk+ support
when checking for "x11" in the DISTRO_FEATURES. As a result x11 and
gtk libraries are included in the qte rootfs. Has anyone an idea
how to prevent this?

Best Regards,

Anatolij

--
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@...

X11 target image - missing libs

Hi 

My own embedded system, based on a PXA166, includes a touchscreen QVGA LCD on which I need to have X11 window
environment running for my end application. 

Using the install scripts as per the ELDK 5.3 Documentation, I've 
downloaded ELDK 5.3 with an armv5te target architecture and X11 target 
configuration. Sorry, I'm a bit of newbie with X11 

When trying to get  the X11 display up and running, I just get a blank screen. I already have the correct
Linux LCD config/initialisation as the LCD displays the Linux bootlog ok via the framebuffer device:
/dev/fb0. 

From the X11 log file and linux boot info I can see that 'libextmod' and 'libdbe' modules are not being
loaded. Also the font paths do not seem to be present/detected in the build (I'm thinking this might be why
the display remains blank).These library extensions should be in /usr/lib/xorg/modules/extensions/
but this directory and files don't exist. Am I missing a crucial step in order to enable these libraries /
fonts to be built and linked at ELDK compile time? Are these X11 extensions really needed for bringing up an
X11 display (libdbe - double buffering support, libextmod - server extensions) ?? 

My X11 setup/config is wrong somewhere....just trying to figure out where!! 

Thanks 

Nige

Below is my linux boot, /var/log/Xorg.0.log, ps dump and xorg.conf. 

[    0.000000] board: aspenite
[    0.000000] chip id: 0xb0a168

Issue about install packages to the rootfs

hi, all  I'm developing a GUI system on a powerpc platform. I want to install some packages to the rootfs. From
the eldk FAQ, I seem to learn that I have to rebuild the eldk from source, is this true? Is there any other
methods?  If I want to rebuild the eldk, the eldk source has to be downloaded from the server by means of git.
Unfortunately, when I use git to clone the source, the bandwidth is only 10KB, and when in download
progress, the git often stops by some reason. So can anyone tell me how I can download a stable 5.3 version
(by which I can rebuild eldk 5.3 from source) with any other methods? 		 	   		  

_______________________________________________
eldk mailing list
eldk@...
http://lists.denx.de/mailman/listinfo/eldk

Re: bitbake of custom ARM kernel to U-Boot uImage not installing properly?

On 23/02/2013 18:47, Hans Beckérus wrote:
> On Sat, Feb 23, 2013 at 5:05 PM, Stefano Babic <sbabic@...> wrote:
>> On 19/02/2013 10:50, Hans Beckérus wrote:
>>> I am using a custom kernel and when building the kernel image using my
>>> own layer the installation phase picks up the wrong image when
>>> installed to ../tmp/deploy/images. The uImage seems to be picked up
>>> from kernel/arch/arm/boot/Image instead of
>>> kernel/arch/arm/boot/uImage? From what I know, is not "Image" just a
>>> stripped down (objcopy) of vmlinux?
>>>
>>> I can see why this is happening in recipes-kernel/linux/linux.inc:
>>>
>>> do_install_prepend() {
>>>         if test -e arch/${ARCH}/boot/Image ; then
>>>              ln -f arch/${ARCH}/boot/Image arch/${ARCH}/boot/uImage
>>>         fi
>>>
>>>         if test -e arch/${ARCH}/boot/images/uImage ; then
>>>              ln -f arch/${ARCH}/boot/images/uImage arch/${ARCH}/boot/uImage
>>>         fi
>>>
>>>         if test -e arch/${ARCH}/kernel/vmlinux.lds ; then
>>>              ln -f arch/${ARCH}/kernel/vmlinux.lds arch/${ARCH}/boot/vmlinux
>>>         fi
>>> }
>>>
>>
>> Try this:
>>
>> do_install_prepend() {

Cross-compiling Linux kernel - unrecognized Opcode

I am trying to compile the Denx Linux-2.6 for the Power PC 85xx
architecture but I'm facing the unrecognized opcode error:

arch/powerpc/kernel/epapr_hcalls.S: Assembler messages:
arch/powerpc/kernel/epapr_hcalls.S:27: Error: Unrecognized opcode: `wrteei'
make[1]: *** [arch/powerpc/kernel/epapr_hcalls.o] Error 1
make: *** [arch/powerpc/kernel] Error 2

I am using Ubuntu 12.04, Linux kernel 3.2.0-37, with ELDK v4.2 (which
installs perfectly). I have also tried Fedora 16 with the same ELDK version
but that still gives me the same errors. I have also tried updating
binutils-devel to version 2.23 but I still cant get the kernel to compile.
Any suggestions?

Thanks,
Qasim

_______________________________________________
eldk mailing list
eldk@...
http://lists.denx.de/mailman/listinfo/eldk

bitbake: how to resolve dependency to ARM kernel-devicetree when building rootfs

I am trying to build a custom ARM image that should include all the
modules from the kernel build but it fails and I can not understand
why. The bitbake error I get is

| Collected errors:
|  * satisfy_dependencies_for: Cannot satisfy the following
dependencies for kernel-modules:
|  *    kernel-devicetree *
|  * opkg_install_cmd: Cannot install package kernel-modules.

My rootfs.bb looks like this

require recipes-core/images/core-image-minimal.bb

# The list of packages used to build images.
IMAGE_INSTALL += "kernel-modules"

# Formats of root filesystem images that you want to have created.
IMAGE_FSTYPES = "jffs2"

The device tree blob is built and located in the kernel deploy image folder.
I can see that I have the following files under the kernel work path

./packages-split/kernel-devicetree
./pkgdata/runtime/kernel-devicetree
./pkgdata/runtime-reverse/kernel-devicetree

What have I missed?

Hans

bitbake of custom ARM kernel to U-Boot uImage not installing properly?

I am using a custom kernel and when building the kernel image using my
own layer the installation phase picks up the wrong image when
installed to ../tmp/deploy/images. The uImage seems to be picked up
from kernel/arch/arm/boot/Image instead of
kernel/arch/arm/boot/uImage? From what I know, is not "Image" just a
stripped down (objcopy) of vmlinux?

I can see why this is happening in recipes-kernel/linux/linux.inc:

do_install_prepend() {
        if test -e arch/${ARCH}/boot/Image ; then
             ln -f arch/${ARCH}/boot/Image arch/${ARCH}/boot/uImage
        fi

        if test -e arch/${ARCH}/boot/images/uImage ; then
             ln -f arch/${ARCH}/boot/images/uImage arch/${ARCH}/boot/uImage
        fi

        if test -e arch/${ARCH}/kernel/vmlinux.lds ; then
             ln -f arch/${ARCH}/kernel/vmlinux.lds arch/${ARCH}/boot/vmlinux
        fi
}

The first test is what breaks it for me. Since it hits the first
condition a "uImage" is deployed based on the wrong image. I expected
it to pick up the second one.
Why is the "Image" an option for installing as a "uImage"? Is the
"Image" ever really a valid "uImage"? I guess I must have made
something wrong, but I can not understand what. Please advise.