From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Joe Touch <touch@isi.edu>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Tue, 7 Jul 2015 08:16:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1507070809451.11810@uplift.swm.pp.se> (raw)
In-Reply-To: <559B2513.3020909@isi.edu>
On Mon, 6 Jul 2015, Joe Touch wrote:
> - CC-rc2 doesn't have a WRT1200AC build
> presumably I should have used mvebu-armada-385-linksys-caiman,
> but it's not at all clear
Yes, that's the one for the WRT1200AC. It's called "caiman" internally at
Linksys it seems.
> - and I'd have to install LUCI and/or reinstall
> factory firmware from the command line, and none
> of that is all that clear, esp. a recovery route
> that doesn't involve voiding warranty to wire in
> a serial port
You can flash back the factory firmware without serial, you just use
sysupgrade with the Linksys factory image. I've done this. It's not easy
to get into the box, and I have plastic dents on my unit now because I
failed to understand how it fits together. I also ended up buying pin
headers with tweezers to connect the TTL-USB serial device to the
connector on the PCB. I have since then received proper cables so now I
have wires sticking out and I'm waiting for connectors so I can make a
more permanent solution.
I have also had to use the serial console on mine because something broke
in the upgrade process one of the 30-40 times I did sysupgrade.
I won't speak of the "declared victory". In my opinion the victory might
be "there is now knowledge on how to do this and there is substantial
awareness in the rest of the industry" but it's definitely not executed
yet.
And yes, you're right, there is very little "mainstream" about OpenWrt.
It's reasonably easy with a lot of devices (and there are guides to read),
but it's not like anyone can do it. It's like changing oil in a car, it's
not that hard, but if you don't know how to do it, you need to study first
and find correct tools in order to do it. Also, if you get it wrong you
might damage things.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2015-07-07 6:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 1:02 Joe Touch
2015-07-07 2:23 ` Rich Brown
2015-07-07 4:22 ` Joe Touch
2015-07-07 7:20 ` Sebastian Moeller
2015-07-07 12:03 ` [Cerowrt-devel] [Bloat] " Kevin Darbyshire-Bryant
2015-07-07 14:07 ` [Cerowrt-devel] " Rich Brown
2015-07-07 18:19 ` Matt Taggart
2015-07-08 1:54 ` Rich Brown
2015-07-08 18:37 ` Joe Touch
2015-07-08 20:15 ` Sebastian Moeller
2015-07-08 20:28 ` Joe Touch
2015-07-08 22:16 ` Sebastian Moeller
2015-07-09 1:34 ` Rich Brown
2015-07-08 0:48 ` Jim Reisert AD1C
2015-07-08 2:47 ` Dave Taht
2015-07-07 6:16 ` Mikael Abrahamsson [this message]
2015-07-07 18:34 ` Joe Touch
2015-07-10 7:03 ` Mikael Abrahamsson
2015-07-10 7:22 ` Joe Touch
2015-07-10 7:48 ` Mikael Abrahamsson
2015-07-10 8:01 ` Sebastian Moeller
2015-07-10 16:57 ` Joe Touch
2015-07-07 15:40 ` Dave Taht
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=alpine.DEB.2.02.1507070809451.11810@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=touch@isi.edu \
/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