How to Enable MTD

2009-02-02 Thread mike zheng
Hello,

I have one AMD29LV640 NOR chip on my system. How can I enable it in
Linux as MTD device? Right now, I can not operate on /dev/mtd in
Linux:

# od -x /dev/mtd
od: /dev/mtd: No such file or directory
od: /dev/mtd: Bad file descriptor
# od -x /dev/mtd0
od: Dec 31 16:02:17 kernel: MTD_open
/dev/mtd0: No such device

I think something wrong with my config flags(listed as followings),
this is a CFI supported device. The physical address starts at
0xbf80

Thanks for your help,

Mike



# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
CONFIG_MTD_LFS_SUPPORT=y



#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
CONFIG_MTD_CFI_NOSWAP=y
# CONFIG_MTD_CFI_BE_BYTE_SWAP is not set
# CONFIG_MTD_CFI_LE_BYTE_SWAP is not set
CONFIG_MTD_CFI_GEOMETRY=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
# CONFIG_MTD_CFI_I2 is not set
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_OTP is not set
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set


#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=0xBF80
CONFIG_MTD_PHYSMAP_LEN=0x0
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_VERIFY_WRITE=y
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_BCM1103=y
CONFIG_MTD_NAND_IDS=y
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_NAND_NANDSIM is not set
# CONFIG_MTD_NAND_PLATFORM is not set
# CONFIG_MTD_ONENAND is not set
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


UC1611 LCD controller driver

2008-12-15 Thread mike zheng
Hi,

Does anyone has the UC1611 LCD controller driver of Kernel2.6?

Thanks for your help,

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


JVM on e500 core

2008-11-28 Thread mike zheng
Hi All,

I am using MPC8568 with e500 core. The cross-compiler I am using from
Freescale - GCC 3_3-e500, glibc 2.3.2 and binutils 2.15.

Any one know if Java Virtual Machine is supported on the e500 core
processor? Has e500 support been added to GCJ?

Thanks for your help,
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: QE in MPC8360MDS

2008-11-01 Thread mike zheng
Anton. Thanks for the info you provide.

The code I have actually works fine on MPC8568. It does NOT work on MPC8360.

The value of following register are correct based on the manual. And
the RxBD flag changed as well. I shall see the bit of UCCE changes,
Right? Do I miss provision anything? Is there any other register shall
I check in order to get the interrupt bit in UCCE?

gumr  : addr - 0xfdf02000, val - 0x400c
ucce  : addr - 0xfdf02010, val - 0x
uccm  : addr - 0xfdf02014, val - 0x7f010001

On Fri, Oct 31, 2008 at 10:01 AM, Anton Vorontsov
<[EMAIL PROTECTED]> wrote:
> On Fri, Oct 31, 2008 at 09:47:18AM -0400, mike zheng wrote:
>> Hi All,
>>
>> Anyone know the difference of QE between MPC8360 and MPC8568?
>>
>> I am using the QE code working for MPC8568 on a MPC8360MDS board.
>> However there is no interrupt generated by UCC0. I set the QE working
>> under loopback mode. The flag of TxBD got changed, but the UCCE
>> remains the same value. Here is the logs and register value.
>
> I recalling these differences:
>
> QEIC to MPIC vs. IPIC cascading (may be the cause of interrupts
> issues).
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=cccd21027c17c27ad275093c22475354b4495814
>
> QE ParIO layout (you may have pins misconfigured):
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=321872dcc07f83f9b60af1be41c6bafbaddf9bf6
>
> --
> Anton Vorontsov
> email: [EMAIL PROTECTED]
> irc://irc.freenode.net/bd2
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


QE in MPC8360MDS

2008-10-31 Thread mike zheng
Hi All,

Anyone know the difference of QE between MPC8360 and MPC8568?

I am using the QE code working for MPC8568 on a MPC8360MDS board.
However there is no interrupt generated by UCC0. I set the QE working
under loopback mode. The flag of TxBD got changed, but the UCCE
remains the same value. Here is the logs and register value.

Thanks,

Mike


===>ucc_geth_start_xmit: Set status queue=0
TxBD[cf48a488].status=982a ucce=10001 uccm=7f010001

ucc_geth_start_xmit: Different value for TxBD after Xmit
TxBD[cf48a488].status=182a






