On Fri, 04 Jan 2013 16:46:18 +0100, Bastian Bittorf bitt...@bluebottle.com
wrote:
* Imre Kaloz ka...@openwrt.org [04.01.2013 16:27]:
I'm fine with the idea but not the way you did it, because if you're serial
attached this gets annoying quite fast. Although we could make this a config
Hi,
As you may know, there are two ways of accessing Broadcom NAND
flashes. On BCM4706 and non-BCM4706.
I own WNDR4500 which is BCM4706 based and I've written bcm47xxnflash
driver for it. It handles BCM4706 nice, it detects flash type, parses
it, allow reading and even installing new firmware.
Hi Rafał.
On 7 January 2013 11:30, Rafał Miłecki zaj...@gmail.com wrote:
Is there anyone around who could test attached patch for me? The only
non-BCM4706 device with NAND flash I know of is WNR3500L v2, but maybe
there are others.
Just ordered it, could test it in a few days time when I
* Imre Kaloz ka...@openwrt.org [07.01.2013 12:55]:
the problem is: most routers are in production and not serial
attached - so you have really a problem if a node (rooftop or solar
powered) dies during boot. if you are a developer, you can simple build
your own image and disable this option,
This becomes crucial when you are using a generic profile to build an image
larger than 4M, e.g. for w502u.
Signed-off-by: Paul Fertser fercer...@gmail.com
---
target/linux/ramips/image/Makefile |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
2013.01.06. 23:10 keltezéssel, Michel Stempin írta:
...
But it looks like the default for id 0 in ath79_register_eth(id) is to set
bit 4 in mask, which is wrong if we swap PHY 0 and 4, is it?
Erm, the 'false, false' in the phy4_switch call above ensures that we don't
swap
the phy address.
Given that this problem is causing bricked (well, only serial console
access) devices on fresh install on newest TL-WR703N v 1.7 routers, is
it advisable to backport the patch to the AA branch?
-Michel
Le 07/01/2013 15:33, Gabor Juhos a écrit :
2013.01.06. 23:10 keltezéssel, Michel Stempin
2013.01.07. 15:52 keltezéssel, Michel Stempin írta:
Given that this problem is causing bricked (well, only serial console access)
devices on fresh install on newest TL-WR703N v 1.7 routers, is it advisable to
backport the patch to the AA branch?
It is done already:
On Monday 07 January 2013 13:17:24 Bastian Bittorf wrote:
* Imre Kaloz ka...@openwrt.org [07.01.2013 12:55]:
the problem is: most routers are in production and not serial
attached - so you have really a problem if a node (rooftop or solar
powered) dies during boot. if you are a developer,
* Oliver oli...@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa [07.01.2013 21:46]:
this is not the idea:
face the fact, that a kernel can panic seldom during boot,
even before preinit, even if the kernel is good.
So if the kernel is good, evidently something else isn't... If you're
shipping
images
Hi!
Its the first time I try this, so please give the attached patches a review.
To simplify, all points which weren't clear to me are:
dd-wrt has an explicit:
(http://svn.dd-wrt.com/browser/src/router/Makefile.pb42)
ifeq ($(CONFIG_DIR825C1),y)
dd if=$(ARCH)-uclibc/root.uimage
On 01/07/2013 03:19 AM, Nathan Hintz wrote:
1) Fix what appears to be a logic error in bgmac_phy_advertise.
2) Fix bgmac_ioctl to use passed phy_id; needed for switch-robo
interface w/ the driver to work correctly. I still have the issue
with the interface always being HD when the
12 matches
Mail list logo
