One image for two different core

[Bizhan Gholikhamseh (bgholikh)]

Hi All,

I am doing a feasibility study whether I can have one image for two
different  platform with e300 ad e500 core. The idea is uboot will
detect which type of the processor is running and pass the information
to the early Linux startup, then the code will configure itself based on
what type of core it is.

One of the issue I see is the tool chain,.

I would like to get your opinion on this please.

Many thanks in advance,

Bizhan

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

PowerPC source tree

[Bizhan Gholikhamseh (bgholikh)]

Hi,
Where can I download the latest (stable) PowerPC source tree? Is it
kernel.org? 
Thanks,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: Graphic Card on Freescale MPC837x-rdb

[Bizhan Gholikhamseh (bgholikh)]

> -Original Message-
> From: Anatolij Gustschin [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, June 25, 2008 12:37 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org; [EMAIL PROTECTED]
> Subject: Re: Graphic Card on Freescale MPC837x-rdb
> 
> Bizhan Gholikhamseh (bgholikh) wrote:
> > HI all,
> > Has anyone tried using a Graphic card on Freescale 
> MPC837x-rdb board? 
> > If so I appreciate any hints and information that I can use.
> 
> take a look at these patches and info in the readme under:
> http://www.scitechsoft.com/ftp/snap/linux/videoboot/
> 
> it is pretty easy to get them working with older ATI Cards 
> (R2xx) on powerpc.
> 
Hi
Do I need to change the DT file for add-on graphic cards?

Regards,
Bizhan 

> Best regards,
> Anatolij
> 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Graphic Card on Freescale MPC837x-rdb

[Bizhan Gholikhamseh (bgholikh)]

HI all,
Has anyone tried using a Graphic card on Freescale MPC837x-rdb board? If
so I appreciate any hints and information that I can use.
 
Many thanks in advance,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Linker error: no init_fcc_ioports

[Bizhan Gholikhamseh (bgholikh)]

Hi
Our platform is based on mpc8541cds, I am using Linux 2.6.24 from
powerpc git tree.
I tried to compile the kernel to include the fcc Ethernet controller and
I got the following
linker  errors:
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
 
arch/powerpc/sysdev/built-in.o: In function `fs_enet_of_init':
arch/powerpc/sysdev/fsl_soc.c:853: undefined reference to
`init_fcc_ioports'
arch/powerpc/sysdev/fsl_soc.c:853: undefined reference to
`init_fcc_ioports'
 
I  have attached the .config file I am using.
Any  help greatly appreciated.
Bizhan



config
Description: config
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Where is fcc_enet.c

[Bizhan Gholikhamseh (bgholikh)]

Hi,
I am porting to Linux 2.6.24 from linux 2.6.11 on mpc85xx cds platform,
I am not able to locate fcc_enet.c file under
linux 2.6.24 source tree, any idea
 
Thanks,
Bizhan 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: build is broken

[Bizhan Gholikhamseh (bgholikh)]

 

> -Original Message-
> From: Scott Wood [mailto:[EMAIL PROTECTED] 
> Sent: Monday, February 04, 2008 8:52 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: build is broken
> 
> On Fri, Feb 01, 2008 at 03:23:21PM -0800, Bizhan Gholikhamseh 
> (bgholikh) wrote:
> >   AS  .tmp_kallsyms2.o
> >   LD  vmlinux
> >   SYSMAP  System.map
> >   SYSMAP  .tmp_System.map
> >   BOOTCC  arch/powerpc/boot/treeboot-walnut.o
> > Assembler messages:
> > Error: Internal assembler error for instruction icbt 
> Internal error, 
> > aborting at 
> > 
> /usr/src/RPM/BUILD/crosstool/source/binutils-2.15/gas/config/tc-ppc.c
> > line 1300 in ppc_setup_opcodes
> > Please report this bug.
> 
> Try using a newer toolchain.
> 
> -Scott
>
Thanks Scott, 
That did it, I upgraded the toolchain to the 4.1 and worked fine.

Thanks again,
Bizhan 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: build is broken

[Bizhan Gholikhamseh (bgholikh)]

> -Original Message-
> From: Josh Boyer [mailto:[EMAIL PROTECTED] 
> Sent: Friday, February 01, 2008 7:24 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: build is broken
> 
> On Fri, 1 Feb 2008 15:23:21 -0800
> "Bizhan Gholikhamseh (bgholikh)" <[EMAIL PROTECTED]> wrote:
> 
> > Hi
> > I just downloaded the latest source tree from :
> > git://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
> > 
> > I am using gnu cross compiler version 3.4.3. I get the an "awk" and 
> > "assmbeler" error.
> > 
> > Please help me out. Thanks
> > 
> > $ <mailto:[EMAIL PROTECTED]>  make ARCH=powerpc
> > CROSS_COMPILE=powerpc-linux-gnu- uImage
> > awk: cmd. line:1: (FILENAME=- FNR=2) fatal: attempt to 
> access field -1
> >   CHK include/linux/version.h
> >   CHK include/linux/utsrelease.h
> >   CALLscripts/checksyscalls.sh
> >   CHK include/linux/compile.h
> >   CALLarch/powerpc/kernel/systbl_chk.sh
> >   LD  vmlinux.o
> >   MODPOST vmlinux.o
> > WARNING: vmlinux.o(.meminit.text+0x9f8): Section mismatch 
> in reference 
> > from the function free_area_init_node() to the function
> > .init.text:__alloc_bootmem_node()
> > The function __meminit free_area_init_node() references a function 
> > __init __alloc_bootmem_node().
> > If free_area_init_node is only used by __alloc_bootmem_node then 
> > annotate free_area_init_node with a matching annotation.
> >  
> >   AS  .tmp_kallsyms2.o
> >   LD  vmlinux
> >   SYSMAP  System.map
> >   SYSMAP  .tmp_System.map
> >   BOOTCC  arch/powerpc/boot/treeboot-walnut.o
> > Assembler messages:
> > Error: Internal assembler error for instruction icbt 
> Internal error, 
> > aborting at 
> > 
> /usr/src/RPM/BUILD/crosstool/source/binutils-2.15/gas/config/tc-ppc.c
> > line 1300 in ppc_setup_opcodes
> > Please report this bug.
> > make[1]: *** [arch/powerpc/boot/treeboot-walnut.o] Error 2
> > make: *** [uImage] Error 2
> 
> I have no idea why you would get that if you have a properly 
> built toolchain.  Can you do a fresh compile with V=1 set?
> 
> josh
>
I did the fresh build with V=1. I still get the same awk error and the
compile's last line output:
  powerpc-linux-gnuspe-gcc -m32
-Wp,-MD,arch/powerpc/boot/.treeboot-walnut.o.d -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -Os -msoft-float
-pipe -fomit-frame-pointer -fno-builtin -fPIC -nostdinc -isystem
/opt/Embedix/usr/local/powerpc-linux-gnuspe/gcc-3.4.3-e500-glibc-2.3.3-s
pe/lib/gcc/powerpc-linux-gnuspe/3.4.3/include -Iarch/powerpc/boot
-I/home/bizhan/PPC/arch/powerpc/boot
-I/home/bizhan/PPC/arch/powerpc/boot/libfdt -mcpu=405 -c -o
arch/powerpc/boot/treeboot-walnut.o arch/powerpc/boot/treeboot-walnut.c
Assembler messages:
Error: Internal assembler error for instruction icbt
Internal error, aborting at
/usr/src/RPM/BUILD/crosstool/source/binutils-2.15/gas/config/tc-ppc.c
line 1300 in ppc_setup_opcodes
Please report this bug.
make[1]: *** [arch/powerpc/boot/treeboot-walnut.o] Error 2
make: *** [uImage] Error 2

Any help greatly apprieciated.

Thanks,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

build is broken

[Bizhan Gholikhamseh (bgholikh)]

Hi 
I just downloaded the latest source tree from :
git://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git

I am using gnu cross compiler version 3.4.3. I get the an "awk" and
"assmbeler" error.

Please help me out. Thanks

$   make ARCH=powerpc
CROSS_COMPILE=powerpc-linux-gnu- uImage
awk: cmd. line:1: (FILENAME=- FNR=2) fatal: attempt to access field -1
  CHK include/linux/version.h
  CHK include/linux/utsrelease.h
  CALLscripts/checksyscalls.sh
  CHK include/linux/compile.h
  CALLarch/powerpc/kernel/systbl_chk.sh
  LD  vmlinux.o
  MODPOST vmlinux.o
WARNING: vmlinux.o(.meminit.text+0x9f8): Section mismatch in reference
from the function free_area_init_node() to the function
.init.text:__alloc_bootmem_node()
The function __meminit free_area_init_node() references
a function __init __alloc_bootmem_node().
If free_area_init_node is only used by __alloc_bootmem_node then
annotate free_area_init_node with a matching annotation.
 
  AS  .tmp_kallsyms2.o
  LD  vmlinux
  SYSMAP  System.map
  SYSMAP  .tmp_System.map
  BOOTCC  arch/powerpc/boot/treeboot-walnut.o
Assembler messages:
Error: Internal assembler error for instruction icbt
Internal error, aborting at
/usr/src/RPM/BUILD/crosstool/source/binutils-2.15/gas/config/tc-ppc.c
line 1300 in ppc_setup_opcodes
Please report this bug.
make[1]: *** [arch/powerpc/boot/treeboot-walnut.o] Error 2
make: *** [uImage] Error 2

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Enabling MSR debugging mode on MPC8541cds

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
I am working on powerpc git tree version
Linux-2.6.22-rc4-geff2ebd2-dirty.
Our custom board is based on mpc8541cds. I am trying to use Jtag to
debug
the kernel issues. I have done the following changes to the source tree:
 
On the top directory Makefile:
 
CC= $(CROSS_COMPILE)gcc -g2 -gdwarf-2
AFLAG_KERNEL = -Wa,gdwarf2
 
include/asm-powerpc/reg_booke.h:
/* Default MSR for kernel mode. */ 
#if defined (CONFIG_40x) 
#define MSR_KERNEL (MSR_ME|MSR_RI|MSR_IR|MSR_DR|MSR_CE|MSR_DE)  
#elif defined(CONFIG_BOOKE) 
#define MSR_KERNEL (MSR_ME|MSR_RI|MSR_CE|MSR_DE)
 
However, I can see through Jtag that the MSR_DE (the debug bit) is not
set on the, 
so I am not able to set break points.
 
Any help greatly appreciated.
 
Regards,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: Failed to mount rootfs

[Bizhan Gholikhamseh (bgholikh)]

 
Hi Heiko, 
> "Bizhan Gholikhamseh (bgholikh)" <[EMAIL PROTECTED]> wrote:
> > Our custom board is leveraged from MPC8541cds from freescale.
> > We have been running Linux 2.6.11 on it recently I have 
> tried to boot 
> > the system with the latest Linux 2.6.22-rc4 from PowerPC git tree.
> >  
> > I did ported the libfdt to our older version of the uboot and were 
> > able to
> 
> Hmm... why you didnt use actual code?
> 
> [...]
> > chosen {
> > linux,stdout-path = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
> > };
> > chosen {
> > name = "chosen";
> > bootargs = "root=/dev/ram rw console=ttyS1,115200";
> > linux,platform = <600>;
> > linux,initrd-start = <1ef33000>;
> > linux,initrd-end = <1fe190aa>;
> > linux,stdout-path = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
> > };
> > };
> 
> Here is your problem, you have 2 choosen nodes:
> 
> 64k data, 108k bss, 116k init) Mount-cache hash table entries: 512
> device-tree: Duplicate name in /, renamed to "chosen#1"
> ^^^
> -> Linux didnt find your commandline ...
> 
> Hmm... do you have CONFIG_OF_FLAT_TREE and CONFIG_OF_LIBFDT defined?
> If so, this would explain, why you have 2 choosen nodes.

Yes I do have both CONFIG_OF_FLAT_TREE and CONFIG_OF_LIBFDT defined. Is
there a document to tell more about these options please?

Thanks,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: Failed to mount rootfs

[Bizhan Gholikhamseh (bgholikh)]

Hi Jochen, 

> 
> > device-tree: Duplicate name in /, renamed to "chosen#1"
> 
> > And here is the device tree:
> > chosen {
> > linux,stdout-path = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
> > };
> > chosen {
> > name = "chosen";
> > bootargs = "root=/dev/ram rw console=ttyS1,115200";
> > linux,platform = <600>;
> > linux,initrd-start = <1ef33000>;
> > linux,initrd-end = <1fe190aa>;
> > linux,stdout-path = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
> > };
> 
> you can't have two chosen nodes. Linux renames the second one 
> to chosen#1 and thus can't find the kernel arguments.
>
I do not know why it is creating two chosen node. In my dts file I have
placed one empty chosen node: 
chosen{
};
If I do not do this,  I get the following error during boot process:

libfdt: FDT_ERR_TRUNCATED
Failed creating the /chosen node (0x00C0), aborting.

Any reason??
 
Thanks,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Failed to mount rootfs

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
Our custom board is leveraged from MPC8541cds from freescale.
We have been running Linux 2.6.11 on it recently I have tried to boot
the system with the latest Linux 2.6.22-rc4 from PowerPC git tree.
 
I did ported the libfdt to our older version of the uboot and were able
to
resolve the device tree. After downloading the uImage, dtb file and
ramdisk
I use the bootm command to boot the linux, but it failes..

...
driver initialized: 16 RAM disks of 4096K size 1024 blocksize
VFS: Cannot open root device "" or unknown-block(0,0) Please
append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0) Rebooting in 180 seconds..

...
 
During boot I observeed that the "kernel Command Line:" is empty, is
this parameter should be supplied by fdt also?
 
I have copied the boot log and dump of the device tree below, Any help
greatly appreicate it.
 
Thanks,
 
 
 
Last Reset Type: Power On
FLASH: 8 MB
L2 cache 256KB:enabled
In: serial
Out: serial
Err: serial
Net: TSEC0.
IDE: Compact Flash: Bus 0: OK
Device 0: Model: STI Flash 7.4.0 Firm: 01.25.06 Ser#: STI
J106306241050439
Type: Hard Disk
Capacity: 245.0 MB = 0.2 GB (501760 x 512) System watchdog: is now
stopped.
=> printenv
bootcmd=setenv bootargs root=/dev/hda2 rw console=$consoledev,$baudrate
$othbootargs;setenv autostart yes;diskboot $l; nfsboot=setenv bootargs
root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostnar
bootdelay=2
baudrate=115200
loads_echo=1
rootpath=/nfsroot
hostname=unknown
loadaddr=100
netdev=eth0
consoledev=ttyS1
ramdiskaddr=100
ramdiskfile=ramdisk.UBoot
ethact=TSEC0
firstboot=no
bootargs=root=/dev/ram rw console=ttyS1,115200 fdfile=biz3.dtb
bootfile=uImage
ramboot=setenv bootargs root=/dev/ram rw console=ttyS1,115200
filesize=8 fileaddr=10
ipaddr=172.28.176.13
serverip=172.28.176.140
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:18:18:8f:a6:ac
eth1addr=00:18:18:8f:a6:ad
eth2addr=00:18:18:8f:a6:ae
pid=CTS-CODEC-PRIM=
serial=FSJC0537522
ver_id=V01
hwver=0400
ver=U-boot 1.1.2(pq3-20050113-0) (Jan 20 2008 - 18:03:58)
Environment size: 1050/8188 bytes
=> tftp 10 uImage
Using TSEC0 device
TFTP from server 172.28.176.140; our IP address is 172.28.176.13
Filename 'uImage'.
Load address: 0x10
Loading:
#
###
done
Bytes transferred = 629989 (99ce5 hex)
=> tftp 200 ramdisk.u-boot
Using TSEC0 device
TFTP from server 172.28.176.140; our IP address is 172.28.176.13
Filename 'ramdisk.u-boot'.
Load address: 0x200
Loading:
#
#
#
#
#
#
#
#
#
#
done
Bytes transferred = 15622378 (ee60ea hex) => tftp c0 board.dtb Using
TSEC0 device TFTP from server 172.28.176.140; our IP address is
172.28.176.13 Filename 'board.dtb'.
Load address: 0xc0
Loading: #
done
Bytes transferred = 4273 (10b1 hex)
=> bootm 10 200 c0
## Booting image at 0010 ...
Image Name: Linux-2.6.22-rc4-geff2ebd2-dirty
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 629925 Bytes = 615.2 kB
Load Address: 
Entry Point: 
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
>>> inside do_bootm_linux 
## Loading RAMDisk Image at 0200 ...
Image Name: MPC85xxCDS MTWKS Ramdisk
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 15622314 Bytes = 14.9 MB
Load Address: 
Entry Point: 
Verifying Checksum ... OK
Booting using flat device tree at 0xc0
Loading Ramdisk to 1ef33000, end 1fe190aa ... OK vfpga watchdog not
supported in this CTS version. Keeping watchdog disabled System
watchdog: is now stopped.
## Transferring control to Kernel (at address ) ...
Using MPC85xx CDS machine description
Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb Linux
version 2.6.22-rc4-geff2ebd2-dirty ([EMAIL PROTECTED]) (gcc
version 3.4.3) #6 Sun Jan 20 22:51:26 PST8
setup_arch: bootmem
mpc85xx_cds_setup_arch()
CDS Version = 0xff in slot 4
Found MPC85xx PCI host bridge at 0xe0008000. Firmware bus
number: 0->0 Fou

Differences between git tree

[Bizhan Gholikhamseh (bgholikh)]

Hi,
Could someone let me know what is the each of these git tree are?

http://opensource.freescale.com/pub/scm/linux-2.6-jdl.git
AND
http://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git

Many thanks in advance,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Unwinding stack frame

[Bizhan Gholikhamseh \(bgholikh\)]

Hi,
We are using MPC 8541 processor. Running Linux 2.6.11.
 
I have a question regarding unwinding stack frame in userland.
 
To understand the stack frame format, I am using gdb to walk through
nested function calls frame.
I am not able to understand where the PC (program counter) of callee
functions is saved on the stack/register.
 
Here are my questions:
1- Is there any available software like "pstack" ported to powerpc that
I can use?
I know the stack pointer of  the last frame is save in "R1" register.
2- How about PC, and number of the input parameters to the function.
 
Many thanks in advance,
BZ
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: help on dts compiler please.

[Bizhan Gholikhamseh \(bgholikh\)]

 
> > $ dtc -f -I dts -O dtb mpc8541cds.dts
> > DTC: dts->dtb  on file "mpc8541cds.dts"
> > syntax error at line 15
> > FATAL ERROR: Couldn't read input tree
> 
> Where did you get your dtc version from?
> 
Sorry I answered the question wrong. I downloaded the gzip tar file from
David Gibson web page.

> josh
> 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: help on dts compiler please.

[Bizhan Gholikhamseh \(bgholikh\)]

 

> -Original Message-
> From: Josh Boyer [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 02, 2007 6:33 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: help on dts compiler please.
> 
> On Mon, 2007-07-02 at 17:04 -0700, Bizhan Gholikhamseh 
> (bgholikh) wrote:
> > Hi
> > I have downloaded the latest Linux code from the following git tree:
> > git:// git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
> >  
> > I have also installed dtc compiler version.
> > I am trying to create dtb file from mpc8541cds.dts.
> > I ran the following command and get error:
> >  
> > $ dtc -f -I dts -O dtb mpc8541cds.dts
> > DTC: dts->dtb  on file "mpc8541cds.dts"
> > syntax error at line 15
> > FATAL ERROR: Couldn't read input tree
> 
> Where did you get your dtc version from?

I got it from the git tree two days ago:git://
git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git

I have attached the file.
It appears it complains about "compatibility" property on all the dts
file.

Thanks,
Bizhan

> 
> josh
> 


mpc8541cds.dts
Description: mpc8541cds.dts
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

help on dts compiler please.

[Bizhan Gholikhamseh \(bgholikh\)]

Hi 
I have downloaded the latest Linux code from the following git tree:
git:// git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
 
I have also installed dtc compiler version.
I am trying to create dtb file from mpc8541cds.dts.
I ran the following command and get error:
 
$ dtc -f -I dts -O dtb mpc8541cds.dts
DTC: dts->dtb  on file "mpc8541cds.dts"
syntax error at line 15
FATAL ERROR: Couldn't read input tree

 
Many thanks in advance,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

cuImage question

[Bizhan Gholikhamseh \(bgholikh\)]

Hi All,
I am kind of new to the concept of "cuImage" and I am not able to find
any info on the net(?).
 
We are using older version of the uboot: 1.1.2. I have compiled the
latest kernel from git tree for
MPC8541E from freescale. 
 
I would appreciate any hints on how to use 'cuImage" to load this image
with our legacy uboot version?
 
Many thanks in advance,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

ARCH=ppc or ARCH=powerpc

[Bizhan Gholikhamseh \(bgholikh\)]

Hi All,
Sorry for asking this question again, I am still not clear on some of
the issues.
Background:
We have developed a custom board based on Freescale reference board:
MPC8555_CDS with MPC8541E processor running Linux 2.6.11 and uboot 1.1.2
version.
 
I would like to update the Linux kernel to the latest available kernel
2.6.21.
Here are my questions:
1- Should I use ARCH=ppc or ARCH=powerpc to build the kernel?
2- I have seen similar filenames under arch/ppc and arch/powerpc, which
one applies to MPC8541E?
3- Once I build the kernel, could I load the kernel with uboot version
1.1.2 or not? if not what I should do?
 
Many thanks in advance,
Bizhan
 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: General question on upgrading Linux version

[Bizhan Gholikhamseh \(bgholikh\)]

 

> -Original Message-
> From: Andy Fleming [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, June 20, 2007 2:52 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: General question on upgrading Linux version
> 
> 
> On Jun 20, 2007, at 16:29, Bizhan Gholikhamseh ((bgholikh)) wrote:
> 
> > Hi All,
> > We are using MPC8541 processor from freescale. Our current kernel 
> > version is based on 2.6.11 plus some patches provided by Freescale.
> > I would like to update our Kernel version to a more recent version.
> > I would greatly appreciate if you could provide me with 
> some general 
> > guideline on how to proceed .
> 
> You should be able to check out the latest sources from 
> git:// git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git

The current stable kernel release is 2.6.21. Could I use that tree
instead ?

> 
> You will probably also need a newer u-boot from here:
> 
> git://www.denx.de/git/u-boot-mpc85xx.git
Currently we are using uboot 1.2. Do I have to update the u-boot version
also or I can bypass that for now?
Thanks,
Bizhan

> 
> Please tell me if you have any problems using these.
> 
> Andy
> 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: General question on upgrading Linux version

[Bizhan Gholikhamseh \(bgholikh\)]

 

> -Original Message-
> From: Andy Fleming [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, June 20, 2007 2:52 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: General question on upgrading Linux version
> 
> 
> On Jun 20, 2007, at 16:29, Bizhan Gholikhamseh ((bgholikh)) wrote:
> 
> > Hi All,
> > We are using MPC8541 processor from freescale. Our current kernel 
> > version is based on 2.6.11 plus some patches provided by Freescale.
> > I would like to update our Kernel version to a more recent version.
> > I would greatly appreciate if you could provide me with 
> some general 
> > guideline on how to proceed .
> 
> You should be able to check out the latest sources from 
> git:// git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
> 
> You will probably also need a newer u-boot from here:
> 
> git://www.denx.de/git/u-boot-mpc85xx.git
> 
> Please tell me if you have any problems using these.

Thanks will do.

> 
> Andy
> 
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

General question on upgrading Linux version

[Bizhan Gholikhamseh \(bgholikh\)]

Hi All,
We are using MPC8541 processor from freescale. Our current kernel
version is based on 2.6.11 plus some patches provided by Freescale. I
would like to update our Kernel version to a more recent version. 
I would greatly appreciate if you could provide me with some general
guideline on how to proceed .
 
Many thanks in advance,
B
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Support for Linux Trace Tool (ltt)

[Bizhan Gholikhamseh \(bgholikh\)]

Hi 
All,
Is there any support 
for Linux ltt on Linux 2.6 (perfably 2.6.11) for ppc architecture 
(MPC8541E)?
Thanks,
BG
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

kprobe support for ppc 32 bit

[Bizhan Gholikhamseh \(bgholikh\)]

My understanding is 
that the kprobe  is part of the standard linux 2.6 source 
tree.
I am not able to 
find any files related to the kprobe in ppc 32 bit architecture source 
tree
, however, 
there are 
some related files for ppc 64 bit architecture source tree.
directory. 

What am I 
missing?
 
Many thanks in 
advance,
Bizhan
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

kprobe support for ppc 32 bit

[Bizhan Gholikhamseh (bgholikh)]

My understanding is that the kprobe  is part of the standard linux 2.6
source tree.
I am not able to find any files related to the kprobe in ppc 32 bit
architecture source tree
, however, there are some related files for ppc 64 bit architecture
source tree.
directory. 
What am I missing?
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060908/73cc94ed/attachment.htm
 

kernel panic: BUG in cascade at kernel/timer.c

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
We have developed our own custom board based on MPC8541 board running
linux 2.6.11
During stress testing the system we get following kernel panic which
related to timer cascase.
Any hints greatly apprieciated. Many thanks in advance:
 
kernel BUG in cascade at kernel/timer.c:416!
Oops: Exception in kernel mode, sig: 5 [#1]
PREEMPT 
NIP: C0023AB4 LR: C0023CC8 SP: C02DDDF0 REGS: c02ddd40 TRAP: 0700
Tainted: P
MSR: 00021200 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
TASK = c02bb730[0] 'swapper' THREAD: c02dc000
Last syscall: 120 

File timer.c line 416 :
401 static int cascade(tvec_base_t *base, tvec_t *tv, int index)
402 {
403 /* cascade all the timers from tv up one level */
404 struct list_head *head, *curr;
405 
406 head = tv->vec + index;
407 curr = head->next;
408 /*
409  * We are removing _all_ timers from the list, so we
don't  have
 to
410  * detach them individually, just clear the list
afterwards.
411  */ 
412 while (curr != head) {
413 struct timer_list *tmp;
414 
415 tmp = list_entry(curr, struct timer_list,
entry);
416 BUG_ON(tmp->base != base);
417 curr = curr->next;
418 internal_add_timer(base, tmp);
419 }
420 INIT_LIST_HEAD(head);
421 
422 return index;

 
Regards,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060810/2fc7640b/attachment.htm
 

Help: problem with gdb

[Bizhan Gholikhamseh (bgholikh)]

HI,
We are running Linux 2.6.11 on our platform with MPC8541.
One of the application gets segmentation fault and creates core dump
upon exit.
 
I moved the core dump to the development environment and when I try to
run 
gdb on the core dump I get the following gdb internal errors. If you
have
any idea to help I greatly apprieciate. Many thanks in advance,
 
[bizhan at vs ~]$ powerpc-linux-gdb app core.app.9707
GNU gdb 5.3
Copyright 2002 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-pc-linux-gnu
--target=powerpc-linux"...
(no debugging symbols found)...
Core was generated by `/usr/local/bin/cma'.
Program terminated with signal 11, Segmentation fault.
../../../gdb-5.3/gdb/regcache.c:472: gdb-internal-error:
set_register_cached: Assertion `regnum <
current_regcache->descr->nr_raw_registers' failed.
An internal GDB error was detected.  This may make further
debugging unreliable.  Quit this debugging session? (y or n) 
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060712/75911d86/attachment.htm
 

zero-copy support on TSEC?

[Bizhan Gholikhamseh (bgholikh)]

Hi ALL,
We have developed a custom board mother board based on
MPC8541 processor running Linux 2.6.11.
 
In our system, most of the ingress UDP packets  are retransmitted
with one modification to data portion of the packet (one byte). As you 
see there are many copy overhead due to copy from system to userland 
and vise versa which has impacted our system performance. 
 
Is there a zero-copy support for TSEC 
to eliminate the buffer copy from kernel to userland and vise versa?
 
Are there any other technique that we need to do to eliminate packet
coping?
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060626/79e6e21b/attachment.htm
 

Diagnostic tool

[Bizhan Gholikhamseh (bgholikh)]

Hi,

I am using PQIII Freescale cpu 8541 on a custom board.

Is anyone aware of diagnostics tool as a kernel module to test cpu,
memory and other hardware components that may be out there. This is
normally a test suit that will be used manufacturing for extensive HW
testing. 

Thanks and Regards,

Bizhan

-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060324/d3e81fb4/attachment.htm
 

VLAN support on TSEC for MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
I have asked this question in past with no response. Are there any VLAN
implementation of TSEC driver for MPC8541 (with CPM core)?
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060321/c04e27c4/attachment.htm
 

Hints on hard hang

[Bizhan Gholikhamseh (bgholikh)]

Hi All,

Our custom board based on 8541 processor running Linux 2.6.11 gets hard
hang during run time. We can't soft reset (SRESET, Pin#AF20) and get a
machine check interrupt when the hang happens, and JTAG can not
communicate with the processor. We do not know how to go to debug this
issue. If you have any idea or hints, we greatly appreciate.

Many thanks in advance,

Bizhan

-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060307/24a9a265/attachment.htm
 

System hang and NMI support on 8541

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
Our custom board 8541 base processor running Linux 2..11 hangs during
stress testing. Is there a support for a 
Non Mask able interrupt?
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060306/d0912c29/attachment.htm
 

VLAN support on TSEC

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
We are using custom board 8541 based processor, running Linux version
2.6.11. 
In our board, the TSEC interface is connected to a BCM switch chip. We
need to configure the interface to support VLAN . The TSEC hardware has
no VLAN support and the current driver, gianfar.c, has no support for
VLAN either. Are there any implementation of gianfar.c  which supports
VLAN?
 
Many thanks in advance,
Bizhan   
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060303/1321fd73/attachment.htm
 

Help: FCC driver does not handle IPV6 multicast packet

[Bizhan Gholikhamseh (bgholikh)]

HI All,
Our custom board is based on PPC 8541 running Linux 2.6.11.
We have NO issue if FCC is operating in 100 Mbs. However, if we
configure the interface  in 10 Mbs we see the following behavior:
If IPV6 is enabled, as soon as the FCC network interface is plumbed
through "ifconfig" system call, we observe the CPU load increases to 90
percent 
and most of the load is related to softirq process. A traceroute command
on the interface displays an IPV6 multicast packet continuously getting
transmitted.
If we bring the interface down through the ifconfig, we do not observe
the problem
no longer. The strange thing is we do not observe this behavior if the
interface
is plumbed 100 Mbs.
We need to root cause this and have no idea what to look for, any idea
greatly
appreciated.
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060124/ea239926/attachment.htm
 

compact flash driver

[Bizhan Gholikhamseh (bgholikh)]

> "Alex" == Alex Zeffertt  writes:

>> Hello All, Are there any compact flash driver supported for Linux

>> 2.6? If there is where can i get the source code. Thanks, Bizhan

>> 

Alex> I think that CF cards just get treated the same as any other

Alex> IDE disk by linux. No special driver needed.

>Yes. There are some gotchas with newer pcmcia/cardbus flash cards.

>For instance, Silicon Systems devices claim to support IORDY, but
don't, which results in a system hang. I imagine that the same >kind of
things will show up in newer CF devices, although I think that CF can't
support DMA.

>It also depends upon how you interface CF: via an IDE controller, or
via a cardbus interface.

>I expect to have a git tree with stuff available soon.

Do you have an early release code? I can start to work at.

Many thanks in advance,

Bizhan

-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20051102/ea9c7570/attachment.htm
 

compact flash driver

[Bizhan Gholikhamseh (bgholikh)]

Hello All,
Are there any compact flash driver supported for Linux 2.6? If there is
where can i get the source code.
Thanks,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20051025/40547208/attachment.htm
 

Need help Please:IOMEM memory allocation

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
I am trying to develop a SPI driver for MPC8541. 
I need to allocate memory buffers within kernel that their physical
address is
on 64 byte boundary and initialize the transmit and receive buffer
descriptors with the
their physical locations. Since I am not sure how to do this within the
kernel here is how I am doing it:
 
 unsigned long mem_addr_rx = __get_free_page(GFP_KERNEL);  //receive
buffer
 unsigned long mem_addr_tx = __get_free_page(GFP_KERNEL); //transmit
buffer
.
rx_buffer_addr = __pa(mem_addr_rx);
tx_buffer_addr=__pa(mem_addr_tx);
 
My assumption is by allocating a page, I am guaranteed that I will have
64 byte boundary condition.
Is this correct?
 
I have also told, the SPI does not have snoop bit, so I need to allocate
buffers from iomem, I have
no idea how to do this.
 
Please help,
Many thanks in advance,
Regards,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20051017/4a43bd21/attachment.htm
 

SPI driver for MPC8541

[Bizhan Gholikhamseh (bgholikh)]

HI All,
Are there any SPI driver for MC8541? If there is, could someone point me
to it.
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20051011/e15fd1d5/attachment.htm
 

Interrupt mapping for MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Hi ALL,
We are developing a custom board mother board based on
MPC8541 processor trying to run with Linux 2.6.11. The custom board has
hardwire the
interrupt lines for PCI peripherals with specific interrupt number for
each peripheral. 
The MPC8541 has on Ethernet chip which during boot process the Linux
kernel assign 
interrupt number 96 to it. Unfortunately one of our PCI peripheral that
is hardwire need that
interrupt number and this causes conflict. 
Is there anyway we can avoid reserving this interrupt number so kernel
does not assign it unless it is asked specifically?
 
Thanks,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050913/22278ea1/attachment.htm
 

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

HI Kumar,
I have attached the /proc/ioports and /proc/iomem for 8541E.
Also the CONFIG_ 85XX_PCI2 is set to yes.

Freescale does not support 2.6.13 so I am not able to update to that
version yet.

Thanks,
Bizhan

-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 10, 2005 12:11 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

No problem.  I'm hunting around the problem, but trying to figure out
exactly where the bug is.  What's a little odd is that in 2.6.11 we  
should have excluded all the devices that are on the VIA chipset.   
However, in the logs you sent me we see those devices. Part of the
problem is that your TI DSP has its own P2P bridge on it.  Therefor the
bus numbers for the devices start changing around a bit.

What is CONFIG_85xx_PCI2 set to in your .config?

Can you send me the output of the following on the 8555 CDS:
cat /proc/ioports
cat /proc/iomem

Also, if you feel daring, grab the latest 2.6.13-rc6 kernel and build it
for 8555 CDS and see what happens.

Oh, is this card something standard or a custom thing?  The issue of  
having a card with P2P bridge on it has come up more than once.   
However, I'm not sure of any standard PC PCI cards do this (at least
none of the simple cards we have do).  I'd like to see if we can find
something that we could start testing with.

thanks

- kumar

On Aug 10, 2005, at 1:03 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Kumar,
> Sorry it took a while. I have attached the 8540 PCI boot log and 
> /proc/pci. Also I found out the functions you mentioned are not used 
> in my environment.
>
> Thanks,
> Bizhan
>
> -Original Message-
> From: Kumar Gala [mailto:kumar.gala at freescale.com]
> Sent: Wednesday, August 10, 2005 9:06 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded at ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> It would be extremely helpful to get the output from the work MPC8540 
> for lspci and cat /proc/pci.
>
> Also, I forget if 2.6.11 has CDS VIA support, but if it does you can 
> try disabling it by commenting out the calls to:
> mpc85xx_cds_enable_via() & mpc85xx_cds_fixup_via() in arch/ppc/syslib/

> ppc85xx_setup.c and see what happens.
>
> - k
>
> On Aug 10, 2005, at 10:58 AM, Bizhan Gholikhamseh \\((bgholikh\\))
> wrote:
>
>
>>  <> Kumar,
>> We do not support or care about VIA IDE controller. I have enabled 
>> the
>>
>
>
>> DEBUG flag and attached the debug messages during boot. This is for 
>> 8541E.
>> Regards,
>> Bizhan
>>
>> -Original Message-
>> From: Kumar Gala [mailto:kumar.gala at freescale.com]
>> Sent: Tuesday, August 09, 2005 4:11 PM
>> To: Bizhan Gholikhamseh (bgholikh)
>> Cc: linuxppc-embedded at ozlabs.org
>> Subject: Re: pci_enable_device fails on MPC8541
>>
>> Do you need support for the VIA IDE controller?  I'm not sure if that

>> is causing you issues.
>>
>> Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a 
>> boot log.  I'm trying to figure out what is causing the resource 
>> conflict.  It appears that the memory resource is reasonable, but 
>> there could be possible conflict on the IO resource side.
>>
>> Also, if you can send logs of the same thing from the working 8540 
>> ADS
>>
>
>
>> that would be helpful.
>>
>> - kumar
>>
>> On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>> wrote:
>>
>>
>>
>>> Hi Kumar,
>>> I am using Linux 2.6.11, u-boot 1.1.2.
>>> I see failure in pci_enable_device with message:
>>> "PCI: Device :02:01.0 not available because of resource 
>>> collisions"
>>>
>>> I have attached three files:
>>> lspci_output.txt: out put of the "lspci -v"
>>> proc_pci.txt: output of the "cat /proc/pci"
>>> u-boot.txt: output of the "pci command at u-boot"
>>>
>>> Any help greatly appreciated,
>>> Bizhan
>>> -Original Message-
>>> From: Kumar Gala [mailto:kumar.gala at freescale.com]
>>> Sent: Monday, August 08, 2005 1:34 PM
>>> To: Bizhan Gholikhamseh (bgholikh)
>>> Cc: linuxppc-embedded at ozlabs.org
>>> Subject: Re: pci_enable_device fails on MPC8541
>>>
>>> Bizhan,
>>>
>>> A few questions:
>>>
>>> 1. what kernel version are you using on these boards:
>>> 2. can you do an lspci -v on the boards
>>>
>>> - kumar
>>>
>>> On Aug 

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Kumar,
Sorry it took a while. I have attached the 8540 PCI boot log and
/proc/pci. Also I found out the functions you mentioned are not used in
my environment.

Thanks,
Bizhan 

-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 10, 2005 9:06 AM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

It would be extremely helpful to get the output from the work MPC8540
for lspci and cat /proc/pci.

Also, I forget if 2.6.11 has CDS VIA support, but if it does you can try
disabling it by commenting out the calls to:
mpc85xx_cds_enable_via() & mpc85xx_cds_fixup_via() in arch/ppc/syslib/
ppc85xx_setup.c and see what happens.

- k

On Aug 10, 2005, at 10:58 AM, Bizhan Gholikhamseh \\((bgholikh\\))
wrote:

>  <> Kumar,
> We do not support or care about VIA IDE controller. I have enabled the

> DEBUG flag and attached the debug messages during boot. This is for 
> 8541E.
> Regards,
> Bizhan
>
> -Original Message-
> From: Kumar Gala [mailto:kumar.gala at freescale.com]
> Sent: Tuesday, August 09, 2005 4:11 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded at ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> Do you need support for the VIA IDE controller?  I'm not sure if that 
> is causing you issues.
>
> Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a 
> boot log.  I'm trying to figure out what is causing the resource 
> conflict.  It appears that the memory resource is reasonable, but 
> there could be possible conflict on the IO resource side.
>
> Also, if you can send logs of the same thing from the working 8540 ADS

> that would be helpful.
>
> - kumar
>
> On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))
> wrote:
>
>
>> Hi Kumar,
>> I am using Linux 2.6.11, u-boot 1.1.2.
>> I see failure in pci_enable_device with message:
>> "PCI: Device :02:01.0 not available because of resource
>> collisions"
>>
>> I have attached three files:
>> lspci_output.txt: out put of the "lspci -v"
>> proc_pci.txt: output of the "cat /proc/pci"
>> u-boot.txt: output of the "pci command at u-boot"
>>
>> Any help greatly appreciated,
>> Bizhan
>> -Original Message-
>> From: Kumar Gala [mailto:kumar.gala at freescale.com]
>> Sent: Monday, August 08, 2005 1:34 PM
>> To: Bizhan Gholikhamseh (bgholikh)
>> Cc: linuxppc-embedded at ozlabs.org
>> Subject: Re: pci_enable_device fails on MPC8541
>>
>> Bizhan,
>>
>> A few questions:
>>
>> 1. what kernel version are you using on these boards:
>> 2. can you do an lspci -v on the boards
>>
>> - kumar
>>
>> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>> wrote:
>>
>>
>>
>>> Hi All,
>>> I am using two evaluation board from freescale, 8540ADS and MPC8541.
>>> The same PCI driver is being compiled and loaded on both platforms.
>>> The same PCI driver (developed by me) for DSP board compiled and
>>> loaded on both platforms.
>>>
>>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>>> error:
>>> "PCI: Device :02:01.0 not available because of resource
>>> collisions"
>>> This messages is because of the execution of the generic PCI Linux
>>> command:
>>> "pci_enable_device(pdev)"
>>> The same API has no problem on 8540ADS.
>>>
>>>
>>>
>>>
>>>> From UBOOT I can see my device is on bus 3:
>>>>
>>>>
>>>>
>>> => pci 3
>>> Scanning PCI devices on bus 3
>>> BusDev FUNVendorIDDeviceIDDevice ClassSub-Class
>>> 

>>> -
>>>
>
>
>>> -
>>> --
>>> 
>>> 03.01.000x104c0xa106.
>>>
>>> Any idea why the insmod fails on one board and not on the other one?
>>>
>>> Many thanks in advance,
>>> Bizhan
>>>
>>> 
>>>
>>>
>>> 
>>> 
>>> 
>>>
>>
>>
>> 
>> 
>
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: pci_boot_8540.txt
Url: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050810/3932d0c5/attachment.txt
 
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: proc_pci_8540.txt
Url: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050810/3932d0c5/attachment-0001.txt
 

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

 <> Kumar,
We do not support or care about VIA IDE controller. I have enabled the
DEBUG flag and attached the debug messages during boot. This is for
8541E.
Regards,
Bizhan 

-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 09, 2005 4:11 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

Do you need support for the VIA IDE controller?  I'm not sure if that is
causing you issues.

Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a
boot log.  I'm trying to figure out what is causing the resource
conflict.  It appears that the memory resource is reasonable, but there
could be possible conflict on the IO resource side.

Also, if you can send logs of the same thing from the working 8540 ADS
that would be helpful.

- kumar

On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi Kumar,
> I am using Linux 2.6.11, u-boot 1.1.2.
> I see failure in pci_enable_device with message:
> "PCI: Device :02:01.0 not available because of resource 
> collisions"
>
> I have attached three files:
> lspci_output.txt: out put of the "lspci -v"
> proc_pci.txt: output of the "cat /proc/pci"
> u-boot.txt: output of the "pci command at u-boot"
>
> Any help greatly appreciated,
> Bizhan
> -Original Message-
> From: Kumar Gala [mailto:kumar.gala at freescale.com]
> Sent: Monday, August 08, 2005 1:34 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded at ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> Bizhan,
>
> A few questions:
>
> 1. what kernel version are you using on these boards:
> 2. can you do an lspci -v on the boards
>
> - kumar
>
> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
> wrote:
>
>
>> Hi All,
>> I am using two evaluation board from freescale, 8540ADS and MPC8541.
>> The same PCI driver is being compiled and loaded on both platforms.
>> The same PCI driver (developed by me) for DSP board compiled and
>> loaded on both platforms.
>>
>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>> error:
>> "PCI: Device :02:01.0 not available because of resource
>> collisions"
>> This messages is because of the execution of the generic PCI Linux
>> command:
>> "pci_enable_device(pdev)"
>> The same API has no problem on 8540ADS.
>>
>>
>>
>>> From UBOOT I can see my device is on bus 3:
>>>
>>>
>> => pci 3
>> Scanning PCI devices on bus 3
>> BusDev FUNVendorIDDeviceIDDevice ClassSub-Class
>> -

>> -
>> --
>> 
>> 03.01.000x104c0xa106.
>>
>> Any idea why the insmod fails on one board and not on the other one?
>>
>> Many thanks in advance,
>> Bizhan
>>
>> 
>>
>>
>> 
>> 
>> 
>
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: pci_boot.txt
Url: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050810/59c0c6a5/attachment.txt
 
-- next part --
A non-text attachment was scrubbed...
Name: pci_boot.pdf
Type: application/octet-stream
Size: 8370 bytes
Desc: pci_boot.pdf
Url : 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050810/59c0c6a5/attachment.obj
 

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Hi Kumar,
I am using Linux 2.6.11, u-boot 1.1.2.
I see failure in pci_enable_device with message: 
"PCI: Device :02:01.0 not available because of resource collisions" 

I have attached three files:
lspci_output.txt: out put of the "lspci -v"
proc_pci.txt: output of the "cat /proc/pci"
u-boot.txt: output of the "pci command at u-boot"

Any help greatly appreciated,
Bizhan
-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 08, 2005 1:34 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

Bizhan,

A few questions:

1. what kernel version are you using on these boards:
2. can you do an lspci -v on the boards

- kumar

On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi All,
> I am using two evaluation board from freescale, 8540ADS and MPC8541. 
> The same PCI driver is being compiled and loaded on both platforms. 
> The same PCI driver (developed by me) for DSP board compiled and 
> loaded on both platforms.
>
> When I type: "insmod C6415.ko" on 8541 board, I get the following
> error:
> "PCI: Device :02:01.0 not available because of resource 
> collisions"
> This messages is because of the execution of the generic PCI Linux
> command:
> "pci_enable_device(pdev)"
> The same API has no problem on 8540ADS.
>
>
>> From UBOOT I can see my device is on bus 3:
>>
> => pci 3
> Scanning PCI devices on bus 3
> BusDev FUNVendorIDDeviceIDDevice ClassSub-Class
> --
> --
> 
> 03.01.000x104c0xa106.
>
> Any idea why the insmod fails on one board and not on the other one?
>
> Many thanks in advance,
> Bizhan
>
> 
>
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: lspci_output.txt
Url: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050809/71fd11d7/attachment.txt
 
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: proc_pci.txt
Url: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050809/71fd11d7/attachment-0001.txt
 
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: u-boot.txt
Url: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050809/71fd11d7/attachment-0002.txt
 

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Kumar,
I am using Linux 2.6.11 version. Currently I do not have
the "lspci" patch integrated into my Linux image, however the /proc/pci
exists. The Freescale FAE is telling me to turn ON bit 3 on SW1 (i.e.
making Tsi320 to transparent bridge) on the mother board (i.e. arcadia
board). After doing that, the system hangs during boot right after the
decompressing the Linux image.
 
Regards,
Bizhan

-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 08, 2005 1:34 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

Bizhan,

A few questions:

1. what kernel version are you using on these boards:
2. can you do an lspci -v on the boards

- kumar

On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi All,
> I am using two evaluation board from freescale, 8540ADS and MPC8541. 
> The same PCI driver is being compiled and loaded on both platforms. 
> The same PCI driver (developed by me) for DSP board compiled and 
> loaded on both platforms.
>
> When I type: "insmod C6415.ko" on 8541 board, I get the following
> error:
> "PCI: Device :02:01.0 not available because of resource 
> collisions"
> This messages is because of the execution of the generic PCI Linux
> command:
> "pci_enable_device(pdev)"
> The same API has no problem on 8540ADS.
>
>
>> From UBOOT I can see my device is on bus 3:
>>
> => pci 3
> Scanning PCI devices on bus 3
> BusDev FUNVendorIDDeviceIDDevice ClassSub-Class
> --
> --
> 
> 03.01.000x104c0xa106.
>
> Any idea why the insmod fails on one board and not on the other one?
>
> Many thanks in advance,
> Bizhan
>
> 
>

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
I am using two evaluation board from freescale, 8540ADS and MPC8541. The
same PCI driver is being compiled and loaded on both platforms. The same
PCI driver (developed by me) for DSP board compiled and loaded on both
platforms. 
 
When I type: "insmod C6415.ko" on 8541 board, I get the following error:
"PCI: Device :02:01.0 not available because of resource collisions"
This messages is because of the execution of the generic PCI Linux
command:
"pci_enable_device(pdev)"
The same API has no problem on 8540ADS.
 
>From UBOOT I can see my device is on bus 3:
=> pci 3
Scanning PCI devices on bus 3
BusDev FUNVendorIDDeviceIDDevice ClassSub-Class


03.01.000x104c0xa106.
 
Any idea why the insmod fails on one board and not on the other one?
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050808/48e402df/attachment.htm
 

MPC8541E DMA transfer

[Bizhan Gholikhamseh (bgholikh)]

Hi Clemens,
Thanks for the code, the processor I am using is MPC8541E which I
believe have the same DMA engine as mpc8540. I will try it and will let
you know how it worked.

Thanks,
Bizhan 

-Original Message-
From: Clemens Koller [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 04, 2005 5:13 AM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: MPC8541E DMA transfer

Hello, Bizhan!
and all the other mpc85xx DMA fans.

I am working on the mpc85xx dma stuff (based on Jason's work) on the
lastest 2.6.x kernels. My cpu is a mpc8540.
That's all work in progress, so have a look at the code.

Attached you will find some of my test code (a separate kernal module)
which should compile fine for 2.6 now. Make a symlink ~/linux to the
latest 2.6 kernel or change the makefile. There is also the latest
immap_85xx.h (almost complete) included. Some old code is commented
out...

Not all code is enabled in the module yet, and the dma_test routine
copys data from physical memory you might not have in your hardware.
Please change that according to your setup.

Feedback is welcome!

Enjoy!

Clemens Koller
___
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19


Bizhan Gholikhamseh (bgholikh) wrote:
> Is there any support in Linux 2.6.X for using this controller, if so, 
> are you aware of any test driver I can take a look at?
> 
> Thanks,
> Bizhan
> 
> Many thanks in
> 
> -Original Message-
> From: Kumar Gala [mailto:kumar.gala at freescale.com]
> Sent: Wednesday, August 03, 2005 11:24 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded at ozlabs.org
> Subject: Re: MPC8541E DMA transfer
> 
> I dont see any reason you couldn't use the internal DMA engine on the 
> MPC8541E to do what you need.  You will just need to schedule the work

> every 10ms.
> 
> - kumar
> 
> On Aug 3, 2005, at 10:04 AM, Bizhan Gholikhamseh \(((bgholikh\)))
wrote:
> 
> 
>>Hi all,
>>I am developing a linux driver (2.6.10) for Freescale MPC8541E 
>>(customized board) to read and write 8 buffers (each buffer is 960 
>>bytes
>>long) every 10 ms to/from a custom made PCI card with on board DSP 
>>Chip.
>>The chip's internal and external memories are memory mapped to the CPU
> 
> 
>>address space.
>>For reason that is beyond the discussion here, the DMA request line on
> 
> 
>>the PCI card is not connected although the PCI card has DMA 
>>capabilities.
>>So what are my options?
>>Could I still do DMA transfer from the Host to the device?
>>
>>Many thanks in advance,
>>Bizhan
>>
>>
>>
> ___
> Linuxppc-embedded mailing list
> Linuxppc-embedded at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

MPC8541E DMA transfer

[Bizhan Gholikhamseh (bgholikh)]

Is there any support in Linux 2.6.X for using this controller, if so,
are you aware of any test driver I can take a look at?

Thanks,
Bizhan

Many thanks in  

-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 03, 2005 11:24 AM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: MPC8541E DMA transfer

I dont see any reason you couldn't use the internal DMA engine on the
MPC8541E to do what you need.  You will just need to schedule the work
every 10ms.

- kumar

On Aug 3, 2005, at 10:04 AM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

>
> Hi all,
> I am developing a linux driver (2.6.10) for Freescale MPC8541E 
> (customized board) to read and write 8 buffers (each buffer is 960 
> bytes
> long) every 10 ms to/from a custom made PCI card with on board DSP 
> Chip.
> The chip's internal and external memories are memory mapped to the CPU

> address space.
> For reason that is beyond the discussion here, the DMA request line on

> the PCI card is not connected although the PCI card has DMA 
> capabilities.
> So what are my options?
> Could I still do DMA transfer from the Host to the device?
>
> Many thanks in advance,
> Bizhan
>
> 
>

MPC8541E DMA transfer

[Bizhan Gholikhamseh (bgholikh)]

 
Hi all,
I am developing a linux driver (2.6.10) for Freescale MPC8541E
(customized board) to read and write 8 buffers (each buffer is 960 bytes
long) every 10 ms to/from a custom made PCI card with on board DSP Chip.
The chip's internal and external memories are memory mapped to the CPU
address space. 
For reason that is beyond the discussion here, the DMA request line on
the PCI card is not connected although the PCI card has DMA
capabilities. 
So what are my options? 
Could I still do DMA transfer from the Host to the device?
 
Many thanks in advance,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050803/369878ae/attachment.htm
 

remap_page_range not resolved

[Bizhan Gholikhamseh (bgholikh)]

Hi All,
I am porting a Linux PCI driver originally developed for X86 platform to
MPC8540ADS reference  board by Freescale running 2.6 Linux. 
The "insmod" command fails when I am trying to load the module. The
failure is because the reference to a function name can not be resolved:
"remap_page_range"
Could someone help me please to find out what I am missing from my
kernel image?
 
Regards,
Bizhan
-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050707/84d20574/attachment.htm