ase address: 0xfdf02000
gumr  : addr - 0xfdf02000, val - 0x400c
upsmr : addr - 0xfdf02004, val - 0x2000
utodr : addr - 0xfdf02008, val - 0x
udsr  : addr - 0xfdf0200c, val - 0x7e7e
ucce  : addr - 0xfdf02010, val - 0x
uccm  : addr - 0xfdf02014, val - 0x7f010001
uccs  : addr - 0xfdf02018, val - 0x00
urfb  : addr - 0xfdf02020, val - 0x3488
urfs  : addr - 0xfdf02024, val - 0x1000
urfet : addr - 0xfdf02028, val - 0x0800
urfset: addr - 0xfdf0202a, val - 0x0c00
utfb  : addr - 0xfdf0202c, val - 0x1480
utfs  : addr - 0xfdf02030, val - 0x2000
utfet : addr - 0xfdf02034, val - 0x1000
utftt : addr - 0xfdf02038, val - 0x0400
utpt  : addr - 0xfdf0203c, val - 0x0100
urtry : addr - 0xfdf02040, val - 0x
guemr : addr - 0xfdf02090, val - 0x13
UCC0 Geth registers:
Base address: 0xfdf02000
maccfg1: addr - 0xfdf02100, val - 0x0035
maccfg2: addr - 0xfdf02104, val - 0x0020
ipgifg : addr - 0xfdf02108, val - 0x40605060
hafdup : addr - 0xfdf0210c, val - 0x00a1f037
ifctl  : addr - 0xfdf02138, val - 0x0100
ifstat : addr - 0xfdf0213c, val - 0x
macstnaddr1: addr - 0xfdf02140, val - 0x
macstnaddr2: addr - 0xfdf02144, val - 0x
uempr  : addr - 0xfdf02150, val - 0x
utbipar: addr - 0xfdf02154, val - 0x0010
uescr  : addr - 0xfdf02158, val - 0x0804
tx64   : addr - 0xfdf02180, val - 0x
tx127  : addr - 0xfdf02184, val - 0x
tx255  : addr - 0xfdf02188, val - 0x
rx64   : addr - 0xfdf0218c, val - 0x
rx127  : addr - 0xfdf02190, val - 0x
rx255  : addr - 0xfdf02194, val - 0x
txok   : addr - 0xfdf02198, val - 0x
txcf   : addr - 0xfdf0219c, val - 0x
tmca   : addr - 0xfdf021a0, val - 0x
tbca   : addr - 0xfdf021a4, val - 0x
rxfok  : addr - 0xfdf021a8, val - 0x
rxbok  : addr - 0xfdf021ac, val - 0x
rbyt   : addr - 0xfdf021b0, val - 0x
rmca   : addr - 0xfdf021b4, val - 0x
rbca   : addr - 0xfdf021b8, val - 0x
scar   : addr - 0xfdf021bc, val - 0x
scam   : addr - 0xfdf021c0, val - 0x
Thread data TXs:
Base address: 0xfdf14600
Thread data TX[0]:
Base address: 0xfdf14600
0xfdf14600: 3800 3880002a 1800 1880002a
0xfdf14610: 1800 1880002a 1800 1880002a
0xfdf14620: 1800 1880002a 1800 1880002a
0xfdf14630: 1800 1880002a 1800 1880002a
0xfdf14640: 800017c8 3a2a 0f48a4f8 0c094242
0xfdf14650: 80001678 1a2a 0f48a4c8 0c0b4e22
0xfdf14660: 800016e8 1a2a
Thread data TX[1]:
Base address: 0xfdf14668
0xfdf14668: 0f48a4d8 0c0b4f22 80001758 1a2a
0xfdf14678: 0f48a4e8 0c094142 80001790 1a2a
0xfdf14688: 0f48a4f0 0c0941c2 80001640 1a2a
0xfdf14698: 0f48a4c0 0c0b4da2 800016b0 1a2a
0xfdf146a8: 0f48a4d0 0c0b4ea2 80001720 1a2a
0xfdf146b8: 0f48a4e0 0c0940c2 0d004dc0 
0xfdf146c8: 14004e40 0001
Thread data RX:
Base address: 0xfdf14a00
Thread data RX[0]:
Base address: 0xfdf14a00
0xfdf14a00:    
0xfdf14a10:    
0xfdf14a20:  
Thread data RX[1]:
Base address: 0xfdf14a28
0xfdf14a28:    
0xfdf14a38:   4c00 0005
0xfdf14a48: 4d00 000c
TX global param:
Base address: 0xfdf14500
temoder  : addr - 0xfdf14500, val - 0xc000
sqptr: addr - 0xfdf14538, val - 0x4780
schedulerbasepointer: addr - 0xfdf1453c, val - 0x
txrmonbaseptr: addr - 0xfdf14540, val - 0x
tstate   : addr - 0xfdf14544, val - 0x3000
iphoffset[0] : addr - 0xfdf14548, val - 0x00
iphoffset[1] : addr - 0xfdf14549, val - 0x00
iphoffset[2] : addr - 0xfdf1454a, val - 0x00
iphoffset[3] : addr - 0xfdf1454b, val - 0x00
iphoffset[4] : addr - 0xfdf1454c, val - 0x00
iphoffset[5] : addr - 0xfdf1454d, val - 0x00
iphoffset[6] : addr - 0xfdf1454e, val - 0x00
iphoffset[7] : addr - 0xfdf1454f, val - 0x00
vtagtable[0] : addr - 0xfdf14550, val - 0x
vtagtable[1] : addr - 0xfdf14554, val - 0x
vtagtable[2] : addr - 0xfdf14558, val - 0x
vtagtable[3] : addr - 0xfdf1455c, val - 0x
vtagtable[4] : addr - 0xfdf14560, val - 0x
vtagtable[5] : addr - 0xfdf14564, val - 0x
vtagtable[6] : addr - 0xfdf14568, val - 0x
vtagtable[7] : addr - 0xfdf1456c, val - 0x
tqptr: addr - 0xfdf14570, val - 0x460

