[OpenWrt-Devel] [PATCH 5/5] Comtrend (BRCM63XX 96348-A122) Support
This adds support for Comtrend 5365. I'm sending this again due to the removal
of kernel 2.6.39 support.
5/5 (originally 5/4 -> kernel 3.3 was added after patch submission): Kernel
v3.3-rc2
Signed-off-by: Álvaro Fernández Rojas
Index: target/linux/brcm63xx/patches-3.3/200-extended-platform-devices.patch
===
--- target/linux/brcm63xx/patches-3.3/200-extended-platform-devices.patch
(revisión: 30344)
+++ target/linux/brcm63xx/patches-3.3/200-extended-platform-devices.patch
(copia de trabajo)
@@ -15,7 +15,7 @@
@@ -62,6 +62,10 @@ struct board_info {
/* Buttons */
- struct gpio_button buttons[2];
+ struct gpio_button buttons[4];
+
+ /* Additional platform devices */
+ struct platform_device **devs;
Index: target/linux/brcm63xx/patches-3.3/457-board_96348A-122.patch
===
--- target/linux/brcm63xx/patches-3.3/457-board_96348A-122.patch
(revisión: 0)
+++ target/linux/brcm63xx/patches-3.3/457-board_96348A-122.patch
(revisión: 0)
@@ -0,0 +1,78 @@
+--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
b/arch/mips/bcm63xx/boards/board_bcm963xx.c
+@@ -1010,6 +1010,67 @@
+ },
+ };
+
++static struct board_info __initdata board_96348A_122 = {
++ .name = "96348A-122",
++ .expected_cpu_id= 0x6348,
++
++ .has_uart0 = 1,
++ .has_enet1 = 1,
++ .has_pci= 1,
++
++ .enet1 = {
++ .force_speed_100= 1,
++ .force_duplex_full = 1,
++ },
++
++ .has_ohci0 = 1,
++
++ .leds = {
++ {
++ .name = "power",
++ .gpio = 0,
++ .active_low = 1,
++ .default_trigger = "default-on",
++ },
++ {
++ .name = "alarm",
++ .gpio = 2,
++ .active_low = 1,
++ },
++ {
++ .name = "wps",
++ .gpio = 6,
++ .active_low = 1,
++ },
++ },
++ .buttons = {
++ {
++ .desc = "reset",
++ .gpio = 33,
++ .active_low = 1,
++ .type = EV_KEY,
++ .code = KEY_RESTART,
++ .threshold = 3,
++ },
++ {
++ .desc = "wifi",
++ .gpio = 34,
++ .active_low = 1,
++ .type = EV_KEY,
++ .code = BTN_0,
++ .threshold = 3,
++ },
++ {
++ .desc = "wps",
++ .gpio = 35,
++ .active_low = 1,
++ .type = EV_KEY,
++ .code = KEY_WPS_BUTTON,
++ .threshold = 3,
++ },
++ },
++};
++
+ #endif
+
+ /*
+@@ -2069,6 +2130,7 @@
+ &board_V2500V_BB,
+ &board_V2110,
+ &board_ct536_ct5621,
++ &board_96348A_122,
+ #endif
+
+ #ifdef CONFIG_BCM63XX_CPU_6358
Cambios de propiedades en
target/linux/brcm63xx/patches-3.3/457-board_96348A-122.patch
___
Añadido: svn:executable
+ *
Index: target/linux/brcm63xx/patches-3.3/100-reset_buttons.patch
===
--- target/linux/brcm63xx/patches-3.3/100-reset_buttons.patch (revisión:
30344)
+++ target/linux/brcm63xx/patches-3.3/100-reset_buttons.patch (copia de
trabajo)
@@ -100,7 +100,7 @@
struct gpio_led leds[5];
+
+ /* Buttons */
-+ struct gpio_button buttons[2];
++ struct gpio_button buttons[4];
};
#endif /* ! BOARD_BCM963XX_H_ */
Index: target/linux/brcm63xx/patches-3.3/977-ssb_export_fallback_sprom.patch
===
--- target/linux/brcm63xx/patches-3.3/977-ssb_export_fallback_sprom.patch
(revisión: 30344)
+++ target/linux/brcm63xx/patches-3.3/977-ssb_export_fallback_sprom.patch
(copia de trabajo)
@@ -1,6 +1,6 @@
--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
+++ b/arch/mips/bcm63xx/boards/board_bcm963xx.c
-@@ -2109,7 +2109,7 @@ static void __init nb4_nvram_fixup(void)
+@@ -2171,7 +2171,7 @@ static void __init nb4_nvram_fixup(void)
* bcm4318 WLAN work
*/
#ifdef CONFIG_SSB_PCIHOST
@@ -9,7 +9,7 @@
.revision = 0x02,
.board_rev = 0x17,
Re: [OpenWrt-Devel] Low level boot on MIPS CPUs
On Monday 06 February 2012 19:20:21 jonsm...@gmail.com wrote: > On Mon, Feb 6, 2012 at 1:08 PM, Florian Fainelli wrote: > > On Monday 06 February 2012 18:00:17 Peter Naulls wrote: > >> On 02/06/2012 08:52 AM, jonsm...@gmail.com wrote: > >> > Most ARM CPUs have boot ROMs for getting the initial image out of > >> > flash. I'm referring to the boot loader that loads uboot, not uboot. > >> > The ARM CPUs I've worked with search for a signature in flash, if they > >> > can't find a valid signature they load from UART instead. Or you can > >> > use a jumper to force loading from UART. This allows you to recover > >> > from being bricked or initially load the flash without needing a > >> > special programmer. > >> > > >> > Do the MIPS based router CPUs have this ability? What does the on MIPS > >> > CPU ROM do if the image in flash is invalid? > >> > >> MIPS systems varies as much as ARM ones do. The short answer, is > >> it depends upon the hardware. For systems which lack serial/ROM > >> level recovery, you'll need to use JTAG. Some systems I work > >> with lack even that. > > > > Actually, I have never seen a single MIPS system out there having such a > > boot ROM capability. > > It is a very useful ability. You can solder the flash chips on empty > and then use the UART to program them during test. > > UART first loads a little program to tiny on-CPU-chip SRAM. This > program in turns knows how to program the flash chip and then reads > the full image from UART with error detection. You need the SRAM > because the DRAM controller is not set up yet. u-boot support this, > check out CONFIG_SPL. > > Takes about 30 seconds and no special equipment to initially program > our ARM boards. Same procedure can unbrick them. Yeah, I have used that on a custom AT91 board, it definitively is useful, but MIPS integrators did not feel the need to get this standardized or even brought to customers, so, if you want a similar feature, you'd have to use a custom bootloader and protect the region of the flash where this rescue bootloader is. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Low level boot on MIPS CPUs
On Mon, Feb 6, 2012 at 1:08 PM, Florian Fainelli wrote: > On Monday 06 February 2012 18:00:17 Peter Naulls wrote: >> On 02/06/2012 08:52 AM, jonsm...@gmail.com wrote: >> > Most ARM CPUs have boot ROMs for getting the initial image out of >> > flash. I'm referring to the boot loader that loads uboot, not uboot. >> > The ARM CPUs I've worked with search for a signature in flash, if they >> > can't find a valid signature they load from UART instead. Or you can >> > use a jumper to force loading from UART. This allows you to recover >> > from being bricked or initially load the flash without needing a >> > special programmer. >> > >> > Do the MIPS based router CPUs have this ability? What does the on MIPS >> > CPU ROM do if the image in flash is invalid? >> >> MIPS systems varies as much as ARM ones do. The short answer, is >> it depends upon the hardware. For systems which lack serial/ROM >> level recovery, you'll need to use JTAG. Some systems I work >> with lack even that. > > Actually, I have never seen a single MIPS system out there having such a boot > ROM capability. It is a very useful ability. You can solder the flash chips on empty and then use the UART to program them during test. UART first loads a little program to tiny on-CPU-chip SRAM. This program in turns knows how to program the flash chip and then reads the full image from UART with error detection. You need the SRAM because the DRAM controller is not set up yet. u-boot support this, check out CONFIG_SPL. Takes about 30 seconds and no special equipment to initially program our ARM boards. Same procedure can unbrick them. > -- > Florian > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Low level boot on MIPS CPUs
On Monday 06 February 2012 18:00:17 Peter Naulls wrote: > On 02/06/2012 08:52 AM, jonsm...@gmail.com wrote: > > Most ARM CPUs have boot ROMs for getting the initial image out of > > flash. I'm referring to the boot loader that loads uboot, not uboot. > > The ARM CPUs I've worked with search for a signature in flash, if they > > can't find a valid signature they load from UART instead. Or you can > > use a jumper to force loading from UART. This allows you to recover > > from being bricked or initially load the flash without needing a > > special programmer. > > > > Do the MIPS based router CPUs have this ability? What does the on MIPS > > CPU ROM do if the image in flash is invalid? > > MIPS systems varies as much as ARM ones do. The short answer, is > it depends upon the hardware. For systems which lack serial/ROM > level recovery, you'll need to use JTAG. Some systems I work > with lack even that. Actually, I have never seen a single MIPS system out there having such a boot ROM capability. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Low level boot on MIPS CPUs
On 02/06/2012 08:52 AM, jonsm...@gmail.com wrote: Most ARM CPUs have boot ROMs for getting the initial image out of flash. I'm referring to the boot loader that loads uboot, not uboot. The ARM CPUs I've worked with search for a signature in flash, if they can't find a valid signature they load from UART instead. Or you can use a jumper to force loading from UART. This allows you to recover from being bricked or initially load the flash without needing a special programmer. Do the MIPS based router CPUs have this ability? What does the on MIPS CPU ROM do if the image in flash is invalid? MIPS systems varies as much as ARM ones do. The short answer, is it depends upon the hardware. For systems which lack serial/ROM level recovery, you'll need to use JTAG. Some systems I work with lack even that. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Low level boot on MIPS CPUs
Most ARM CPUs have boot ROMs for getting the initial image out of flash. I'm referring to the boot loader that loads uboot, not uboot. The ARM CPUs I've worked with search for a signature in flash, if they can't find a valid signature they load from UART instead. Or you can use a jumper to force loading from UART. This allows you to recover from being bricked or initially load the flash without needing a special programmer. Do the MIPS based router CPUs have this ability? What does the on MIPS CPU ROM do if the image in flash is invalid? -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] USB support for rt305x chips
On 02/06/2012 12:40 AM, jonsm...@gmail.com wrote: We have a bunch of sensors - temp, humidy, contact, motion, etc with 802.15.4 radios. I need a gateway device (the router) to route between the 802.15.4 network and wifi. 802.15.4 network is all IPv6. Hi I saw the 802.15.4. since our device also using OpenWRt as system and this device called Ben Nanonote also have a 802.15.4 gadget that can make Ben Nanonote connect to each other or to a PC. we are using IPv4. I would like share some links. just fyi: http://en.qi-hardware.com/wiki/Ben_NanoNote http://en.qi-hardware.com/wiki/Ben_WPAN http://en.qi-hardware.com/wiki/Applications Best Regards xiangfu ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] php5 update to 5.3.10
hello, dani@x60t ~/wr740n/trunk $ grep PKG_VERSION feeds/packages/lang/php5/Makefile PKG_VERSION:=5.3.9 maybe the maintainer can help us with the latest update patch? http://www.php.net/archive/2012.php#id2012-02-02-1 "Security Fixes in PHP 5.3.10: Fixed arbitrary remote code execution vulnerability reported by Stefan Esser, CVE-2012-0830. All users are strongly encouraged to upgrade to PHP 5.3.10." thanks! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
