From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 3 01:56:03 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05864106566C for ; Mon, 3 Oct 2011 01:56:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id AA8E28FC08 for ; Mon, 3 Oct 2011 01:56:02 +0000 (UTC) Received: by gyf2 with SMTP id 2so3782546gyf.13 for ; Sun, 02 Oct 2011 18:56:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=vvhtbf9RHPRu9HvH1TLWG0ufRCUyeKZSZSz+cxzAqPM=; b=f2zRpvzd3l81aDUQ2Y+zCEB8xhx5SZ9+SuC2gEh/P452AZGwRqgwkq61SRvepsKgQP unUppEGbmQUqqWWj2JyK5bm/hsqx5SlDwMEDcH2QsOcAUNsuwH6iHHVIsk6KkUQOO0dY JazRYfGnd87czmx+s+Nc/y/dl6NpCU+ey4/KU= MIME-Version: 1.0 Received: by 10.236.129.165 with SMTP id h25mr26838933yhi.38.1317606962077; Sun, 02 Oct 2011 18:56:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.111.42 with HTTP; Sun, 2 Oct 2011 18:56:02 -0700 (PDT) In-Reply-To: <20111002232848.GA1943@reemsky> References: <20111002232848.GA1943@reemsky> Date: Mon, 3 Oct 2011 09:56:02 +0800 X-Google-Sender-Auth: viNObPJkonG_7nmdu8LiST4Yb5A Message-ID: From: Adrian Chadd To: Roman Bogorodskiy Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: bwn + BETA3/ppc = very unstable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2011 01:56:03 -0000 There've been a few comments about bwn stability and performance when running on ppc. Unfortunately I don't have any ppc hardware that's suitable. The performance issue is likely due to endianness in some eeprom fiddling code. The illegal instruction? i'm not sure; can you please get a backtrace from the debugger so we can see exactly where it's dying? THanks, Adrian