This Ethernet driver is in early development stage and still has some problems.
This was working on my bcm4716 based device.
Thanks to Rafał Miłecki <zajec5@gmail.com> for writing this driver.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34995 3c298f89-4303-0410-b956-a3cf2f4a3e73
In addition check_module is not needed, nobody checks the return value.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34993 3c298f89-4303-0410-b956-a3cf2f4a3e73
Adjust the IRQ Flag value from 8 to 7 for I2S Core for BCM4716 and
BCM4748 (per the Broadcom SDK). IRQ Flag values greater than 7 are
ignored when setting the interrupt masks.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34990 3c298f89-4303-0410-b956-a3cf2f4a3e73
This was party inspirited by patches send by Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34989 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is the version like it was send for mainline inclusion.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34988 3c298f89-4303-0410-b956-a3cf2f4a3e73
The behaviour of calling 'mount' differed depending on whether it called
the busybox-mount, the mount of util-linux, the mount defined in
/lib/functions.sh and /lib/functions/boot.sh
/etc/preinit even included /lib/functions.sh and /lib/functions/boot.sh,
both re-defining 'mount'.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34792 3c298f89-4303-0410-b956-a3cf2f4a3e73
I noticed these changes when reviewing the 2011 Broadcom SDK. I haven't
noticed any obvious changes in behavior with them applied; but thought I
should at least pass them on.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34670 3c298f89-4303-0410-b956-a3cf2f4a3e73
The irq signal numbers that are send by the cpu are increased by 2 from
the number programmed into the mips core by bcma.
Return the irq number on which the irqs are send in bcma_core_irq() now.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34669 3c298f89-4303-0410-b956-a3cf2f4a3e73
These patches are not specific to bcm47xx and will be used on other
platforms as well.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34501 3c298f89-4303-0410-b956-a3cf2f4a3e73
The removed symbols are present in the generic configuration.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34404 3c298f89-4303-0410-b956-a3cf2f4a3e73
The removed symbols are present in the generic configuration.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34403 3c298f89-4303-0410-b956-a3cf2f4a3e73
The ASUS WL-520gU and some other similar Asus devices have a BCM5354
running at 200MHZ and not at 240 which is the default for this SoC.
This fixes#4083.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34325 3c298f89-4303-0410-b956-a3cf2f4a3e73
In the old configuration the SoC issued a reboot if the watchdog was
killed also if it was kill with TERM and not KILL.
This will fix#11724.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34324 3c298f89-4303-0410-b956-a3cf2f4a3e73
This watchdog driver should work with SoC having a PMU.
This fixes#11720.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34323 3c298f89-4303-0410-b956-a3cf2f4a3e73
For sysupgrade the generic image should be used and the special image for the wgt634u is just needed for initial flashing over CFE.
russell reported that with this patch sysupgrdae did not worked for him any more and he could not reproduce the error described in #11420.
With the patch the linux partition also contained the loader which is in the first 128KB.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34201 3c298f89-4303-0410-b956-a3cf2f4a3e73
CONFIG_SSB_DRIVER_GIGE is set in the target config of the brcm47xx target, so it will always be activated and the kmod-ssb-gige is not needed any more.
The kmod-ssb-gige package is not generated in an build as it does not contain any files and the makes the image builder fail when generating a image integrating this package.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34150 3c298f89-4303-0410-b956-a3cf2f4a3e73
The image format for the wgt634u is different from the normal format.
Without this patch the partition parser detects a 128kb bigger
partition after every update.
This closes#11420
Thank you b.sander for the patch.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33935 3c298f89-4303-0410-b956-a3cf2f4a3e73
* update the flash driver for bcm47xx to use the stubs already in bcma
* do some misc enhancements to the flash drivers for bcm47xx
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33920 3c298f89-4303-0410-b956-a3cf2f4a3e73
Before it was tried to initialize the deactivated PCIe core in client
mode, but this causes the SoC to hang. Just do not initialize it at all
and ignore the core it is not working and nothing is connected to it
when the specific bit is set in the boardflags.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33620 3c298f89-4303-0410-b956-a3cf2f4a3e73
Sometimes the PCIe card indicates that it has a sprom somewhere and we
are able to read the memory region, but it is empty and not valid. In
these cases we should try to use the fallback sprom as a last chance.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33601 3c298f89-4303-0410-b956-a3cf2f4a3e73
The chip common and the PCIe code are accessing the sprom struct which
is not filled when these cores are initialized. Fix this by adding an
early initialize and fill the sprom struct before accessing it in other
code.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33600 3c298f89-4303-0410-b956-a3cf2f4a3e73
The bcma based SoCs with a ieee80211 core on the SoC and an other
connected via PCIe or USB store the sprom for the SoC with a sb/1/
prefix. The SoC with just one wifi core do not use prefixes. The
BCM4706 do not use a prefix for the SoC part at all, because the prefix
is the path to the ieee80211 core and there is non on the BCM4706.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33597 3c298f89-4303-0410-b956-a3cf2f4a3e73
Sometimes the port 0 was the WAN port or there could be some device
where the port 0 is not wired to an actual Ethernet port. Now telnet in
failsafe will listen on all ports of the switch so user do not have to
search for the correct port any more. This change will make the switch
leak traffic between the WAN and the LAN port, but you should not use
failsafe while connected to a untrusted network.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33544 3c298f89-4303-0410-b956-a3cf2f4a3e73
When not removing support for the wait instruction, when ruining on the
BCM4706 SoC the system stops after msleep() without an exception. I
haven't seen this problem on the other Broadcom SoCs with a 74K CPU,
but in the Broadcom SDK it is deactivated for all CPUs of this type.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33496 3c298f89-4303-0410-b956-a3cf2f4a3e73
There are some ifdefs missing so when only ssb or only bcma was
selected in the kernel config it did not build.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33209 3c298f89-4303-0410-b956-a3cf2f4a3e73
I did not add the last patch, because it add some stubs for the flash drivers and our patches have to be changed for that, if the flash support in bcma is able to do something I will integrate it.
This also contains 3 additional patches fixing some bugs in bcma.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32880 3c298f89-4303-0410-b956-a3cf2f4a3e73
The dcache bug that it works around is a generic issue, not a brcm47xx cache quirk
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32395 3c298f89-4303-0410-b956-a3cf2f4a3e73
Now tg3 works with the Ethernet core of the Linksys WRT610N v1 (again).
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31694 3c298f89-4303-0410-b956-a3cf2f4a3e73
The existing code (prior to the patch) does an "ioremap_nocache" on a
subset of a memory region that I think has already been mapped, and then
un-maps that smaller region when it is finished.
Thanks Nathan Hintz for the patch
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31481 3c298f89-4303-0410-b956-a3cf2f4a3e73
Noticed these while reviewing the code.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31471 3c298f89-4303-0410-b956-a3cf2f4a3e73
Because of api change of nvram_getenv, the workaround failed to detect the hardware.
Based on patch by b.sander
Fixes#11268.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31470 3c298f89-4303-0410-b956-a3cf2f4a3e73
Also remove a duplicate patch from lantiq (already in generic).
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31158 3c298f89-4303-0410-b956-a3cf2f4a3e73
This probably doesn't matter, but reads/writes are always 4 bytes, so always map 4 bytes.
Changes since v1: Moved changes to new patch file (234-bcma-always-map-4-bytes.patch).
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31119 3c298f89-4303-0410-b956-a3cf2f4a3e73
This patch add support for the NAND flash on BCM5357 based devices like the WNR3500Lv2.
Thank you Tathagata Das <tathagata@alumnux.com> for the patch
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30943 3c298f89-4303-0410-b956-a3cf2f4a3e73
The patches are now grouped by the part what they are doing and are using three digest numbers.
This does not remove or adds anything
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30942 3c298f89-4303-0410-b956-a3cf2f4a3e73
The SPROM is initialized in bcm47xx_fill_sprom, so move the call to bcm47xx_fill_sprom_ethernet after it.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30873 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is commented out until we get report of working devices.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30639 3c298f89-4303-0410-b956-a3cf2f4a3e73
This adds support for parsing sprom form nvram for sprom version form 1 to 9.
It also adds sprom from nvram support for devices on the bcma bus.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30638 3c298f89-4303-0410-b956-a3cf2f4a3e73
These devices have two devices on the bus, the host controller itself and the device.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29923 3c298f89-4303-0410-b956-a3cf2f4a3e73
This also adds minimal support for the BCMA43224 pcie wireless card.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29843 3c298f89-4303-0410-b956-a3cf2f4a3e73
Add workarround for BCM5357 and BCM4749.
This patch contains the following fixes from George Kashperko:
* separate subroutines for controller initialization workarounds -
following CodingStyle recommendations;
* __devinit __devexit __devinitconst annotations for CONFIG_HOTPLUG;
* fix leak in ssb_hcd_create_pdev/bcma_hcd_create_pdev - as hci_res being
kmalloc'ed is never freed anywhere while platform_device_add_resources
will kmemdup resources right away;
* fix compilation error in ssb_hcd_resume - it will fail as soon as
CONFIG_PM is selected.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29734 3c298f89-4303-0410-b956-a3cf2f4a3e73
This new usb driver uses an extra device so the ehci and the ohci driver are not depending on ech other any more.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29575 3c298f89-4303-0410-b956-a3cf2f4a3e73
There are problems with the patches for kernel 2.6.39 and I do not want to support two different sets of patches.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29573 3c298f89-4303-0410-b956-a3cf2f4a3e73
Hi,
this patch adds the correct vlan definitions for the Siemens SE505v2. It
applies to trunk as well as backfire (please apply here too). On
backfire this also patches brcm-2,4, because brcm47xx base-files is just
symlinked to brcm-2.4.
It also fixes two whitespace issues.
Tested with brcm47xx on both trunk and backfire branch and works as
expected.
Signed-off-by: Manuel Munz <freifunk@somakoma.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@28336 3c298f89-4303-0410-b956-a3cf2f4a3e73
As this target changes often these days it is hard to support more kernel versions. Now only kernel 3.0 is supported.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27906 3c298f89-4303-0410-b956-a3cf2f4a3e73
* this adds sflash support for ssb devices
* the flash is now a platform device
* minor updates
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27902 3c298f89-4303-0410-b956-a3cf2f4a3e73
ssb_pcicore_fix_sprom_core_index accesses the sprom on the pci bus but
this causes a data bus error (oops) on a SoC.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27758 3c298f89-4303-0410-b956-a3cf2f4a3e73
Now we can assume that every brcm47xx kernel has the bcma module build
into the kernel. This is not needed for this version as this does not
support bcma as system bus but kernel 3.0 will.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27733 3c298f89-4303-0410-b956-a3cf2f4a3e73
* add new patches for bcm4716 SoC
* add support for serial flash on bcma bus
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27723 3c298f89-4303-0410-b956-a3cf2f4a3e73
The image will not boot because serial flash support is missing this is only for experts.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27302 3c298f89-4303-0410-b956-a3cf2f4a3e73
Ethernet and wifi are not working and this is highly experimental.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27301 3c298f89-4303-0410-b956-a3cf2f4a3e73
2.4 isn't present anymore, so it will always be 2.6 (or newer). Since the
2.6 check will break with 3.0, remove it alltogether.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27185 3c298f89-4303-0410-b956-a3cf2f4a3e73
The flash driver code should be cleaned up and the broad detection code should be placed into arch code and used here.
This fixes#9323
Thank you Will Holmes for the patch.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27005 3c298f89-4303-0410-b956-a3cf2f4a3e73
If there is no sprom on an ssb based pci device on the brcm47xx
architecture ssb now asks the architecture code to look into the nvram
to get some sprom data for this device. Now we are able to read out
pci/1/1/ foo or pci/1/3/ foo config options.
This will fix some problems where the wireless devices does not got an
mac address and the following message was show:
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26801 3c298f89-4303-0410-b956-a3cf2f4a3e73
This package creates some error messages on startup
Thank you russell-- for reporting
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26240 3c298f89-4303-0410-b956-a3cf2f4a3e73
The Netgear wgt634u uses minus between the hex digest of the mac
address and all other broadcom devices are using colons between the hex
digest. Now the mac address is correctly parsed also when minus is used.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@24749 3c298f89-4303-0410-b956-a3cf2f4a3e73
This fixes a problem with wrt350n.
It boots only if this config option is set, otherwise it reboots after "Switching to clocksource MIPS"
Thank you sn9 for fixing this problem.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@24626 3c298f89-4303-0410-b956-a3cf2f4a3e73
Broadcom removed these pci id, but at least the wrt350n has a Ethernet
controller with a pci id of 14e4:1676
Thank you sn9 for fixing this problem.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@24625 3c298f89-4303-0410-b956-a3cf2f4a3e73
Backport patches from r24162
brcm47xx: reorder patches like they were commitet upstream
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@24266 3c298f89-4303-0410-b956-a3cf2f4a3e73
0x4243) functionality. Revert that patch until we get a proper fix.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@24096 3c298f89-4303-0410-b956-a3cf2f4a3e73
Readd the workarround from the old version again which was removed in r22296 and refresh the patches.
This should close#7874
Thank you Russell Senior for testing.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@23911 3c298f89-4303-0410-b956-a3cf2f4a3e73
Reading the CFE properties causes system hangs on some devices. With
this patch nvram read will be successful very time so cfe will no be
read out. This code is not really correct but it will work around some
problems for some people.
Related ticket: #7693
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22663 3c298f89-4303-0410-b956-a3cf2f4a3e73
Thank you realopty for the patch.
tools/firmware-utils/src/mkchkimg.c is from http://www.myopenrouter.com/download/10611/mkchkimg/
This closes#7702.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22516 3c298f89-4303-0410-b956-a3cf2f4a3e73
space is used to store config values. When overwriting it the device
will not start any more.
closes#7630
Thank you realopty for testing.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22475 3c298f89-4303-0410-b956-a3cf2f4a3e73
* fix return codes of nvram_getenv. Now it behaves like cfe_getenv.
* also check cfe for kernel_args param.
* some style fixes
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22424 3c298f89-4303-0410-b956-a3cf2f4a3e73
CFE does not boot images generated with these checksums because of
wrong checksum.
After flashing then with tftp to my Asus wl500-GPv1 the following messages
are show:
Null Rescue Flag.
Boot program checksum is invalid
Hello!! Enter Rescue Mode: (Check error)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22418 3c298f89-4303-0410-b956-a3cf2f4a3e73
* reduce image size for CRC calculation by fs_mark size
sysupgrade sometimes failed for me and I noticed that it was due
to incorrect CRC values in trx-header after performing it.
It seems that the fs_mark was completely included in the calculation
and that it was nevertheless modified by sysupgrade while appending
the jffs data.
This only occurs for the first boot after sysupgrade as the flashmap
driver recalculates the CRC to an even smaller area when it boots.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22396 3c298f89-4303-0410-b956-a3cf2f4a3e73
more and more users are getting confused by this, and consider it a regression in brcm47xx,
because brcm-2.4 was not showing this message. It's not particularly interesting for debugging,
most of the time it only happens because of an unconnected port.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22110 3c298f89-4303-0410-b956-a3cf2f4a3e73
some CFE versions (i.e. WRT54G3Gv2-VF) expect two separate firmware
images which each consume half of the available flash space.
these changes check for the TRX header version and set the partition
size correctly.
Tested on G3Gv2-VF and Asus WL-500GP
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22019 3c298f89-4303-0410-b956-a3cf2f4a3e73
'factory' and 'sysupgrade' did not make much sense. A discussion
with jow convinced me that .trx results in a helpdesk disaster.
So I decided to use '.bin' for normal bin-headers and '.noheader.bin'
for the trx-v2 image.
I fixed the wiki accordingly.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22013 3c298f89-4303-0410-b956-a3cf2f4a3e73
It is selected by CONFIG_JFFS2_LZMA which is set in the generic config.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@21437 3c298f89-4303-0410-b956-a3cf2f4a3e73
* update pointers in struct hc_driver
* make ssb_ehci_detach more look like the pci version
* remove resume and suspend as they are never activated and not compiling
* replace ssb_ehci_start with ehci_run as it only calls this method
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@21427 3c298f89-4303-0410-b956-a3cf2f4a3e73
Disable some calls the WRT54G3G implementation does not like
and enable interrupts to allow hotplugging.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@20240 3c298f89-4303-0410-b956-a3cf2f4a3e73
The defined offset is wrong and the fixup-code overrides it
later on so that it never gets used for most PCI devices.
Unfortunately the yenta-socket allocates its own resources
and crashes because of the wrong mem_offset.
It seems that the offset and fixup code came from 2.4 where
resource allocation was handled differently.
This patch removes the unneeded parts and thus enables
the yenta_socket on the WRT54G3G platform.
It was tested on Asus WL500G-Premium (v1 and v2), Linksys
WRT54G3G, Netgear WGT634U
Signed-off-by: Michael Buesch <mb@bu3sch.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@20239 3c298f89-4303-0410-b956-a3cf2f4a3e73
The patch commited in r18413 was wrong.
This patch prevents prom_init_mem from scanning over 128MB ram.
This is from #6765 and #3177
Refresh all patches
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@20072 3c298f89-4303-0410-b956-a3cf2f4a3e73
Explicitely enable shared interrupt 2 for any core that didn't get a dedicated IRQ
anymore (fallthrough case) and for EXTIF cores to make gpio interrupts work.
Also remove a bogus comment.
Signed-off-by: Jochen Friedrich <jochen@scram.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@19895 3c298f89-4303-0410-b956-a3cf2f4a3e73
Hauke Mehrtens
Mirko Vogt
Gabor Juhos
Florian Fainelli
Imre Kaloz
Jonas Gorski
John Crispin
Felix Fietkau
Jo-Philipp Wich
Alexandros C. Couloumbis
Markus Wigge
Daniel Dickinson
Nicolas Thill
Lars-Peter Clausen
Travis Kemen
Michael Büsch