Re: CONFIG_PCI interaction with pata_platform driver on MPC834x board

2008-01-23 Thread Johns Daniel
I am asking this question once more since my previous try -- right
before the Christmas break -- did not elicit any responses!   ;~)

Without PCI support configured in the kernel, the CompactFlash card is
discovered and configured by the kernel. With PCI support configured
in the kernel, it fails to discover the CF card through the
pata_platform driver.

(Note that both PCI and CF work fine on this same board with the
generic IDE driver!)

There are only two differences that I notice between the two kernel
setups that might be significant:
1.) The libata virq changes from 19 to 20.
2.) The isa_io_base changes from 0x0 to 0xfcfff000.
Are either of these two changes significant?

I am using the arch/powerpc kernel, version 2.6.20.21. The CF is
wired directly to the local bus in True IDE mode.

I have some debug info included in my previous message at:

http://www.nabble.com/CONFIG_PCI-interaction-with-pata_platform-driver-on-MPC834x-board-tc14457502.html

TIA!

-- Johns
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Kernel boot hangs by parallel flood pings

2005-01-19 Thread Johns Daniel
I have had better luck with the following fcc_enet.c patch (against the ELDK 
2.4.4 kernel):

~
1.) In static void mii_display_status(struct net_device *dev):
 
if (!fep-link  !fep-old_link) {
/* Link is still down - don't print anything */
return;
}
 
printk(%s: status: , dev-name);
 
if (!fep-link) {
+netif_carrier_off(dev);
printk(link down);
} else {
+netif_carrier_on(dev);
printk(link up);
 
switch(s  PHY_STAT_SPMASK) {
~

2.) In fcc_enet_open(struct net_device *dev):

mii_do_cmd(dev, fep-phy-startup);
 #ifdef CONFIG_PM826
/* Read the autonegotiation results */
mii_do_cmd(dev, fep-phy-ack_int);
mii_do_cmd(dev, phy_cmd_relink);
 #endif /* CONFIG_PM826 */
+if (fep-link) {
+netif_carrier_on(dev);
+} else {
+netif_carrier_off(dev);
+}
netif_start_queue(dev);
return 0;   /* Success */
}
return -ENODEV; /* No PHY we understand */
 #else
fep-link = 1;
~

This communicates the link status to the kernel TCP/IP stack. Obviously, this 
assumes that MDIO is working!

-- Johns Daniel, Advent Networks, Inc.

-Original Message-
From:   linuxppc-embedded-bounces at ozlabs.org on behalf of Ho Lee
Sent:   Wed 1/12/2005 6:14 PM
To: 'linuxppc'
Cc: 'Steffen Rumler'
Subject:RE: Kernel boot hangs by parallel flood pings



-Original Message-
From:   linuxppc-embedded-bounces at ozlabs.org on behalf of Ho Lee
Sent:   Wed 1/12/2005 6:14 PM
To: 'linuxppc'
Cc: 'Steffen Rumler'
Subject:RE: Kernel boot hangs by parallel flood pings

I met the same problem in CPM driver, and there could be many 
solutions. I think the right place to fix is the fec driver. 
The fec driver registers interrupt handler during the 
initialization not when the device is opened, so it may
receive packets even the device is not up and running (also 
before the network subsystem is initialized) My fix was to 
ignore the received packets if the driver is not opened. 

--- linux-2.4.26.orig/arch/ppc/8xx_io/fec.c
+++ linux-2.4.26/arch/ppc/8xx_io/fec.c 
@@ -587,6 +587,9 @@
goto rx_processing_done;
}
 
+   if (!netif_running(dev))
+   goto rx_processing_done;
+
/* Process the incoming frame.
 */
fep-stats.rx_packets++;


Regards,
Ho

-Original Message-
From: [EMAIL PROTECTED]
[mailto:linuxppc-embedded-bounces at ozlabs.org] On Behalf Of Rune Torgersen
Sent: Wednesday, January 12, 2005 7:32 AM
To: Steffen Rumler; linuxppc
Subject: RE: Kernel boot hangs by parallel flood pings

--- Kernel.old/net/ipv4/ip_output.c Thu Jun  5 09:00:39 2003
+++ Kernel/net/ipv4/ip_output.c Thu Jun  5 09:00:28 2003
@@ -1087,11 +1087,11 @@

 void __init ip_init(void)
 {
-   dev_add_pack(ip_packet_type);
-
ip_rt_init();
inet_initpeers();

+   dev_add_pack(ip_packet_type);
+
 #ifdef CONFIG_IP_MULTICAST
proc_net_create(igmp, 0, ip_mc_procinfo);
 #endif



___
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded








PowerSpan II support

2003-06-27 Thread Johns Daniel

Anybody know of Linux software for the Tundra PowerSpan II PCI-to-60x
bridge? I would like to use the PSII with an 8260.

Thank you!

-- Johns


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





Running Linux From RAM

2003-06-06 Thread Johns Daniel

I would like to do some short-term development work on an evaluation
board. I was wondering whether I would be able to do this without
writing anything to the on-board FLASH -- which does have an embedded
monitor that will perform board initialization.

It is an 8260 board, and I have BDI2000 working on it. I can think of
two possibilities:
1. Use the BDI to download the Linux image to SDRAM. Execute the go
address command of the embedded monitor or the BDI.
2. Use the BDI to download U-Boot to SDRAM. Then get U-Boot to load the
Linux kernel.

Unfortunately, I need some more information:
- what Linux kernel target to make (make zImage?)
- what address to download the kernel or U-boot to
- what address to go to
- any customization necessary (e.g., hard code board info into the
embed_config.c file of arch/ppc/boot/simple/.)
- any sequence of steps that are critical

Any pointers or suggestions would be welcome!

-- Johns


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