TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Thomas Maenner]

Hi everyone,

need from the experts on the list again.
The CPU freezes after the ramdisk gets loaded!

Trying get a working kernel: boot from flash and use ramdisk from flash with 
the following configuration:
TQM 860L, 64MB RAM (not 16MB as the standard module)
ELDK4.1
Kernel 2.6.19 from ELDK
u-boot 1.1.6

u-boot environment:
=> printenv
bootcmd=run flash_self
bootdelay=5
baudrate=115200
loads_echo=1
preboot=echo;echo TQ-Module Bootloader for ABTS;echo Type "run flash_nfs" to 
mount root filesystem over NFS;echo
netdev=eth0
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath}
addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:
${netmask}:${hostname}:${netdev}:off panic=1
flash_nfs=run nfsargs addip;bootm ${kernel_addr}
flash_self=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr}
net_nfs=tftp 200000 ${bootfile};run nfsargs addip;bootm
rootpath=/opt/eldk/ppc_8xx
kernel_addr=40040000
serial#=TQM860LDDBA3-P80.210 11090659
ethaddr=00:D0:93:04:DC:1B
eth1addr=00:D0:93:04:DC:1B
ethprime=FEC ETHERNET
bootfile=/TQM860L/uImage
fileaddr=100000
ramdisk_addr=40200000
ramargs=setenv bootargs ramdisk_size=6144 root=/dev/ram rw
initrd_high=30000000
stdin=serial
stdout=serial
stderr=serial
ethact=FEC ETHERNET
bootcount=39

Environment size: 928/16379 bytes
-----

Output after u-boot boot:
=> boot
## Booting image at 40040000 ...
   Image Name:   Linux-2.6.19.2
   Created:      2007-03-22   3:22:04 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    738664 Bytes = 721.4 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 40200000 ...
   Image Name:   Simple Embedded Linux Framework
   Created:      2007-01-20  23:09:28 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    1589504 Bytes =  1.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 03e24000, end 03fa8100 ... OK
<<< CPU / module freezes after that >>>

kernel .config:
CONFIG_MMU=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_GENERIC_NVRAM=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_KMOD=y
CONFIG_BLOCK=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_CFQ=y
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_8xx=y
CONFIG_MATH_EMULATION=y
CONFIG_EMBEDDEDBOOT=y
CONFIG_NOT_COHERENT_CACHE=y
CONFIG_TQM860L=y
CONFIG_TQM8xxL=y
CONFIG_CPM1=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_HZ_250=y
CONFIG_HZ=250
CONFIG_PREEMPT_NONE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_BINFMT_ELF=y
CONFIG_SECCOMP=y
CONFIG_ISA_DMA_API=y
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_TASK_SIZE=0x80000000
CONFIG_CONSISTENT_START=0xff100000
CONFIG_CONSISTENT_SIZE=0x00200000
CONFIG_BOOT_LOAD=0x00400000
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_CFI=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_ROM=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=0x8000000
CONFIG_MTD_PHYSMAP_LEN=0
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_TQM8XXL=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=6144
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_BLK_DEV_INITRD=y
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_USE_MDIO=y
CONFIG_INPUT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_CPM=y
CONFIG_SERIAL_CPM_CONSOLE=y
CONFIG_SERIAL_CPM_SMC1=y
CONFIG_UNIX98_PTYS=y
CONFIG_GEN_RTC=y
CONFIG_HWMON=y
CONFIG_EXT2_FS=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_DNOTIFY=y
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_PARTITION_ADVANCED=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_SCC_ENET=y
CONFIG_SCC2_ENET=y
CONFIG_FEC_ENET=y
CONFIG_FEC_LXT971=y
CONFIG_ENET_BIG_BUFFERS=y
CONFIG_8xx_COPYBACK=y
CONFIG_I2C_SPI_UCODE_PATCH=y
CONFIG_UCODE_PATCH=y
CONFIG_PLIST=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_LOG_BUF_SHIFT=14
---

Sorry for the long post and thanks in advance
Tom

-- 
Thomas Maenner
E-Mail: mailto:tmaenner@aehr.com

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Wolfgang Denk]

In message <200703212044.40611.tmaenner@aehr.com> you wrote:
> 
> need from the experts on the list again.
> The CPU freezes after the ramdisk gets loaded!

