Hi Andy,
Thank you for your information. So the driver is not the issue, but better
to upgraded.
I will check the board once more. The PHY doesn't work because the 8bit bus
between MAC and PHY is locked(TX_EN and RX_DV all disabled from the scope's
view) and also you can't see any signals
was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060609/8bff30f2/attachment.htm
On Jun 8, 2006, at 12:51, Guo Jaffe wrote:
Hi Andy,
Thank you for your information. So the driver is not the issue, but
better to upgraded.
I will check the board once more. The PHY doesn't work because the
8bit bus between MAC and PHY is locked(TX_EN and RX_DV all
disabled
In message 4488D8D1.3F.15159 at bj163app14.163.com you wrote:
I use the linux 2.6.14 of your website, and compile it with the ELDK4.0
succesfully, but when I download it to my PPC405 board, it stopped after
initialized the MMU, and encounter an exception in _start_here.
Is this a
Hello Arnd,
I found a problem on unsolved symbol XIo_In32 and XIo_Out32: in the linux
kernel directory of kernel/arch/ppc/platforms/xilinx_ocp, the original
xio.h file lying there is provided by MontaVista. But when I use xilinx EDK
to generate the driver for my perapheral, it generates such a
Dear Arnd,
Thanks a lot for your help. Now I have solved the problem of version
mismatch. The reason is I haven't include the sentence of #define MODULE.
However the problem of unresolved symbol XIo_In32 and XIo_Out32 still
exists. I will try to solve it following your suggestion. If any
Dear Arnd,
I have tried to replace the original definations for XIn_In32 and XIn_Out32
by what you suggested:
#define XIo_In32(p) in_le32(x) (Should that be
in_le32(p) instead of x?)
#define XIO_Out32(p,v) out_le32(p, v)
The following warnings are generated:
From: Andy Fleming afleming at freescale.com
To: Guo Jaffe jianfei616 at hotmail.com
CC: Linuxppc-embedded at ozlabs.org
Subject: Re: does Gianfar Ethernet Controller Version 1.1 support MARVELL
88E?
Date: Thu, 8 Jun 2006 14:25:44 -0500
On Jun 8, 2006, at 12:51, Guo Jaffe wrote:
Hi
On Friday 09 June 2006 16:07, Ming Liu wrote:
Are in_le32 and out_le32 two functions defined by the kernel to input and
output 32-bit data? When we define XIo_In32 and XIo_Out32 as them, which is
we use out_le32 and in_le32 to input and output data, they are still not
resolvable. Any other
I've now determined that my kernel seems to stop in the following line
of code, in the function init(void * unused), in init/main.c:
run_init_process(/sbin/init);
I've determined that it stops at this call by stepping through the code
with a BDI2000.
My boot arguments are:
console=ttyS0,57600n8
The init is from Busybox. Since I'm getting output from my serial port
during the kernel boot process, I think it's safe to say that my
/dev/ttyS0 is properly configured. Besides passing the kernel argument
console=ttyS0,57600, is there anything else I need to do to properly
configure the
Hi everyone,
I am not sure if this is a linux question or a u-boot question. I have
a custom MPC8540 board running U-boot 1.1.4. With a NFS root
configuration, I have booted and run 2.6.15 with memory from 256MB to
2GB. If I build a ramdisk image (or even if I use the ramdisk image
with the
Chris,
Does your serial output stop after Freeing unused kernel memory...
If it does, you may have an interrupt problem with the UART. I had to
track down that very problem the other day. As a test, even if my UART
interrupt was purposely misconfigured, I still saw all of the output up
to and
I think it's a u-boot 'feature' and has nothing to do with the kernel.
xianghua
Scott Coulter wrote:
Xianghua,
That seems to have worked.
Do you think that this is worth investigating?
Thanks,
Scott
___
Scott N.
Hi Scott,
That is where my output stops. What was the cause of your interrupt
problem? Were you able to fix it?
- Chris
Scott Coulter wrote:
Chris,
Does your serial output stop after Freeing unused kernel memory...
If it does, you may have an interrupt problem with the UART. I had to
track
Chris,
I was getting linux 2.6.15 running an MPC8560 board with an external
UART. In my board specific code that was setting up the Programmable
Interrupt Controller (openpic), I had a problem with a loop index and
the external interrupts were not getting setup correctly, but the
internal
On 6/9/06, Chris Dumoulin cdumoulin at ics-ltd.com wrote:
The init is from Busybox. Since I'm getting output from my serial port
during the kernel boot process, I think it's safe to say that my
/dev/ttyS0 is properly configured. Besides passing the kernel argument
console=ttyS0,57600, is there
Scott, you are my saviour. The problem was in fact the IRQ setting. I
changed the IRQ and now I get a shell, prompt, and everything. I never
would have thought to check the UART settings, since I was getting
output during kernel boot-up, I thought everything was good.
Thanks again,
Chris
I'm using Linux 2.6.6 with the Motorola Computer Group patch for the
MVME6100 available at
https://mcg.motorola.com/cfm/templates/swDetails.cfm?PageID=704Software
ID=6ProductID=202
and compiling with GCC from ELDK 3.1.1, although using the userspace
module utils (e.g. insmod) from ELDK 4.0.
The
19 matches
Mail list logo
