Re: [OpenWrt-Devel] Fwd: Removing Telnet

On Tue, Sep 8, 2015 at 4:13 AM, Jakub Jančo wrote: > Is slow login still present on ssh? > Because we had problem, that ssh login takes about 10seconds and > telnet is instant. It is difference if we do initial bulk setup for > more devices. Experience with SSH breakage tells

Re: [OpenWrt-Devel] Optimize for speed, not for size

On Mon, Jan 17, 2011 at 00:32, Bastian Bittorf bitt...@bluebottle.com wrote: this is theory as must be checked. If the GCC man page is theoretical, then I'm obviously a big fan of fiction. Please spend an evening with 'man 1 gcc' and learn what optimizations are turned on with what switches and

Re: [OpenWrt-Devel] Optimize for speed, not for size

On Sun, Jan 16, 2011 at 10:06, Bastian Bittorf bitt...@bluebottle.com wrote: what is the best point to enforce an compilation with -O3 instead of -Os ? Sorry to answer a question with another question, but why -O3? Are you aware that on these size- and performance-restricted platforms -Os is

Re: [OpenWrt-Devel] Hooks for preconfiguring the system before cutting images

se, but any file/directory structure that's placed in a directory called files at the root of your build directory gets placed in the root of your filesystem image prior to cutting it. RB ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] [PATCH] WRT54G3GV2-VF support and trx.c fix

the only commercial PCMCIA on MIPS I'm aware of. RB ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] WRT54G3GV2-VF support and trx.c fix

On Thu, Jul 1, 2010 at 11:58, Niclas Koeser n...@informatik.uni-kiel.de wrote: Please note 4c164de5.5030...@informatik.uni-kiel.de. ;) I understand, and gather that you're booting 2.6 on the system (which I was able to do as well). My main question is whether the PCMCIA works properly now or

Re: [OpenWrt-Devel] [PATCH] WRT54G3GV2-VF support and trx.c fix

On Thu, Jul 1, 2010 at 12:15, Niclas Koeser n...@informatik.uni-kiel.de wrote: I wonder if there are differrent Versions of the V2 around... Entirely plausible. Unfortunately, that job's long behind me and I don't have any of the hardware laying around...

Re: [OpenWrt-Devel] a lot of webservices of openwrt.org are broken

On Tue, Apr 14, 2009 at 09:44, Weedy weedy2...@gmail.com wrote: N. Fresh start is good. Just look at gentoo-wiki.{com,info} Take a breath... Good. :) There's a lot of really good information in the old wiki, much of which is still valid but poorly maintained. The

Re: [OpenWrt-Devel] a lot of webservices of openwrt.org are broken

On Tue, Apr 14, 2009 at 17:43, Benjamin Henrion b...@udev.org wrote: BTW, is it possible to have a ZIP copy of the full wiki, including the history of the pages? That's what we (Kloschi and I) are waiting on. I have contributed to the wiki, and I expect that the history of pages will

Re: [OpenWrt-Devel] After server upgrade

On Mon, Apr 13, 2009 at 19:22, poelzi poe...@poelzi.org wrote: - SVN access: There has been a switch from https:// (webdav) url to svn:// url. Should you encounter problems with updating your local copy, the please run the following command in the local directory: btw. it would be good if

Re: [OpenWrt-Devel] Broken Link for WRT54G3G in Wiki

Currently I am working on the brcm 2.4 build and was hoping to move to the 2.6 kernel if the wifi and pcmcia support was resolved. I saw a post in the forums saying wifi was reasonably stable so was going to check out head and build and see how it goes. I also did some work on the PCMCIA bit.

Re: [OpenWrt-Devel] upgrading kernel

On Wed, Feb 18, 2009 at 08:54, Kövesdi György k...@deverto.hu wrote: The opkg upgrade upgraded my kernel from 2.6.25.19 to 2.6.28.5. After reboot, the old kernel runs. What can I do to solve it? Full re-flash. The kernel may appear to be upgraded, but is monolithically integrated with the

Re: [OpenWrt-Devel] development workflow for kernel patching

On Tue, Jan 20, 2009 at 00:30, Warren Turkal w...@penguintechs.org wrote: 1. What specific kernel version is the 2.6.28 kernel patch set designed to be applied (2.6.28 or 2.6.28.1)? How do I look this information up for myself? That's set in the LINUX_VERSION variable in the target's Makefile

Re: [OpenWrt-Devel] Fwd: ENC: Port solution to Our board Request

Took me a few hours I *REALLY* I wish I were as smart as most of you !! Notice I put port in quotes - all the groundwork was laid, I just had to set the version magic, poke around a little to make sure things were compatible, and flash. Hardly anything intelligent. RB

