| .. |
|
007-usb-ohci-support.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
008-usb-ehci-support.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
010-add_bcm63xx_ohci_controller.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
011-add_bcm63xx_ehci_controller.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
020-watchdog.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
040-bcm963xx_flashmap.patch
|
mtd flashmap: Switched to calculating the rootfs size rather than depending on being given the size in the imagetag. This is because solving the problem of second boot CRC errors requires changeing the rootfs size in the image to zero.
|
2010-12-26 04:17:56 +00:00 |
|
070_bcm63xx_enet_vlan_incoming_fixed.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
100-reset_buttons.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
110-gpiodev.patch
|
refresh 2.6.35 patches
|
2010-09-12 21:23:29 +00:00 |
|
120-spi-bitbang-norxtx-support.patch
|
backport SPI master with no RXTX support (from 2.6.36)
|
2010-10-17 14:08:39 +00:00 |
|
121-spi-gpio-norxtx-support.patch
|
backport SPI master with no RXTX support (from 2.6.36)
|
2010-10-17 14:08:39 +00:00 |
|
141-led_count.patch
|
patches: Renamed 150-led_count to 141-led_count so it comes before the 15-alice_gate2_leds.patch as which led count was mistakenly given the same number.
|
2010-12-07 17:32:29 +00:00 |
|
150-alice_gate2_leds.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
170-board_livebox.patch
|
register uart driver on livebox (#8013)
|
2010-10-27 10:02:13 +00:00 |
|
180-udc_preliminary_support.patch
|
patches: Refreshed patches after led_count
|
2010-12-07 15:15:51 +00:00 |
|
200-extended-platform-devices.patch
|
patches: Refreshed patches after led_count
|
2010-12-07 15:15:51 +00:00 |
|
200-spi-board-info.patch
|
patches: Refreshed patches after led_count
|
2010-12-07 15:15:51 +00:00 |
|
211-gen-74x164-gpio-chip-driver.patch
|
Fix nxp_74hc164 driver compile error (builbot)
|
2010-10-24 16:10:41 +00:00 |
|
220-board-D4PW.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
221-board-NB4.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
240-spi.patch
|
patches: Refreshed patches after led_count
|
2010-12-07 15:15:51 +00:00 |
|
250-6358-enet1-external-mii-clk.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
260-no_ehci_over_current_check.patch
|
add 2.6.35 support
|
2010-08-25 19:56:08 +00:00 |
|
270-board-96338W2_E7T.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
300-wl_exports.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
310-CPVA642_board.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
400-board_96358gw.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
410-boardid_fixup.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
420-board_spw500v.patch
|
Remove patch 140-new_bcm96348gw_leds because it is really the GW6200 leds, not the generic 96348GW. Another commit will add the GW6200 specific boardid and leds. This removal reverts the 96348GW leds to the reference design GPIOs.
|
2010-12-07 15:15:41 +00:00 |
|
430-board_gw6200_gw6000.patch
|
boards: Added GW6x00 fixups and GPIOs. The GW6200 GPIOs are different than the reference design 96348GW so we use fixup to allow us to define the correct ones, also the GW6000 has no GPIO-controlled leds.
|
2010-12-07 15:15:54 +00:00 |
|
440-new_96348gw-11_leds.patch
|
Fixed Comtrend CT536_CT5621 board settings. These boards are based on the 96348GW-11 reference design but have different GPIOs therefore we use the board fixups now availabed (thanks the patches by Jonas Gorski) to create a separate board entry for these boards and leave the reference design with reference GPIOs. Also these boards only have enet1 (no enet0) so we set that in the board definition, and use a defconfig for a single interface network.
|
2010-12-10 18:59:58 +00:00 |