Re: Kernel Oops when run ifconfig on MPC8360MDS board

2008-10-21 Thread mike zheng
Enable the debug flag on ucc_geth.c: there is the dmesg:

ucc_geth_open: IN
ucc_geth_startup: IN
Machine check in kernel mode.
Caused by (from SRR1=49030): Transfer error ack signal
Oops: machine check, sig: 7
NIP: C0126910 XER: 2000 LR: C01268D0 SP: CFD0DD80 REGS: cfd0dcd0
TRAP: 0200Not tainted
MSR: 00049030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = cfd0c000[398] 'ifconfig' Last syscall: 54
last math cfd0c000 last altivec 
GPR00:  CFD0DD80 CFD0C000  1032 CC10E000 C0247264 C04D1F74
GPR08: BA2E8BA3 D110 C01EE55C  4808 100235F8  
GPR16:   1002 1002 9032 CFD0DE78  
GPR24: 8914 C000 C01D CFD0DDB8 D100 C0586D20 C0269C20 
Call backtrace:
C0126890 C00D59D0 C00D761C C012F400 C0130DD4 C01746B4 C017712C
C0127770 C004D8B0 C0005ABC  10001214 100023C4 0FEC4E00



On Tue, Oct 21, 2008 at 12:26 AM, mike zheng <[EMAIL PROTECTED]> wrote:
> Oh, I forgot to metion just now. The linux is based on a custom built
> kernel 2.4.22, not from Freescale.
>
> On 10/20/08, mike zheng <[EMAIL PROTECTED]> wrote:
>> On 10/20/08, Kim Phillips <[EMAIL PROTECTED]> wrote:
>> > On Mon, 20 Oct 2008 15:00:33 -0700
>> > "mike zheng" <[EMAIL PROTECTED]> wrote:
>> >
>> > > I have following kernel Oops when I run ifconfig to setup the UEC0 of
>> > > MPC8360MDS board. There is no hardware problem, the UEC0 runs well
>> > > under Uboot.
>> >
>> > does this occur on vanilla u-boot and kernel versions?  if so, which
>> > ones, and on what board revision?
>> >
>> The kernel Oops happened under Linux when I try to use "ifconfig" to
>> setup the eth0. Under Uboot, the UEC0 works fine. I am able to do
>> ping, tftp via the ethernet port.
>>
>>
>> > > Call backtrace:
>> > > C0126890 C00D59D0 C00D761C C012F400 C0130DD4 C01746B4 C017712C
>> > > C0127770 C004D8B0 C0005ABC  10001214 100023C4 0FEC4E00
>> > > 
>> >
>> > might want to turn on verbose debugging while you're at it.
>>
>> Which flag shall I turned on? I am not formaliar to the network driver. 
>> Thanks!
>> >
>> > Kim
>> >
>>
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: Kernel Oops when run ifconfig on MPC8360MDS board

2008-10-20 Thread mike zheng
Oh, I forgot to metion just now. The linux is based on a custom built
kernel 2.4.22, not from Freescale.

On 10/20/08, mike zheng <[EMAIL PROTECTED]> wrote:
> On 10/20/08, Kim Phillips <[EMAIL PROTECTED]> wrote:
> > On Mon, 20 Oct 2008 15:00:33 -0700
> > "mike zheng" <[EMAIL PROTECTED]> wrote:
> >
> > > I have following kernel Oops when I run ifconfig to setup the UEC0 of
> > > MPC8360MDS board. There is no hardware problem, the UEC0 runs well
> > > under Uboot.
> >
> > does this occur on vanilla u-boot and kernel versions?  if so, which
> > ones, and on what board revision?
> >
> The kernel Oops happened under Linux when I try to use "ifconfig" to
> setup the eth0. Under Uboot, the UEC0 works fine. I am able to do
> ping, tftp via the ethernet port.
>
>
> > > Call backtrace:
> > > C0126890 C00D59D0 C00D761C C012F400 C0130DD4 C01746B4 C017712C
> > > C0127770 C004D8B0 C0005ABC  10001214 100023C4 0FEC4E00
> > > 
> >
> > might want to turn on verbose debugging while you're at it.
>
> Which flag shall I turned on? I am not formaliar to the network driver. 
> Thanks!
> >
> > Kim
> >
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: Kernel Oops when run ifconfig on MPC8360MDS board

