WIFI eeprom:
As discussed, it is impossible for nand and spi flash platforms to have the eeprom data available from mtd. I suggested to load the eeprom from user-space. I've looked into regular firmware loading but this is only possible when using modules. I've created a sysfs entry that allows reading and writing the eeprom data to the platform data. After loading the eeprom data I rely on pci-hotplug support to disable the bogus pci device and rescan the bus (with fixups and all). Because hotplug is not available, an init script is created that performs the copy from mtd to platform data. I think it is best to eventually move the sysfs functions to dev_wifi_athxk.c file, this would get rid of the external to the ath9k platform data.
SPI flash:
It seems that the spi-xway driver is not really working. It causes my kernel to crash in all sorts of ways. I added to bitbang SPI to be able to the calibration data mention above.
I've kept the original mtd partitioning that Netgear uses.
Buttons/LED:
Both buttons are working properly. Two leds are not enabled: The red internet led is connected to the pci_gnt1 pin... I can't disable it because then DMA stops working.
The green wifi led is connected to an unknown atheros gpio.
Signed-off-by: Pieter Voorthuijsen <p.voorthuijsen at gmail.com>
SVN-Revision: 31910
moves the linux partition, removes the config partition and the
buttons settings have small adjustments.
Signed-off-by: Luka Perkov <openwrt@lukaperkov.net>
SVN-Revision: 31909
Build images for D-Link DSL-274XB revision F1. Flashing
through original web UI as well as CFE works.
Known issues:
* wifi led inverted (on when wifi is off and vice cersa)
* same issues as generic bcm6328 support
SVN-Revision: 31885
BCM6328 support is in a usable state, with the following issues
* internal switch port not configurable
* external phys not supported
* broadcom wifis will probably not work correctly
* and all other generic bcm63xx issues (so yes, still no ADSL)
SVN-Revision: 31883
bcm_enetsw_probe did not properly reset port states, resulting in
connected ports staying disabled after bringing up the interface the
second time.
SVN-Revision: 31881
John Crispin