From: Dave Taht <dave.taht@gmail.com>
To: Lars Kruse <lists@sumpfralle.de>
Cc: lede-dev@lists.infradead.org,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [LEDE-DEV] lede integration issues remaining from the detrius of cerowrt
Date: Sun, 12 Jun 2016 08:23:04 -0700 [thread overview]
Message-ID: <CAA93jw52Umkw7Q2c73tBLebVXbvmN6r0a0VauczFev0BNc+vuA@mail.gmail.com> (raw)
In-Reply-To: <20160612000748.4b208d1f@erker.lan>
On Sat, Jun 11, 2016 at 3:07 PM, Lars Kruse <lists@sumpfralle.de> wrote:
> Hi Dave,
>
>> D) https://github.com/dtaht/ceropackages-3.10/tree/master/utils/nanom5poe
>>
>> I don't know what landed upstream to control poe for the nano-m5
>> radios, if anything?
>
> I submitted a patch (that was accepted) for GPIO-based POE control - at least
> for Nanostations XM/XW and for TP-Link CPE210 and CPE510:
> https://git.lede-project.org/?p=source.git;a=commitdiff;h=d65916047b44d6d157d88d15e8e3d92555c5e6f8
Groovy. There are quite a few other devices that have POE (edgerouter
is the first that comes to mind), perhaps this can be built on
generically?
> Only the luci interface is missing ...
noted....
>
> Cheers,
> Lars
>
> _______________________________________________
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-06-12 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 17:44 [Cerowrt-devel] " Dave Taht
2016-06-11 18:19 ` [Cerowrt-devel] [LEDE-DEV] " Rosen Penev
2016-06-11 22:07 ` Lars Kruse
2016-06-12 15:23 ` Dave Taht [this message]
2016-06-12 15:39 ` Lars Kruse
2016-06-12 0:38 ` Daniel Curran-Dickinson
2016-06-12 0:56 ` David Lang
2016-06-12 16:10 ` Dave Taht
2016-06-12 8:06 ` [Cerowrt-devel] " Alan Jenkins
2016-06-12 15:31 ` Dave Taht
2016-06-12 9:17 ` [Cerowrt-devel] [LEDE-DEV] " Dirk Neukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw52Umkw7Q2c73tBLebVXbvmN6r0a0VauczFev0BNc+vuA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=lede-dev@lists.infradead.org \
--cc=lists@sumpfralle.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox