The uImage target will always fail on a clean build due to dependency issues.
Building the uImage isn't necessary anyway as its re-built with correct
entry points in image/Makefile so remove it.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 39778
Update our copies of the brcm2708 patches to the latest rpi-3.10-y
rebased against linux-3.10.y stable (3.10.32). This should hopefully
make it easier for us in the future to leverage the raspberry/rpi-*
branches.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39770
Define KERNELNAME to Image to get the build system to copy this image
over $(KDIR) automatically for us.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39768
We already clean up tx descriptors in the napi eth_poll() function so it
would likely be rare to run out of available descriptors in eth_xmit. Thus
we can clean them up only when needed and return busy only when we
still don't have enough.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 39762
The combination of r35942 and r35952 causes an issue where eth_schedule_poll()
can be called from a different CPU between the call to napi_complete() and the
setting of cur_index which can break the rx ring accounting and cause ethernet
latency and/or ethernet stalls. The issue can be easilly created by adding
a couple of artificial delays such as:
@@ -715,6 +715,7 @@ static int eth_poll(struct napi_struct *napi, int budget)
if (!received) {
napi_complete(napi);
+udelay(1000);
enable_irq(IRQ_CNS3XXX_SW_R0RXC);
}
@@ -727,6 +728,7 @@ static int eth_poll(struct napi_struct *napi, int budget)
rx_ring->cur_index = i;
wmb();
+udelay(1000);
enable_rx_dma(sw);
return received;
This patch moves the setting of cur_index back up where it needs to be and
addresses the original corner case that r35942 was trying to catch in an
improved fashion by checking to see if the rx descriptor ring has become
full before interrupts were re-enabled so that a poll can be scheduled again
and avoid an rx stall caused by rx interrupts ceasing to fire again.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 39761
The IMX6 SoC uses an ARM Cortext-A9 which has both NEON and VFPv3 hardware
blocks. This will tune gcc to use neon instead of vfpv3 which will outperform
VFPv3.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 39760
The OpenWrt build system uses MACHINE_FEATURES of fpu to set the HAS_FPU which
in turn sets the default of CONFIG_SOFT_FLOAT as well as uClibc configuration.
As the IMX6 SoC has both vfpv3 and NEON hardware support we want to add fpu
to the feature list. This will default the IMX6 target to use -mfloat-abi=hard
which will the be most efficient use of floating point.
When switching to hard float, we also need to enable VFP support in the kernel.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 39759
We were copying the actual vmlinux-initramfs.elf kernel which cannot be
launched by QEMU or a real bootloader, use zImage-initramfs instead.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39756
The ar71xx platform always uses the eth0 interface to provide
access to the device in failsafe mode. Due to this, failsafe
access is broken on devices where the LAN ports are connected
to the 'eth1' interface.
Update the relevant script to correctly set the ifname variable
for these devices.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39752
Add support for 3.13 as a development kernel. Mostly untested, only net
booted. If flashed may brick your router or kill your cat.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39746
Let the switch start the carrier and set the duplex mode independently
if this nic is up of not.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 39733
We did not start the PHY when an external phy was in use. Without this
patch the driver uses half duplex mode and the switch uses full duplex
mode, which causes problems.
Thank you fback for spotting this problem.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 39719
The RB91x boards are using a serial shift register
connected to the SPI bus to drive some of the LEDs.
Rework the board setup code to register a SPI device
for that. This makes it possible to use the 'spi-74x164'
driver to control the device.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39703
That will be used to drive the 74HC595 serial-in/parallel-out
8-bits shift register which can be found on some RouterBOARDs.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39702
The serial flash devices used on the ROuterBOARDs are
supporting 4KiB erase blocks. Enable the small sector
erase option in the m25p80 driver to avoid superfluous
erase/write of adjacent blocks.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39696
This is a backported patch for the gianfar ethernet driver
used in TPLink 4900 v1. It is supposed to fix the error which
show up in dmesg with:
NETDEV WATCHDOG: eth0 (fsl-gianfar): transmit queue xy timed out
Full upstream patch is at: http://patchwork.ozlabs.org/patch/271242
Signed-off-by: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
SVN-Revision: 39692
Only netboot tested, so no images or now.
GbE ports are only working in FE mode, and leds do not work.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39679
Completely untested except for booting from network; wan port
only works in 10/HD, lan1 only in 100/FD.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39678
BCM63168 has 6 ports (3 FE PHY, 1 GE PHY, two RGMII) and BCM63268
has two additional RGMII ports, making it 8.
Fix this by checking the chip variant and applying an appropriate
limit.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39677
Support for Asmax AR 1004g router
Signed-off-by: Adrian Feliks <mexit@o2.pl>
Patchwork: http://patchwork.openwrt.org/patch/4464/
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39674
This adds profile and build image for Sagemcom F@st2704, using b43
driver.
For WiFi to work properly BCMA fallback SPROM support patch must
be applied (http://git.io/z1Ki8A).
Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4212/
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39673
This adds userspace support for Sagemcom F@st 2704 router.
Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4215/
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39672
This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
router.
It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
modem equipped with 64 MiB RAM and 8 MiB flash.
Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4266/
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39671
Update the Ventana device-tree to match upstream:
- Add IMX6Q/IMX6DL variants for GW54xx/GW53xx/GW52xx/GW51xx
- align pinctrl with upstream
- consolidate multiple patches into one
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 39644
I noticed that the patch at http://patchwork.openwrt.org/patch/4017/
for adding support for the MikroTik RouterBOARD 951Ui-2HnD had been
abandoned because it wasn't generated and sent to the mailing list
correctly and doesn't apply as a result. I have cleaned up this patch.
When testing this on real hardware, I also noticed that wireless didn't
work, so this patch fixes that as well.
This patch applies cleanly to SVN 39392.
Signed-off-by: Matthew Reeve <mreeve@tenxnetworks.com>
Patchwork: http://patchwork.openwrt.org/patch/4773/
[juhosg:
- drop the 'rb951ui_wlan_init' function and rework the code to
use the recently introduced rb95x_wlan_init function instead,
- fix GPIO number of the port5 LED,
- rename LEDs according to the standard LED naming conventions,
and use 'rb' prefix in the names]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39641
This is a backport of code to improve the quality of fq_codel
hashing for 3.10 for some encapsulated protocols.
Not needed in 3.11 and later.
Patch-by: Dave Taht <dave.taht@bufferbloat.net>
Patchwork: http://patchwork.openwrt.org/patch/4902/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39640
Patch-by: TenNinjas <tenninjas@tenninjas.ca>
Patchwork: http://patchwork.openwrt.org/patch/4849/
[juhosg:
- use the Archer C7 specific LED setup instead of adding
identical code]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39636
This missing bit of the hack saves hugely on instruction traps
on tcp connections to ar71xx based routers.
Patch-by: Dave Taht <dave.taht@bufferbloat.net>
Patchwork: http://patchwork.openwrt.org/patch/4905/
[juhosg: adjust subject, refresh kernel patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39626
Solves ticket #14356 <https://dev.openwrt.org/ticket/14356>
Without this patch, UART output will show only 4 partitions:
[ 0.740000] 4 cmdlinepart partitions found on MTD device spi0.0
[ 0.750000] Creating 4 MTD partitions on "spi0.0":
[ 0.750000] 0x000000000000-0x000000050000 : "u-boot"
[ 0.760000] 0x000000050000-0x000000070000 : "u-boot-env"
[ 0.770000] 0x000000070000-0x0000007f0000 : "firmware"
[ 0.790000] 0x0000007f0000-0x000000800000 : "art"
and then linux complains :VFS: Cannot open root device "(null)"
With this patch, UART out will show 7 partitions:
[ 0.740000] 4 cmdlinepart partitions found on MTD device spi0.0
[ 0.750000] Creating 4 MTD partitions on "spi0.0":
[ 0.750000] 0x000000000000-0x000000040000 : "u-boot"
[ 0.760000] 0x000000040000-0x000000050000 : "u-boot-env"
[ 0.770000] 0x000000050000-0x0000007f0000 : "firmware"
[ 0.780000] 2 netgear-fw partitions found on MTD device firmware
[ 0.780000] 0x000000050000-0x00000014b440 : "kernel"
[ 0.790000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.800000] 0x00000014b440-0x0000007f0000 : "rootfs"
[ 0.810000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.820000] mtd: device 4 (rootfs) set to be root filesystem
[ 0.830000] 1 squashfs-split partitions found on MTD device rootfs
[ 0.830000] 0x000000340000-0x0000007f0000 : "rootfs_data"
[ 0.840000] 0x0000007f0000-0x000000800000 : "art"
This patch is tested against r39502 of trunk.
Signed-off-by: Jonathan Chang <changcs@santos.ee.ntu.edu.tw>
Patchwork: http://patchwork.openwrt.org/patch/4870/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39625
The board is optimized for ubi(fs) and boots OpenWrt without changes to uboot
environment if OpenWrt's uboot package is used. In order to flash the image run
following commands in uboot shell:
nand erase 0x200000 0xfe00000
ubi part root ; ubi remove rootfs ; ubi create rootfs
tftpboot 0x800000 openwrt-kirkwood-dockstar-rootfs.ubifs ; ubi write 0x800000 rootfs ${filesize} ; reset
Signed-off-by: Luka Perkov <luka@openwrt.org>
Tested-by: Alexander Couzens <lynxis@fe80.eu>
CC: Imre Kaloz <kaloz@openwrt.org>
SVN-Revision: 39593
The board is optimized for ubi(fs) and boots OpenWrt without changes to uboot
environment if OpenWrt's uboot package is used. In order to flash the image run
following commands in uboot shell:
nand erase 0x200000 0xfe00000
ubi part root ; ubi remove rootfs ; ubi create rootfs
tftpboot 0x800000 openwrt-kirkwood-ib62x0-rootfs.ubifs ; ubi write 0x800000 rootfs ${filesize} ; reset
Signed-off-by: Luka Perkov <luka@openwrt.org>
Tested-by: Luka Perkov <luka@openwrt.org>
CC: Imre Kaloz <kaloz@openwrt.org>
SVN-Revision: 39592
Previous patch was pushed due to false user report. While at it fix alphabetic
ordering.
The board is optimized for ubi(fs) and boots OpenWrt without changes to uboot
environment if OpenWrt's uboot package is used. In order to flash the image run
following commands in uboot shell:
nand erase 0x200000 0x1fe00000
ubi part root ; ubi remove rootfs ; ubi create rootfs
tftpboot 0x800000 openwrt-kirkwood-iconnect-rootfs.ubifs ; ubi write 0x800000 rootfs ${filesize} ; reset
Signed-off-by: Luka Perkov <luka@openwrt.org>
CC: Imre Kaloz <kaloz@openwrt.org>
SVN-Revision: 39591
Some ARV4510PW units seem to have unstable PCI due to missing pull-up
resistors. This patch makes sure that the GPIO lines are driven properly.
Signed-off-by: Matti Laakso <malaakso@elisanet.fi>
SVN-Revision: 39587
The mtdpartsize macro triggers shell errors on various Linux distributions
when the partname argument $(1) does not appear within the partmap $(2).
Change the sed pattern to only emit anything if a successful substitution
occured and only evaluate the arithmetic expression if something was printed
by the sed program.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
SVN-Revision: 39583
This Armada XP GP board from Marvell comes with:
* 2GB DDR3 DIMM
* 1GB NAND flash (8-bit interface)
* 16MB NOR flash (16-bot interrface)
* 16MB SPI flash
* SDIO module
* 3 PCIe
* 1 SATA link
* 2 USB EHCI
* 1 internal SSD
* 4 Ethernet Gigabit
* 1 RS232 port over USB
Signed-off-by: Seif Mazareeb <seif.mazareeb@gmail.com>
SVN-Revision: 39568
The config-3.10 doesn't specify the configuration of the backported PCI
features, and the Marvell EBU Device Bus Controller, this will prevent
a clean compile. This patch enables these features to archive a clean compile
without having to specify the state of these configuration after starting to
compile.
Signed-off-by: Seif Mazareeb <seif.mazareeb@gmail.com>
SVN-Revision: 39567
This is a backport of the patches accepted to the Linux mainline related to
mvebu SoC (Armada XP and Armada 370) between Linux v3.12, and Linux v3.13.
This work mainly covers:
* Finishes work for sharing the pxa nand driver(drivers/mtd/nand/pxa3xx_nand.c)
between the PXA family, and the Armada family.
* timer initialization update, and access function for the Armada family.
* Generic IRQ handling backporting.
* Some bug fixes.
Signed-off-by: Seif Mazareeb <seif.mazareeb@gmail.com>
CC: Luka Perkov <luka@openwrt.org>
SVN-Revision: 39566
This is a backport of the patches accepted to the Linux mainline related to
mvebu SoC (Armada XP and Armada 370) between Linux v3.11, and Linux v3.12.
This work mainly covers:
* Ground work for sharing the pxa nand driver(drivers/mtd/nand/pxa3xx_nand.c)
between the PXA family,and the Armada family.
* Further updates to the mvebu MBus.
* Work and ground work for enabling MSI on the Armada family.
* some phy / mdio bus initialization related work.
* Device tree binding documentation update.
Signed-off-by: Seif Mazareeb <seif.mazareeb@gmail.com>
CC: Luka Perkov <luka@openwrt.org>
SVN-Revision: 39565
This is a backport of the patches accepted to the Linux mainline related to
mvebu SoC (Armada XP and Armada 370) between Linux v3.10, and Linux v3.11.
This work mainly covers:
* Enabling USB storage, and PCI to mvebu_defconfig.
* Add support for NOR flash.
* Some PCI device tree related updates, and bus parsing.
* Adding Armada XP & 370 PCI driver, and update some clock gating
specifics.
* Introduce Marvell EBU Device Bus driver.
* Enaling USB in the armada*.dts.
* Enabling, and updating the mvebu-mbus.
* Some SATA and Ethernet related fixes.
Signed-off-by: Seif Mazareeb <seif.mazareeb@gmail.com>
CC: Luka Perkov <luka@openwrt.org>
SVN-Revision: 39564
smsc95xx.ko depends on crc16.ko on kernel >= 3.8
There was an additional kmod-usb-net-smsc95xx definition in the mxs
target code which conflicted with the one in the common area.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 39562
This adds empty definitions for the PCI quirks functions when they
should not be included in the kernel.
This is based on a patch by Daniel <daniel@makrotopia.org>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 39534
The int brnf_call_ebtables in the header should be extern, otherwise
every object file gets its own int and they will conflict when linking
the binary.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 39533
These should either be disabled or not present in the config, else
they might cause build issues because of unexpected unpackaged
modules, as it is the case for LEDS_CLASS.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39529
The 3.10.x infrastructure has been present for some time, and seems to
run fine here.
Signed-off-by: Russell Senior <russell@personaltelco.net>
SVN-Revision: 39483
It was recently sent to linux-mips for comments. It adds workaround for
WNR3500L to enable USB port.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 39469
This does not add any new features, just some changes to the patches
and a first try to use dt to set the irqs.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 39466
The original dragino2 board support was missing some changes from the
upstream svn repository (http://svn.dragino.com/dragino2) that supported
sysupgrade.
[juhosg: change subject]
Signed-off-by: Karl Palsson <karlp@remake.is>
Patchwork: http://patchwork.openwrt.org/patch/4801/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39429
Since the yaffs code update (r39084), it is not
possible to install OpenWrt on RouterBoards with
small-page NAND chips. Fix the yaffs code to make
it work again.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39409
The 3.6 kernel isn't used by any of the x86 subtargets, so remove it.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39403
Use the 'swconfig_trig_set_brightness' function to set
the brightness value of the LED when the link goes down.
This ensures that the last brighness value is saved into
a local variable which is used to track the actual LED
status.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39402
On recent TL-WDR4300 boards the external LNAs of the 2.4GHz
interface are connected to GPIO lines. Because these GPIO
lines are disabled by default, the RX sensitivity of the
device is quite bad.
Setup the GPIOs of the external LNAs to fix the issue.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39392
Get the size of the mtd partitions directly from the
MTD layout and remove the superfluous macro parameters.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39384
The macro checks the size of the rootfs image even if
the second parameter of the macro contains the size of
an eraseblock. It is wrong because the size of the
kernel image will be adjusted to the next eraseblock
and the resulting image might be too large.
Fix the macro to check the size of the final image
instead of the rootfs image.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39383
This reverts r38197.
The automatically created firmware partition includes
the partition_table partition. Apart from the partition
table, this partition contains sensitive data on some
Compex devices which data can be destroyed when the
firmware partition gets modified. Revert the change to
prevent that.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39382
Since that was the last configuration in defconfig directory we can drop the
defconfig init script too.
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 39373
The default inittab uses "askconsole" which is implemented by procd
and uses the console provided by the kernel command line.
Hence, this platform specific workaround is not necessary anymore.
Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39367
Add kernel support for the BCM963269BHR board, USB and Ethernet switch,
LEDs and buttons are working.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39363
Allow using the HSSPI controller since it works just fine, as well as
the integrated switch core, since that one works too.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39362
The HIFN driver is a PCI driver, thus requires PCI support to be enabled
to compile. Therefore let it depend on PCI..
Should fix mvebu builds.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39357
The eth5 LED on the RB2011 is not working because the
LED control rule is missing. Fix it.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39335
Update a few devices with their actual port numbers, especially those
with two ports.
Should allow properly using the second port on the Neufboxen and HW553
and HW556.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39325
Allow setting the number of available usb host ports for boards with
additional sanity checks to allow using the second port on devices
where it is available.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39324
USB will fail to work if compiling with BCM6318 only if BCM63XX_HAS_EHCI
and BCM63XX_HAS_OHCI are not selected.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39322
Return the same clock for usbh and usbd on BCM6318 to prevent the clock
getting disabled despite being supposed to be enabled, e.g. by the
following sequence:
clk_enable(usbh); <- usbh->usage = 1, enabled
clk_enable(usbd); <- usbd->usage = 1, enabled (no effect)
clk_disable(usbd); <- usbd->usage = 0, -> disabled!
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39321
Changeset r39302 updated a board section and added twice .has_ehci0,
this is not necessary, so fix it.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39304
BCM6318 has a special initialization sequence which involves touching
PLL control registers in the USBH_PRIV register space, as well as
toggling a bit the Simulation control register.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39302
The rt2x00 wifi driver may still need updating to
function with this device.
Signed-off-by: Christopher Lais <chris+openwrt@zenthought.org>
SVN-Revision: 39298
Enable the use of the USB gadget device at the board level so we can use
bcm63xx_udc on this board.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39292
Also fixing a build warning due to a misplaced parenthesis in the
previous submission.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39291
Very similar to the BCM96318REF board except for the name and the
SDRAM/DDR configuration which is totally transparent for us.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39286
Add basic support for the BCM96318REF board which is comprised of:
- HS-SPI flash support
- Ethernet switch support
- USB slave device support
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39283
Provide clock toggling for the USB host and slave controller as well as
for the Ethernet Switch. The bcm63xx_enetsw driver is changed not to use
request_mem_region() as the Roboswitch register overlaps with the
Roboswitch IUDMA channels, hence making the driver return -EBUSY. A
future fix might be to use variable size RSET_ENETSW sizes depending on
the chip we are targetting.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39282
While adding support for BCM6345 Ethernet, some changes in the macros
ENETDMA{C,S} where introduced which now make the bcm63xx USB gadget
driver fail to build. Fix this.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39279
A missing condition check in dev-hsspi.c prevented the controller from
being registered on 6318 where it is fully functional.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39278
varid might both unused and unitialized when building for e.g: bcm6318,
fix these two warnings turned into errors.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 39277
BCM63XX's ohci controller does not need the frame number shift, but that
was guarded with a PPC symbol. Fix this by making the no-fix generally
available.
This is a regression from the previous conversion to ohci platform driver.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39274
CFE seems to leave the SPI flash mapping in an invalid state after
loading the kernel on some reference boards, so fix it up on boot.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39273
Add inital support for BCM6318, but keep it disabled for now until
most things are supported.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39272
Add initial support for the BCM63268 family of SoCs, but keep it
disabled for now as most things don't work yet.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39271
Some SoCs have variants which are mostly the same, but use a different
chip id (or not). Add code for detecting them and handling them as
their standard counterparts.
This adds support for e.g. BCM6369.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39269
Remove the non runtime detect code since its effectiveness is dubious
and almost never used.
Also update affinity patches to work on top of it.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39268
Update bmips cleanup patches with upstream submission and backport a few
bmips fixes.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39267
Fixes generic SPI flash accesses on BCM6358/BCM6368. BCM6338 still needs
additional fixes for M25P80, so it remains broken for now.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39266
Fixes e.g. SPI flash access on BCM6358/BCM6368. Transfers < 256 bytes
are not affected.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39265
Update the HSSPI driver with the upstream submitted one that has a
workaround for the auto cs down issue.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 39264
