On 2011-09-07 9:59 PM, Daniel Golle wrote:
This patchs adds support for the Allnet ALL0258N outdoor AP/bridge.
The ALL0258N is based on the AR7240 SoC paired with an AR9285 radio, it got 8MB
of NOR and 32MB SDRAM.
Signed-off-by: Daniel Golledgo...@allnet.de
Index:
Hi,
On Fri, 09 Sep 2011 01:17:09 +0200, Matthew Eaton w...@divinehawk.com wrote:
Based upon the patch at http://forum.doozan.com/read.php?2,5579 and
the existing dockstar patches.
This patch adds support for the Pogoplug model POGO-E02.
Signed-off-by: Matthew Eaton wrt at divinehawk.com
Hi,
On Fri, 09 Sep 2011 01:17:09 +0200, Matthew Eaton w...@divinehawk.com wrote:
Based upon the patch at http://forum.doozan.com/read.php?2,5579 and
the existing dockstar patches.
This patch adds support for the Pogoplug model POGO-E02.
Signed-off-by: Matthew Eaton wrt at divinehawk.com
Hi,
On Fri, 09 Sep 2011 01:17:09 +0200, Matthew Eaton w...@divinehawk.com wrote:
Based upon the patch at http://forum.doozan.com/read.php?2,5579 and
the existing dockstar patches.
This patch adds support for the Pogoplug model POGO-E02.
Signed-off-by: Matthew Eaton wrt at divinehawk.com
On Fri, 09 Sep 2011 14:18:21 +0200, Matthew Eaton w...@divinehawk.com wrote:
Hi,
On Fri, 09 Sep 2011 01:17:09 +0200, Matthew Eaton w...@divinehawk.com wrote:
Based upon the patch at http://forum.doozan.com/read.php?2,5579 and
the existing dockstar patches.
This patch adds support for the
On Fri, Sep 09, 2011 at 07:59:54AM +0200, Felix Fietkau wrote:
I think you should drop the fifo cfg overrides and let the code use the
defaults.
Thanks, indeed, removing the fifo cfg overrides didn't do any harm. I added it
when trying to get the secondary ethernet port to work, actually
On 6 September 2011 18:37, Roman Yeryomin leroi.li...@gmail.com wrote:
Did anyone think of separating buildroot-ng from the content (packages
and targets) into a separate project (under OpenWrt name of cause)?
Then one can do something like `make content' and depending on what is
configured
On Fri, Sep 9, 2011 at 8:31 AM, Imre Kaloz ka...@openwrt.org wrote:
On Fri, 09 Sep 2011 14:18:21 +0200, Matthew Eaton w...@divinehawk.com
wrote:
Hi,
On Fri, 09 Sep 2011 01:17:09 +0200, Matthew Eaton w...@divinehawk.com
wrote:
Based upon the patch at http://forum.doozan.com/read.php?2,5579
With 2.6.37 and later, there will be no more mini_fo bugs - mini_fo has
been replaced with overlayfs there, which seems to be *much* more stable
than mini_fo ever was.
- Felix
Hi Felix,
I missed your original post. I'm on too many lists (18k emails in my
inbox ;) ).
So you have seen good
Hi
this patch fixes 3 things in the imagebuilder, one of them is literally big:
When running package_install the imagebuilder generates package list(s),
which are stored in $(TARGET_DIR)/usr/lib/opkg/lists/ and then copied
into the final image, which wastes around 200kB in the resulting image
ag71xx_check_dma_stuck was introduced in r27975 and reads:
AG71XX_REG_FIFO_DEPTH
AG71XX_REG_RX_SM
AG71XX_REG_TX_SM
This patch add those registers in the whitelist of ag71xx_check_reg_offset.
Those registers can be used by ag71xx_check_dma_stuck under heavy traffic load.
Signed-off-by: Frédéric
On 09/09/2011 08:42 AM, Manuel Munz wrote:
Hi
this patch fixes 3 things in the imagebuilder, one of them is literally big:
When running package_install the imagebuilder generates package list(s),
which are stored in $(TARGET_DIR)/usr/lib/opkg/lists/ and then copied
into the final image, which
On 09.09.2011 18:05, Peter Naulls wrote:
On 09/09/2011 08:42 AM, Manuel Munz wrote:
Hi
this patch fixes 3 things in the imagebuilder, one of them is
literally big:
When running package_install the imagebuilder generates package list(s),
which are stored in $(TARGET_DIR)/usr/lib/opkg/lists/
On 09/09/2011 10:02 AM, Manuel Munz wrote:
But why is CLEAN_IPKG not
selected by default? And can we have a backport of this to backfire?
Why should it be? If you want it on, select it. It's the same option
from menuconfig.
Thats not an option for me. I build the most generic profile and
On 09.09.2011 19:22, Peter Naulls wrote:
On 09/09/2011 10:02 AM, Manuel Munz wrote:
But why is CLEAN_IPKG not
selected by default? And can we have a backport of this to backfire?
Why should it be? If you want it on, select it. It's the same option
from menuconfig.
Ok, i've checked it a
Good day to all,
As I already had posted to the list, I'm experimenting with OpenWRT installation
on my fresh-new DIR-615 rev. E4 box. Looks like that current trunk it is pretty
unstable on it - I've got unexpected reboots or hangs at random intervals,
varying from several minutes to the several
16 matches
Mail list logo
