This adds detection support and all GPIO-accessible LED and button
mappings for WRT300N v1.1 to the broadcom-diag package.
Also adds proper CyberTAN "EWC2" signature to image Makefile so it
builds proper openwrt-wrt300n_v11-*.bin firmwares, and changes the
firmware version for the v1 to the proper
https://dev.openwrt.org/wiki/GetSource
or more specifically
svn co svn://svn.openwrt.org/openwrt/trunk/
You can't simply download a tarball from the svn browser, you have to
use svn which will download the tree. After initial full checkout
("co") you can later use "svn up" in the project base d
I do not know specifically about the hardware you are working with, but
based on general boot processes I know from other flash-based embedded
platforms, the clue you may need is to use the uncompressed and
non-bootstrapped image for external boot. If you upload the compressed and
bootstrapped ima
The WRT300N versions so far supported did not include the v1.1 which is
a bit different than the others. The current build does not run properly
and inits the switch incorrectly. This patch adds detection to
broadcom-diag and patches the netconfig script to avoid the incorrect
switch settings. Also
This is for an ancient platform, Askey RT210W, which is the same board
used in Belkin F5D4230-4 before but not including v1444 (the old larger
format model with MiniPCI BCM4306 wifi and dual antennae) and original
Siemens SE505v1 (w/o CFE or RAM upgrade), and probably several others.
Sets up prop
(Reminder Copy of original message)
Forwarded Message
> From: Spudz76
> Reply-to: spud...@gmail.com
> To: OpenWrt Development List
> Subject: New Enhancement Ticket (with patch) for WRT300Nv1.1 support
> Date: Fri, 18 Dec 2009 15:31:39 -0600
>
> The WR
(Reminder Copy of original message)
Forwarded Message
> From: Spudz76
> Reply-to: spud...@gmail.com
> To: OpenWrt Development List
> Subject: New Enhancement Ticket (with patch) for RT210W support
> Date: Fri, 18 Dec 2009 16:02:48 -0600
>
> This is fo
Just a friendly reminder to apply this patch, preferably to the 8.09
tree in addition to trunk. Patch is based on 8.09 r18988, but should
apply to trunk just as well. This will instantly enable a bunch of
routers which currently don't work with OpenWRT due to not being
equipped with any parallel
due to missing function references.
On Sat, 2010-01-02 at 12:16 -0600, Spudz76 wrote:
> Just a friendly reminder to apply this patch, preferably to the 8.09
> tree in addition to trunk. Patch is based on 8.09 r18988, but should
> apply to trunk just as well. This will instantly enable a
In many (most?) cases, the wifi driver does not allow you to modify the
MAC address. It's all about spoof protections as was mentioned before.
The only other method I've used with success to achieve something like
you're trying to do without using WDS is to set up a bridge-mode (tap
device, not tu
Ping.
On Sat, 2010-01-09 at 10:00 -0600, Spudz76 wrote:
> I have responded to the ticket and added proper patches for both 8.09
> and trunk, both tested and working on an sflash router. Original 8.09
> patch was missing one file change (linker inclusion for the new
> sflash.o object
https://dev.openwrt.org/ticket/6442
Please note I believe this ticket has been overlooked, with the recent
milestone release and all going on, and it had been tagged for the
completed milestone but wasn't applied as I needed to repair the patch.
I have reminded/pinged a couple times, and would not
YES. In fact, I volunteer for whatever would help with this initiative.
I know reviewing patches is probably the most time consuming bit, so
perhaps if the incoming submissions were prioritized by the submissions
moderator, and then assigned across to a patch reviewer (or a few of
them) who could
I have an MMC-over-GPIO enabled Broadcom but I can't get it to take a
proper flash and boot for some reason with more recent checkouts. It
runs (gasp) DD-WRT just fine though so I'm confused. If I can get it
working again I'll test this, especially since I had to do a whole lot
of fiddling with t
Thank you, thank you, thank you!
On Sat, 2010-01-16 at 16:13 +0100, Jo-Philipp Wich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Committed to trunk in r19171.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.
mebody complains,
> especially as this is not totally new, but based on work already in trunk.
>
> .. bud
>
>
> On 16.01.2010 19:36, Spudz76 wrote:
> > I have an MMC-over-GPIO enabled Broadcom but I can't get it to take a
> > proper flash and boot for some reason with
Confirm this is working with brcm-2.4 now, booted trunk successfully on
ancient BCM4702 platform (RT210W) which didn't previously work except
with 809 SVN tree.
brcm47xx (2.6) still will not boot on this platform with 809 or trunk.
No UART for console either, so it's a complete guessing game. Per
I've got a RTL8651B based platform to work with and I know a couple
other people have been tinkering with it, I'd like to join in on the
fun. If you've got any unreleased/unfinished Realtek/Lexra patches or
etc, please email me. Thanks!
___
openwrt-dev
I have noticed various times that a reboot of the router after
installing luci packages made it work - assuming you didn't try a reboot
yet.
Also sometimes installing luci-admin-mini on its own (with prerequisites
and theme) followed by a reboot, then ensure the interface comes up,
then install lu
Looks like it is completely self-contained and doesn't require any
(usually huge) external libs for crypto or etc. Thus would take up less
space with this plus dropbear, versus full OpenSSH plus the OpenSSL libs
(not sure if OpenSSH uses those, but I think it does).
On Fri, 2010-02-19 at 18:08 +0
I am also still working on the expanded version, as time permits, to
support older cores (4702/4710/4712) without the direct register access
(using the gpio calls via SB). It will all be configurable via module
options, with the fastest access technique used by default. I may also
add some core d
On Wed, 2010-02-24 at 15:27 -0500, Stefan Monnier wrote:
> Indeed. The only difference is that there is no predefined config for
> such small targets, so you have to manually select the part of busybox
> you want to strip, and similarly for the kernel config.
> You should be able to get pretty clo
Committed revision 19862. Thanks!
On Mon, 2010-02-22 at 14:14 +0100, Raphaël HUCK wrote:
> Hi,
>
> this patch adds wide-dhcpv6 package.
>
> -Raphael
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mail
Committed revision 19881.
Also minor change, I set libsysfs to show up in menuconfig under
"Libraries/Filesystem" instead of just "Libraries", to better match the
sysfsutils placement under "Utilities/Filesystem".
Thanks!
___
openwrt-devel mailing list
> > Apart from this, the original value seems to be wrong:
> >
> > (((1UL << 10) - 1) << 0) = 0x3ff = 1023
> >
> > The switch should be able to handle larger frames than this.
> You're right. The datasheet says bits 0:10, so it should have been 11
> bits not 10. Fixed in r20110
Following this lo
This may be a slightly odd question, so let me fill in the history
behind it:
- I have a router model, Netcore NW618
- DD-WRT also supports this router
- I've repaired sflash support in brcm-2.4, so it boots OpenWRT
When running DD-WRT latest version and their version of broadcom-wl
(4.150.10.31)
On Mon, 2010-03-15 at 09:33 +0100, Bas Mevissen wrote:
> On Sat, 2010-03-13 at 18:31 +0100, Joerg Albert wrote:
> > I use a Prolific PL2303 serial USB adapter which works fine with other
> > hardware. Someone else?
>
> Do you have access to an oscilloscope? It might be that the signal level
> or s
Thank you for your tenacity in getting this added to OpenWRT, and my
personal apologies/commiseration for the extra effort and aggravation
you went through - I also had a few patches that seemed to take forever
to be reviewed and applied, and did all the same sort of reposts,
rebasing, and friendly
You probably need to comment out the console entries for the serial
port(s) in /etc/inittab and then try again. That should free up the
port for use with minicom (or any other serial app).
You have to reboot to have the change take effect, unless you customize
your busybox (compile your own image
That official submission policy is a bit outdated and we intend to
update it at some point.
Due to the issues with email clients and inline patches being mangled
more often than not, the current best method that works no matter what
is to create a ticket in Trac, attach your patch(es) to it, and r
I think you might be right. I'll email off-list tonight.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I'd take it for dev work, I've been wanting to get into some of the
Atheros platforms.
Let me know how much for shipping and where to paypal or whatever. I'll
even send it back to you once it's fully supported and repaired, if you
want. Thanks!
On Sat, 2010-04-03 at 16:07 -0500, W.MichaelP wrot
You either suffer throughput, or turn up the beacon interval to
something that still works but doesn't blow as much combined bandwidth
over time. Default is usually 100ms so you're sending an AP beacon
frame for each SSID ten times a second. You could turn it up to
something more like 500ms but t
Nope, it goofed up the tabs. Contrary to the list/submission guidelines
you can just attach the patches/diffs rather than trying to get them
inlined properly.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailm
Sent off-list email with tar containing the mk/unsquashfs-lzma from my
64-bit tree. Still should run 32-bit binaries if you have all the right
lib32* compatibility pkgs installed, but maybe not (due to differences
in size of int, etc). But now you have the native x86-64 ones so those
should d
Sent x86-64 binaries from Backfire, which uses squashfs4. First set was
squashfs3 from Kamikaze tree. Apologies. At least you're prepared with
both versions now. :)
Not really any easy way to cross compile x86-64 binaries on a 32-bit
host, that I know of. A little easier to do 32-bit on a
Still wonder why they make these so hard to get and mark them
obnoxiously like it's going to burn down their company if the "wrong
people" get their hands on them.
jason duhamell wrote:
ar2317 datasheet
___
openwrt-devel mailing list
openwrt-devel@l
ul 16, 2010 at 9:11 PM, Spudz76 <mailto:spud...@gmail.com>> wrote:
Still wonder why they make these so hard to get and mark them
obnoxiously like it's going to burn down their company if the
"wrong people" get their hands on them.
jason duhamell wro
I'm positive it's not his own NDA that is being violated, he's just
resourceful and weird things happen in China. He never made such an
agreement and is not bound by the scary little grey watermarks, and
neither are we. The only people or projects at any real risk here are
whoever leaked it a
would like to discuss that, feel free to join in the conversation.
On Fri, Jul 16, 2010 at 10:00 PM, Spudz76 <mailto:spud...@gmail.com>> wrote:
I'm positive it's not his own NDA that is being violated, he's
just resourceful and weird things happen in China. He nev
40 matches
Mail list logo