2008-10-20 Thread mike zheng
On 10/20/08, Kim Phillips <[EMAIL PROTECTED]> wrote:
> On Mon, 20 Oct 2008 15:00:33 -0700
> "mike zheng" <[EMAIL PROTECTED]> wrote:
>
> > I have following kernel Oops when I run ifconfig to setup the UEC0 of
> > MPC8360MDS board. There is no hardware problem, the UEC0 runs well
> > under Uboot.
>
> does this occur on vanilla u-boot and kernel versions?  if so, which
> ones, and on what board revision?
>
The kernel Oops happened under Linux when I try to use "ifconfig" to
setup the eth0. Under Uboot, the UEC0 works fine. I am able to do
ping, tftp via the ethernet port.


> > Call backtrace:
> > C0126890 C00D59D0 C00D761C C012F400 C0130DD4 C01746B4 C017712C
> > C0127770 C004D8B0 C0005ABC  10001214 100023C4 0FEC4E00
> > 
>
> might want to turn on verbose debugging while you're at it.

Which flag shall I turned on? I am not formaliar to the network driver. Thanks!
>
> Kim
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Kernel Oops when run ifconfig on MPC8360MDS board

2008-10-20 Thread mike zheng
Hi All,

I have following kernel Oops when I run ifconfig to setup the UEC0 of
MPC8360MDS board. There is no hardware problem, the UEC0 runs well
under Uboot.

Any idea on this issue?

Thanks,

Mike


[EMAIL PROTECTED] root]# ifconfig eth0 47.135.148.158
Oops: machine check, sig: 7
NIP: C0126910 XER: 2000 LR: C01268D0 SP: CC10DD80 REGS: cc10dcd0
TRAP: 0200Not tainted
MSR: 00049030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = cc10c000[349] 'ifconfig' Last syscall: 54
last math cc10c000 last altivec 
GPR00:  CC10DD80 CC10C000  1032 CC12D000 C0247264 C04D24C8
GPR08: BA2E8BA3 D110 C01EE55C  4808 100235F8  
GPR16:   1002 1002 9032 CC10DE78  
GPR24: 8914 C000 C01D CC10DDB8 D100 C0586E60 C0269C20 
Call backtrace:
C0126890 C00D59D0 C00D761C C012F400 C0130DD4 C01746B4 C017712C
C0127770 C004D8B0 C0005ABC  10001214 100023C4 0FEC4E00

Bus error
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


BSP on Kernel2.4 needed for MPC8360E-MDS

2008-10-06 Thread mike zheng
Hi All,

Is there any BSP on kernel 2.4 for MPC8360EMDS board?

Thanks,

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


BDI2000 configuration file for MPC8323e-RDB board

2008-09-09 Thread mike zheng
Hello,

Anyone has the BDI2000 board configuration file for Freescale's
MPC8323e-RDB board?

Thanks for your help,

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


MPC8323RDB BSP on Kernel2.4

2008-07-28 Thread mike zheng
Hi All,

Is the any MPC8323RDB BSP on Kernel 2.4? I have the BSP on Kernel 2.6
provided by Freescale. Unfortunate we are using Kernel2.4. Is there
any exist BSP of this board on Kernel2.4? Or a BSP of similar board on
Kernel2.4?

Thanks in advance,

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


Freescale SEC driver with cryptoloop on MPC8567e

2008-07-08 Thread mike zheng
Hello,

Any one know how can I integrate the Freescale's SEC driver with
cryptoloop in Kernel2.4 on MPC8567e? Or which version of kernel shall
I take if it is already there?

Thanks for your help,

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


MCC problem of MPC8568

2008-04-15 Thread mike zheng
Hi,

Currently, I have problem of the UBoot MCC driver. I setup the
internal loopback on MPC8568. And here is the data of each channel:

   Channel #Tx DataRx Data
  0 0x010x9D
  1 0x020xE1
  2 0x030x9E
  3 0x040xF1
  4 0x050x83
   ...

Any idea on this issue? Or where can I find a working MCC Uboot driver
of MPC8568?

Thanks for your help,

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


mpc8568mds bootup problem

2008-03-19 Thread mike zheng
Hi All,

My mpc8568mds board does not bootup. I am using Freescale's BSP on
kernel2.6.23. The following is the log from serial port. Any idea?
What is the next module to be initialized after the cfq? Where can I
comment it out for debugging purpose?

Thanks for your help,

Mike


=> bootm 100 200 40
bootm 100 200 40
## Booting image at 0100 ...
   Image Name:   Linux-2.6.23
   Created:  2008-03-18  20:48:11 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:1283304 Bytes =  1.2 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 0200 ...
   Image Name:   uboot ext2 ramdisk rootfs
   Created:  2007-06-26   4:25:24 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:3719970 Bytes =  3.5 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Booting using flat device tree at 0x40
   Loading Ramdisk to 1f1c2000, end 1f54e322 ... OK
