I followed your sequence which is I show below. But I got problem shown
below. Plz Suggest me. How can I solve this one.
make mrproper
CLEAN scripts/basic
CLEAN scripts/kconfig
CLEAN include/config
CLEAN .config .config.old include/linux/autoconf.h
[EMAIL PROTECTED] linu
Has anybody had a similar problem accessing external memory from CPMs?
Any idea on something I can try?
What is more critical? Accessing slow or quick external devices?
David
David Beamonte escribió:
I have checked that bit and it is not set. In fact, that register has
the same value as the
Hi Georg,
Can you post linux bootup message where its says PHY is detected at
paticular address, and check with your hardware what is actual address
of PHY. Also I would like to know the configuration of your hardware
whether its configured of 10MBPS OR 100MBPS.
Hi Georg,
I don't really know much about the state of the emac lite driver in the
Git tree. I inherited the Git tree with some stuff already in it.
I test the LL TEMAC driver, but haven't had the bandwidth and priority
to do any emac lite testing.
Thanks,
John
> -Original Message-
> Fro
Hi Ed,
I have duplicated your problem with the Dell keyboard.
I then connected a Logitech keyboard and that worked.
I added a bunch of debug messages to track what was going on and I ended up in
the function usb_find_interface_driver(...) in usb.c.
As far as I can tell, both keyboards are reco
Hi,
Our kernel 2.6.26 on MPC8248 board crashes as the cache reaches 12MB,
giving the following Oops message.
Oops: kernel access of bad area, sig: 11 [#1]
NIP: c0013638 LR: c00138bc CTR: c00c0c08
REGS: c7ce1e40 TRAP: 0300 Not tainted (2.6.26)
MSR: 1032 CR: 24004024 XER
Hi all,
im trying to use the emaclite core which comes with the EDK10.1 with the
2.6.26 kernel from git.xilinx.com on virtex4fx12 minimodul. the emac is
detect by the kernel:
xilinx_emaclite xilinx_emaclite.0: MAC address is now 2: 0: 0: 0: 0: 0
xilinx_emaclite xilinx_emaclite.0: using fifo
I have checked that bit and it is not set. In fact, that register has
the same value as the one in our ADS8272 (0x100c), which works.
Anyway, it must be an issue of this kind, from the beginning I have
thought that we have a problem of arbitration of the bus that makes the
processor hang w