Does it really  freeze?  I  mean,  did  you  verify  this  witha  BDM
debugger,  or  do you just see no further output on the console? Note
that these are two fundamentally different things...

> u-boot environment:
> => printenv
> bootcmd=run flash_self
> bootdelay=5
> baudrate=115200
> loads_echo=1
> preboot=echo;echo TQ-Module Bootloader for ABTS;echo Type "run flash_nfs" to 
> mount root filesystem over NFS;echo
> netdev=eth0
> nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath}
> addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:
> ${netmask}:${hostname}:${netdev}:off panic=1
> flash_nfs=run nfsargs addip;bootm ${kernel_addr}
> flash_self=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr}
> net_nfs=tftp 200000 ${bootfile};run nfsargs addip;bootm
> rootpath=/opt/eldk/ppc_8xx
> kernel_addr=40040000
> serial#=TQM860LDDBA3-P80.210 11090659
> ethaddr=00:D0:93:04:DC:1B
> eth1addr=00:D0:93:04:DC:1B
> ethprime=FEC ETHERNET
> bootfile=/TQM860L/uImage
> fileaddr=100000
> ramdisk_addr=40200000
> ramargs=setenv bootargs ramdisk_size=6144 root=/dev/ram rw
> initrd_high=30000000
> stdin=serial
> stdout=serial
> stderr=serial
> ethact=FEC ETHERNET
> bootcount=39

I don't see you passing any console=ttyCPM0 argument here?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Not one hundred percent efficient, of course ... but nothing ever is.
	-- Kirk, "Metamorphosis", stardate 3219.8

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Thomas Maenner]

Thanks Wolfgang for your reply,

You're right, I can not really tell, whether it's frozen since I don't
have a BDM...
I'll try the console command you suggested, which I haven't had to use
before (U-boot 1.1.2 and older, Kernel 2.4, older ELDK)

Thanks
Tom

On 3/22/07, Wolfgang Denk <wd@denx.de> wrote:
> In message <200703212044.40611.tmaenner@aehr.com> you wrote:
> >
> > need from the experts on the list again.
> > The CPU freezes after the ramdisk gets loaded!
>
> Does it really  freeze?  I  mean,  did  you  verify  this  witha  BDM
> debugger,  or  do you just see no further output on the console? Note
> that these are two fundamentally different things...
>
> > u-boot environment:
> > => printenv
> > bootcmd=run flash_self
> > bootdelay=5
> > baudrate=115200
> > loads_echo=1
> > preboot=echo;echo TQ-Module Bootloader for ABTS;echo Type "run flash_nfs" to
> > mount root filesystem over NFS;echo
> > netdev=eth0
> > nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath}
> > addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:
> > ${netmask}:${hostname}:${netdev}:off panic=1
> > flash_nfs=run nfsargs addip;bootm ${kernel_addr}
> > flash_self=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr}
> > net_nfs=tftp 200000 ${bootfile};run nfsargs addip;bootm
> > rootpath=/opt/eldk/ppc_8xx
> > kernel_addr=40040000
> > serial#=TQM860LDDBA3-P80.210 11090659
> > ethaddr=00:D0:93:04:DC:1B
> > eth1addr=00:D0:93:04:DC:1B
> > ethprime=FEC ETHERNET
> > bootfile=/TQM860L/uImage
> > fileaddr=100000
> > ramdisk_addr=40200000
> > ramargs=setenv bootargs ramdisk_size=6144 root=/dev/ram rw
> > initrd_high=30000000
> > stdin=serial
> > stdout=serial
> > stderr=serial
> > ethact=FEC ETHERNET
> > bootcount=39
>
> I don't see you passing any console=ttyCPM0 argument here?
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
> Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> Not one hundred percent efficient, of course ... but nothing ever is.
>         -- Kirk, "Metamorphosis", stardate 3219.8
>



-- 
Thomas Maenner
Engineering Project Manager
AEHR Test Systems
400 Kato Terrace
Fremont, CA 94539
Phone: +1-510-623-9400x323
Cell: +1-925-389-6653
Fax: +1-510-623-9450
E-Mail: mailto:tmaenner@aehr.com

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Thomas Maenner]

Tried out the following u-boot "setting":
setenv ramargs setenv bootargs ramdisk_size=3D6144 root=3D/dev/ram console=
=3DttyCPM0=20
rw

No change; still no output in the console

