Anyone try to use a 3com NIC card on the Walnut board?
I can load the module but when I try to bring up the
interface I get a stream of bus errors.
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
eth1: PCI bus error, bus status 80000020
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
eth1: PCI bus error, bus status 80000020
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
I am using the 2.4.2 version of the Walnut kernel dated
Mar 1 on the ftp site.
There are changes to the 3com driver in the pre patches
but I have not tried it yet.
Most docs say this is a hardware failure so I might want
to change the PCI slot I am using.
Has anyone successfully used a PCI network card in the
Walnut board.
If it is just a driver bug I do not want to spend time
fixing it, I would just want to get a card that works.
I just want to do some perf testing on board itself.
Thanks
--
Andrew May
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Well switching the card to J25 PCI Slot 3 seems to solve
the problem.
I was using J31 Slot 0. The docs on the board say that this
slot can be used with a 3.3v card at 66MHz if the connector
is reversed.
Since the connector on my board is in the 5v config, I
would hope the programming resistors were shipped in
the correct config, but I did not check.
So I don't know what the problem was and I don't really
care, but I will just stay away from using J31 for now.
On Wed, Mar 14, 2001 at 02:53:58PM -0800, andrew may wrote:
Anyone try to use a 3com NIC card on the Walnut board?
I can load the module but when I try to bring up the
interface I get a stream of bus errors.
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
eth1: PCI bus error, bus status 80000020
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
eth1: PCI bus error, bus status 80000020
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
I am using the 2.4.2 version of the Walnut kernel dated
Mar 1 on the ftp site.
There are changes to the 3com driver in the pre patches
but I have not tried it yet.
Most docs say this is a hardware failure so I might want
to change the PCI slot I am using.
Has anyone successfully used a PCI network card in the
Walnut board.
If it is just a driver bug I do not want to spend time
fixing it, I would just want to get a card that works.
I just want to do some perf testing on board itself.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Hi,
I am writting a code to automatically suspend the CPU (MPC823) and system
after it goes idle a few minutes.
I try to modify the idled() function in /arch/ppc/kernel/idle.c to count if
the CPU running in this code more than 5 minutes without reschedule , so I
will consider it idle.
for(;;)
{
if(work) start_idle = jiffies;
if(jiffies - start_idle > HARD_IDLE_TIMEOUT) {
detect_idle(); // suspend CPU here
}
work = current->need_resched;
__sti();
check_pgt_cache();
....
}
However just after every 20s, the current->need_resched turn on, as a result
I can not detect the system idle (I already kill all process, excepet
init,kupdate,bdflush,sh).
I found out the init will automatically wake up after 20s.
My question is:
1. How the Linux Kernel for PC do this? I can see PC will automatically
suspend after 15 minutes.
2. Where should be the best place to put the suspend code ? (in idled() ?)
3. Is there anyone have implemented this feature for MPC823, where can I get
the information?
Thank in advances
Jerry
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/