Quetions : insmod command error

2004-04-02 Thread ???

Hi,

I have a problem with module loading for kernel 2.6.3.

 environment 
1) target : ppc8260 custom board.
2) kernel has compiled with module support
3) using kernel 2.6.3
4) using modutils 2.4.22
5) include/config/modules.h had #define CONFIG_MODULES 1

 test message 
bash-2.05b# ls
Makefile  Makefile.l  hello.c  hello.ko  hello.mod.c  hello.mod.o  hello.o
bash-2.05b# insmod hello.ko
insmod: QM_MODULES: Function not implemented

bash-2.05b# depmod -V
depmod version 2.4.22
depmod: QM_MODULES: Function not implemented

and
I heard that mode-init-utils upgrade.
I got to module-init-tools-3.0.tar.gz'
After install, the following error message

VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 76k init
request_module: runaway loop modprobe binfmt-4c46
request_module: runaway loop modprobe binfmt-4c46
request_module: runaway loop modprobe binfmt-4c46
request_module: runaway loop modprobe binfmt-4c46
request_module: runaway loop modprobe binfmt-4c46

stopped..

Any help would be appreciated.
Thanks,
call me Lone
shchoi at airpoint.co.kr

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





LSP(Linux support package) for PPC405EP

2004-04-02 Thread Shiva Kumar Yenigalla

Hi,

Is Open Source Linux Kernel supports IBM's PPC405EP Evaluation Platform? I
have seen some files in linux kernel(open souce) related to 405EP. But, i
want to make sure that whether there is a complete support for PPC405EP in
Open source Linux kernel. If so, please tell me which version includes this
support.

As far as boot loader is concerned, I know that uBoot is good. But, i am
looking for BSP(Board support package).

Thanks,
Shiva


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Quetions : insmod command error

2004-04-02 Thread Ing.Gianfranco Morandi (LAN)

 3) using kernel 2.6.3
 4) using modutils 2.4.22
 5) include/config/modules.h had #define CONFIG_MODULES 1

For what is my knowledge loading a module in 2.6.x is quite different from
previous 2.4.x.

Look at the available HOWTOs.

Gianfranco


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





relocation error: GLIBC_2.0 not defined

2004-04-02 Thread S. Hebbar

I am getting the following error when I execute any command from the linux
prompt. After rebooting the node, the problem went away.


Error:
=

 ls -al



ls: relocation error: ls: symbol
, version GLIBC_2.0 not defined in file libc.so.6 with link time reference


 su



bash-2.05# su
bash-2.05# ls
ls: relocation error: ls: symbol
, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
bash-2.05# tail
tail: relocation error: tail: symbol
, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
bash-2.05#
===



Target Processor: MPC8260
Target OS: Linux 2.4.20-denx

LibC: (Included in denx CD).


