Hi All,
What can I do next?
Thanks
Daniel
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf
Of Daniel Niasoff
Sent: 19 August 2016 13:21
To: John Crispin ; Mathias Kresin
Cc: OpenWrt Development List ;
lede-dev@lists.infradead.org
Subj
Hello. See below:
On 24/08/2016 11:12, Сергеев Сергей wrote:
Hello. Ok. Leave all as is. But...(comments below):
On 13/08/2016 13:04, ad...@yapic.net wrote:
From: Sergey Sergeev
scp uls(like this
scp://adron@192.168.88.6:lede/lede-ar71xx-mikrotik-NAND-512b-squashfs-sysupgrade.bin)
Add Support for the ESMT_F25L32QA and ESMT_F25L64QA
These are 4MB and 8MB Flash Chips from Elite Semiconductor Memory Technology
Signed-off-by: L. D. Pinney
---
target/linux/generic/patches-4.4/477-mtd-spi-nor-add-support-ESMT_f25l32qa_and_f25l64qa
| 14 ++
1 file changed, 14 inse
From: Ben Greear
Removes a useless splat in ath10k, and adds some safety code
around setting keys in the firmware.
Signed-off-by: Ben Greear
---
package/kernel/ath10k-ct/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/kernel/ath10k-ct/Makefile
b/packag
From: Ben Greear
This fixes a nasty memory corruption bug, among other things.
Signed-off-by: Ben Greear
---
package/firmware/ath10k-firmware/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/firmware/ath10k-firmware/Makefile
b/package/firmware/ath10k-fi
From: Ben Greear
This tool can periodically check for ath10k firmware crashes.
If it finds a crash, it will package up the binary crash dump,
some OS level things like dmesg, lspci, etc into a tar file.
It then notifies the user about the crash and asks them to report
the bug to the appropriate
I'm looking to see if I can add a couple of Zyxel devices I own in LEDE
(NSA310 and NSA325), possibly more as I can take dtb files for quite a
few other out-of-tree Kirkwood devices from a Debian-on-Kirkwood
community I know.
I see you have already the NSA310s in the source, so I was grepping
Historically on ARC we started from initramfs-based images because:
a) It was much easier to debug especially when toolchain and other
components were changing quite dynamically
b) It was our usual approach for embedded Linux
But now with ARC port of Lede/OpenWRT getting more stable and matu
If we want to boot from SD-card we need to have corresponding
drivers already built-in so there's no point in having these
modules.
Signed-off-by: Alexey Brodkin
---
target/linux/arc770/generic/profiles/00-default.mk | 2 +-
target/linux/arc770/generic/profiles/02-axs101.mk | 2 +-
2 files chan
As support of ARC 770 in OpenWRT/Lede matures we don't need
debug-only output binaries any longer, so purging vmlinux for
AXS10x boards.
As for uImage for nSIM it makes completely no sense because there's no
way to run U-Boot on nSIM.
So we remove add_arcYYY_XXX scripts making code more compact a
Note this series implement exactly the same thing as it was done for
ARC HS38 recently with only one important difference - this time we're
not creating new subtargets keeping everything in generic one.
Historically on ARC we started from initramfs-based images because:
a) It was much easier to
Now when we're switching to FS on SD-card it's necessary to have
full stack of MMC block & FC drivers built-in otherwise kernel won't
be able to mount FS with needed modules.
Also we enable parsing of input parameters passed to the kernel by
U-Boot. Otherwise kernel won't know where to look for co
On 2016-08-24 15:44, Kenneth Johansson wrote:
Have a feeling this is going to be a face palm moment once I figure
out what the issue is.
solved.
It was the spi driver. It also share the pins with nand so when it was
loaded later than the nand drive things stopped working after the probe
wa
On 2016-08-24 14:40, John Crispin wrote:
On 24/08/2016 14:32, Kenneth Johansson wrote:
[4.19] Device not found, ID: ecf1
[4.20] Not Support this Device!
[4.20] chip_mode=0002
your error log has this in it. there is a hackish table with magic
values doing magic thing
On 2016-08-24 14:40, John Crispin wrote:
On 24/08/2016 14:32, Kenneth Johansson wrote:
[4.19] Device not found, ID: ecf1
[4.20] Not Support this Device!
[4.20] chip_mode=0002
your error log has this in it. there is a hackish table with magic
values doing magic thing
DW GMAC on ARC SDP boards doesn't enter promiscuous mode if
Ethernet PHY haven't got established link. Good examples are
auto-negotiation in progress or disconnected cable.
We do see Linux kernel sets GMAC's MAC filter register
properly but GMAC's hardware doesn't accept new settings.
We believe
On 24/08/2016 14:32, Kenneth Johansson wrote:
> [4.19] Device not found, ID: ecf1
> [4.20] Not Support this Device!
> [4.20] chip_mode=0002
your error log has this in it. there is a hackish table with magic
values doing magic things to make the HW work with various ch
On 2016-08-24 13:49, John Crispin wrote:
On 24/08/2016 13:44, Kenneth Johansson wrote:
On 2016-08-24 13:32, John Crispin wrote:
On 24/08/2016 13:25, Kenneth Johansson wrote:
What is the status of the nand driver for mt7621 ??
when I try to use it the probing is ok but it fails when I try to
On 24/08/2016 13:44, Kenneth Johansson wrote:
> On 2016-08-24 13:32, John Crispin wrote:
>>
>> On 24/08/2016 13:25, Kenneth Johansson wrote:
>>> What is the status of the nand driver for mt7621 ??
>>>
>>> when I try to use it the probing is ok but it fails when I try to
>>> read/write.
>>>
>>>
>>
On 2016-08-24 13:32, John Crispin wrote:
On 24/08/2016 13:25, Kenneth Johansson wrote:
What is the status of the nand driver for mt7621 ??
when I try to use it the probing is ok but it fails when I try to
read/write.
known to be working and i used it on the ERX just last week. what
specifc
On 24/08/2016 13:25, Kenneth Johansson wrote:
> What is the status of the nand driver for mt7621 ??
>
> when I try to use it the probing is ok but it fails when I try to
> read/write.
>
>
known to be working and i used it on the ERX just last week. what
specifc board is this and can you post
What is the status of the nand driver for mt7621 ??
when I try to use it the probing is ok but it fails when I try to
read/write.
[4.15] MediaTek Nand driver init, version v2.1 Fix AHB virt2phys
error
[4.17] Allocate 16 byte aligned buffer: 806f3100
[4.18] Enable NFI
As autostart is now more aligned to user intention of automatic
starting the wdev, to add retry_setup_failed to status msg may be of a help
for current stating how setup is proceeding.
Signed-off-by: Eduardo Abinader
---
wireless.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/wireless.c b
On 24/08/2016 11:12, Сергеев Сергей wrote:
> Hello. Ok. Leave all as is. But...(comments below):
>>
>> On 13/08/2016 13:04, ad...@yapic.net wrote:
>>> From: Sergey Sergeev
>>>
>>>scp uls(like this
>>> scp://adron@192.168.88.6:lede/lede-ar71xx-mikrotik-NAND-512b-squashfs-sysupgrade.bin)
>>>
>
Hello. Ok. Leave all as is. But...(comments below):
On 13/08/2016 13:04, ad...@yapic.net wrote:
From: Sergey Sergeev
scp uls(like this
scp://adron@192.168.88.6:lede/lede-ar71xx-mikrotik-NAND-512b-squashfs-sysupgrade.bin)
is supported too. And you also can specify custom ssh
port(...
On 24/08/2016 09:54, Oswald Buddenhagen wrote:
> On Tue, Aug 23, 2016 at 09:14:36PM +0200, Mathias Kresin wrote:
>> With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
>> eeprom extraction to an alternate code path. Unfortunately this code
>> seams to be broken since ages and broke
On 23/08/2016 21:14, Mathias Kresin wrote:
> With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
> eeprom extraction to an alternate code path. Unfortunately this code
> seams to be broken since ages and broke the ath5k EEPROM extraction.
>
> Reported-by: Mohammed Berdai
> Signed
On 13/08/2016 13:04, ad...@yapic.net wrote:
> From: Sergey Sergeev
>
> scp uls(like this
> scp://adron@192.168.88.6:lede/lede-ar71xx-mikrotik-NAND-512b-squashfs-sysupgrade.bin)
> is supported too. And you also can specify custom ssh
> port(...8.88.6:22110:lede...)
>
> Signed-off-by: Se
On Tue, Aug 23, 2016 at 09:14:36PM +0200, Mathias Kresin wrote:
> With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
> eeprom extraction to an alternate code path. Unfortunately this code
> seams to be broken since ages and broke the ath5k EEPROM extraction.
>
i have no particular
29 matches
Mail list logo