Using MPC85xx MDS machine description
Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
Linux version 2.6.23 () (gcc version 4.0.2 20060628 (Wasabi)) #9 Tue
Mar 18 16:48:04 EDT 2008
Found initrd at 0xdf1c2000:0xdf54e322
-> find_legacy_serial_port()
stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED]
legacy_serial_console = 1
default console speed = 115340
<- find_legacy_serial_port()
console [udbg0] enabled
setup_arch: bootmem
mpc85xx_mds_setup_arch()
Found FSL PCI host bridge at 0xe0008000.Firmware bus number: 0->0
pio-handle not available
pio-handle not available
arch: exit
Zone PFN ranges:
  DMA 0 ->   131072
  Normal 131072 ->   131072
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0:0 ->   131072
Built 1 zonelists in Zone order.  Total pages: 130048
Kernel command line: ramdisk_size=42000 root=/dev/ram rw console=ttyS1,115200
mpic: Setting up MPIC " OpenPIC  " version 1.2 at e004, max 1 CPUs
mpic: ISU size: 80, shift: 7, mask: 7f
mpic: Initializing for 80 sources
QEIC (64 IRQ sources) at fd6ed080
PID hash table entries: 2048 (order: 11, 8192 bytes)
-> check_legacy_serial_console()
console was specified !
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512896k/524288k available (2556k kernel code, 10952k reserved,
108k data, 102k bss, 144k init)
Mount-cache hash table entries: 512
NET: Registered protocol family 16

rstcr compatible register does not exist!
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 0 of device :00:02.0
PCI: Cannot allocate resource region 0 of device :00:02.1
PCI: Cannot allocate resource region 0 of device :00:02.2
PCI: Cannot allocate resource region 0 of device :00:03.0
PCI: Cannot allocate resource region 0 of device :00:03.1
PCI: Cannot allocate resource region 0 of device :00:03.2
PCI: Cannot allocate resource region 0 of device :00:04.0
...

PCI: Cannot allocate resource region 0 of device :00:1f.0
PCI: Cannot allocate resource region 0 of device :00:1f.1
PCI: Cannot allocate resource region 0 of device :00:1f.2
Generic PHY: Registered new driver
SCSI subsystem initialized
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 3632k freed
Fixing serial ports interrupts and IO ports ...
fixup_port_irq(0)
fixup_port_mmio(0)
fixup_port_irq(1)
fixup_port_mmio(1)
Registering platform serial ports
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Early Debug message on MPC8568MDS

2008-03-12 Thread mike zheng
Hello,

How can I enable the early debug message on 2.6.23 kernel for
MPC8568MDS board? What is the first line shall be displayed on the
serial port? The board uses the first port of UART, where does it
defined?

Thanks for your help,

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


Kernel oops in MPC8568MDS BSP

2008-01-31 Thread mike zheng
Hello,

I am using MPC8568MDS BSP on my board, which has same memory map with
MPC8568MDS board. However I have kernel Ooop at
free_bootmem_with_active_regions() within do_init_bootmem(). Any idea
on this issue?


Thanks,


Mike

bootm 0x100 0x200 0x40
## Booting image at 0100 ...
   Image Name:   Linux-2.6.23
   Created:  2008-01-31  18:52:45 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:1370100 Bytes =  1.3 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 0200 ...
   Image Name:   uboot ext2 ramdisk rootfs
   Created:  2007-11-26   2:28:38 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:4001113 Bytes =  3.8 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Booting using flat device tree at 0x40
   Loading Ramdisk to 1fb6e000, end 1ff3ed59 ... OK
Using MPC85xx MDS machine description
Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
Linux version 2.6.23 () (gcc version 4.1.2) #3 Thu Jan 31 13:52:40 EST 2008
Found initrd at 0xdfb6e000:0xdff3ed59
console [udbg0] enabled

