From owner-freebsd-embedded@FreeBSD.ORG Wed Jul 10 22:59:35 2013 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 64F64581 for ; Wed, 10 Jul 2013 22:59:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 27BAD1040 for ; Wed, 10 Jul 2013 22:59:35 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id n1so3972334qcw.16 for ; Wed, 10 Jul 2013 15:59:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9wqpxfXG+F8BlYN/KXI+ffcx5IkiuuuX0A1Vs7bDZtY=; b=Q6GqAAiCX4TlKLnVfd/FfY7knXZmeNqijblXpmJca2Jp8C8iM3PufAlAiVv53DckfF DJRGvlnc1/P9JXCRgWnw+m4yDzZ4wnVFKe9YIlz13whUYvdXjn7bX062CJ4mZNQPM1Aq OpPKP9CpQpQiMA4C6U8vUReyzCMdY3Efoi+8XjHvTmpoT95pP7KmMITUvUoivd3TIQXK euW26uD4ey+T9hTamsTePDkFvffzeuTfaTWKKgG91LbHGfO/YH/EJi6GaNRK3jWcT17v TBwXPdt2eWnEOpMlunwHtolZWtxC28m1oVr01lqXLEf6CnAbx8CfzgGIxUdG9QHRgIOf BP/A== MIME-Version: 1.0 X-Received: by 10.224.127.73 with SMTP id f9mr30058022qas.4.1373497174583; Wed, 10 Jul 2013 15:59:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Wed, 10 Jul 2013 15:59:34 -0700 (PDT) In-Reply-To: References: <20130701152313.60982@relay.ibs.dn.ua> <20130701220301.1636@relay.ibs.dn.ua> <20130702085213.52064@relay.ibs.dn.ua> <18a9b686d7f49d3773ad63eb853b1c88.squirrel@arroway.org> Date: Wed, 10 Jul 2013 15:59:34 -0700 X-Google-Sender-Auth: 7uFi40xhZHKcsFhH1L8g8A-0se8 Message-ID: Subject: Re: FreeBSD on ASUS, TP-Link and D-Link routers? From: Adrian Chadd To: Nenhum_de_Nos Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 22:59:35 -0000 Yeah: [mktplinkfw] *** error: separate kernel image is too big lucy# ../../build/trunk/build/bin/build tl-wr1043nd tplink *** Configuration file : tl-wr1043nd *** Platform : mipseb *** Target : tplink 4096+2 records in 4096+1 records out 2097287 bytes transferred in 2.249939 secs (932153 bytes/sec) [mktplinkfw] *** error: separate kernel image is too big: 2097287 bytes > 2096640 bytes The kernel image is just plain too big. 5mb for an uncompressed cut-down kernel? Sigh. The downside? We can't build a cut down ath module right now that'll work, as the module API doesn't pull in kernel config options. Sigh. adrian