From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] 4300 or 3700v4 support?
Date: Mon, 27 May 2013 06:40:12 -0700 [thread overview]
Message-ID: <CAA93jw4Ey+0dub7gtaz1SDu0BZkxTTodSOwh3XkENjY-FG-9wA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
forking this thread...
On Mon, May 27, 2013 at 6:32 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
>
> On Mon, May 27, 2013 at 2:32 AM, David Lang <david@lang.hm> wrote:
>
>> On Sun, 26 May 2013, Lance Hepler wrote:
>>
>> That's tragic. I just picked up a Netgear WNDR4300 (openbox on sale at
>>> the
>>> local Fry's) to see if I could hack up a CeroWrt clone on it. It seems to
>>> be mostly the same hardware as the WNDR3700v4 and the TP-Link WDR43[01]0,
>>> with things just wired up slightly differently.
>>>
>>
>> As I understnad it, the difference between the WNDR3700v4 and WNDR4300 is
>> that the 4300 has a slightly better wireless chip.
>>
>> Unfortunantly from what I've seen so far, they did something wierd with
>> the storage and as a result the stock openwrt can't access it. I've seen
>> reports of people getting it to run from an initramfs, but this means that
>> no settings can be preserved across reboot.
>>
>> If you've seen anything different, I'd be very interested to hear about
>> it (I picked up a 3700v4 and a couple 4300's for testing)
>>
>
> according to a birdie, "it looks like it's an ONFI with quirks, or nobody
> has realised that it's ONFI at all.". Perhaps that's enough clue to get
> someone started? but I fear jtag debugging will be needed. Flash chips tend
> to have interesting race conditions....
>
Same birdie:
"Ok, according to
http://www.linux-mtd.infradead.org/nand-data/nanddata.html<http://www.google.com/url?q=http%3A%2F%2Fwww.linux-mtd.infradead.org%2Fnand-data%2Fnanddata.html&sa=D&sntz=1&usg=AFQjCNGiWikrVFzTMiaKh-hXh2QW16hAzQ>it
has a detection bug, that may or may not be significant.
So, it's ONFI 1.0 with quirks
(part is a *Micron 29F1G08ABADA)"
*
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 2900 bytes --]
reply other threads:[~2013-05-27 13:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw4Ey+0dub7gtaz1SDu0BZkxTTodSOwh3XkENjY-FG-9wA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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