> I've just added few more commits, so the Git history should looks like this:
>
> fb4f264 fixup! WIP: ath79: Add support for Ubiquiti Nanostation M (XW)
> 12a0c28 fixup! WIP: ath79: Add support for Ubiquiti Nanostation M (XW)
> 1c2f603 fixup! ath79: Add support for Ubiquity Bullet M (XW)
> 681
Petr Štetiar [2018-11-18 01:02:34]:
Hi Joe,
> cd openwrt.git
> git remote add github-ynezz https://github.com/ynezz/openwrt.git
> git fetch github-ynezz
> git checkout -b nanostation-m-xw github-ynezz/wip/nanostation-m-xw
> echo -e
> "CONFIG_TARGET_ath79=y\nCONFIG_TARGET_ath79_generic=y\nC
The recently released technical guideline for secure broadband routers
is simply a disservice to customers. This guideline will not prevent
widespread malfunction of routers and their security problems in the
future. The consumers will not get a useful way to distinguish secure
and long living devi
Hi all,
I'm trying to get a dlink dir-825-c1 working with a device tree setup.
So far it can boot, the partitions are correctly set up, the Ethernet
ports seem to work and the wireless devices are coming up.
I'm a bit stumped with mac addresses as well as LAN port leds, though.
In ar71xx ath79_p
On Mon, Nov 19, 2018 at 6:43 PM Jason A. Donenfeld wrote:
>
> * chacha20,poly1305: fix up for win64
> * poly1305: only export neon symbols when in use
> * poly1305: cleanup leftover debugging changes
> * crypto: resolve target prefix on buggy kernels
> * chacha20,poly1305: don't do compiler testin
From: Joe Ayers
Ubiquity allows flashing of unsigned factory images via TFTP recovery
method[1]. They claim in airOS v6.0.7 release changelog[2] following:
All future airOS versions will be signed in this way and not allow
unsigned firmware to be loaded except via TFTP.
U-boot bootloader on M
Joe Ayers [2018-11-18 08:37:54]:
> On the serial console, could see why your node is not going into tftp
> server mode or if other reason?
I simply couldn't see anything, it has never interrupted the booting process.
According to your information I've simply checked the functionality of the
rese
>> if I haven't overlooked it, the patch does not provide a "factory" Image as
>> in ar71xx, at least according to "Flashing instructions".
> if I parse this correctly, then my answer is, that I simply didn't included
> instructions for flashing of factory image as it wasn't possible at that time,
* chacha20,poly1305: fix up for win64
* poly1305: only export neon symbols when in use
* poly1305: cleanup leftover debugging changes
* crypto: resolve target prefix on buggy kernels
* chacha20,poly1305: don't do compiler testing in generator and remove xor
helper
* crypto: better path resolution