Note that my module has 64MB, rather that 16; I thought it doesn't matter, =
or?

Thanks again for your help
Tom

On Thursday 22 March 2007 08:01, Thomas Maenner wrote:
> Thanks Wolfgang for your reply,
>
> You're right, I can not really tell, whether it's frozen since I don't
> have a BDM...
> I'll try the console command you suggested, which I haven't had to use
> before (U-boot 1.1.2 and older, Kernel 2.4, older ELDK)
>
> Thanks
> Tom
>
> On 3/22/07, Wolfgang Denk <wd@denx.de> wrote:
> > In message <200703212044.40611.tmaenner@aehr.com> you wrote:
> > > need from the experts on the list again.
> > > The CPU freezes after the ramdisk gets loaded!
> >
> > Does it really  freeze?  I  mean,  did  you  verify  this  witha  BDM
> > debugger,  or  do you just see no further output on the console? Note
> > that these are two fundamentally different things...
> >
> > > u-boot environment:
> > > =3D> printenv
> > > bootcmd=3Drun flash_self
> > > bootdelay=3D5
> > > baudrate=3D115200
> > > loads_echo=3D1
> > > preboot=3Decho;echo TQ-Module Bootloader for ABTS;echo Type "run
> > > flash_nfs" to mount root filesystem over NFS;echo
> > > netdev=3Deth0
> > > nfsargs=3Dsetenv bootargs root=3D/dev/nfs rw
> > > nfsroot=3D${serverip}:${rootpath} addip=3Dsetenv bootargs ${bootargs}
> > > ip=3D${ipaddr}:${serverip}:${gatewayip}:
> > > ${netmask}:${hostname}:${netdev}:off panic=3D1
> > > flash_nfs=3Drun nfsargs addip;bootm ${kernel_addr}
> > > flash_self=3Drun ramargs addip;bootm ${kernel_addr} ${ramdisk_addr}
> > > net_nfs=3Dtftp 200000 ${bootfile};run nfsargs addip;bootm
> > > rootpath=3D/opt/eldk/ppc_8xx
> > > kernel_addr=3D40040000
> > > serial#=3DTQM860LDDBA3-P80.210 11090659
> > > ethaddr=3D00:D0:93:04:DC:1B
> > > eth1addr=3D00:D0:93:04:DC:1B
> > > ethprime=3DFEC ETHERNET
> > > bootfile=3D/TQM860L/uImage
> > > fileaddr=3D100000
> > > ramdisk_addr=3D40200000
> > > ramargs=3Dsetenv bootargs ramdisk_size=3D6144 root=3D/dev/ram rw
> > > initrd_high=3D30000000
> > > stdin=3Dserial
> > > stdout=3Dserial
> > > stderr=3Dserial
> > > ethact=3DFEC ETHERNET
> > > bootcount=3D39
> >
> > I don't see you passing any console=3DttyCPM0 argument here?
> >
> > Best regards,
> >
> > Wolfgang Denk
> >
> > --
> > DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
> > Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
> > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> > Not one hundred percent efficient, of course ... but nothing ever is.
> >         -- Kirk, "Metamorphosis", stardate 3219.8

=2D-=20
Thomas Maenner
Engineering Project Manager
AEHR Test Systems
400 Kato Terrace
=46remont, CA 94539
Phone: =A0+1-510-623-9400x323
Cell: =A0 +1-925-389-6653
=46ax: =A0 =A0+1-510-623-9450
E-Mail: mailto:tmaenner@aehr.com

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Wolfgang Denk]

In message <200703221410.37767.tmaenner@aehr.com> you wrote:
> Tried out the following u-boot "setting":
> setenv ramargs setenv bootargs ramdisk_size=6144 root=/dev/ram console=ttyCPM0 rw
> 
> No change; still no output in the console

Then buy a debugger and dig into it...

> Note that my module has 64MB, rather that 16; I thought it doesn't matter, or?

It doesn't.

You are aware that TQM8xxL is not yet supported in the context of the
2.6 Linux kernel, aren't you? [And we will  not  support  it  in  the
ARCH=ppc context any more.]

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
We are all agreed that your  theory  is  crazy.  The  question  which
divides  us  is  whether it is crazy enough to have a chance of being
correct. My own feeling is that it is not crazy enough.  - Niels Bohr

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Ralph Hempel]

