07.05.2017 23:24, Sven Roederer:
On Sonntag, 7. Mai 2017 12:25:39 CEST you wrote:
Just an opinion: being able to disable/enable PoE for each port is really
useful when you want to remotely reboot a device plugged into your PoE
switch/router. Most PoE-capable devices expose this option with the
On 2017-05-06 14:47, Jo-Philipp Wich wrote:
Hi,
Are there any comments about this patch?
can't you achieve the same by simply watching ifdown events and
checking
ifstatus/devstatus indicators?
No, unfortunately not. An ifdown event is only generated when the
interface has already been up
This patch adds supports for the GL-inet GL-MT300N-V2.
Specification:
- SoC: MediaTek MT7628AN
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR
- Ethernet: 1 x WAN (100 Mbps) and 1 x LAN (100 Mbps)
- USB: 1 x USB 2.0 port
- Button: 1 x switch button, 1 x reset button
- LED: 3 x LEDS (system power
On Sonntag, 7. Mai 2017 12:25:39 CEST you wrote:
> Just an opinion: being able to disable/enable PoE for each port is really
> useful when you want to remotely reboot a device plugged into your PoE
> switch/router. Most PoE-capable devices expose this option with the stock
> firmware.
>
> Does yo
When running "make {config|defconfig|oldconfig}" with symlinked .config
(e.g. to env/.config) it renames symlink to .config.old, creates new
.config file, and writes the updated configuration into it.
This breaks the desired workflow when changes in the configuration can
be checked using "scripts/
On Sat, May 06, 2017 at 08:08:54PM +0200, Mathias Kresin wrote:
> 06.05.2017 14:31, Sven Roederer:
> >On Freitag, 5. Mai 2017 14:32:12 CEST Mathias Kresin wrote:
> >>Is it necessary to control the GPIOs from userspace/via config files?
> >>If not, add a gpio_export node to the dts and set the outpu
