Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] tp-link 4300 evaluation
Date: Mon, 27 May 2013 06:33:14 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1305270630570.13408@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw540NNdvfd=9vn1QhA-bUXhCG+WWwi+pSnjY217gi0oHg@mail.gmail.com>

On Mon, 27 May 2013, Dave Taht 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....

Given that we have the GPL source for the kernel available from Netgear, I'm a 
little puzzled that we are having to reverse engineer this instead of working 
from the source.

Even if the first version was little more than a cut-n-paste of the netgear 
butchered driver until people have time to analyse it fully.

David Lang

  reply	other threads:[~2013-05-27 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27  1:23 Lance Hepler
2013-05-27  9:32 ` David Lang
2013-05-27 13:32   ` Dave Taht
2013-05-27 13:33     ` David Lang [this message]
2013-05-27 16:30       ` Lance Hepler
2013-05-27 13:13 ` Dave Taht
2013-05-27 21:08   ` Lance Hepler
2013-05-27 23:41     ` Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2013-05-26 12:08 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.1305270630570.13408@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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