this commit allows to make both a standalone and
a second-stage u-boot for nsa310b, but only
first-stage u-boot is added in the makefile and
available in the build system.
The reason is that while both work fine if installed to flash
or loaded with kwboot, I could not get stock u-boot nor
bodhi's u-boot to chainload any second stage u-boot
(I also tried with dockstar's uboot that works fine
on this device if loaded with kwboot).

> this commit allows to make both a standalone and
> a second-stage u-boot for nsa310b, but only
> first-stage u-boot is added in the makefile and
> available in the build system.
>
> The reason is that while both work fine if
> installed to flash
> or loaded with kwboot, I could not get stock
> u-boot nor
> bodhi's u-boot to chainload any second stage
> u-boot
> (I also tried with dockstar's uboot that works
> fine
> on this device if loaded with kwboot).
>

Ah! that LEDE 2nd stage. IMHO, it is a poor approach. So I will not support it.

It seems nbd merged an older patch for the u-boot, it has wrong mtdparts and usb does not work. Will send again a patch for that later.

For now, install bodhi's uboot for nsa310 and its envs, then change or create envs to allow booting LEDE (it will work also in the future, no need to install LEDE's uboot when I fix it) with these commands

I have added support for the two devices I own (nsa310 and nsa325), and I'm going to try adding all other kirkwoods you support to LEDE, but I'll need a place for someone with the device to test it.

But apart from that it's not going to see much use, as I'm sending patches to LEDE, not making my own downstream project like you are doing with Debian.
So people should use LEDE download servers to get the firmwares and forums for any question.

I actually told kofec to use LEDE forums for his issues, not to come bother people here. :)

If you are ok with letting me make a "let's add support to LEDE/OpenWRT for kirkwood boxes" thread in the Debian section (even if it is not Debian, just for visibility), it's probably enough for me, and it will go dead and can be moved somewhere else after I'm done.

> If you are ok with letting me make a "let's add su
> pport to LEDE/OpenWRT for kirkwood boxes" thread i
> n the Debian section (even if it is not Debian, ju
> st for visibility), it's probably enough for me, a
> nd it will go dead and can be moved somewhere else
> after I'm done.

Please go ahead and make a thread for it in Debian section.

But have a description in the first post that describes the use cases for LEDE/OpenWrt. Things such as why would ones want to use LEDE. For example, embedded systems only, memory restriction, don't care much for latest security patches...etc. Things that emdebian used to exists for. Note that we have a sticky emdebian thread before: http://forum.doozan.com/read.php?2,72. So what you do is great, IMO. As long as we don't advocate people using it as a NAS (Debian is a better fit for that). I know you can make it a NAS with further modification, but that would be a distraction in a Debian forum.

It is not working but it is not critical. With the original Zyxel firmware it works this way that I'm able to wake on lan via eth addr provided with device till there is no power outage. But when there is no power on NSA310 I have to use 00:00:00:00:00:30 also.

Quotebobafetthotmai
How is Wake on Lan working with this firmware after you set mac address?
Does it still want 00:00:00:00:00:30 or it works with right mac address?

Please, enter the code that you see below in the input field.
This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right.
If you enter the wrong code, a new image is created and you get
another chance to enter it right.