mangoo wrote: jr wrote:
use no_phy_scan=1 parameter when loading ixp400_eth.ko.
Why? It doesn't seem to make a difference.
BTW, only two out of four ports work for me, is there some magic to manipulate it?
Well you already answered your own question: If you don't use no_phy_scan parameter only two of four ports work.
You can manage individual ethernet ports using "mii-diag" and "-p" parameter with port number. Link was posted to this same forum couple days ago. Regular "mii-tool" will work for WAN port, but not for LAN because it's internally connected to switch.
'm getting these from time to time (in dmesg):
Badness in dma_free_coherent at arch/arm/mm/consistent.c:351
There's one match on google when you search for that error saying it's bug in 2.6.15 kernel. Perhaps it's still present in in 2.6.16.
I also get "scheduling while atomic: ifconfig/0x00000001/930" error when running ifconfig with two ethernet interfaces active. Shutting either one of them down with "ifconfig ethx down" silences it. Might be related to netdevice_notifier and code that checks if MAC addresses are valid each time network device is probed as it does when you run ifconfig.
Status of FSG-3 with non-Freecom kernels:
* Board support: Ok with slightly modified NSLU2 patches (Machine ID, GPIO mapping, PCI INTs)
* IDE: Ok with slightly modified patch from VIA. Both SATA and PATA working.
* USB: Ok with stock 2.6.16 drivers. All ports work.
* Ethernet: Ok with driver from Intel and few patches. MAC address setup fixed based on NSLU2 code.
* I2C: Ok based on NSLU2 sources (GPIO's are 12/SDA and 13/SCL)
* RTC: Ok with single line patch to fix typo on original driver. Driver was posted to LKML couple weeks ago.
* FAN control and sensors: Ok with stock 2.6.16 drivers. lm-sensors report sensible values and I can control fan RPM thru pwm1 (0-255).
* Buttons: Not tested. I have made list of GPIO's and there's code I can copy from NSLU2 patches.
* Mini-PCI: Not tested. WLAN card on Mini-PCI slot detected, but haven't tried with drivers yet.
* LEDs: Not working, connected to IXP4XX_EXP_BUS_CS2. Seems led driver included with kernel doesn't support it yet (only GPIO leds). There's "ledman" from Snapgear for 2.6 that Freecom uses with 2.4 kernel, but I'd rather used standard interface.
* HW Crypto: Not tested. Sources downloadable from Intel, but I don't know if they work in little-endian mode at all.
* Kernel args: Kernel crashes on boot if trying to pass arguments to it.
Buttons shouldn't be a problem, but I'm not capable of writing LED support part. Also finding out why passing arguments to kernel causes crash is beyond my skills. I can try compiling hw crypto support but if it doesn't work as is then there's nothing I can do.
So far everything has been just taking code from here and there, fixing typos, offsets and machine specific mappings based on samples - that's easy part. Rest requires actual knowledge so someone else has to take care of them.
(Last edited by jr on 10 Jul 2006, 09:21)