This is a bug in openocd. I have a fix but what to do with it is being
discussed on the openocd list.
On Sun, Jun 9, 2013 at 8:28 AM, Karl P wrote:
>
> I've seen this a lot with openocd and arm cortex-m targets. There's always
> lots of finger pointing, but it's "incompatible" gdb version and gd
Hi Jinzcheng. Indeed, you are correct that LUCI's speed of operation would
not be directly related to memory requirements for a v3.x kernel.
Likewise, Manuel is correct that older versions of OpenWRT should run OK
with 16MB RAM, e.g. Backfire v10.03.1 or so, and that pre-compiling LUCI's
source fi
>My understanding is that OpenWRT Attitude Adjustment, along with current
>versions of trunk, are not expected to run in any reliable way under less
>than 32MB of RAM. In particular, the v3.x kernel is not supported for so
>little memory, and the OpenWRT dev community likewise doesn't support it.
On 10.06.2013 20:13, Ben West wrote:
> My understanding is that OpenWRT Attitude Adjustment, along with current
> versions of trunk, are not expected to run in any reliable way under less
> than 32MB of RAM. In particular, the v3.x kernel is not supported for so
> little memory, and the OpenWRT de
Try to use 'openwrt' theme (old)
10.06.2013 22:13 пользователь "Ben West" написал:
> My understanding is that OpenWRT Attitude Adjustment, along with current
> versions of trunk, are not expected to run in any reliable way under less
> than 32MB of RAM. In particular, the v3.x kernel is not supp
My understanding is that OpenWRT Attitude Adjustment, along with current
versions of trunk, are not expected to run in any reliable way under less
than 32MB of RAM. In particular, the v3.x kernel is not supported for so
little memory, and the OpenWRT dev community likewise doesn't support it.
On
on small custom device with rt3052, 16MB RAM, 4MB SPI-FLASH
Is it an known issue?
Are there any advices?
Best regards.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>On 6/8/2013 8:10 PM, Mitch Kelly wrote:
>>
>> Hi,
>>
>> The 703N can only supply 200mA out the USB port, Its likely this issue
>> is caused by the device using more power that can be supplied and the
>> device resetting.
>>
>> TP-Link have a compatibility Martix for devices, It is based on Power
>On 6/8/2013 8:10 PM, Mitch Kelly wrote:
>>
>> Hi,
>>
>> The 703N can only supply 200mA out the USB port, Its likely this issue
>> is caused by the device using more power that can be supplied and the
>> device resetting.
>>
>> TP-Link have a compatibility Martix for devices, It is based on Power
Hi,
can you already switch the power on/off for the socket ?
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
10 matches
Mail list logo