Kernel BUG at c0296a68 [verbose debug info unavailable]
Oops: Exception in kernel mode, sig: 5 [#1]
MPC85xx MDS
Modules linked in:
NIP: c0296a68 LR: c0298100 CTR: 1c00
REGS: c02c7ec0 TRAP: 0700   Not tainted  (2.6.23)
MSR: 00021000   CR: 24002028  XER: 2000
TASK = c02ac5e0[0] 'swapper' THREAD: c02c6000
GPR00: 0001 c02c7f70 c02ac5e0 c02daa2c 0001e401 2000 
0356
GPR08: 0001  25e9 25e9 24002022 6000 1ffbd400
007fff00
GPR16:  1ffb9824 0004 1fffc830 0080  007ffeb0
003d0d59
GPR24:  1ff3fe50 1140 c02b  c02a5320 0002

Call Trace:
[c02c7f90] [c0291144]
[c02c7fb0] [c028f250]
[c02c7fc0] [c028681c]
[c02c7ff0] [c388]
Instruction dump:
5489e8fa 7d30 7d295a14 7d604828 7d6a0078 7d40492d 40a2fff4
7c095839
38840001 4182000c 4200ffd0 4e800020 <0fe0> 4800 3d20c02b
7c601b78
Kernel panic - not syncing: Attempted to kill the idle task!
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Quick Engine Support on Kernel 2.4

2008-01-11 Thread mike zheng
Hi All,

Is there any BSP on Linux Kernel 2.4 support Quick Engine of MPC8568?
If not, which BSP shall I start the porting? The BSP(on Kernel2.6) of
MPC8568MDS from Freescale supports CPM2, but not QE. What the
difference between CPM2 and QE?

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


Re: printk() does not work on UART1

2008-01-09 Thread mike zheng
I found the problem. The CONFIG_CMDLINE was overwritten. Right now, it
is working.

Thanks for all the help,

Mike


On 1/9/08, Haiying Wang <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-01-09 at 00:06 -0500, mike zheng wrote:
> >  Hi All,
> >
> >  I have one mpc8568 board using UART1 as the serial port.  The OS is
> >  Linux Kernel2.4.  If I use the polling mode driver of
> >  gen550_progress(), it works fine. However the printk() does not work
> >  after the console_init(). Anyone know what shall I change in the
> >  kernel to use UART1 as serial console? I assume the default is UART0,
> >  but I don't know where the value is set. I changed the CONFIG_CMDLINE
> >  to ttyS1, it does NOT work.
>
> Make sure you've configured PC0/1/2/3 for UART1 SOUT/RTS/CTS/SIN in
> u-boot.
>
> Haiying
>
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: printk() does not work on UART1

2008-01-08 Thread mike zheng
 Hi All,

 I have one mpc8568 board using UART1 as the serial port.  The OS is
 Linux Kernel2.4.  If I use the polling mode driver of
 gen550_progress(), it works fine. However the printk() does not work
 after the console_init(). Anyone know what shall I change in the
 kernel to use UART1 as serial console? I assume the default is UART0,
 but I don't know where the value is set. I changed the CONFIG_CMDLINE
 to ttyS1, it does NOT work.

 Thanks for your help,

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


printk() does not work on UART1

2008-01-08 Thread mike zheng
Hi All,

I have one mpc8568 board using UART1 as the serial port.  The OS is
Linux Kernel2.4.  If I use the polling mode driver of
gen550_progress(), it works fine. However the printk() does not work
after the console_init(). Anyone know what shall I change in the
kernel to use UART1 as serial console? I assume the default is UART0,
but I don't know where the value is set. I changed the CONFIG_CMDLINE
to ttyS1, it does NOT work.

Thanks for your help,

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


PCI configuration registers(BARs)

2007-11-30 Thread mike zheng
Hi All,

I set PCI configuration registers(BARs) of a PCI adapter as following in Uboot:


  base address 0 =  0xf401
  base address 1 =  0xf441
  base address 2 =  0xf481
  base address 3 =  0xa000
  base address 4 =  0xa002
  base address 5 =  0x

However when I start Linux2.4 kernel, the same adapter's PCI
configuration registers have following values:
BaseAddr[0]=0x3c0
BaseAddr[1]=0x3b0
BaseAddr[2]=0x300
After ioremap BaseAddr[3]=0xa1002000
BaseAddr[3]=0xa1002000
After ioremap BaseAddr[4]=0xa1004000
BaseAddr[4]=0xa1004000
BaseAddr[5]=0x0

This is a working system on MPC8548, everything including PCI adapter
works fine. My question is why the values are different in Uboot and
Linux? The value under Uboot is reasonable, since the PCI outbound
window is set up as 0xA000 and 0XF400. In addition, the value
seems falling into the outbound window after the ioremap() is called
on BAR3 and BAR4. The ioremap() will failed if I try to convert BAR0,
BAR1, BAR2.

Thanks in advance,

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


Marvell 88se6121 in Kernel2.4

2007-10-10 Thread mike zheng
Hello,

Anyone has the source code of kernel2.4 device driver for Marvel 88se6121?

Thanks in advance,

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

8555CDS BSP on 8548CDS board

2007-08-24 Thread mike zheng
 Hi,

I was told Freescale's 8555CDS board is very similar to 8548CDS board. I
just wonder what exactly the differences are. can I just put the 8555CDS BSP
onto the 8548CDS board?

Thanks  in advance,

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

Re: System crash on boot_e500.S

2007-08-15 Thread mike zheng
On 8/15/07, Scott Wood <[EMAIL PROTECTED]> wrote:
>
> mike zheng wrote:
> > Unfortunately, all the applications are running on 2.4 kernel. I can not
> > just throw the 2.4 kernel.
>
> And in what way does 2.6 break these applications?


All the device drivers are based on 2.4 kernel. We plan to upgrade to 2.6 in
the middle of next year.

> I took the some core specific code from
> > ppc.bkbits.net, such as head_e500.S and mpc85xx_cds_common.c. I assume
> the
> > image should work on the 8548 CDS board, or at least for the bootup. I
> shall
> > able to have the serial port working in platform_init(). However , the
> > code stops in the head_e500.S. This does not make any sense. Please
> correct
> > me if I am wrong.
>
> Of course it makes sense -- you can't just go around ripping random
> files from a codebase, sticking them in a version from several years
> earlier, and expecting it to "just work".


All those files are e500 core specific. When we use bootm from Uboot to
start the kernel, head_e500.S is first file being called, and then the
mpc85xx_cds_common.c. I also merged some BOOKE related include files into
our source tree as well.

Our 2.4 kernel version is different from ppc.bkbits.net. I did not expect it
"just work". However the serial console should come out when platform_init()
called. Everything before that is the same for any processor with e500 core.




> Any suggest or comment is welcome, I am struggling with this issue for
> > almost one week.. :-(
>
> How long would you have struggled with getting your applications running
> on a more recent kernel instead?


Don't know, maybe 16 weeks. That is out of my control. I only deal with the
kernel.:-)

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

Re: System crash on boot_e500.S

2007-08-15 Thread mike zheng
Unfortunately, all the applications are running on 2.4 kernel. I can not
just throw the 2.4 kernel. I took the some core specific code from
ppc.bkbits.net, such as head_e500.S and mpc85xx_cds_common.c. I assume the
image should work on the 8548 CDS board, or at least for the bootup. I shall
able to have the serial port working in platform_init(). However , the
code stops in the head_e500.S. This does not make any sense. Please correct
me if I am wrong.

BTW, I am using the tool-chain gcc-3_4-e5000glibc-2.3.4-dp, which is from
Freescale for the 8548 CDS BSP of 2.6 kernel.

Any suggest or comment is welcome, I am struggling with this issue for
almost one week.. :-(


On 8/15/07, Becky Bruce <[EMAIL PROTECTED]> wrote:
>
>
> On Aug 15, 2007, at 11:28 AM, Kumar Gala wrote:
>
> >
> > On Aug 15, 2007, at 11:02 AM, Scott Wood wrote:
> >
> >> On Wed, Aug 15, 2007 at 09:57:59AM -0400, mike zheng wrote:
> >>> Did you done similar work before? Current 2.6 code need many other
> >>> files,  I
> >>> have following errors when I try to use the head_e500.S from 2.6
> >>> code:
> >>>
> >>>
> >>> /kernel->   powerpc-linux-gnuspe-gcc -m32 -Wp,-MD,arch/ppc/
> >>> kernel/.entry.o.d
> >>> -nostdinc -isystem /opt/mtwk/usr/local/gcc-3_4-
> >>> e500-glibc-2.3.4-dp/powerpc-linux-gnuspe/lib/gcc/powerpc-linux-
> >>> gnuspe/3.4.3/include
> >>> -D__KERNEL__ -Iinclude  -Iarch/ppc -D__ASSEMBLY__ -Iarch/ppc -Wa,-
> >>> me500 -c
> >>> -o arch/ppc/kernel/entry.o arch/ppc/kernel/entry.S
> >>> arch/ppc/kernel/entry.S: Assembler messages:
> >>>
> >>> entry.S:819: Error: unsupported relocation against CSRR0
> >>> entry.S:820: Error: unsupported relocation against CSRR1
> >>> entry.S:888: Error: unsupported relocation against MCSRR0
> >>> entry.S:889: Error: unsupported relocation against MCSRR1
> >>> entry.S:909: Error: unsupported relocation against CSRR0
> >>> entry.S:911: Error: unsupported relocation against CSRR1
> >>
> >> Try arch/powerpc; arch/ppc is deprecated.
> >
> > He's trying a 2.4 kernel.
>
> I think maybe he misunderstood Jon's advive to "use 2.6" as using
> just some files from 2.6.  I think the above is probably some strange
> mix of 2.4 and 2.6, which, of course, won't work.
>
> Jon's real advice was "use 2.6", as in, the whole thing.
>
> -B
> ___
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Re: System crash on boot_e500.S

2007-08-15 Thread mike zheng
Did you done similar work before? Current 2.6 code need many other files,  I
have following errors when I try to use the head_e500.S from 2.6 code:


/kernel->   powerpc-linux-gnuspe-gcc -m32 -Wp,-MD,arch/ppc/kernel/.entry.o.d
-nostdinc -isystem /opt/mtwk/usr/local/gcc-3_4-
e500-glibc-2.3.4-dp/powerpc-linux-gnuspe/lib/gcc/powerpc-linux-gnuspe/3.4.3/include
-D__KERNEL__ -Iinclude  -Iarch/ppc -D__ASSEMBLY__ -Iarch/ppc -Wa,-me500 -c
-o arch/ppc/kernel/entry.o arch/ppc/kernel/entry.S
arch/ppc/kernel/entry.S: Assembler messages:

entry.S:819: Error: unsupported relocation against CSRR0
entry.S:820: Error: unsupported relocation against CSRR1
entry.S:888: Error: unsupported relocation against MCSRR0
entry.S:889: Error: unsupported relocation against MCSRR1
entry.S:909: Error: unsupported relocation against CSRR0
entry.S:911: Error: unsupported relocation against CSRR1



entry.S

819   mtspr CSRR0, r11
820   mtspr CSRR1, r12





On 8/14/07, Jon Loeliger <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2007-08-14 at 15:14, mike zheng wrote:
> > Hi All,
> >
> > I am trying to bring up MPC8548 CDS board on 2.4 kernel. I have
> > problem in the head
>
> Ow, it hurts when I do this!
>
> > _e500.S. The "mtspr SRR0, r7; mtspr SRR1 r6" does not work for me. The
> > content of R7 and R6 are not moved to SRR0 and SRR1.  I am using the
> > tool-chain from Freescale for 2.6 kernel.
> >
> > Any idea on this issue?
>
> Maybe use current 2.6 code?
>
> jdl
>
>
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

System crash on boot_e500.S

2007-08-14 Thread mike zheng
 Hi All,

I am trying to bring up MPC8548 CDS board on 2.4 kernel. I have problem in
the head_e500.S. The "mtspr SRR0, r7; mtspr SRR1 r6" does not work for me.
The content of R7 and R6 are not moved to SRR0 and SRR1.  I am using the
tool-chain from Freescale for 2.6 kernel.

Any idea on this issue?

Thanks,

Mike



Code of head_e500.S:


  slwi  r6,r6,5 /* setup new context with other address space */
  bl1f  /* Find our address */
1:mflr  r9
  rlwimi  r7,r9,0,20,31
  addi  r7,r7,24
  mtspr SRR0,r7   No change in SRR0
  mtspr SRR1,r6   No change in SRR1
  rfi System crash

/* 4. Clear out PIDs & Search info */  l
  lir6,0
  mtspr SPRN_PID0,r6
  mtspr SPRN_PID1,r6
  mtspr SPRN_PID2,r6
  mtspr SPRN_MAS6,r6
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Error: unsupported relocation against CSRR0

2007-08-12 Thread mike zheng
Hi All,

I have "unsupported relocation against" problem, while compiling entry.S in
2.4 Kernel against e500 core.  Does anyone know what is the problem? Is
there any option I missed?

Thanks in advance,

MikeZ


/kernel->   powerpc-linux-gnuspe-gcc -m32 -Wp,-MD,arch/ppc/kernel/.entry.o.d
-nostdinc -isystem
/opt/mtwk/usr/local/gcc-3_4-e500-glibc-2.3.4-dp/powerpc-linux-gnuspe/lib/gcc/powerpc-linux-gnuspe/3.4.3/include
-D__KERNEL__ -Iinclude  -Iarch/ppc -D__ASSEMBLY__ -Iarch/ppc -Wa,-me500-c
-o arch/ppc/kernel/entry.o arch/ppc/kernel/entry.S
arch/ppc/kernel/entry.S: Assembler messages:

entry.S:819: Error: unsupported relocation against CSRR0
entry.S:820: Error: unsupported relocation against CSRR1
entry.S:888: Error: unsupported relocation against MCSRR0
entry.S:889: Error: unsupported relocation against MCSRR1
entry.S:909: Error: unsupported relocation against CSRR0
entry.S:911: Error: unsupported relocation against CSRR1



entry.S

819   mtspr CSRR0, r11
820   mtspr CSRR1, r12
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Early UART configuration for 85xx on 2.6 Kernel

2007-08-10 Thread mike zheng
Hi All,

In order to debug the 8548 CDS BSP of kernel 2.6, I want setup serial port
with UART on mpc85xx as early as possible. . I add the register access
code at the beginning of  platform_init(). However the system just hanging
there with this line. If I comment out this
line"WRITE8_ADDR(M85xx_EIIADDR,0)", then linux kernel runs well.

Thanks in advance,

Mike Z

Here is the code of my mpc85xx_cds_common.c:

#define WRITE8_ADDR(address, value) \
((*((volatile u8 *)(address))) = (u8)(value))

#define M85xx_EII_ADDR 0xe0004500

void __init
platform_init(unsigned long r3, unsigned long r4, unsigned long r5,
   unsigned long r6, unsigned long r7)
{
   /* parse_bootinfo must always be called first */
   parse_bootinfo(find_bootinfo());

  /* Now we try to access register of UART */
  WRITE8_ADDR(M85xx_EII_ADDR, 0);

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

Early UART setup on 2.6 kernel for mpc85xx

2007-08-10 Thread mike zheng
Hi All,

In order to debug the kernel 2.6, I want setup serial port with UART on
mpc85xx as early as possible. I add the register access code at the
beginning of  platform_init(). For example, I try to write THR
register(0xe0004500). However the system just hanging there with this line.
If I comment out this line, everything works fine.

Here is the code my mpc85xx_cds_common.c:

void __init
platform_init(unsigned long r3, unsigned long r4, unsigned long r5,
   unsigned long r6, unsigned long r7)
{


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