From owner-freebsd-mips@FreeBSD.ORG Sun Nov 21 07:18:48 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 425DF106564A for ; Sun, 21 Nov 2010 07:18:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id C50968FC14 for ; Sun, 21 Nov 2010 07:18:47 +0000 (UTC) Received: by wwd20 with SMTP id 20so5986538wwd.31 for ; Sat, 20 Nov 2010 23:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=ue/CSWqq61wKStPy5yF4v5yTGuW2b5dDRHc1cD4JRhI=; b=PoRrlZ1eWUJSsbffox9+ZGTMG9hLkTK+L1PCEovZ0igyPfJAFqeQwdPmJTtf3K3/B0 kREHkCUGL5VlP2ZIiYi+WDIdpULQYqGR64N4v6NQm7USAmD7TrZsp1vYJCYSWgM7J+f2 nTWGBySz7F9tVPrNPXZSzYc6pvLSYlUWiD4Ss= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=bcDJGpdRH56dkz1zRoSyM+4eiLwNfv6QSDywNas0ZZK0a4J2fDfv5thtTsrdBZ1wD3 KkiKB3TjgLno4bBhWKMjkgiJdm04quw+yDIM5su+wNRpRpnZZqDWOgMPXw7ul8hTVpv/ TOpBd2XvCu0dolAuGD9m67CvpUmAHvJibIdzo= MIME-Version: 1.0 Received: by 10.216.46.193 with SMTP id r43mr180770web.20.1290323925940; Sat, 20 Nov 2010 23:18:45 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Sat, 20 Nov 2010 23:18:45 -0800 (PST) In-Reply-To: References: <201011191201.47230.freebsd-mips@dino.sk> Date: Sun, 21 Nov 2010 15:18:45 +0800 X-Google-Sender-Auth: xr9-Al-RCOjtO4u8xidf1leYWAE Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mips@freebsd.org Subject: Re: First RSPRO deployed ! X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 07:18:48 -0000 Nah, the problem is: * the large, fixed blocksize that the current flash code has; * ffs isn't really optimised for this kind of flash; * this kind of flash is will not like constant 4k erase cycles, which is unfortunately what you'll end up with. My current path forward is: * aim to get geom_ulzma into the base :-) * modify it a bit so it exports two GEOM devices - a read-only device with the lzma'ed FS in it, and a read-write'able "rest"; * modify GEOM to pass through disk parameters from the provider, so the flash device can export attributes (read size, write sizes, etc); * modify the flash driver to have a small default block size (say, 128 bytes) so small transactions don't require huge amounts of SPI bus access; * experiment with a simple append-only flash FS, which mounts on top of a read-only base filesystem. This mirrors what the flash device/fs stuff in linux does to some extent. The "rootfs" partition has a read only bit. Any filesystem modifications happen in the read-write part -after- that. If the user wants, they can simply erase the rootfs part -after- the read-only lzma'ed FFS partition, giving them a clean "default" system. If someone else wants to give this a go, be my guest. :-) Adrian On 19 November 2010 19:06, Monthadar Al Jaberi wrote: > On Fri, Nov 19, 2010 at 12:01 PM, Milan Obuch wrote: >> On Thursday 18 November 2010 13:43:51 Monthadar Al Jaberi wrote: >>> OMG, thank you Luiz for the file.... Adrian forgot to mention that you >>> need to add kern_memstart field to the fw_layout_data structure!!! >>> >>> Its works...so I guess to boot from flash we need to play with the >>> flash driver and ffs... thats a totally different story though :P >>> >> >> Well, with mkfwimage it is possible to write FreeBSD into flash on RSPRO and >> boot from it. I just verified this. Using it the way it's used in mkflash >> script has one drawback, I think - your setup is static and you are not using >> whole flash to its best potential as well. Actually, with patches you are able >> to read flash (verified) and probably write to it, too, so the 'only' >> remaining part is ffs tuned to use it... > > mm, as I understood it it should be easy for ffs2 to work, just need > to fix some macros so that the code that probes for the superblock > work... > reading/writting to flash with correct sectorsize is no problem.... > >> >> Regards, >> Milan >> > > > > -- > //Monthadar Al Jaberi > _______________________________________________ > freebsd-mips@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org" > From owner-freebsd-mips@FreeBSD.ORG Sun Nov 21 07:20:37 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66A4D106564A for ; Sun, 21 Nov 2010 07:20:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id EDE908FC08 for ; Sun, 21 Nov 2010 07:20:36 +0000 (UTC) Received: by wwd20 with SMTP id 20so5987138wwd.31 for ; Sat, 20 Nov 2010 23:20:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=qb57LRA0iRBfLOG2FvhfFardk3ggZWYH2d9GqRnpMwQ=; b=wc9y1YefDQeNtQFukygYICJ4ec/qXM59O+Vtig24AMXjFZIgl4PcvqMVx1tG6Z2j10 sPAS4w/2PJpHbBrT49OOWmY7DrJxyP1uRSgIDfvxKcVNjIMfzYjm9oKtPftHZm/Ce54q Dg0W6BnB7MezKYECbSShmYK01ot1nxZUztk0E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=d254XckBHPjA8qUY+yghVO73MafnLHEXRBb5raIKpTJdSOYsVUGHfcfMDZ4w6GX3iX +26SdzwCjrUhZpkQst+m/9aH0LGOzVivSIAneiUHdxGTvVvP+paCopU/VSJVC+YcmOQN fQo1nRxQQ1vBfiWqVnILu7pN4EG53oO9ok6mQ= MIME-Version: 1.0 Received: by 10.216.179.81 with SMTP id g59mr4291958wem.35.1290324035533; Sat, 20 Nov 2010 23:20:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Sat, 20 Nov 2010 23:20:35 -0800 (PST) In-Reply-To: <20101118125812.60e9aafc.ray@dlink.ua> References: <4CE491ED.3030308@userid.org> <20101118125812.60e9aafc.ray@dlink.ua> Date: Sun, 21 Nov 2010 15:20:35 +0800 X-Google-Sender-Auth: EbmyZyrkKqL1vlkUtnkaN_XS5Ec Message-ID: From: Adrian Chadd To: Alexandr Rybalko Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mips@freebsd.org Subject: Re: What platforms are you running? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 07:20:37 -0000 This sounds like the beginnings of a "Actively developed devices" section on the Wiki. :-) Adrian On 18 November 2010 18:58, Alexandr Rybalko wrote: > On Wed, 17 Nov 2010 21:39:41 -0500 > Pierre Lamy wrote: > >>> I'm curious, what specific MIPS platforms will the -CURRENT tree run on, >>> and what are you developing on? >>> > > I'm using Broadcom BCM5354 and Ralink RT3052F. > > -- > Alexandr Rybalko > aka Alex RAY > _______________________________________________ > freebsd-mips@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org" > From owner-freebsd-mips@FreeBSD.ORG Sun Nov 21 14:04:17 2010 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AA101065672; Sun, 21 Nov 2010 14:04:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 3A2668FC0C; Sun, 21 Nov 2010 14:04:17 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id oALE4G0b067017; Sun, 21 Nov 2010 09:04:16 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id oALE4GjQ067008; Sun, 21 Nov 2010 14:04:16 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 21 Nov 2010 14:04:16 GMT Message-Id: <201011211404.oALE4GjQ067008@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on mips/mips X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 14:04:17 -0000 TB --- 2010-11-21 13:10:37 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-11-21 13:10:37 - starting HEAD tinderbox run for mips/mips TB --- 2010-11-21 13:10:37 - cleaning the object tree TB --- 2010-11-21 13:10:47 - cvsupping the source tree TB --- 2010-11-21 13:10:47 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2010-11-21 13:11:02 - building world TB --- 2010-11-21 13:11:02 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-21 13:11:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-21 13:11:02 - TARGET=mips TB --- 2010-11-21 13:11:02 - TARGET_ARCH=mips TB --- 2010-11-21 13:11:02 - TZ=UTC TB --- 2010-11-21 13:11:02 - __MAKE_CONF=/dev/null TB --- 2010-11-21 13:11:02 - cd /src TB --- 2010-11-21 13:11:02 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 21 13:11:03 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /src/usr.bin/xargs/xargs.c: In function 'pids_init': /src/usr.bin/xargs/xargs.c:629: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'pids_empty': /src/usr.bin/xargs/xargs.c:641: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'pids_full': /src/usr.bin/xargs/xargs.c:647: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'findfreeslot': /src/usr.bin/xargs/xargs.c:676: warning: old-style function definition *** Error code 1 Stop in /src/usr.bin/xargs. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-11-21 14:04:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-11-21 14:04:16 - ERROR: failed to build world TB --- 2010-11-21 14:04:16 - 2221.34 user 575.13 system 3218.94 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-mips@FreeBSD.ORG Sun Nov 21 14:28:58 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 344671065670; Sun, 21 Nov 2010 14:28:58 +0000 (UTC) (envelope-from ray@ddteam.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 96B238FC14; Sun, 21 Nov 2010 14:28:57 +0000 (UTC) Received: by fxm19 with SMTP id 19so4269240fxm.13 for ; Sun, 21 Nov 2010 06:28:56 -0800 (PST) Received: by 10.223.74.198 with SMTP id v6mr4134155faj.4.1290347916367; Sun, 21 Nov 2010 05:58:36 -0800 (PST) Received: from rnote.ddteam.net (68-13-133-95.pool.ukrtel.net [95.133.13.68]) by mx.google.com with ESMTPS id e6sm1045563fav.8.2010.11.21.05.58.33 (version=SSLv3 cipher=RC4-MD5); Sun, 21 Nov 2010 05:58:34 -0800 (PST) Date: Sun, 21 Nov 2010 15:58:10 +0200 From: Aleksandr Rybalko To: Adrian Chadd Message-Id: <20101121155810.e615d4ad.ray@ddteam.net> In-Reply-To: References: <201011191201.47230.freebsd-mips@dino.sk> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; i386-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-mips@freebsd.org Subject: Re: First RSPRO deployed ! X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 14:28:58 -0000 Hi, On Sun, 21 Nov 2010 15:18:45 +0800 Adrian Chadd wrote: > Nah, the problem is: > > * the large, fixed blocksize that the current flash code has; > * ffs isn't really optimised for this kind of flash; > * this kind of flash is will not like constant 4k erase cycles, which > is unfortunately what you'll end up with. > > My current path forward is: > > * aim to get geom_ulzma into the base :-) No problem to add geom_ulzma into base, problem with lzma. LZMA decoder currently stored in geom_ulzma.c, this one has style(9) problems. Another one decoder live in libarchive, this one inaccessible by kernel. So we need something middle, like zlib in kernel code (why it in net subdir, but uses with many parts) > * modify it a bit so it exports two GEOM devices - a read-only device > with the lzma'ed FS in it, and a read-write'able "rest"; For what? flash splited by parts by geom_map (old name geom_mtd, loos@ name geom_flash IIRC), that parts rw, parts where stored ulzma compressed data handled by GEOM_ULZMA, that RO. I also use small hack enabled writing for overlapped parts. Biggest part named "upgrade" overlapped with "kernel" part and "rootfs", so we can upgrade box when "kernel" and "rootfs" are opened. > * modify GEOM to pass through disk parameters from the provider, so > the flash device can export attributes (read size, write sizes, etc); > * modify the flash driver to have a small default block size (say, 128 > bytes) so small transactions don't require huge amounts of SPI bus > access; I use BS=4, since I know many devices that map their FS not to block boundary. > * experiment with a simple append-only flash FS, which mounts on top > of a read-only base filesystem. > > This mirrors what the flash device/fs stuff in linux does to some > extent. The "rootfs" partition has a read only bit. Any filesystem > modifications happen in the read-write part -after- that. If the user > wants, they can simply erase the rootfs part -after- the read-only > lzma'ed FFS partition, giving them a clean "default" system. > > If someone else wants to give this a go, be my guest. :-) > > > Adrian > > On 19 November 2010 19:06, Monthadar Al Jaberi > wrote: > > On Fri, Nov 19, 2010 at 12:01 PM, Milan Obuch > > wrote: > >> On Thursday 18 November 2010 13:43:51 Monthadar Al Jaberi wrote: > >>> OMG, thank you Luiz for the file.... Adrian forgot to mention > >>> that you need to add kern_memstart field to the fw_layout_data > >>> structure!!! > >>> > >>> Its works...so I guess to boot from flash we need to play with the > >>> flash driver and ffs... thats a totally different story though :P > >>> > >> > >> Well, with mkfwimage it is possible to write FreeBSD into flash on > >> RSPRO and boot from it. I just verified this. Using it the way > >> it's used in mkflash script has one drawback, I think - your setup > >> is static and you are not using whole flash to its best potential > >> as well. Actually, with patches you are able to read flash > >> (verified) and probably write to it, too, so the 'only' remaining > >> part is ffs tuned to use it... > > > > mm, as I understood it it should be easy for ffs2 to work, just need > > to fix some macros so that the code that probes for the superblock > > work... > > reading/writting to flash with correct sectorsize is no problem.... > > > >> > >> Regards, > >> Milan > >> > > > > > > > > -- > > //Monthadar Al Jaberi > > _______________________________________________ > > freebsd-mips@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > > To unsubscribe, send any mail to > > "freebsd-mips-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-mips@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to > "freebsd-mips-unsubscribe@freebsd.org" -- Aleksandr Rybalko From owner-freebsd-mips@FreeBSD.ORG Sun Nov 21 17:38:12 2010 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4497106566B; Sun, 21 Nov 2010 17:38:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 52A968FC15; Sun, 21 Nov 2010 17:38:12 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id oALHcBIm040252; Sun, 21 Nov 2010 12:38:11 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id oALHcBoV040251; Sun, 21 Nov 2010 17:38:11 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 21 Nov 2010 17:38:11 GMT Message-Id: <201011211738.oALHcBoV040251@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on mips/mips X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 17:38:12 -0000 TB --- 2010-11-21 16:45:32 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-11-21 16:45:32 - starting HEAD tinderbox run for mips/mips TB --- 2010-11-21 16:45:32 - cleaning the object tree TB --- 2010-11-21 16:45:40 - cvsupping the source tree TB --- 2010-11-21 16:45:40 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2010-11-21 16:46:01 - building world TB --- 2010-11-21 16:46:01 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-21 16:46:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-21 16:46:01 - TARGET=mips TB --- 2010-11-21 16:46:01 - TARGET_ARCH=mips TB --- 2010-11-21 16:46:01 - TZ=UTC TB --- 2010-11-21 16:46:01 - __MAKE_CONF=/dev/null TB --- 2010-11-21 16:46:01 - cd /src TB --- 2010-11-21 16:46:01 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 21 16:46:01 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /src/usr.bin/xargs/xargs.c: In function 'pids_init': /src/usr.bin/xargs/xargs.c:629: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'pids_empty': /src/usr.bin/xargs/xargs.c:641: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'pids_full': /src/usr.bin/xargs/xargs.c:647: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'findfreeslot': /src/usr.bin/xargs/xargs.c:676: warning: old-style function definition *** Error code 1 Stop in /src/usr.bin/xargs. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-11-21 17:38:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-11-21 17:38:11 - ERROR: failed to build world TB --- 2010-11-21 17:38:11 - 2233.18 user 592.09 system 3159.30 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-mips@FreeBSD.ORG Sun Nov 21 21:08:41 2010 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2F551065674; Sun, 21 Nov 2010 21:08:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 82AED8FC13; Sun, 21 Nov 2010 21:08:41 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id oALL8epk006996; Sun, 21 Nov 2010 16:08:40 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id oALL8eLq006994; Sun, 21 Nov 2010 21:08:40 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 21 Nov 2010 21:08:40 GMT Message-Id: <201011212108.oALL8eLq006994@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on mips/mips X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2010 21:08:42 -0000 TB --- 2010-11-21 20:15:57 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-11-21 20:15:57 - starting HEAD tinderbox run for mips/mips TB --- 2010-11-21 20:15:57 - cleaning the object tree TB --- 2010-11-21 20:16:07 - cvsupping the source tree TB --- 2010-11-21 20:16:07 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2010-11-21 20:16:23 - building world TB --- 2010-11-21 20:16:23 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-21 20:16:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-21 20:16:23 - TARGET=mips TB --- 2010-11-21 20:16:23 - TARGET_ARCH=mips TB --- 2010-11-21 20:16:23 - TZ=UTC TB --- 2010-11-21 20:16:23 - __MAKE_CONF=/dev/null TB --- 2010-11-21 20:16:23 - cd /src TB --- 2010-11-21 20:16:23 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 21 20:16:23 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /src/usr.bin/xargs/xargs.c: In function 'pids_init': /src/usr.bin/xargs/xargs.c:629: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'pids_empty': /src/usr.bin/xargs/xargs.c:641: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'pids_full': /src/usr.bin/xargs/xargs.c:647: warning: old-style function definition /src/usr.bin/xargs/xargs.c: In function 'findfreeslot': /src/usr.bin/xargs/xargs.c:676: warning: old-style function definition *** Error code 1 Stop in /src/usr.bin/xargs. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-11-21 21:08:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-11-21 21:08:40 - ERROR: failed to build world TB --- 2010-11-21 21:08:40 - 2230.92 user 591.59 system 3162.61 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-mips@FreeBSD.ORG Mon Nov 22 07:54:32 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC6071065670 for ; Mon, 22 Nov 2010 07:54:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3AEB18FC17 for ; Mon, 22 Nov 2010 07:54:31 +0000 (UTC) Received: by wwd20 with SMTP id 20so6775201wwd.31 for ; Sun, 21 Nov 2010 23:54:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=2CXevff6Tld+uhykEv37WBVabCfQFtpMRn5taTy12zk=; b=OPlGdUzLNY4BV11c8m5lJoQYhU6DY8leIN+b60aSPJX0YDtrvQmIvim1JbSGU3i2wk i7Qx8mHbyv1UlqqymkWZiISxrkYHMAWIof9TxD1yGChkBHr2qObq4UC/FLq+HdtnSKaf FTEL/gVArFYED4/jeDf4nSmjU6PL2Orbe45Hs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=WfhUFzm05IbqDQ28VOQrNswpl8Ep/8N7C6nhDlIfmPEOHR/8bJpk7GhfZbmBfZ82kw I9FCCRyzq4l1/qvEE3GEj/L8CrLfyApwswIy8WXF196a0LIGzZ6fhDIS7kaqirNm2Lae njPpNk18VISIXGp86TELme3FBjjUHfKOEStrw= MIME-Version: 1.0 Received: by 10.216.157.6 with SMTP id n6mr4756619wek.35.1290412466065; Sun, 21 Nov 2010 23:54:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Sun, 21 Nov 2010 23:54:25 -0800 (PST) In-Reply-To: <20101121155810.e615d4ad.ray@ddteam.net> References: <201011191201.47230.freebsd-mips@dino.sk> <20101121155810.e615d4ad.ray@ddteam.net> Date: Mon, 22 Nov 2010 15:54:25 +0800 X-Google-Sender-Auth: Udjbrn_u28IerMf2nDgKixOi954 Message-ID: From: Adrian Chadd To: Aleksandr Rybalko Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mips@freebsd.org Subject: Re: First RSPRO deployed ! X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2010 07:54:32 -0000 On 21 November 2010 21:58, Aleksandr Rybalko wrote: >> * aim to get geom_ulzma into the base :-) > No problem to add geom_ulzma into base, problem with lzma. > LZMA decoder currently stored in geom_ulzma.c, this one has style(9) > problems. > Another one decoder live in libarchive, this one inaccessible by > kernel. > So we need something middle, like zlib in kernel code (why it in net > subdir, but uses with many parts) Well, it may be possible to create a liblzma for the kernel, if someone's willing to do the legwork to tidy up the style(9) stuff. >> * modify it a bit so it exports two GEOM devices - a read-only device >> with the lzma'ed FS in it, and a read-write'able "rest"; > For what? > flash splited by parts by geom_map (old name geom_mtd, loos@ name > geom_flash IIRC), that parts rw, parts where stored ulzma compressed > data handled by GEOM_ULZMA, that RO. Can you explain it a bit better? The idea is to not have the RW offset/length hardcoded, it instead is based on whatever is left in the partition after the RO LZMA section. > I also use small hack enabled writing for overlapped parts. > Biggest part named "upgrade" overlapped with "kernel" part and "rootfs", > so we can upgrade box when "kernel" and "rootfs" are opened. How do you overwrite "rootfs" if you're running from it? (Without remounting root into a ramdisk and upgrading, openwrt-style.) >> * modify GEOM to pass through disk parameters from the provider, so >> the flash device can export attributes (read size, write sizes, etc); >> * modify the flash driver to have a small default block size (say, 128 >> bytes) so small transactions don't require huge amounts of SPI bus >> access; > I use BS=4, since I know many devices that map their FS not to block > boundary. :( Yup. But I can't help but think BS=4 is going to be very inefficient for any FSes which do lots of small IO. The other thing to consider is what BIO_WRITE means. RIght now it's effectively BIO_READ_OVERWRITE_WRITE - ie, the disk devices handle this as "read in the underlying sector(s), modify what we need to, and write out the results." This is a bit inefficient for flash devices. It may be cleaner to add a new BIO for "flash writes" that have flash-write semantics - ie, depending upon the flash device behaviour, either bits get set 0->1 or they get set 1->0, but an ERASE is needed to reset them. That then begs the question - what about BIO_FLASH_ERASE? Adrian From owner-freebsd-mips@FreeBSD.ORG Mon Nov 22 11:54:26 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5E6D106564A for ; Mon, 22 Nov 2010 11:54:26 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 296998FC14 for ; Mon, 22 Nov 2010 11:54:25 +0000 (UTC) Received: from gw-lan1.kiev.dlink.ua ([192.168.10.10] helo=terran) by dlink.ua with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1PKUyV-0007yP-NF; Mon, 22 Nov 2010 13:54:23 +0200 Date: Mon, 22 Nov 2010 13:57:03 +0200 From: Alexandr Rybalko To: Adrian Chadd Message-Id: <20101122135703.1487660c.ray@dlink.ua> In-Reply-To: References: <201011191201.47230.freebsd-mips@dino.sk> <20101121155810.e615d4ad.ray@ddteam.net> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Aleksandr Rybalko , freebsd-mips@freebsd.org Subject: Re: First RSPRO deployed ! X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2010 11:54:26 -0000 On Mon, 22 Nov 2010 15:54:25 +0800 Adrian Chadd wrote: >> On 21 November 2010 21:58, Aleksandr Rybalko wrote: >> >> >> * aim to get geom_ulzma into the base :-) >> > No problem to add geom_ulzma into base, problem with lzma. >> > LZMA decoder currently stored in geom_ulzma.c, this one has style(9) >> > problems. >> > Another one decoder live in libarchive, this one inaccessible by >> > kernel. >> > So we need something middle, like zlib in kernel code (why it in net >> > subdir, but uses with many parts) >> >> Well, it may be possible to create a liblzma for the kernel, if >> someone's willing to do the legwork to tidy up the style(9) stuff. Thought ideal one is make copy of libarchive part, that have lzma and xz, last based on lzma but have little more power. >> >> >> * modify it a bit so it exports two GEOM devices - a read-only device >> >> with the lzma'ed FS in it, and a read-write'able "rest"; >> > For what? >> > flash splited by parts by geom_map (old name geom_mtd, loos@ name >> > geom_flash IIRC), that parts rw, parts where stored ulzma compressed >> > data handled by GEOM_ULZMA, that RO. >> >> Can you explain it a bit better? The idea is to not have the RW >> offset/length hardcoded, it instead is based on whatever is left in >> the partition after the RO LZMA section. Ah, now I`m understand you. That possible with geom_map. Example: hint.map.0.at="cfid0" hint.map.0.start=0x00000000 hint.map.0.end=0x00030000 hint.map.0.name="cfe" hint.map.0.readonly=1 hint.map.1.at="cfid0" hint.map.1.start=0x00030000 hint.map.1.end=0x00040000 hint.map.1.name="rgdb" hint.map.2.at="cfid0" hint.map.2.start=0x00040000 hint.map.2.end=0x003e0000 hint.map.2.name="upgrade" hint.map.3.at="cfid0" hint.map.3.start=0x003f8000 hint.map.3.end=0x00400000 hint.map.3.name="nvram" hint.map.4.at="cfid0" hint.map.4.start=0x003f6000 hint.map.4.end=0x003f8000 hint.map.4.name="bdcfg" hint.map.5.at="cfid0" hint.map.5.start=0x00040000 hint.map.5.end=0x00120000 hint.map.5.name="kernel" hint.map.5.offset="96" hint.map.6.at="cfid0" hint.map.6.start=0x00120000 hint.map.6.name="rootfs_ro" hint.map.6.offset="96" # File system start without image header hint.map.6.end="search" hint.map.6.searchkey="--some-delimiter--" hint.map.6.searchstart=0x00130000 hint.map.6.searchstep="65536" hint.map.7.at="cfid0" hint.map.7.end=0x003e0000 hint.map.7.name="rootfs_rw" hint.map.7.offset="32" # Skip delimiter size hint.map.7.start="search" hint.map.7.searchkey="--some-delimiter--" hint.map.7.searchstart=0x00130000 hint.map.7.searchstep="65536" In that example GEOM_MAP setup 8 parts, part called rootfs_ro is where lzma-ed rootfs live, part called rootfs_rw is blank part for rw data. GEOM_MAP search for keyword "--some-delimiter--" in flash from searchstart=0x00130000 with step 64k (searchstep="65536") This require correct alignment of key. TODO: make possible to search different start and end keys for parts with float both start and end. make search behavior easiest to define maybe make possible to parts definition via FDT >> >> > I also use small hack enabled writing for overlapped parts. >> > Biggest part named "upgrade" overlapped with "kernel" part and "rootfs", >> > so we can upgrade box when "kernel" and "rootfs" are opened. >> >> How do you overwrite "rootfs" if you're running from it? >> (Without remounting root into a ramdisk and upgrading, openwrt-style.) Embedded device don`t do many operations on roots (all required soft already in memory), so I only omit checking of overlapped parts and do direct write of new image to part (named "upgrade" in example) >> >> >> * modify GEOM to pass through disk parameters from the provider, so >> >> the flash device can export attributes (read size, write sizes, etc); >> >> * modify the flash driver to have a small default block size (say, 128 >> >> bytes) so small transactions don't require huge amounts of SPI bus >> >> access; >> > I use BS=4, since I know many devices that map their FS not to block >> > boundary. >> >> :( Yup. But I can't help but think BS=4 is going to be very >> inefficient for any FSes which do lots of small IO. I`s not about embedded devices :) >> >> The other thing to consider is what BIO_WRITE means. RIght now it's >> effectively BIO_READ_OVERWRITE_WRITE - ie, the disk devices handle >> this as "read in the underlying sector(s), modify what we need to, and >> write out the results." This is a bit inefficient for flash devices. >> It may be cleaner to add a new BIO for "flash writes" that have >> flash-write semantics - ie, depending upon the flash device behaviour, >> either bits get set 0->1 or they get set 1->0, but an ERASE is needed >> to reset them. That then begs the question - what about >> BIO_FLASH_ERASE? Good idea, but think we still need special FS for NOR like flash. >> >> >> Adrian -- Alexandr Rybalko aka Alex RAY From owner-freebsd-mips@FreeBSD.ORG Mon Nov 22 14:57:16 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 046AE1065679 for ; Mon, 22 Nov 2010 14:57:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 849FF8FC19 for ; Mon, 22 Nov 2010 14:57:15 +0000 (UTC) Received: by wye20 with SMTP id 20so125158wye.13 for ; Mon, 22 Nov 2010 06:57:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=jaSpsfQ7C7lO8E0FjZWGO618PPHOTPJkjdpf4Tct4L8=; b=n8b85V/YMNdhG4Jmu1eqkiNsyJap6taQ4jw9+D6KDnGAeYoOI8bxY/jME6eJax8NnK k6GKN3JtbwOPgq8xCS8Rs5s+xtqHpNV4DzPASxelbX7B8xo57ExoO1ivtTCzrwNiRGXn amI4M36h550dDKthDJXZR0oHQvtCEUMY5Re9I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=F/hs8ziztASxUQaFZqbNozllKCKs3wMrZOMOspNTYQIQCS7m6Dnow5+1XHK0TgpnSt dHVFKQxIrvUXA7wVy4k/c/Mes6Ln/dFUMMR9C5fTt2VlhmvV0DMorIN7S1yHsegk3fXD r80UhhB7Gs4A+NqGw2vAkbQ9/crGwVgc3y4e0= MIME-Version: 1.0 Received: by 10.216.191.210 with SMTP id g60mr5228367wen.5.1290437827384; Mon, 22 Nov 2010 06:57:07 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Mon, 22 Nov 2010 06:57:06 -0800 (PST) In-Reply-To: <20101122135703.1487660c.ray@dlink.ua> References: <201011191201.47230.freebsd-mips@dino.sk> <20101121155810.e615d4ad.ray@ddteam.net> <20101122135703.1487660c.ray@dlink.ua> Date: Mon, 22 Nov 2010 22:57:06 +0800 X-Google-Sender-Auth: 225lDTnya_RQOfPiF3eRp6y816A Message-ID: From: Adrian Chadd To: Alexandr Rybalko Content-Type: text/plain; charset=ISO-8859-1 Cc: Aleksandr Rybalko , freebsd-mips@freebsd.org Subject: Re: First RSPRO deployed ! X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2010 14:57:16 -0000 On 22 November 2010 19:57, Alexandr Rybalko wrote: >>> Can you explain it a bit better? The idea is to not have the RW >>> offset/length hardcoded, it instead is based on whatever is left in >>> the partition after the RO LZMA section. > Ah, now I`m understand you. That possible with geom_map. [snip] > In that example GEOM_MAP setup 8 parts, > part called rootfs_ro is where lzma-ed rootfs live, > part called rootfs_rw is blank part for rw data. > GEOM_MAP search for keyword "--some-delimiter--" in flash from searchstart=0x00130000 with step 64k (searchstep="65536") > This require correct alignment of key. Right. The openwrt board config code has things like the above hard coded. I like the idea of having to above to list flash partitions but not to go grovelling through the flash partition to find 'filesystem markers'. :-) Anyway, that's personal preference. Whatever works, works. :) >>> The other thing to consider is what BIO_WRITE means. RIght now it's >>> effectively BIO_READ_OVERWRITE_WRITE - ie, the disk devices handle >>> this as "read in the underlying sector(s), modify what we need to, and >>> write out the results." This is a bit inefficient for flash devices. >>> It may be cleaner to add a new BIO for "flash writes" that have >>> flash-write semantics - ie, depending upon the flash device behaviour, >>> either bits get set 0->1 or they get set 1->0, but an ERASE is needed >>> to reset them. That then begs the question - what about >>> BIO_FLASH_ERASE? > > Good idea, but think we still need special FS for NOR like flash. We still do. The point is, all of the above work is to lay a foundation to let people experiment with "flash FSes". IMHO right now the entry barrier is too high: a flash fs author would have to invent an MTD layer as well as a flash filesystem layer. I'd rather we take care of a basic MTD layer - whether it be a GEOM extension or something else - and then open the floor to further experimenting. :) Adrian From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 09:09:35 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23FBF106564A; Tue, 23 Nov 2010 09:09:35 +0000 (UTC) (envelope-from larry.vaden@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8393E8FC13; Tue, 23 Nov 2010 09:09:34 +0000 (UTC) Received: by wwd20 with SMTP id 20so8107036wwd.31 for ; Tue, 23 Nov 2010 01:09:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=XP5ENgMER8BW0Bif0nk5YWutkLiqIQ34UEyQQB1qNZE=; b=Gx23pj+KvbdR38lbm7vSifjDOMieGvUgyuWq8a4rdsNgWhOYWasVpuIkBqPA/TCat/ J2sAiW/PELdd2nQzQbWht4YUmavJSKE9p5SgJdqujIdgNMPlD5VfFNXcqJxtijr3ZLqY iHv4T1p+BmR/Go1LHI/ukRU9VflPk9+PzgyAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=E9w7vBh0jWhRG/EukL9JQqMK38BZExYYn2yVSjG8vG8ojmgf5M84C1jKyHHnlUs5hf dzAd6bCOdCdhJ/04sD69wpN8NqOwt6MnziueqbKxhelu6wQromBUl7RgNuR8HTkuJ7Kb 9Tw7gbzbwZnKaKeZSDi/Qvxqk3SdvXDzko1V4= MIME-Version: 1.0 Received: by 10.216.141.209 with SMTP id g59mr6306305wej.10.1290503372766; Tue, 23 Nov 2010 01:09:32 -0800 (PST) Sender: larry.vaden@gmail.com Received: by 10.216.242.12 with HTTP; Tue, 23 Nov 2010 01:09:32 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 03:09:32 -0600 X-Google-Sender-Auth: 1dhDZzCxrAsodSrah3XMYftYMeo Message-ID: From: Larry Vaden To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 09:09:35 -0000 On Fri, Nov 12, 2010 at 10:12 PM, Adrian Chadd wrote: > > I've been working out the kinks in the AR9160 support at the moment in > preparation for some further 11n work. Since I'm mostly doing that in my > spare time at the moment, I've no ETA on it. > > IIRC, AirOS is based on openwrt but with a local, closed-source atheros > driver. :/ > > Ask me about the Bullet M2 in a couple weeks. I'll have finished my exams > then and I'll see if I can bring up FreeBSD on this particular SoC. > > Adrian Adrian, How are the exams going? Happy Thanksgiving! kind regards/ldv From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 14:10:19 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CDCE10656C1 for ; Tue, 23 Nov 2010 14:10:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id EE2088FC0C for ; Tue, 23 Nov 2010 14:10:18 +0000 (UTC) Received: by ewy3 with SMTP id 3so4622433ewy.13 for ; Tue, 23 Nov 2010 06:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=WDFmuBXrIsjFdRHLTb8zY0P6utWo9VEnbAqEDXWr06Q=; b=ElQTVvJ9Zp8wnasLFJgTWAZK9hudIXTW/nOm7jIA10b7eHOkdaZFzJWe2BgUUJxtNj EfZir5dEyVA7+j7ZQLlBgicCukQQZypyGYu6tksqb+aAZ/IEQ2DGWRKQcCYvh7oLImxq /Tg2EBRHGmuA/goOQ+lwMTfGMH6FcGDptg7Sg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=UDWNG6AOwtrFZ2urkyk2bDOvWxcPM/C+EAYcYrnMuB0dPgoNjg7MvN7fwvKg1Hidyv pwLIhBxpVIfapqgycAC1e/IAzDTt/OrICsNjABqpz3JTFORb43fzrNJhHF8DZGFlmPnV DiRLCpgaCdL4UL2/8Tjl1Yi4mw73VJ+NJm/Ak= MIME-Version: 1.0 Received: by 10.216.30.65 with SMTP id j43mr6643543wea.20.1290521417682; Tue, 23 Nov 2010 06:10:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Tue, 23 Nov 2010 06:10:17 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 22:10:17 +0800 X-Google-Sender-Auth: NpUMdU8Jnvjpab7C3bqyX3rHNXA Message-ID: From: Adrian Chadd To: Larry Vaden Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 14:10:19 -0000 On 23 November 2010 17:09, Larry Vaden wrote: >> Ask me about the Bullet M2 in a couple weeks. I'll have finished my exams >> then and I'll see if I can bring up FreeBSD on this particular SoC. >> >> Adrian > > Adrian, > > How are the exams going? They're done! So I'm working on tidying up my 11n TX code. (Yes, I have 11n TX seemingly working.) Adrian From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 14:42:23 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9FD2106566B; Tue, 23 Nov 2010 14:42:23 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 26DC28FC13; Tue, 23 Nov 2010 14:42:22 +0000 (UTC) Received: by wwc33 with SMTP id 33so880406wwc.1 for ; Tue, 23 Nov 2010 06:42:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=+GviAje0DidH0TIPyYtNq9bIV2tlZ9TT+aaOYFmpmD4=; b=unaiLsGIqL2YGNEa5EVDXHk4d1yEIDT34tO13LnnaGhluD3CPJOYFozoBqsg0Fb4/D 9ShS0pd2fglfZneGX3gm/KLsIZgSVPQGwAxNqXRYD5TrVu/j8UojUz7lBrnGqN/s7d/j bl7awXsIwmNJ58GJJKOe6RVfRr3Y7CuZtZZa0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UYKeYEU4r3s9k4bDBKT8O0M14HaqjIcjrVe6uSOoKic1LNV1lDEau3O4+yLH0nLd4i rvZQiqeCC0161+9mJ0ktdUoneihlfsqQ+nbgk3apQPrPDh16U+7PBeUPfm/1IDi7NwXD SoM0Jsa55xDy/Isk7OoRHrcbQ49rlrJLaON1Q= MIME-Version: 1.0 Received: by 10.216.4.82 with SMTP id 60mr991952wei.89.1290521711561; Tue, 23 Nov 2010 06:15:11 -0800 (PST) Received: by 10.216.12.80 with HTTP; Tue, 23 Nov 2010 06:15:10 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 08:15:10 -0600 Message-ID: From: Brandon Gooch To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 14:42:23 -0000 On Tue, Nov 23, 2010 at 8:10 AM, Adrian Chadd wrote: > On 23 November 2010 17:09, Larry Vaden wrote: > >>> Ask me about the Bullet M2 in a couple weeks. I'll have finished my exams >>> then and I'll see if I can bring up FreeBSD on this particular SoC. >>> >>> Adrian >> >> Adrian, >> >> How are the exams going? > > They're done! So I'm working on tidying up my 11n TX code. (Yes, I > have 11n TX seemingly working.) Wow, that excellent news! Congrats! And the 11n thing is awesome too ;) -Brandon From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 15:01:51 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7129A1065674; Tue, 23 Nov 2010 15:01:51 +0000 (UTC) (envelope-from larry.vaden@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 130238FC1B; Tue, 23 Nov 2010 15:01:50 +0000 (UTC) Received: by yxh35 with SMTP id 35so5021428yxh.13 for ; Tue, 23 Nov 2010 07:01:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=2kG6EntaiLrusOgtqNtydZ8j9sv/0N++J/6DhztRj5k=; b=cesdIZxyj5n7hb9DdqROmW1EsyQLsdcWJfrEGfc4S1TjhHBrih9JNb34+9N8h8WOTj vnIs/ovyAYBr7p2ZU/dd6wRBAsOGyTsiAVI6X4x4Fqs3bF93k6w380DDq42dJCiwBLwa a6yy9QnBtX8VzTMeaUq6Zk8F8EeDcrildGWpE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=O3BuLsss76V41bG8cFFIw55+d+BhHSreyk0ngrfa8Xi4CW5hB+C/uEwhPO8GCmzyyZ B03m9HSLGsMwus03AGX7An0ma8lnrSZKFIbFBEHPW0jeR04wapTE4T+rGkyMpCyzt1Cs 5XWQCRQfJq4tts9R7jO5kfq/2vBOtYY/9sQQo= MIME-Version: 1.0 Received: by 10.216.178.13 with SMTP id e13mr6743709wem.25.1290524508792; Tue, 23 Nov 2010 07:01:48 -0800 (PST) Sender: larry.vaden@gmail.com Received: by 10.216.242.12 with HTTP; Tue, 23 Nov 2010 07:01:48 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 09:01:48 -0600 X-Google-Sender-Auth: 80iSTsimpgg9rJRDo2FbGjLsPwg Message-ID: From: Larry Vaden To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 15:01:51 -0000 On Tue, Nov 23, 2010 at 8:10 AM, Adrian Chadd wrote: > On 23 November 2010 17:09, Larry Vaden wrote: > >>> Ask me about the Bullet M2 in a couple weeks. I'll have finished my exams >>> then and I'll see if I can bring up FreeBSD on this particular SoC. >>> >>> Adrian >> >> Adrian, >> >> How are the exams going? > > They're done! So I'm working on tidying up my 11n TX code. (Yes, I > have 11n TX seemingly working.) > > Adrian Adrian, You have been a very productive fellow while taking exams! What can you tell us about how the stuck beacon problem is handled (and indeed if the problem remains in the development code branch)? Will Rogers said "Everybody is ignorant, only on different subjects." and I'm ignorant about TX. Again, congratulations! kind regards/ldv From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 15:18:44 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33CF2106564A; Tue, 23 Nov 2010 15:18:44 +0000 (UTC) (envelope-from larry.vaden@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id C96198FC17; Tue, 23 Nov 2010 15:18:43 +0000 (UTC) Received: by gxk5 with SMTP id 5so274284gxk.13 for ; Tue, 23 Nov 2010 07:18:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=n49OcY9dgN4kYCR1hkffK+YWXkVN/GLXdmA/V49sgb0=; b=SpQoQ6Xrr5zYsfFPcsFljLfk5gL+GbIKP3kmqvHbbzkiCGwZUTyFOFBcR59GSa7NQb Y0iDRK/O1RAVBzM7o1hulgX+tbxzMAT4lN7hgW3ahn4q2Xiv5ew3q8Boffu9TdbO9DHa yp2KDtVFgHD5i3SrysErfubqwqUuadyyZJZ+Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=hU5nLDkbmrvdpRXMADdWrZ2Dg/GdiFprE0tAQdyVXPgD0Qx8jMtfHI8rTGe8m7ilhl +fTBh//IivFdxeVRp7yjeYKkBvVx7FPfFzL2rYN9CCN/dIPzyfuB5YZQIC+WDIzWIlVO RKhC6L9dPK2eTtabwJ3x8E6ciGaf3p8bMRAps= MIME-Version: 1.0 Received: by 10.216.178.13 with SMTP id e13mr6767677wem.25.1290525521387; Tue, 23 Nov 2010 07:18:41 -0800 (PST) Sender: larry.vaden@gmail.com Received: by 10.216.242.12 with HTTP; Tue, 23 Nov 2010 07:18:41 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 09:18:41 -0600 X-Google-Sender-Auth: JOKhI-oL1g_JIEtzcCj0RvZAC0I Message-ID: From: Larry Vaden To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 15:18:44 -0000 On Tue, Nov 23, 2010 at 8:10 AM, Adrian Chadd wrote: > On 23 November 2010 17:09, Larry Vaden wrote: > >>> Ask me about the Bullet M2 in a couple weeks. I'll have finished my exams >>> then and I'll see if I can bring up FreeBSD on this particular SoC. >>> >>> Adrian >> >> Adrian, >> >> How are the exams going? > > They're done! So I'm working on tidying up my 11n TX code. (Yes, I > have 11n TX seemingly working.) > > Adrian Adrian, the reason for my original post (seeking to return to the BSD environs) is that we are seeing gross quantities of stuck beacons in dmesg on the Ubiquiti M series and have recently noted perps diagnosed by the UBTik (a MikroTik in a housing form fit and function compatible with the Rocket M2) trying to associate with _WDS requested_ resulting in latencies of 10x-20x normal latency. We don't run WDS on our 2.4 GHz APs. We only run WDS on Ubiquiti M5 series in PTP because that's the way they produce a transparent Layer 2 bridge. Is the amount of time spent processing such a request, combined with logging and a busy channel, perhaps enough to effectively cause a denial of service? kind regards/ldv p.s.: I refer implicitly to Sam Leffler's comments last year about the likely sources of stuck beacons. From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 15:21:42 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A759A1065670 for ; Tue, 23 Nov 2010 15:21:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 535248FC0A for ; Tue, 23 Nov 2010 15:21:42 +0000 (UTC) Received: by vws9 with SMTP id 9so1207296vws.13 for ; Tue, 23 Nov 2010 07:21:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=MIzS4qp954IiE0MhlcCnzNmN2Ye7lsRx4MPKRluSiVM=; b=hMzjD9E9kQTN3KTW7kI1JyF1KUp2B8u3fU87Q75i0sHgQW3ZoeKx+OVLVBKkDxG0yH S1L/4ydvIE5A47q5/avbdYncfd5OJlqxV9V0BDdHIL0DrYEJemHHbVVnQqLMnul6Pa5+ 8C/g87U/0Y5AAs9+DymiNZf9X7CS/qHGHSZqQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=n9s3sa9otQRw2RQmpZGAUvqF7oLs0swxUQSQSWVp0NjLZteRJQVaO/zp/nRvJwqotE GAX10AL7WB3lC1aEmtaBuEC8IBXIkAgcYaN6bR9EvammtolXcU1g8mzWw+pQ2WpNi5Ev tJOVbmcd/tGwcfwDfhaCIWIzevODOObC+JUg8= MIME-Version: 1.0 Received: by 10.216.191.210 with SMTP id g60mr6758848wen.5.1290525699952; Tue, 23 Nov 2010 07:21:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Tue, 23 Nov 2010 07:21:39 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 23:21:39 +0800 X-Google-Sender-Auth: MeemjM5l084oHBjQil3H880eh2A Message-ID: From: Adrian Chadd To: Larry Vaden Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 15:21:42 -0000 On 23 November 2010 23:01, Larry Vaden wrote: > You have been a very productive fellow while taking exams! Hah! :) I explicitly didn't do any of this during exams! > What can you tell us about how the stuck beacon problem is handled > (and indeed if the problem remains in the development code branch)? "stuck beacon" is a symptom of many, many potentially inter-related causes. I've fixed some of the code related problems that upset the AR9160's I was using. I can't fix RF issues, nor can I fix issues that require detailed documentation about the behaviour of the radio. I have almost no documentation about the atheros stuff and certainly nothing at all about the radio. All I really have is ath5k/ath9k and some helpful contacts that answer the (frequent!) questions I have. I haven't yet sat down and tried to use the AR9280 I have here in any real way; I'm specifically ignoring it until I've finished off the 11n TX path. I have to go over the ath9k code to see what bits we're missing that could impact stability - there's definitely calibration and TX power related code that we don't have in our HAL. Rui had problems with the AR9280 stability and I'm thus focusing on the chipset that -is- closer to working in a useful way (AR9160), even if it's "old" and "unsupported" today. > Will Rogers said "Everybody is ignorant, only on different subjects." > and I'm ignorant about TX. Well, in summary - the TX descriptor format has changed between chipsets (ie, what fields mean in the TX descriptors.) The 11n chipsets have different expectations for programming TX rates, rts/cts stuff, etc. There's also extra stuff to care about for handling 11n TX A-MPDU which I'm just going to ignore for the first pass. I've been slowly figuring out what's going on by reading ath9k/ath5k source and asking a few atheros people some questions but it's taking (a lot of) time. That said, the relevant ath5k/ath9k people have been very, very helpful. :-) I'm short on free time at the moment and I do need a bit of a break from concentration, so there's no real timeline for: * merging my platform work back into -head; * finishing the AR724x so (in theory) the Bullet M2/M5 can boot FreeBSD; * finishing up the if_ath TX path code so it works for both legacy and 11n chipsets "right enough" to trust it; * even thinking about merging any of this initial 11n stuff from Rui/Sam into -HEAD. I'll post an update on -mips when I've hacked together the AR724x support to test. Adrian From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 15:31:00 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18C7A106566B for ; Tue, 23 Nov 2010 15:31:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9A33D8FC0A for ; Tue, 23 Nov 2010 15:30:59 +0000 (UTC) Received: by wye20 with SMTP id 20so352777wye.13 for ; Tue, 23 Nov 2010 07:30:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=TVvfQpaSgfAB+apI9xw43Kha/8VDC+bDa/uNO0jYiBw=; b=iGt7K5iGUR7FBwhYvGJx8yFXNg/cbTNDC7gC0Q64uWc/yIJDvj4NSNdtDAlY5Xzend ucJDuokOwT3gZE7KqMsotoZk3oV9dvd16FNGpvKTXBT0AnKeAmvF5lujACi1DprCUz6y A7avJuA9UNuJWY2eT0wlVwgXoEsZCeVTTza0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=uqmZoA1rB8YUwdotxrBjB7+EqWEvLGF1k39XXO6c0gmvV0t1Ozsghhwqm8z7fwFnSG qzqq9E3qTyr0GL+tbKG/fPSVVdVfTP5Ni1y4tzYSLue+/FDw9+sWfrl/hyoxMUXAmMQ5 FsOj+frf2wEH6xCDcBY5IprzyDVOLKa5V8QEw= MIME-Version: 1.0 Received: by 10.227.143.136 with SMTP id v8mr7787609wbu.90.1290526257336; Tue, 23 Nov 2010 07:30:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.65.210 with HTTP; Tue, 23 Nov 2010 07:30:57 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 23:30:57 +0800 X-Google-Sender-Auth: Ve6jr9vw-8D_QbUn3sTCMQB0qmk Message-ID: From: Adrian Chadd To: Larry Vaden Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 15:31:00 -0000 On 23 November 2010 23:18, Larry Vaden wrote: > Adrian, the reason for my original post (seeking to return to the BSD > environs) is that we are seeing gross quantities of stuck beacons in > dmesg on the Ubiquiti M series and have recently noted perps diagnosed > by the UBTik (a MikroTik in a housing form fit and function compatible > with the Rocket M2) trying to associate with _WDS requested_ resulting > in latencies of 10x-20x normal latency. =A0We don't run WDS on our 2.4 > GHz APs. =A0We only run WDS on Ubiquiti M5 series in PTP because that's > the way they produce a transparent Layer 2 bridge. > > Is the amount of time spent processing such a request, combined with > logging and a busy channel, perhaps enough to effectively cause a > denial of service? I've no idea. I haven't at all looked at WDS. As Sam likely pointed out, stuck beacons can include: * because the RF environment is somehow hilariously bad, congested or dirty (seen this); * because the code needing to setup the beacon frames, flush it to RAM before the TBTT (and related) timers fire just doesn't get a chance to run (seen this); * because your backend PCI bus/CPU/FSB bus/etc is busy, and thus the beacon frame doesn't go out in time (haven't seen this); * because the chip is being fondled in the wrong way somehow and it's locking up something (definitely seen this.) It's just a shame that people focus on "stuck beacon!" rather than trying to figure out what other events are occuring at the same time. :-) To track down stuck beacons at my wireless contract, I ended up doing a -lot- of instrumentation to try and figure out what was going on when stuck beacons occured. For example, stuck beacons were occuring in the deep past because the initial noise floor calibrations were being done every 1/10th of a second during a periodic calibration (every 20 minutes), rather than every few seconds, and this tended to upset the radio. Adrian From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 15:31:23 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE315106564A; Tue, 23 Nov 2010 15:31:23 +0000 (UTC) (envelope-from larry.vaden@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5F6398FC1D; Tue, 23 Nov 2010 15:31:23 +0000 (UTC) Received: by gxk5 with SMTP id 5so284074gxk.13 for ; Tue, 23 Nov 2010 07:31:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=ojkiavNB5Dy3nPQ/Vor8agfoJC7L9xpjrF2/EdeSGeE=; b=qJrEURbmmDuL9oKuYZ4qwMXMF7UMOmSurpAYIGOIgC2s2dXsGlS1jFDqcNJb6Irvvh GiPWWkAGJ/cjNcY480ocadgpcNwcflladQwofqvZR2l9xC0+Lt8V5ZRzYabTJsvYHAiG 3RQCSVHYmVDlIF+t0q8HYvf8mX14cT+vM6B1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=tBIX1d1K4fKiTqu8ADWaxuezM4cTreFyMU3Dn9g2W+9Knt+sD/HmOqwbuEw2X5e+/M ND9ojpYSWc1+KUkeSuEL/LYbHyPDRx89BPfA4tgdXLMGnpmJBeHewbh2ZZQmX9o4XrYL LbWGiLXTTNC326k26KWJbNiePph5fQ6HYsG1w= MIME-Version: 1.0 Received: by 10.216.178.13 with SMTP id e13mr6786246wem.25.1290526281713; Tue, 23 Nov 2010 07:31:21 -0800 (PST) Sender: larry.vaden@gmail.com Received: by 10.216.242.12 with HTTP; Tue, 23 Nov 2010 07:31:21 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 09:31:21 -0600 X-Google-Sender-Auth: sIF22ZjJ-EgZGkUpeQwg0aJLEsE Message-ID: From: Larry Vaden To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 15:31:23 -0000 On Tue, Nov 23, 2010 at 9:21 AM, Adrian Chadd wrote: > > I'll post an update on -mips when I've hacked together the AR724x > support to test. > > Adrian We eagerly await your contributions, but thank you in the present tense. kidn regards/ldv From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 16:44:00 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B3271065673; Tue, 23 Nov 2010 16:44:00 +0000 (UTC) (envelope-from larry.vaden@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A84B18FC0C; Tue, 23 Nov 2010 16:43:59 +0000 (UTC) Received: by wwd20 with SMTP id 20so8520245wwd.31 for ; Tue, 23 Nov 2010 08:43:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=ZExMKBrwnloRDIS4STVYAJSuBE8u3Ra/ogNn9CVSekQ=; b=jANaR8vOGeLIlwM+/qyR8Eq5edUA3HKVOo4pVbGHQhKmr7E/IvI4wPcIZ1uq6LBOv3 6gsc9lhG9eTcSxzzcbJ+ZRkm2ttVkYtCTDQUGAuqphwhoohe3L29QwG1qwNOnk91JgKT Q7DF770LygVa4sM6mgzyPMCKrJtFWl4sIE/EA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=n3Ik/ChwTtKkoYy+00A8BqQIkgjadq/+HBXO1C4WxkPPdMvfTW0CLVx2kOUX0lCoet Ef78ZZvZtWUlOjNncDDQVNWeYM935bkQXzSGD8uB8N3S3ACK8TZDieCSuZMIHgYw7Pb7 7qS2oAFflLJ/+6zkD8vLPlMJCIhRA0c3xzAf8= MIME-Version: 1.0 Received: by 10.227.174.206 with SMTP id u14mr7876652wbz.40.1290530637447; Tue, 23 Nov 2010 08:43:57 -0800 (PST) Sender: larry.vaden@gmail.com Received: by 10.216.242.12 with HTTP; Tue, 23 Nov 2010 08:43:57 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 10:43:57 -0600 X-Google-Sender-Auth: D8ZQAStZTmIwcbER_Zx55QEdAGc Message-ID: From: Larry Vaden To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 16:44:00 -0000 On Tue, Nov 23, 2010 at 9:30 AM, Adrian Chadd wrote: > > I've no idea. I haven't at all looked at WDS. > > As Sam likely pointed out, stuck beacons can include: > > * because the RF environment is somehow hilariously bad, congested or > dirty (seen this); > * because the code needing to setup the beacon frames, flush it to RAM > before the TBTT (and related) timers fire just doesn't get a chance to > run (seen this); > * because your backend PCI bus/CPU/FSB bus/etc is busy, and thus the > beacon frame doesn't go out in time (haven't seen this); > * because the chip is being fondled in the wrong way somehow and it's > locking up something (definitely seen this.) > > It's just a shame that people focus on "stuck beacon!" rather than > trying to figure out what other events are occuring at the same time. > :-) > > To track down stuck beacons at my wireless contract, I ended up doing > a -lot- of instrumentation to try and figure out what was going on > when stuck beacons occured. For example, stuck beacons were occuring > in the deep past because the initial noise floor calibrations were > being done every 1/10th of a second during a periodic calibration > (every 20 minutes), rather than every few seconds, and this tended to > upset the radio. > > Adrian Adrian, Thanks for your reply. I agree with you and we are trying to understand the underlying causes and what can be done. I also agree that changing the intervals can help; we found that a beacon interval of 200-250 msec resulted in better latency for subscribers, but that higher beacon intervals seemed to be unstable (CPEs would reassociate every few seconds). This was on Ubiquiti gear. AFAIK, the beacon interval on Mikrotik's RouterOS is fixed at 100 msec (read: not under operator control), and the recalibration interval is 00:01:00, also not under operator control. In these cases, I refer to WinBox, not the CLI, which I haven't checked. kind regards/ldv From owner-freebsd-mips@FreeBSD.ORG Wed Nov 24 10:45:52 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1210E106566B for ; Wed, 24 Nov 2010 10:45:52 +0000 (UTC) (envelope-from freebsd-mips@dino.sk) Received: from loki.netlab.sk (loki.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id C77DF8FC19 for ; Wed, 24 Nov 2010 10:45:51 +0000 (UTC) Received: from door.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Wed, 24 Nov 2010 11:53:18 +0100 id 00033C19.4CECEE9E.00008DBA From: Milan Obuch To: freebsd-mips@freebsd.org Date: Wed, 24 Nov 2010 11:45:41 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.5.3; i386; ; ) References: <201011181136.47152.milu@dat.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011241145.43480.freebsd-mips@dino.sk> Cc: Subject: [Re: First RSPRO deployed!] flash utility mkfwimage and RSPRO boot question X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2010 10:45:52 -0000 On Thursday 18 November 2010 12:07:34 Luiz Otavio O Souza wrote: > On Nov 18, 2010, at 8:36 AM, Maciej Milewski wrote: > >>> Do you have proper name of this fw image? I've read somewhere that it's > >>> required. > >>> My working name is RSPRO.ar7100pro.FreeBSD.Test and you can change the > >>> last two words for sure. > >> > >> You mean the name of the file that mkfwimage generates? > >> I just called it something like firmware-image... > >> > >> I changed the name, but still got: > >> TFTPD: Incoming connection from 192.168.1.102:25789 > >> Received: 6881688 bytes > >> Invalid image format (error: -2) > > > > Actually not the filename but if you run mkfwimage with parameters then > > you have the version string which in my case is as above. > > > > For building image I run: > > mkfwimage -v RSPRO.ar7100pro.FreeBSD.Test -B RSPRO -o image.bin -k > > kernel.gz\ -r rootfs > > Yes, that is correct, i've used the following two version strings with > success: > > RS.ar7100.FreeBSD - for routerstation > > RSPRO.ar7100pro.FreeBSD - for rspro > > Just pick the correct one for your board. > > I've my scripts here (together with mkfwimage files): > /loos.no-ip.org:280/rspro/rs-mkfwimage.tar.gz > > Hope it helps. > Hi, I can succesfully build world and kernel and using mkflash create an image usable to be loaded by redboot and this is used on regular boot after power on. Fine. I am using currently kernel in on board flash (spiflash) and filesystem on USB flash key. This way I am able to try native buildworld on RSPRO (not too quick, much slower than cross build, but this is expected), test ports etc. I observed one thing - original flash is partitioned into five parts, executing 'geom redboot list' tells names 1. Name: redboot/RedBoot 2. Name: redboot/RedBoot config 3. Name: redboot/FIS directory 4. Name: redboot/kernel 5. Name: redboot/rootfs and sizes Mediasize: 196608 (192K) Mediasize: 4096 (4.0K) Mediasize: 61440 (60K) Mediasize: 917504 (896K) Mediasize: 15466496 (15M) (total is 128 k, i. e. 2 * 64k blocksize, less than full flash, 16 M). After flashing my kernel, sizes are Mediasize: 196608 (192K) Mediasize: 4096 (4.0K) Mediasize: 61440 (60K) Mediasize: 1638400 (1.6M) Mediasize: 9895936 (9.4M) (total is 4864 k, i. e. 76 * 64k blocksize, less full flash, 16 M). My original impression was that rest after kernel is left for rootfs, and while it's not a problem in my scenario, if I would like to put a real filesystem there, would it be limited in size this way or can I use all available flash left after kernel? Could it be a bug in mkfwimage or some layout table needs to be modified? Also, is it possible to have new, 'non-standard' partition created, used e. g. to store some user config/data? And, one more, could a redboot partition be assigned filesystem label? On a related problem - there is no boot loader for mips (as /boot/loader is for i386/amd64 and some variants). I would like to try it in place of kernel and have real kernel with some kernel modules (if built and placed in /boot/kernel, they work just fine - I did it with nullfs module, having if_vlan loaded gives me possibility to create arge1.1 etc) and some loader config, which could be used to set some FDT object properties if we decide to move later in this direction. All this would mean greater flexibility in my eyes. Naturally, flash aware filesystem would be the most elegant solution, but we are not here, yet, unfortunatelly... Regards, Milan From owner-freebsd-mips@FreeBSD.ORG Thu Nov 25 11:12:15 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F911065672 for ; Thu, 25 Nov 2010 11:12:15 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id AF1668FC0A for ; Thu, 25 Nov 2010 11:12:14 +0000 (UTC) Received: by yxh35 with SMTP id 35so416652yxh.13 for ; Thu, 25 Nov 2010 03:12:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=NimQdFlfWTUZ8bqcg9ylNJxGPlNf6KumgGJd4Zb958Q=; b=MJWbq2ldCc8vdiVzo4sxLc4kwEzLbFblY2zPosG5L9X8iYXO/hQyNS7s8lRchECZvu AC69vTYWRSqV2zRrkg0foUc6bsu2+f5IMzyMo5ituqA66gh6HxPrRkCks8wl2z2PXofc QuT1VyWjPO4aQYNYkWaRvPXrr15tcVvkXCAj4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=i3S4h+C6H7SQ70rASbQo8/JC6vT8HGK7s5BeQeEwECPi9Nr3yzwvBF5+H7GewGUURA 6Na7t10Hfoc7x97dqE/5NtOBIOarV8T1gPorwRUY7MzqOo8BouaqjhiKFXzCcIQsiNKb TIFjsjLRcgDrIol7Sd0TFThVWhUwmHBps/l1Q= Received: by 10.150.52.18 with SMTP id z18mr2759144ybz.378.1290683532856; Thu, 25 Nov 2010 03:12:12 -0800 (PST) Received: from [192.168.0.86] ([187.39.15.80]) by mx.google.com with ESMTPS id p1sm513135ybn.5.2010.11.25.03.12.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 25 Nov 2010 03:12:11 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Luiz Otavio O Souza In-Reply-To: <201011241145.43480.freebsd-mips@dino.sk> Date: Thu, 25 Nov 2010 09:12:06 -0200 Content-Transfer-Encoding: quoted-printable Message-Id: <21DE95C5-CD5F-48C0-9569-C40D15BDC215@gmail.com> References: <201011181136.47152.milu@dat.pl> <201011241145.43480.freebsd-mips@dino.sk> To: Milan Obuch X-Mailer: Apple Mail (2.1081) Cc: freebsd-mips@freebsd.org Subject: Re: [Re: First RSPRO deployed!] flash utility mkfwimage and RSPRO boot question X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2010 11:12:15 -0000 On Nov 24, 2010, at 8:45 AM, Milan Obuch wrote: > On Thursday 18 November 2010 12:07:34 Luiz Otavio O Souza wrote: >> On Nov 18, 2010, at 8:36 AM, Maciej Milewski wrote: >>>>> Do you have proper name of this fw image? I've read somewhere that = it's >>>>> required. >>>>> My working name is RSPRO.ar7100pro.FreeBSD.Test and you can change = the >>>>> last two words for sure. >>>>=20 >>>> You mean the name of the file that mkfwimage generates? >>>> I just called it something like firmware-image... >>>>=20 >>>> I changed the name, but still got: >>>> TFTPD: Incoming connection from 192.168.1.102:25789 >>>> Received: 6881688 bytes >>>> Invalid image format (error: -2) >>>=20 >>> Actually not the filename but if you run mkfwimage with parameters = then >>> you have the version string which in my case is as above. >>>=20 >>> For building image I run: >>> mkfwimage -v RSPRO.ar7100pro.FreeBSD.Test -B RSPRO -o image.bin -k >>> kernel.gz\ -r rootfs >>=20 >> Yes, that is correct, i've used the following two version strings = with >> success: >>=20 >> RS.ar7100.FreeBSD - for routerstation >>=20 >> RSPRO.ar7100pro.FreeBSD - for rspro >>=20 >> Just pick the correct one for your board. >>=20 >> I've my scripts here (together with mkfwimage files): >> http://loos.no-ip.org:280/rspro/rs-mkfwimage.tar.gz >>=20 >> Hope it helps. >>=20 >=20 > Hi, >=20 > I can succesfully build world and kernel and using mkflash create an = image=20 > usable to be loaded by redboot and this is used on regular boot after = power=20 > on. Fine. I am using currently kernel in on board flash (spiflash) and=20= > filesystem on USB flash key. This way I am able to try native = buildworld on=20 > RSPRO (not too quick, much slower than cross build, but this is = expected),=20 > test ports etc. Great ! Building world works with CPUTYPE=3Dmips32 and for ports, add the = following line to /etc/make.conf: CFLAGS=3D-O2 -pipe -march=3Dmips32 > I observed one thing - original flash is partitioned into five parts,=20= > executing 'geom redboot list' tells names >=20 > 1. Name: redboot/RedBoot > 2. Name: redboot/RedBoot config > 3. Name: redboot/FIS directory > 4. Name: redboot/kernel > 5. Name: redboot/rootfs >=20 > and sizes >=20 > Mediasize: 196608 (192K) > Mediasize: 4096 (4.0K) > Mediasize: 61440 (60K) > Mediasize: 917504 (896K) > Mediasize: 15466496 (15M) >=20 > (total is 128 k, i. e. 2 * 64k blocksize, less than full flash, 16 M). = After=20 > flashing my kernel, sizes are >=20 > Mediasize: 196608 (192K) > Mediasize: 4096 (4.0K) > Mediasize: 61440 (60K) > Mediasize: 1638400 (1.6M) > Mediasize: 9895936 (9.4M) >=20 > (total is 4864 k, i. e. 76 * 64k blocksize, less full flash, 16 M). My=20= > original impression was that rest after kernel is left for rootfs, and = while=20 > it's not a problem in my scenario, if I would like to put a real = filesystem=20 > there, would it be limited in size this way or can I use all available = flash=20 > left after kernel? Could it be a bug in mkfwimage or some layout table = needs=20 > to be modified? I don't understand the calculation you've done... But that is the way the mkfwimage tool works, it creates two slices, on = for kernel and another for rootfs (the first three slices are fixed). It will extend the rootfs to 'all remaining space' on flash (even if we = set it as an empty 64k block - like the sample on my script). So in this case you can use the rootfs slice (with 9.4M) as you want = (remember it only works with 64k reads and writes). > Also, is it possible to have new, 'non-standard' partition created, = used e. g.=20 > to store some user config/data? And, one more, could a redboot = partition be=20 > assigned filesystem label? Yes, but not with mkfwimage. Look at pfsense sample: http://devwiki.pfsense.org/RouterStationPRO You can create the slices by hand that way. The geom_redboot class already add the slice label to /dev/redboot/label > On a related problem - there is no boot loader for mips (as = /boot/loader is=20 > for i386/amd64 and some variants). I would like to try it in place of = kernel=20 > and have real kernel with some kernel modules (if built and placed in=20= > /boot/kernel, they work just fine - I did it with nullfs module, = having=20 > if_vlan loaded gives me possibility to create arge1.1 etc) and some = loader=20 > config, which could be used to set some FDT object properties if we = decide to=20 > move later in this direction. All this would mean greater flexibility = in my=20 > eyes. Yeah, this is one is really missing... >=20 > Naturally, flash aware filesystem would be the most elegant solution, = but we=20 > are not here, yet, unfortunatelly... Unfortunatelly not yet... Regards, Luiz From owner-freebsd-mips@FreeBSD.ORG Fri Nov 26 05:56:28 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E74410656C2 for ; Fri, 26 Nov 2010 05:56:28 +0000 (UTC) (envelope-from joe.joeoptions@gmail.com) Received: from 123843-www1.gri5th.com (123843-www1.gri5th.com [74.205.126.210]) by mx1.freebsd.org (Postfix) with ESMTP id C4A348FC1C for ; Fri, 26 Nov 2010 05:56:27 +0000 (UTC) Received: (qmail 8750 invoked by uid 48); 25 Nov 2010 22:22:29 -0600 To: freebsd-mips@freebsd.org User-Agent: ExpressionEngine 1.6.8 Date: Thu, 25 Nov 2010 22:22:29 -0600 From: "Joe" X-Sender: joe.joeoptions@gmail.com X-Mailer: ExpressionEngine 1.6.8 X-Priority: 3 (Normal) Message-ID: <4cef3605236f6@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Your Rental Property Listing X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "joe.joeoptions@gmail.com" List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2010 05:56:28 -0000 Hi! I believe there is a faster and easier way to rent, trade, buy and sell destination real estate and thought you might be interested in my new rental website called JoeOptions: http://www.joeoptions.com/. Here's how JoeOptions benefits you: * FREE listings through December 31, 2011 for properties created on JoeOptions. * UNLIMITED pictures/videos/links to help promote and better represent your Property and the Destination. * HomeAway Connect integration eliminating the need to manage multiple calendars * Unique property management tool allowing Renters to find your property based on Date, Price and Location in one step. * Meet People Where They Are: Social Media integration with Facebook, Twitter, YouTube, etc. Check out this video that explains why JoeOptions: http://www.youtube.com/watch?v=kohBjcuPMhE We look forward to you joining us at JoeOptions! Best Regards, Joe We've sent you this email because we think you'll enjoy using JoeOptions. If you'd rather not receive any more emails from us, please email unsubscribe@joeoptions.com, and we'll take you off our list. To remove your email from the "20101125" mailing list, click here: http://cs.joeoptions.com/index.php?ACT=5&id=dxjr2QNeJJ From owner-freebsd-mips@FreeBSD.ORG Fri Nov 26 15:54:45 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CBF51065670 for ; Fri, 26 Nov 2010 15:54:45 +0000 (UTC) (envelope-from freebsd-mips@dino.sk) Received: from loki.netlab.sk (ns3.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id BF2A38FC20 for ; Fri, 26 Nov 2010 15:54:43 +0000 (UTC) Received: from door.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Fri, 26 Nov 2010 17:01:58 +0100 id 00033C0F.4CEFD9F6.0001723F From: Milan Obuch To: Luiz Otavio O Souza Date: Fri, 26 Nov 2010 16:54:48 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.5.3; i386; ; ) References: <201011241145.43480.freebsd-mips@dino.sk> <21DE95C5-CD5F-48C0-9569-C40D15BDC215@gmail.com> In-Reply-To: <21DE95C5-CD5F-48C0-9569-C40D15BDC215@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011261654.50452.freebsd-mips@dino.sk> Cc: freebsd-mips@freebsd.org Subject: Re: [Re: First RSPRO deployed!] flash utility mkfwimage and RSPRO boot question X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2010 15:54:45 -0000 On Thursday 25 November 2010 12:12:06 Luiz Otavio O Souza wrote: > On Nov 24, 2010, at 8:45 AM, Milan Obuch wrote: > > On Thursday 18 November 2010 12:07:34 Luiz Otavio O Souza wrote: [snip] > > Hi, > > > > I can succesfully build world and kernel and using mkflash create an > > image usable to be loaded by redboot and this is used on regular boot > > after power on. Fine. I am using currently kernel in on board flash > > (spiflash) and filesystem on USB flash key. This way I am able to try > > native buildworld on RSPRO (not too quick, much slower than cross build, > > but this is expected), test ports etc. > > Great ! > > Building world works with CPUTYPE=mips32 and for ports, add the following > line to /etc/make.conf: > > CFLAGS=-O2 -pipe -march=mips32 > Hmm, I put just TARGET_ARCH=mipseb into /etc/make.conf and compiled almost all world (accidentally broken just before end, but that's a pilot error in this case) and sysutils/screen port compiled and run with no CPUTYPE nor CFLAGS definition. That should not be read as better from any side, but surely simpler :) Maybe even TARGET_ARCH should be known from running kernel, this would be similar how native build works on both i386 and amd64 platforms. Now, with screen in place I am going to test buildworld again (with some WITHOUT_XXX=YES in /etc/make.conf) to verify native builds... they are slowish here, which is expected, but seems to work, which is great. Regards, Milan From owner-freebsd-mips@FreeBSD.ORG Fri Nov 26 17:04:10 2010 Return-Path: Delivered-To: freebsd-mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F96106564A for ; Fri, 26 Nov 2010 17:04:10 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id BA6038FC14 for ; Fri, 26 Nov 2010 17:04:09 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id oAQGx5K8083923 for ; Fri, 26 Nov 2010 09:59:05 -0700 (MST) (envelope-from imp@bsdimp.com) Message-ID: <4CEFE759.3050601@bsdimp.com> Date: Fri, 26 Nov 2010 09:59:05 -0700 From: Warner Losh User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-mips@FreeBSD.org References: <201011241145.43480.freebsd-mips@dino.sk> <21DE95C5-CD5F-48C0-9569-C40D15BDC215@gmail.com> <201011261654.50452.freebsd-mips@dino.sk> In-Reply-To: <201011261654.50452.freebsd-mips@dino.sk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: [Re: First RSPRO deployed!] flash utility mkfwimage and RSPRO boot question X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2010 17:04:10 -0000 On 11/26/2010 08:54, Milan Obuch wrote: > On Thursday 25 November 2010 12:12:06 Luiz Otavio O Souza wrote: >> On Nov 24, 2010, at 8:45 AM, Milan Obuch wrote: >>> On Thursday 18 November 2010 12:07:34 Luiz Otavio O Souza wrote: > [snip] > >>> Hi, >>> >>> I can succesfully build world and kernel and using mkflash create an >>> image usable to be loaded by redboot and this is used on regular boot >>> after power on. Fine. I am using currently kernel in on board flash >>> (spiflash) and filesystem on USB flash key. This way I am able to try >>> native buildworld on RSPRO (not too quick, much slower than cross build, >>> but this is expected), test ports etc. >> Great ! >> >> Building world works with CPUTYPE=mips32 and for ports, add the following >> line to /etc/make.conf: >> >> CFLAGS=-O2 -pipe -march=mips32 >> > Hmm, I put just TARGET_ARCH=mipseb into /etc/make.conf and compiled almost all > world (accidentally broken just before end, but that's a pilot error in this > case) and sysutils/screen port compiled and run with no CPUTYPE nor CFLAGS > definition. > > That should not be read as better from any side, but surely simpler :) Maybe > even TARGET_ARCH should be known from running kernel, this would be similar > how native build works on both i386 and amd64 platforms. Now, with screen in > place I am going to test buildworld again (with some WITHOUT_XXX=YES in > /etc/make.conf) to verify native builds... they are slowish here, which is > expected, but seems to work, which is great. what does uname -a tell you? Warner > Regards, > Milan > _______________________________________________ > freebsd-mips@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org" > > > From owner-freebsd-mips@FreeBSD.ORG Fri Nov 26 18:35:44 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D066106564A for ; Fri, 26 Nov 2010 18:35:44 +0000 (UTC) (envelope-from freebsd-mips@dino.sk) Received: from loki.netlab.sk (ns3.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id B559B8FC08 for ; Fri, 26 Nov 2010 18:35:43 +0000 (UTC) Received: from door.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Fri, 26 Nov 2010 19:42:56 +0100 id 00033C0F.4CEFFFB0.0001782D From: Milan Obuch To: freebsd-mips@freebsd.org Date: Fri, 26 Nov 2010 19:35:49 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.5.3; i386; ; ) References: <201011261654.50452.freebsd-mips@dino.sk> <4CEFE759.3050601@bsdimp.com> In-Reply-To: <4CEFE759.3050601@bsdimp.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011261935.50734.freebsd-mips@dino.sk> Cc: Subject: Re: [Re: First RSPRO deployed!] flash utility mkfwimage and RSPRO boot question X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2010 18:35:44 -0000 On Friday 26 November 2010 17:59:05 Warner Losh wrote: > On 11/26/2010 08:54, Milan Obuch wrote: > > On Thursday 25 November 2010 12:12:06 Luiz Otavio O Souza wrote: [ snip] > >> Building world works with CPUTYPE=mips32 and for ports, add the > >> following line to /etc/make.conf: > >> > >> CFLAGS=-O2 -pipe -march=mips32 > > > > Hmm, I put just TARGET_ARCH=mipseb into /etc/make.conf and compiled > > almost all world (accidentally broken just before end, but that's a > > pilot error in this case) and sysutils/screen port compiled and run with > > no CPUTYPE nor CFLAGS definition. > > > > That should not be read as better from any side, but surely simpler :) > > Maybe even TARGET_ARCH should be known from running kernel, this would > > be similar how native build works on both i386 and amd64 platforms. Now, > > with screen in place I am going to test buildworld again (with some > > WITHOUT_XXX=YES in /etc/make.conf) to verify native builds... they are > > slowish here, which is expected, but seems to work, which is great. > > what does uname -a tell you? > FreeBSD argo.dino.sk 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Wed Nov 24 10:16:14 CET 2010 root@wind.dino.sk:/tmp/rspro/obj/mips.mipseb/data/src9/sys/RSPRO mips Currently running world and kernel is from cross build on i386 host. Native buildworld just ended, I am going to try native buildkernel... for that I must apply some patches (already published on this list). Milan From owner-freebsd-mips@FreeBSD.ORG Sat Nov 27 13:12:36 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2536F10656BE; Sat, 27 Nov 2010 13:12:36 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 65E088FC13; Sat, 27 Nov 2010 13:12:35 +0000 (UTC) Received: by wyf19 with SMTP id 19so2806606wyf.13 for ; Sat, 27 Nov 2010 05:12:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=xyh2Q1VjpieA4mlnNeEyJ8QcLxFNgGDMS4j472wyifk=; b=Xk2llS3gUe4mZpOykvLRgKY6I7UqKF+dx/tUzqa9eUoPHEn6JEWt9bl8vQ0u4zcii1 N/OuyMEIqCn+4W0Y9SkcOZEW+VYIqQICQzHT8as3tCVVkxVRlJldypw/fnX7jZDWvt98 wip1hVyMsPc9imoky8uk+P/qAk3zRQKhs8uUU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=bMDDNadvJLKHEJzXBK4WLqHiXDFe+fCGIcteeGf7IfbbFghdnj2IZo6z74XG+acQb2 tNwprGcYiKzb7u7C1cjZ0zdsYpncy14eo9EXw7fH7NWdqWHHBCrDyYsq2i4GrTduSOAw n5eQ9SmXnQWsjZthAb8khjv8dB2/2KRvGIaY4= MIME-Version: 1.0 Received: by 10.227.128.211 with SMTP id l19mr3620819wbs.73.1290863554195; Sat, 27 Nov 2010 05:12:34 -0800 (PST) Received: by 10.227.135.84 with HTTP; Sat, 27 Nov 2010 05:12:34 -0800 (PST) Date: Sat, 27 Nov 2010 18:42:34 +0530 Message-ID: From: "Jayachandran C." To: freebsd-mips@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Neel Natu Subject: mips merged into 8-STABLE X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2010 13:12:36 -0000 Hi all, I've merged MIPS to 8-STABLE, currently just XLR works, but I think most other platforms can be made to work with minor fixes. To get octeon platform working we need to MFC some toolchain changes. I'll have a look at this if nobody volunteers. The mips/mips/tick.c is still missing some changes from -CURRENT. Please checkout stable/8 and let me know if you find any issues. Many thanks goes to alc@ and kib@ for reviews of the non-MIPS bits and merge approval. JC.