GNU C Library stable release version 2.2.5, by Roland McGrath et al.
Copyright (C) 1992-2001, 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 2.95.4 20010319 (prerelease/franzo/20011204).
Compiled on a Linux 2.4.18-26.7.x system on 2003-04-08.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.9 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
software FPU emulation by Richard Henderson, Jakub Jelinek and others
Report bugs using the `glibcbug' script to bugs at gnu.org.



** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Insmod trouble

2004-04-02 Thread Wolfgang Denk

In message DCEAAC0833DD314AB0B58112AD99B93B06DAAE at 
ismail.innsys.innovsys.com you wrote:

 I get the following unresolved functions when trying to insmod a module
 with some floating point math in it:

You cannot use floating point in kernel mode.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
God made machine language; all the rest is the work of man.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





C++ on PowerQUICC 1

2004-04-02 Thread [EMAIL PROTECTED]

Hi:

I would like to run a C++ program on a PowerQUICC I with 8MB of Ram. I have 
been told that this may not be possible to do. Does anyone have experience with 
the memory requirements for C++ with a PQ1?

Thank you,

Bob Davis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





kernel oops -- shmem_read_super

2004-04-02 Thread J Kang

Hi Everyone,
I am an newbie with linux and boards!
I am trying to do a kernel build for custom board (IBM
440 gx processor, M Vista 3.0)

I used ksymoops and I'm getting oops at
shmem_read_super.

I'm trying to understand what exactly shmem_read_super
is doing and how to fix this problem.
Can someone please give me an advice?

I'd really appreciate your help.

Sincerely,
Jagbir



ksymoops 2.4.4 on i686 2.4.18-3.  Options used
 -v JKANG/linux-2.4.18_mvl30/vmlinux (specified)
 -K (specified)
 -L (specified)
 -O (specified)
 -m JKANG/linux-2.4.18_mvl30/System.map
(specified)

CPU: 512 MHz
BEDBUG:ready
Oops: Exception in kernel mode, sig: 4
NIP: C003A900 XER:  LR: C0045968 SP: C0203EE0
REGS: c0203e20 TRAP: 0700Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
MSR: 9030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c0202000[1] 'swapper' Last syscall: 120
last math  last altivec 
GPR00: C0045950 C0203EE0 C0202000 CFFFBA00 
 063C C0140197
GPR08:  0001 0034 C0203DF0 C016
3000 0FFF1C00 0001
GPR16: 007FFC0E  0001 007FFC00 0FFEF428
  
GPR24:  0080  C003A900 
 CFFFBA00 CFFFBA48
Call backtrace:
C0045950 C0045F44 C0046698 C00466E4 C014F380 C014A7E8
C014A834
C00012C4 C0003E1C
Kernel panic: Attempted to kill init!
Oops: Exception in kernel mode, sig: 4
NIP: C003FAD0 XER:  LR: C0013924 SP: C0203D00
REGS: c0203c40 TRAP: 0700Not tainted
MSR: 9030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c0202000[1] 'swapper' Last syscall: 120
last math  last altivec 
GPR00: 0001 C0203D00 C0202000 C011B3F8 1030
 093C C0140197
GPR08:  C0164B80 0030  C016
3000 0FFF1C00 0001
GPR16: 007FFC0E  0001 007FFC00 9032
C0203E10  C00017D8
GPR24: C0001BE0 0080  C003A900 C016
C011BB38 C0202000 C0119148
Call backtrace:
C0013854 C0018114 C000199C C00019F4 C0001C38 C00017D8
C0045950
C0045F44 C0046698 C00466E4 C014F380 C014A7E8 C014A834
C00012C4
C0003E1C
Kernel panic: Attempted to kill init!
Oops: Exception in kernel mode, sig: 4
NIP: C003FAD0 XER:  LR: C0013924 SP: C0203B20
REGS: c0203a60 TRAP: 0700Not tainted
MSR: 9030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c0202000[1] 'swapper' Last syscall: 120
last math  last altivec 
GPR00: 0001 C0203B20 C0202000 C011B3F8 1030
 0C76 C0140197
GPR08:  C0164B80 0030  C016
3000 0FFF1C00 0001
GPR16: 007FFC0E  0001 007FFC00 9032
C0203C30  C00017D8
GPR24: C0001BE0 0080  C003A900 C016
C011BB38 C0202000 C0119148
Call backtrace:
Warning (Oops_read): Code line not seen, dumping what
data is available

EIP; c003a900 shmem_read_super+0/13c   =
Trace; c0045950 read_super+80/1e4
Trace; c0045f44 get_sb_nodev+58/7c
Trace; c0046698 do_kern_mount+1bc/1e8
Trace; c00466e4 kern_mount+20/30
Trace; c014f380 init_shmem_fs+78/e4
Trace; c014a7e8 do_initcalls+30/50
Trace; c014a834 do_basic_setup+2c/3c
Trace; c00012c4 init+28/224
Trace; c0003e1c kernel_thread+30/3c
EIP; c003fad0 sys_sync+0/28   =
Trace; c0013854 panic+68/13c
Trace; c0018114 complete_and_exit+0/28
Trace; c000199c die+88/90
Trace; c00019f4 _exception+50/54
Trace; c0001c38 ProgramCheckException+58/74
Trace; c00017d8 ret_from_except+0/34
Trace; c0045950 read_super+80/1e4
Trace; c0045f44 get_sb_nodev+58/7c
Trace; c0046698 do_kern_mount+1bc/1e8
Trace; c00466e4 kern_mount+20/30
Trace; c014f380 init_shmem_fs+78/e4
Trace; c014a7e8 do_initcalls+30/50
Trace; c014a834 do_basic_setup+2c/3c
Trace; c00012c4 init+28/224
Trace; c0003e1c kernel_thread+30/3c
EIP; c003fad0 sys_sync+0/28   =


Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Jeff Tucker

Hi, guys.

I sent a message like this to the U-Boot mailing list last night. I've been
told this is definitely not a U-Boot problem, so I'm hoping that the people
on this list can help me.

I'm having a hard time getting U-Boot to boot Linux on an IBM 405EP
evaluation board. Here's what I've tried:

First, I think my kernels are fine. I can compile 2.4.18 from an older
version of the ELDK or I can compile 2.4.24 from the latest released ELDK.
I'm using ELDK tools for all of my builds. Using the IBM bootloader that
comes on the board and the treeboot image file format, I can get the IBM
board to tftp my kernel over the lan and run it. So, I think the kernel is
working fine.

I also don't have any problem running U-Boot. I compiled 1.0.2 and
installed it on the board. U-Boot runs fine and I can make it tftp a file
over the network as well. Using iminfo, I can see that it read what I
expect. However, no matter what I try, I can't get the kernel to actually
boot.

In the older kernel, I'm using a make pImage and in the newer kernel I do
make uImage. I've also tried running the mkimage tool manually with
various options to see if I could get a kernel to boot. iminfo says the
kernel is fine and I get to the Uncompressing Linux Kernel ... OK stage
but it stops there.

I'm aware that the denx.de site has a FAQ which appears to address this
issue:
http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel

However, the structure mentioned there (bd_info) doesn't even seem to apply
for a 405EP-based board. The ppcboot.h file isn't included by the files
used when building a 405EP kernel for the 405EP evaluation board.

It still could be a problem passing parameters to the kernel, I suppose,
but I am not sure how those are defined in the first place.

I searched the mailing list archives but couldn't find anyone who had a
similar problem. So, if someone is using U-Boot to boot a kernel on the
405EP evaluation board would be willing to give me some pointers, I'd
appreciate it.

Thanks
Jeff



--
Jeff Tucker
jeff at jltnet.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





SystemACE but not V2PRO

2004-04-02 Thread Scott Anderson

Hi there,
The current ML300 maintainer is Andrei Konovalov
akonovalov at ru.mvista.com
(cc'ed on this message).  I'm guessing he didn't reply to your message
last week because he's swamped, but hopefully having this directly
addressed to him will prompt a response.

   Scott

On Apr 1, 2004, at 6:38 PM, Stephen Williams wrote:


 The attached patch is my spin at getting the existing xsysace
 block driver working on systems that have SystemACE chips, but
 do not use Virtex-II-Pro chips. The adapter.c file assumes that
 the system ace halt will halt the processor. This is not the
 case in general, so this patch ifdefs that part of the code out
 using CONFIG_VIRTEX_II_PRO.

 This is only part of the story for getting the systemace
 working in general, but the remaining bits are configuration
 issues, not code/driver support.

 Question: Who is the maintainer for this section of code? It
 is maybe MonteVista?
 --
 Steve WilliamsThe woods are lovely, dark and deep.
 steve at XX   But I have promises to keep,
 http://www.XX and lines to code before I sleep,
 http://www.picturel.com   And lines to code before I sleep.
 Index: drivers/block/xilinx_sysace/adapter.c
 ===
 RCS file:
 /cvsroot/linuxppc_2_4_devel/drivers/block/xilinx_sysace/adapter.c,v
 retrieving revision 1.3
 diff -p -u -r1.3 adapter.c
 --- drivers/block/xilinx_sysace/adapter.c 30 Oct 2003 00:32:49
 - 1.3
 +++ drivers/block/xilinx_sysace/adapter.c 2 Apr 2004 02:27:37 -
 @@ -74,7 +74,9 @@ MODULE_LICENSE(GPL);
  static const int dont_spin = 0;

  static u32 save_BaseAddress; /* Saved physical base address */
 +#ifdef CONFIG_VIRTEX_II_PRO
  static void (*old_restart) (char *cmd) = NULL;   /* old ppc_md.restart
 */
 +#endif

  static unsigned char heads;
  static unsigned char sectors;
 @@ -277,6 +279,13 @@ proc_cleanup(void)
  }
  #endif

 +#ifdef CONFIG_VIRTEX_II_PRO
 +/*
 + * The XSysAce_ResetCfg function causes the SystemACE to reset the
 + * Xilinx chain that is attached to it. If I am a Virtex II Pro, then
 + * presumably that includes me. Thus, The ResetCfg will ultimately
 + * reset me, the processor, end of story.
 + */
  static void
  xsysace_restart(char *cmd)
  {
 @@ -285,6 +294,7 @@ xsysace_restart(char *cmd)
   /* Wait for reset. */
   for (;;) ;
  }
 +#endif

  /*
   * The code to handle the block device starts here.
 @@ -725,8 +735,10 @@ cleanup(void)
   iounmap((void *) cfg-BaseAddress);
   cfg-BaseAddress = save_BaseAddress;

 +#ifdef CONFIG_VIRTEX_II_PRO
   if (old_restart)
   ppc_md.restart = old_restart;
 +#endif
  }

  static int __init
 @@ -837,9 +849,11 @@ xsysace_init(void)
  DEVICE_NAME, save_BaseAddress, cfg-BaseAddress, XSA_IRQ,
  size / 2);

 +#ifdef CONFIG_VIRTEX_II_PRO
   /* Hook our reset function into system's restart code. */
   old_restart = ppc_md.restart;
   ppc_md.restart = xsysace_restart;
 +#endif

   if (proc_init())
   printk(KERN_WARNING %s: could not register /proc interface.\n,


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





C++ Memory Requirements for PowerQUICC 1

2004-04-02 Thread Steven Blakeslee

It depends on the application.  An entire Linux kernel complete with ramdisk
can run on 8MB of RAM.

-Original Message-
From: vze8n24y at verizon.net [mailto:[EMAIL PROTECTED]
Sent: Friday, April 02, 2004 12:30 PM
To: linuxppc-embedded at lists.linuxppc.org
Subject: C++ Memory Requirements for PowerQUICC 1



Hi:

I would like to run C++ on a PowerQUICC I system that has 8 MB of RAM. I was
told by a friend that this was not enough memory to run a C++ program with
the C++ libraries. Does anyone have experience with this?

Regards,

Bob Davis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Eugene Surovegin

On Fri, Apr 02, 2004 at 12:34:56PM -0500, Jeff Tucker wrote:

 Hi, guys.

 I sent a message like this to the U-Boot mailing list last night. I've been
 told this is definitely not a U-Boot problem, so I'm hoping that the people
 on this list can help me.

 I'm having a hard time getting U-Boot to boot Linux on an IBM 405EP
 evaluation board. Here's what I've tried:

 First, I think my kernels are fine. I can compile 2.4.18 from an older
 version of the ELDK or I can compile 2.4.24 from the latest released ELDK.
 I'm using ELDK tools for all of my builds. Using the IBM bootloader that
 comes on the board and the treeboot image file format, I can get the IBM
 board to tftp my kernel over the lan and run it. So, I think the kernel is
 working fine.

Hmm...

Standard bootloader which comes with 405ep eval board works fine with the Linux
kernel, U-Boot - doesn't, and you are being told that it's not a U-Boot
problem ?

So why don't you just use IBM bootloader and not U-Boot if you cannot get help
from u-boot maillist?

Eugene.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Jeff Tucker

--On Friday, April 02, 2004 12:34 PM -0500 Jeff Tucker jeff at jltnet.com
wrote:


 Hi, guys.

 I sent a message like this to the U-Boot mailing list last night. I've
 been
 told this is definitely not a U-Boot problem, so I'm hoping that the
 people
 on this list can help me.

 I'm having a hard time getting U-Boot to boot Linux on an IBM 405EP
 evaluation board. Here's what I've tried:


Just to follow up to my own posting. I've found that in my linux-2.4.18
kernel, there is a file arch/ppc/platforms/evb405ep.h which does include a
board_info struct which is quite a bit different from the struct in
u-boot.h. I've made those match and re-built the kernel, still with no luck.

I've re-built U-Boot in debug mode so I can see what is going on. Here's
what it spits out before the board locks up:

= iminfo 50

## Checking Image at 0050 ...
   Image Name:   Linux-2.4.18_mvl30-405ep_eval
   Created:  2004-04-02  17:59:23 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:733690 Bytes = 716.5 kB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
= bootm 50
## Booting image at 0050 ...
   Image Name:   Linux-2.4.18_mvl30-405ep_eval
   Created:  2004-04-02  17:59:23 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:733690 Bytes = 716.5 kB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Current stack ends at 0x07FB0598 = set upper limit to 0x0080
## cmdline at 0x007FFC00 ... 0x007FFC1B
bd address  = 0x07FB0F8C
memstart= 0x
memsize = 0x0800
flashstart  = 0xFFF8
flashsize   = 0x0008
flashoffset = 0x00027F00
sramstart   = 0x
sramsize= 0x
bootflags   = 0xA000
procfreq= 266.666 MHz
plb_busfreq = 133.333 MHz
pci_busfreq = 33.333 MHz
ethaddr = 00:04:AC:E3:24:A7
IP addr = 192.168.0.91
baudrate=   9600 bps
No initrd
## Transferring control to Linux (at address ) ...

Any ideas?

Thanks
Jeff

--
Jeff Tucker
jeff at jltnet.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Wolfgang Denk

In message [EMAIL PROTECTED] you wrote:

 I sent a message like this to the U-Boot mailing list last night. I've been

And you have received replies thaty pointed to the problem.

 I'm aware that the denx.de site has a FAQ which appears to address this issue:
 http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel

 However, the structure mentioned there (bd_info) doesn't even seem to apply
 for a 405EP-based board. The ppcboot.h file isn't included by the files
 used when building a 405EP kernel for the 405EP evaluation board.

OK. You found the problem: The ppcboot.h file isn't  included.  Seems
you  must  adapt  your  board for use with U-Boot. See the FAQ quoted
above.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Data is a lot like humans: It is  born.  Matures.  Gets  married  to
other  data, divorced. Gets old. One thing that it doesn't do is die.
It has to be killed. - Arthur Miller

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





SystemACE but not V2PRO

2004-04-02 Thread Andrei Konovalov

I've looked at this patch.
At first glance it looks OK, but I'd like to think a little bit more about
it.
I'll come back on Monday, or Tuesday (in worst case).

Thanks,
Andrei

 -Original Message-
 From: Scott Anderson [mailto:scott_anderson at mvista.com]
 Sent: Friday, April 02, 2004 8:36 PM
 To: Stephen Williams
 Cc: linuxppc-embedded at lists.linuxppc.org; Andrei Konovalov
 Subject: Re: SystemACE but not V2PRO


 Hi there,
 The current ML300 maintainer is Andrei Konovalov
 akonovalov at ru.mvista.com
 (cc'ed on this message).  I'm guessing he didn't reply to your message
 last week because he's swamped, but hopefully having this directly
 addressed to him will prompt a response.

Scott

 On Apr 1, 2004, at 6:38 PM, Stephen Williams wrote:

 
  The attached patch is my spin at getting the existing xsysace
  block driver working on systems that have SystemACE chips, but
  do not use Virtex-II-Pro chips. The adapter.c file assumes that
  the system ace halt will halt the processor. This is not the
  case in general, so this patch ifdefs that part of the code out
  using CONFIG_VIRTEX_II_PRO.
 
  This is only part of the story for getting the systemace
  working in general, but the remaining bits are configuration
  issues, not code/driver support.
 
  Question: Who is the maintainer for this section of code? It
  is maybe MonteVista?
  --
  Steve WilliamsThe woods are lovely, dark and deep.
  steve at XX   But I have promises to keep,
  http://www.XX and lines to code before I sleep,
  http://www.picturel.com   And lines to code before I sleep.
  Index: drivers/block/xilinx_sysace/adapter.c
  ===
  RCS file:
  /cvsroot/linuxppc_2_4_devel/drivers/block/xilinx_sysace/adapter.c,v
  retrieving revision 1.3
  diff -p -u -r1.3 adapter.c
  --- drivers/block/xilinx_sysace/adapter.c   30 Oct 2003 00:32:49
  -   1.3
  +++ drivers/block/xilinx_sysace/adapter.c   2 Apr 2004 02:27:37 -
  @@ -74,7 +74,9 @@ MODULE_LICENSE(GPL);
   static const int dont_spin = 0;
 
   static u32 save_BaseAddress;   /* Saved physical base address */
  +#ifdef CONFIG_VIRTEX_II_PRO
   static void (*old_restart) (char *cmd) = NULL; /* old
 ppc_md.restart
  */
  +#endif
 
   static unsigned char heads;
   static unsigned char sectors;
  @@ -277,6 +279,13 @@ proc_cleanup(void)
   }
   #endif
 
  +#ifdef CONFIG_VIRTEX_II_PRO
  +/*
  + * The XSysAce_ResetCfg function causes the SystemACE to reset the
  + * Xilinx chain that is attached to it. If I am a Virtex II Pro, then
  + * presumably that includes me. Thus, The ResetCfg will ultimately
  + * reset me, the processor, end of story.
  + */
   static void
   xsysace_restart(char *cmd)
   {
  @@ -285,6 +294,7 @@ xsysace_restart(char *cmd)
  /* Wait for reset. */
  for (;;) ;
   }
  +#endif
 
   /*
* The code to handle the block device starts here.
  @@ -725,8 +735,10 @@ cleanup(void)
  iounmap((void *) cfg-BaseAddress);
  cfg-BaseAddress = save_BaseAddress;
 
  +#ifdef CONFIG_VIRTEX_II_PRO
  if (old_restart)
  ppc_md.restart = old_restart;
  +#endif
   }
 
   static int __init
  @@ -837,9 +849,11 @@ xsysace_init(void)
 DEVICE_NAME, save_BaseAddress, cfg-BaseAddress, XSA_IRQ,
 size / 2);
 
  +#ifdef CONFIG_VIRTEX_II_PRO
  /* Hook our reset function into system's restart code. */
  old_restart = ppc_md.restart;
  ppc_md.restart = xsysace_restart;
  +#endif
 
  if (proc_init())
  printk(KERN_WARNING %s: could not register /proc
 interface.\n,





** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Wolfgang Denk

In message 20040402182716.GC8540 at gate.ebshome.net you wrote:

 Standard bootloader which comes with 405ep eval board works fine with the 
 Linux
 kernel, U-Boot - doesn't, and you are being told that it's not a U-Boot
 problem ?

It is not a problem that can be fixed in U-boot, as he must make sure
that Linux interptets the arguments passed by U-Boot correctly.

 So why don't you just use IBM bootloader and not U-Boot if you cannot get help
 from u-boot maillist?

He got help. Actually this is a FAQ.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Faith may be defined briefly as an illogical belief in the  occurence
of the improbable.- H. L. Mencken

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Christian Tröster


Am Friday 02 April 2004 20:33 schrieb Jeff Tucker:
 I've re-built U-Boot in debug mode so I can see what is going on. Here's
 what it spits out before the board locks up:
[snip]
 procfreq= 266.666 MHz
 plb_busfreq = 133.333 MHz
 pci_busfreq = 33.333 MHz
 ethaddr = 00:04:AC:E3:24:A7
 IP addr = 192.168.0.91
 baudrate=   9600 bps
 No initrd
 ## Transferring control to Linux (at address ) ...

 Any ideas?
If you're connected via a serial console make sure to append the correct
bootoptions to the kernel to get your output to /dev/ttySx.

Bye, Christian

- --
| mailto:c.troester at gmx.de | http://www.christian.myfen.de/ |

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





Need help booting linux on IBM 405EP eval board

2004-04-02 Thread Jeff Tucker

--On Friday, April 02, 2004 8:51 PM +0200 Wolfgang Denk wd at denx.de wrote:


 In message [EMAIL PROTECTED] you wrote:

 I sent a message like this to the U-Boot mailing list last night. I've
 been

 And you have received replies thaty pointed to the problem.


Indeed, as my later email indicated, I found that the Linux build is using
the file arch/ppc/platforms/evb405ep.[c/h] and that file has a board_info
struct, separate and different from the ppcboot.h file which is in a
totally different directory. I've made evb405ep.h match U-Boot's u-boot.h,
but that hasn't helped my problem.

I guess I have two questions then:
- Does the build environment (from ELDK 3.0) for the 405EP evaluation board
use the file mentioned above? Is that the place where I have to make the
board_info struct match the struct in U-Boot
(u-boot/include/asm-ppc/u-boot.h)?

- Has the Linux/build environment already been ported for this particular
board? It's in the Makefile and there are certainly board-specific files
available in the above directory. So, I figured that I wouldn't have to go
through a porting process to boot Linux. And, again, the IBM bootloader
loads and boots kernels just fine.

Does anyone out there use this evaluation board, Linux 2.4 and U-Boot or am
I really the first?

Thanks
Jeff

--
Jeff Tucker
jeff at jltnet.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/