Re: [OpenWrt-Devel] Fwd: ENC: Port solution to Our board Request

On Tue, Oct 28, 2008 at 09:50, Tripp Lilley [EMAIL PROTECTED] wrote: I read close here as working closely together, not as a typo for closed. :) Thanks for the typo/homonym help! That would certainly make more sense. ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] Smallest Linux

From what I see it is VERY hard to determine what RAM is really needed by the kernel??!! Not sure what you're talking about - one link from the landing page (Size - http://elinux.org/System_Size) indicates you need at least 384k RAM for a 32-bit 2.6 kernel running TCP. Seems pretty clear to

Re: [OpenWrt-Devel] Smallest Linux

50kB of RAM is *far* from sufficient. OpenWRT runs in 8MB of RAM, and might even do something useful in 4MB, but muh below that doesn't sound promising at all. Under 1MB doesn't even sound promising for an utterly minimal 2.4 kernel. OWRT may be pretty tiny, fitting into 2-3MB of flash

Re: [OpenWrt-Devel] [patch] wrt54g3g-st

Seems like you sent the binary image instead of the patch if I am not mistaking ? Far from being mistaken - that was utter fail on my part. Deepest apologies for the 3.4M attachment! wrt54g3g-st-vermagic.patch Description: Binary data ___

Re: [OpenWrt-Devel] [PATCH] NP25G support / cannot create wiki login

I wanted to add this to the NP25G page on the wiki, but when I try to make an account it says 500 Internal Server Error (sorry - we're updating) :-( Welcome to the party. They've been reportedly setting up a new server and migrating stuff over to that for over a year now. Keep trying,

Re: [OpenWrt-Devel] OpenWrt as non-profit

sides is usually restricted to a 1:1 relationship. Enter hit-by-a-bus discussion. What is OpenWrt's current relationship with private business interests? How will that play into a transition? RB ___ openwrt-devel mailing list openwrt-devel

Re: [OpenWrt-Devel] Generate configs for asterisk from uci

snip I'm only just starting to work with Asterisk, but integrating its configuration into UCI will be a great start in that direction. Looks nice! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] Missing wireless and DHCP server on fresh SVN build?

2) On another note: is there a possibility to immediately set the root password and not start up the telnet daemon at first boot? Disable telnetd in your busybox configuration and either place a prepared passwd file in ${BUILDROOT}/files/etc/passwd (copied from

[OpenWrt-Devel] [PATCH] 3/4 remove linux-2.6 dependency for package kmod-usb-serial-sierrawireless

Enable sierra.c to be configured/built for 2.4 as well. Signed-off-by: RB [EMAIL PROTECTED] 003-enable_usb-serial-sierrawireless_2.4.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http

[OpenWrt-Devel] [PATCH] 1/4 Drop generic Sierra support

Removes the generic support for the AirCard 875 from usbserial.c in the generic-2.4 profile Signed-off-by: RB [EMAIL PROTECTED] 001-drop_generic_sierra.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http

[OpenWrt-Devel] [PATCH] 4/4 add maxwait, config fix

for the 3g interface to show up. It also fixes apparent bugs in the rest of setup_interface_3g where config_get is called against $cfg (which isn't declared in that scope) as opposed to $config. Signed-off-by: RB [EMAIL PROTECTED] 004-add_maxwait_config_fix.patch Description: Binary data

Re: [OpenWrt-Devel] Minimal build of OpenWRT

For reference, bricked is a term I use when there is absolutely nothing that can be done to recover a router -- it should not be applied to cases of nihilistic ignorance or apathy. I think most of us here refer to that as a system that isn't even recoverable via serial terminal - the

Re: [OpenWrt-Devel] Minimal build of OpenWRT

On Tue, Jul 15, 2008 at 6:21 AM, Steven Van Ingelgem [EMAIL PROTECTED] wrote: What packages are minimally needed to make an OpenWRT run? The below list is, for all intents and purposes, the minimal list. Notes below on removal. The packages getting compiled are: - base-files - bridge-utils

Re: [OpenWrt-Devel] Minimal build of OpenWRT

The default SVN build is 1.9M in size. IIRC the micro build of whiterussion was like 1.3M, so I wonder what I need to remove to get it back to that size. Whiterussian's build process was completely different, and I don't see much attention being paid to the systems with under 2MB of flash any

Re: [OpenWrt-Devel] [PATCH] 3/4 Latest Asterisk 1.4.21

On 7/13/08, Michael Geddes [EMAIL PROTECTED] wrote: Update to asterisk 1.4.21 (yes there's a 1.4.21.1 but I haven't tested it) Not sure why, but this hit GMail's spam filter for me. Just an FYI - hope it made it to everyone else. ___ openwrt-devel

Re: [OpenWrt-Devel] [PATCH]

be best to submit them as separate patches. If you'll watch the SVN checkin activity, every delta is incremental, if not discrete; if your changes aren't the same it's unlikely that one of the devs will take the time to split your patch apart, individually test the changes, and apply them. RB

Re: [OpenWrt-Devel] How to submit patches to OpenWRT

about this), and the developer-group would be really happy to listen to ideas, suggestions and practical solutions. Although we can make suggestions we think might work, it really comes down to what works best for the core developers (other than ignoring input... ;) ). Off the top of my head I

