| Commit message (Collapse) | Author | Age |
|
|
|
| |
SVN-Revision: 33501
|
|
|
|
| |
SVN-Revision: 33500
|
|
|
|
| |
SVN-Revision: 33499
|
|
|
|
|
|
| |
requirement of 64), fix skb fragment chaining
SVN-Revision: 33498
|
|
|
|
| |
SVN-Revision: 33497
|
|
|
|
|
|
|
|
|
| |
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.
SVN-Revision: 33496
|
|
|
|
| |
SVN-Revision: 33493
|
|
|
|
| |
SVN-Revision: 33492
|
|
|
|
|
|
| |
skb fragment lists
SVN-Revision: 33491
|
|
|
|
| |
SVN-Revision: 33490
|
|
|
|
| |
SVN-Revision: 33489
|
|
|
|
|
|
| |
the new one)
SVN-Revision: 33488
|
|
|
|
| |
SVN-Revision: 33487
|
|
|
|
| |
SVN-Revision: 33486
|
|
|
|
| |
SVN-Revision: 33485
|
|
|
|
| |
SVN-Revision: 33484
|
|
|
|
|
|
|
|
| |
The package block-hotplug doesn't exist, refer to block-mount instead.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33474
|
|
|
|
|
|
|
|
| |
The package block-hotplug doesn't exist, removing reference to it.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33473
|
|
|
|
|
|
| |
Do not change the code any more but use the kconfig options
SVN-Revision: 33463
|
|
|
|
| |
SVN-Revision: 33462
|
|
|
|
| |
SVN-Revision: 33460
|
|
|
|
|
|
|
|
|
|
| |
It should be implemmented in a cleaner way.
This reverts the following commits:
[ar71xx] dir-825-b1: Fix wholeflash images
[ar71xx] dir825b1: Add image for DIR-825-B1 that uses the whole flash"
SVN-Revision: 33459
|
|
|
|
|
|
|
| |
This will make the kernel crash on systems using qemu < 1.1.0. Until fixed
disable VPFv4 capability probing.
SVN-Revision: 33458
|
|
|
|
|
|
| |
The target CFLAGS were also accidentally changed
SVN-Revision: 33457
|
|
|
|
| |
SVN-Revision: 33455
|
|
|
|
| |
SVN-Revision: 33454
|
|
|
|
| |
SVN-Revision: 33453
|
|
|
|
| |
SVN-Revision: 33452
|
|
|
|
| |
SVN-Revision: 33451
|
|
|
|
| |
SVN-Revision: 33450
|
|
|
|
|
|
| |
(-openwrt) image from the normal image would brick (but recoverable via emergency flash) the router if the wholeflash image was larger than the maximum size for a normal image. First we rename the -openwrt images to -wholeflash since -openwrt is really too generic. We also revert the changes to the regular dir-825-b1 image, which now is the same as before, but add a -towholeflash image which is almost the same as the regular dir-825-b1 image, but copies caldata to new location and allows flashing of images that use the full flash (except u-boot, u-boot-env, and caldata paritition space) (these are the -wholeflash images).
SVN-Revision: 33447
|
|
|
|
|
|
| |
ar71xx->ath79 migration, should fix wifi stability issues on ar933x
SVN-Revision: 33446
|
|
|
|
| |
SVN-Revision: 33413
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a patch to connect eth0.1 (lan) to the only
ethernet connector available.
D-Link DAP-1350 goes bricked with AA 12.09-beta.
This is because the current esw configuration for the
board connects eth0.2 (wan) to the *ONE and ONLY*
ethernet connector available, preventing initial access
to the board through 192.168.1.1 on eth0.1 after flashing,
effectively bricking the board.
There are things that should be done to make this board
really useful, but for AA 12.09, this one liner is
indispensable.
Signed of by Yoichi Shinoda <shinoda@jaist.ac.jp>
SVN-Revision: 33411
|
|
|
|
|
|
| |
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33410
|
|
|
|
| |
SVN-Revision: 33409
|
|
|
|
| |
SVN-Revision: 33408
|
|
|
|
| |
SVN-Revision: 33407
|
|
|
|
| |
SVN-Revision: 33406
|
|
|
|
| |
SVN-Revision: 33403
|
|
|
|
| |
SVN-Revision: 33402
|
|
|
|
| |
SVN-Revision: 33389
|
|
|
|
| |
SVN-Revision: 33388
|
|
|
|
| |
SVN-Revision: 33387
|
|
|
|
| |
SVN-Revision: 33386
|
|
|
|
| |
SVN-Revision: 33385
|
|
|
|
| |
SVN-Revision: 33384
|
|
|
|
| |
SVN-Revision: 33383
|
|
|
|
| |
SVN-Revision: 33382
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Somehow detecting the RAM size in common/setup.c doesn't
work here, it always detects 64M and then crashes on devices
with less RAM.
Probably using MEMC_REG_SDRAM_CFG1 to know the RAM size is how
it could be, for now I use the mem=32M kernel parameter to get
stuff working.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33381
|