> You are aware that TQM8xxL is not yet supported in the context of the
> 2.6 Linux kernel, aren't you? [And we will  not  support  it  in  the
> ARCH=ppc context any more.]

hello,

does anybody know if TQ Systems is going to support the 
recent 2.6 kernels ?

br
Ralph Hempel

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Wolfgang Denk]

Dear Ralph,

in message <loom.20070323T121236-994@post.gmane.org> you wrote:
> > You are aware that TQM8xxL is not yet supported in the context of the
> > 2.6 Linux kernel, aren't you? [And we will  not  support  it  in  the
> > ARCH=ppc context any more.]
> 
> does anybody know if TQ Systems is going to support the 
> recent 2.6 kernels ?

You probably should direct this question to TQ (btw: you  should  ask
TQ Components - for example Robert Nerbl or Heinz Hornung).

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
SW engineering is a race between programmers trying  to  make  better
idiot-proof programs and the universe producing greater idiots.

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Thomas Maenner]

Apparently I was not aware, that the TQ8xx are not supported by 2.6...
Will try the linuxppc_2_4_devel version from your cvs repository.

Thanks
Tom

On Thursday 22 March 2007 14:26, Wolfgang Denk wrote:
> In message <200703221410.37767.tmaenner@aehr.com> you wrote:
> > Tried out the following u-boot "setting":
> > setenv ramargs setenv bootargs ramdisk_size=6144 root=/dev/ram
> > console=ttyCPM0 rw
> >
> > No change; still no output in the console
>
> Then buy a debugger and dig into it...
>
> > Note that my module has 64MB, rather that 16; I thought it doesn't
> > matter, or?
>
> It doesn't.
>
> You are aware that TQM8xxL is not yet supported in the context of the
> 2.6 Linux kernel, aren't you? [And we will  not  support  it  in  the
> ARCH=ppc context any more.]
>
> Best regards,
>
> Wolfgang Denk

-- 
Thomas Maenner
E-Mail: mailto:tmaenner@aehr.com

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Thomas Maenner]

Dear Wolfgang,

please enlighten us (or maybe just me) on why the TQ8xx are not supported by 
2.6, since the ppc sources are in the 2.6.19 kernel source tree, that comes 
with ELDK 4.1

Thanks much for your support
Tom

On Friday 23 March 2007 06:27, Wolfgang Denk wrote:
> Dear Ralph,
>
> in message <loom.20070323T121236-994@post.gmane.org> you wrote:
> > > You are aware that TQM8xxL is not yet supported in the context of the
> > > 2.6 Linux kernel, aren't you? [And we will  not  support  it  in  the
> > > ARCH=ppc context any more.]
> >
> > does anybody know if TQ Systems is going to support the
> > recent 2.6 kernels ?
>
> You probably should direct this question to TQ (btw: you  should  ask
> TQ Components - for example Robert Nerbl or Heinz Hornung).
>
> Best regards,
>
> Wolfgang Denk

-- 
Thomas Maenner
E-Mail: mailto:tmaenner@aehr.com

Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19

[Wolfgang Denk]

In message <200703231029.04488.tmaenner@aehr.com> you wrote:
> 
> please enlighten us (or maybe just me) on why the TQ8xx are not supported by 
> 2.6, since the ppc sources are in the 2.6.19 kernel source tree, that comes 
> with ELDK 4.1

The working 2.4 code was copied to 2.5 and later to 2.6 without  ever
being  actively maintained. In early 2.6 kernels, support for 8xx was
more or less broken. Lately, it has become clear that ARCH=ppc  is  a
dead end and things should move to ARCH=powerpc. That's why I said we
(DENX) will not support the 8xx in the ARCH=ppc context.

Last but not least I would like to remind you that 2.6 is bigger and
slower than 2.4, which is especially visible on low end systems like
the 8xx.

The kernel code that comes with the ELDK is very close to the vanilla
kernel.org tree (plus some local extensions that have  not  yet  been
pushed  upstream).  The  8xx  support  in  both  trees  is absolutely
identical, i. e. the fact that 8xx code is in the ELDK has  the  very
same reason why x86 code is there, or why sh4 or etrax or ... code is
theee,  even  if these systems are not supported by the ELDK at all -
this code is part of the vanilla kernel.org tree.

AFAIK, 2.6 has never been fully ported to  the  TQM8xxL  and  TQM8xxM
systems yet.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Computers are not intelligent.  They only think they are.