Re: [OpenWrt-Devel] patch for ip-up

picking my nose, waiting on a patch from you, so i can ignore it and then get back to picking my nose. I doubt any of we who have submitted ignored updates feel that way, and I'm sorry you think we do. The question I have is whether you core devs would prefer patches submitted in a different

Re: [OpenWrt-Devel] [PATCH] Sierra Wireless AIRCARD support for brcm-2.4

I couldn't find any notes about the card I was using in TRAC, so my apologies if this patch is superfluous. Mark Deneen I'm going to incorporate this patch into mine and make the whole thing more atomic (breaking up the actual patch to 2.4.35 more) and re-submit. On a side note, your patch

[OpenWrt-Devel] [PATCH 2/2] kmod_sierra: remove LINUX_2_6 dependency

This patch enables sierra.o to be configured and compiled for the brcm-2.4 platform. Signed-off-by: RB[EMAIL PROTECTED] sierra-allow-2.4.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http

Re: [OpenWrt-Devel] Adding new platform to openWRT

to the workspace. I've added a patched-2.6.20 directory to target/linux/generic-2.6 and this allows me to control exactly which patches are applied against my kernel, but it seems wrong to have to modify the generic-2.6 folder to get what I want. If there is a way to accomplish this

[OpenWrt-Devel] [PATCH] x86 gen_image.sh modifications

by the author in favor of paxctl, so I added a bit of logic to prefer paxctl over chpax. signed-off by: RB[EMAIL PROTECTED] x86-gen_image-paxctl.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org

Re: [OpenWrt-Devel] what is a standard STL implementation?

i'm not sure what that even means. thoughts? Standard Template Library... if OpenWRT doesn't have one it's likely due to a mucked-up C++ implementation (only having covered it briefly in a course 8 years ago myself). ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] PCMCIA take 2

I don't know much about that interrupt thing that you mentioned, but for improved stability, you should switch to trunk when playing with Linux 2.6 on Broadcom. There are some cache coherency / memory management issues in 7.09, which are almost completely fixed in trunk. I'll do that. I had

Re: [OpenWrt-Devel] PCMCIA take 2

KALLSYMS_ALL didn't produce any different output than the one above. If you would like, I can start stripping those parts out until it'll produce a crash with yenta_socket. In the meantime, here is the oops from crashing on yenta_socket, run through ksymoops.

Re: [OpenWrt-Devel] PCMCIA take 2

It didn't fail at the same point, rather (seemingly) when switch_robo was loading. If you want, I can run it through ksymoops but I haven't done anything funny. Kernel bug detected[#1]: Cpu 0 $ 0 : 1000a800 0001 00024000 $ 4 : 812a9000 80258a74 80258a3c $ 8 : 80001000

Re: [OpenWrt-Devel] why is there a difference in PCMCIA support between brcm24 and brcm47xx?

-enable PCMCIA for brcm47xx with the 2.6 tree? Driver/tool breakage I can deal with, but figuring out your build system is giving me new headaches. RB ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman

Re: [OpenWrt-Devel] why is there a difference in PCMCIA support between brcm24 and brcm47xx?

why does the 2.4-based build select PCMCIA support, but not the 2.6? i would have thought that those two builds should be functionally equivalent, at least in terms of features. Same here - I see bits hinting that there are memory resource issues on the one Linksys brcm47xx with PCMCIA

[OpenWrt-Devel] Serial headers

Can anyone point me to a decent resource to start mucking about with serial headers on an unknown motherboard? I have before me what looks like a typical embedded board with a custom-branded processor I suspect is running Linux. It has a 14-pin header (#3 missing) that seems right, but since I'm

Re: [OpenWrt-Devel] packages/kmod-switch

with a 'corrupted' EEPROM, but one can still specify a MAC for it and press on. RB ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel