From owner-freebsd-arm@freebsd.org Sun Feb 7 01:29:06 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78E73AA0585 for ; Sun, 7 Feb 2016 01:29:06 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5DC7719ED for ; Sun, 7 Feb 2016 01:29:06 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=6DR2x44n0eXl8IOzeQ8H9e0PmCOW6JAY/wAjW8KOLGw=; b=c8G0neLAiP80PgFQ66X0MnTD+e NohSdcu5P/HvSdXJBKjc8vdhE8/4WQrsUhHw8EMz8NG+p+WnEbW07ypVIOKIEquyBzKelB33gbm5X pDyLHdwpuLty96zqSgU+/wPAiTKcFF+fCNfPiY+yG8eUyLIaaqPVJhjYVmVpXug/98oc=; Received: from [114.124.33.49] (port=17850 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1aSE7o-002Qlq-Rt; Sat, 06 Feb 2016 18:29:05 -0700 Date: Sun, 7 Feb 2016 09:26:45 +0800 From: Erich Dollansky To: Warner Losh Cc: "freebsd-arm@freebsd.org" Subject: Re: clang++: error: the clang compiler does not support '-march=native' Message-ID: <20160207092645.5e09cdd4@X220.alogt.com> In-Reply-To: References: <20160207050149.39f7e280@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 01:29:06 -0000 Hi, On Sat, 6 Feb 2016 15:49:14 -0700 Warner Losh wrote: > On Sat, Feb 6, 2016 at 2:01 PM, Erich Dollansky > > wrote: > > > Hi, > > > > compiling on a Raspberry Pi B 2 on FreeBSD 11 gives me above's error > > message. > > > > A Internet search shows that this message does not exist. > > > > The program compiles using the same make file on FreeBSD 10 both on > > x86 and an Raspberry Pi B using the default compilers. > > > > Did support for 'march' get removed? > > > > As far as I can tell, it has never worked for either gcc or clang. > this is what I would have liked to find out. Intel claims speed gains of some 40% on their CPUs depending on the work load using gcc. Getting a few per cent on a Raspberry for free would make a real difference. Erich From owner-freebsd-arm@freebsd.org Sun Feb 7 01:57:27 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA1FFA9F34E for ; Sun, 7 Feb 2016 01:57:27 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC9FA15FF for ; Sun, 7 Feb 2016 01:57:27 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=6DR2x44n0eXl8IOzeQ8H9e0PmCOW6JAY/wAjW8KOLGw=; b=sbuYR3XxaKHN4xTvOPKHcTK2Gg ncel9sX9K4UAksH9lWLzIjhMQsABbU5TYYvuP+i7SxPNKGlboHLtIDG4BmBe0JN9LbkDw/UPL2n8Z rlNNriAvvfeyLJsD1+oGnJdtYMWt7+JUVt171czS9/fRoGMCQhMJpBHg4wGF630Lk7Pw=; Received: from [114.121.133.53] (port=29752 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1aSEbO-002iIw-Ak; Sat, 06 Feb 2016 18:57:26 -0700 Date: Sun, 7 Feb 2016 09:57:21 +0800 From: Erich Dollansky To: Warner Losh Cc: "freebsd-arm@freebsd.org" Subject: Re: clang++: error: the clang compiler does not support '-march=native' Message-ID: <20160207095721.57fc3502@X220.alogt.com> In-Reply-To: References: <20160207050149.39f7e280@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 01:57:27 -0000 Hi, On Sat, 6 Feb 2016 15:49:14 -0700 Warner Losh wrote: > On Sat, Feb 6, 2016 at 2:01 PM, Erich Dollansky > > wrote: > > > Hi, > > > > compiling on a Raspberry Pi B 2 on FreeBSD 11 gives me above's error > > message. > > > > A Internet search shows that this message does not exist. > > > > The program compiles using the same make file on FreeBSD 10 both on > > x86 and an Raspberry Pi B using the default compilers. > > > > Did support for 'march' get removed? > > > > As far as I can tell, it has never worked for either gcc or clang. > this is what I would have liked to find out. Intel claims speed gains of some 40% on their CPUs depending on the work load using gcc. Getting a few per cent on a Raspberry for free would make a real difference. Erich From owner-freebsd-arm@freebsd.org Sun Feb 7 04:01:14 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 934B1A9EBD9 for ; Sun, 7 Feb 2016 04:01:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E00C18B7 for ; Sun, 7 Feb 2016 04:01:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk0-x22e.google.com with SMTP id o6so48791067qkc.2 for ; Sat, 06 Feb 2016 20:01:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=bCuLwnss6AUdEYHMKRbLqNfH75+UbTGR7DLw5RVW2Qw=; b=QCSgLt4RKFwGWIV4TM0QC23kOF2T1gFlbdVSNTLXtYE9n2cQ2VnOTbZ6Xdh9KMSmWe 2HpR5XZANGs0vYOnLUaRUvpF4+sOg5GPuh+ApN5gbUHLNafhCl0kIDLQSKXszuW12S8c 9qgOQ5YUpGwmynlFPsWBZtTgm6kvIHa03QQECYTAF1muzKAFvtfJ6lly3nsMbMA+F6Lc nKtrSnOLa7+GJF9bTzpnbWulyM1g0+jAzNeACuAzCDtEG5rAKQAeYSLpBJfK+diE53le leBQcGHPJqKqTTvWsnc65t4mjSXHoveNTLA7ZvlSUd6Ox9Sy3CgxhF+i556iu450reIv ai8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bCuLwnss6AUdEYHMKRbLqNfH75+UbTGR7DLw5RVW2Qw=; b=EagKolNbGybxzjwEANddMe61PFqFMK00IoJsXICvekEt3Mxg8ACl4K313fcaz61/ig +fbTG+ih6JeoUqWG+Jo44BDBfIw8gPM7+t0C6V4J7K1qt5sZ6wivxaPWel+2gdDHzcMA GqwRTV1ii6g084vdTPI/GZOZfpQ8doK1oLA0s+Ddh7fzIFYshO2mAzmnay8+IXPtZNZU gfELbGt7kNUm9UXb4uNVqun4oJb2a0g9x9hXyINYpGvHC6C/UZKKL2EPxdzX9VP9wAg+ JuGoEKXy74zLxVPLdxuYjJghcKZY+8/CCW2gIIe1BEFN62XwAbDu6SOPB7au5M7iflC9 MksA== X-Gm-Message-State: AG10YOQaAUQJ7h0G0itTMvBqjeZ4Cn10EjOz54jOFqEQIS5EdQZr4b5r3gxYpIKj6NjBNbCsFRPIpE35E+5MUg== MIME-Version: 1.0 X-Received: by 10.55.212.28 with SMTP id l28mr3171082qki.93.1454817673148; Sat, 06 Feb 2016 20:01:13 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.30.166 with HTTP; Sat, 6 Feb 2016 20:01:13 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <20160207095721.57fc3502@X220.alogt.com> References: <20160207050149.39f7e280@X220.alogt.com> <20160207095721.57fc3502@X220.alogt.com> Date: Sat, 6 Feb 2016 21:01:13 -0700 X-Google-Sender-Auth: r8IOvNx5qzJlEKs3RsWIH_IHS-o Message-ID: Subject: Re: clang++: error: the clang compiler does not support '-march=native' From: Warner Losh To: Erich Dollansky Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 04:01:14 -0000 On Sat, Feb 6, 2016 at 6:57 PM, Erich Dollansky wrote: > Hi, > > On Sat, 6 Feb 2016 15:49:14 -0700 > Warner Losh wrote: > > > On Sat, Feb 6, 2016 at 2:01 PM, Erich Dollansky > > > > wrote: > > > > > Hi, > > > > > > compiling on a Raspberry Pi B 2 on FreeBSD 11 gives me above's error > > > message. > > > > > > A Internet search shows that this message does not exist. > > > > > > The program compiles using the same make file on FreeBSD 10 both on > > > x86 and an Raspberry Pi B using the default compilers. > > > > > > Did support for 'march' get removed? > > > > > > > As far as I can tell, it has never worked for either gcc or clang. > > > this is what I would have liked to find out. Intel claims speed gains > of some 40% on their CPUs depending on the work load using gcc. > > Getting a few per cent on a Raspberry for free would make a real > difference. > Well, the -march= args work, just not -march=native. The exact details of the core aren't exported from the kernel, so the compiler can't easily query them to guess at the best code generation to use. I think it would be a useful feature, but it just isn't one we have yet. There are some -march values that get so aggressive about optimization that they reveal some alignment issues. However, I think we've kill them all. If not, we'd love to hear about it. I know that the -march=arm1176 works well for the RPi B. Last time I tried it, the -march=cortex-a7 had some alignment issues. Since then I've seen fixes go into the tree and I haven't tried again. Reports from elsewhere indicate that this will give tens of percent in improvement depending on the workload. Warner From owner-freebsd-arm@freebsd.org Sun Feb 7 04:44:13 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CE43AA00D6 for ; Sun, 7 Feb 2016 04:44:13 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70F07B66 for ; Sun, 7 Feb 2016 04:44:13 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=avq6iFs2NLxw871MdPDC1dS/gFVMVsYl5u+hlYmVdmQ=; b=dr5Z36UbqYGEX4jBEPLM2HqnQ+ zn0GcCDX7CTwPyD/YxNBLcnB5twiTMEZQfpDnwBVwF7By9Qr4BtH3nVT6hk/V084xiBU1+6uSNzSu Ifsw19DIYLPRt97e5jzwUXbIZ2fhQse7UmjZYb9UB8JUv9qaoquuIjR2dQ34bHBHlsck=; Received: from [114.124.36.248] (port=55074 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1aSHCl-004Kbv-5Q; Sat, 06 Feb 2016 21:44:11 -0700 Date: Sun, 7 Feb 2016 12:44:04 +0800 From: Erich Dollansky To: Warner Losh Cc: "freebsd-arm@freebsd.org" Subject: Re: clang++: error: the clang compiler does not support '-march=native' Message-ID: <20160207124404.186b395f@X220.alogt.com> In-Reply-To: References: <20160207050149.39f7e280@X220.alogt.com> <20160207095721.57fc3502@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 04:44:13 -0000 Hi, On Sat, 6 Feb 2016 21:01:13 -0700 Warner Losh wrote: > On Sat, Feb 6, 2016 at 6:57 PM, Erich Dollansky > > wrote: > > > On Sat, 6 Feb 2016 15:49:14 -0700 > > Warner Losh wrote: > > > > > On Sat, Feb 6, 2016 at 2:01 PM, Erich Dollansky > > > > > > wrote: > > > > > > > compiling on a Raspberry Pi B 2 on FreeBSD 11 gives me above's > > > > error message. > > > > > > > > A Internet search shows that this message does not exist. > > > > > > > > The program compiles using the same make file on FreeBSD 10 > > > > both on x86 and an Raspberry Pi B using the default compilers. > > > > > > > > Did support for 'march' get removed? > > > > > > > > > > As far as I can tell, it has never worked for either gcc or clang. > > > > > this is what I would have liked to find out. Intel claims speed > > gains of some 40% on their CPUs depending on the work load using > > gcc. > > > > Getting a few per cent on a Raspberry for free would make a real > > difference. > > > > Well, the -march= args work, just not -march=native. > The exact details of the core aren't exported from the kernel, so the > compiler can't easily query them to guess at the best code generation > to use. I think it would be a useful feature, but it just isn't one > we have yet. > > There are some -march values that get so aggressive about optimization > that they reveal some alignment issues. However, I think we've kill > them all. If not, we'd love to hear about it. > > I know that the -march=arm1176 works well for the RPi B. Last time I > tried it, the -march=cortex-a7 had some alignment issues. Since then > I've seen fixes go into the tree and I haven't tried again. Reports > from elsewhere indicate that this will give tens of percent in > improvement depending on the workload. > ok, I will try this then. Is there a list of working architectures somewhere which really applies for clang? I found only random information. Erich From owner-freebsd-arm@freebsd.org Sun Feb 7 04:58:24 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D772AA065A for ; Sun, 7 Feb 2016 04:58:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB208F28 for ; Sun, 7 Feb 2016 04:58:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qg0-x230.google.com with SMTP id y9so93245220qgd.3 for ; Sat, 06 Feb 2016 20:58:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=MTYNqaNQ55IC/+j+XLb0tdAszIcrcy6UljKIEZ7m9Ko=; b=rcJ+hZFawqqwN9cvGFhV1a4qzAcJ0tRZcfgTw3C7Vzn2wx3j8bL6BuFOnhT7z1sNzG nhIw55wYndCJ0nIVrzMGw0xd125mVzJbqxV16fPLmhDzTRibFEjLFMt6wOtYt5KjOS9i ciBUt+Mruf/5tl/P+2lOUOm0eVHzQKG/f1P6x7vfm30cZkkzbhConI1fRIXEGEFmaykg 0Mt9gDV/KbaIbJXpfcCbFf8F1zIg/3KO0cqtA7v9WXqNui+Ik+we9dA60nKZ+qD7tPqR NW1lzW6TqxlqJP6qFAmUMvlRSTdydTcybPp5IXMI1pUiMku/gYYyDSoNXYRAfaf4W/43 YzLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=MTYNqaNQ55IC/+j+XLb0tdAszIcrcy6UljKIEZ7m9Ko=; b=g395CIy6zlOe4abyWD5dXfEe80tOUYLiBS2ug5QaW6MfFmvYUw3rQpdNzz/M+fkFOz UZSbOADGb7e67ICLxJcGg2biDdp/H7e1amsV6ycCvsN2dl82UnnM2uhrKk4UepvFPCuQ zUhOM+V9OKnQDZemeJ1fLJH9L8eY7eLxsRBm6VYPgbyN5h1Kov45P6x17qk2xi6miWwl w+CQ+MNixWLsnl5a8Zqwb/35CacCSb7SlbWYvUNooYKMNE5+ZD87HpLXZ/0/10kxvpv6 upFkINYdFUo8VkPm4lvhdO4uYUp1EOnyMbDvGeWWiQ4WK6d+XZxyYBCpEhR0WfBnke/R 5EAQ== X-Gm-Message-State: AG10YOQdNIADRWDl884OpjfsHcHspB4v874TuK56In4v6cJMchzkDOlLLS1lpWK+qXlDDxxi3t5tW5+EgACrkw== MIME-Version: 1.0 X-Received: by 10.140.43.180 with SMTP id e49mr13692538qga.50.1454821103148; Sat, 06 Feb 2016 20:58:23 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.30.166 with HTTP; Sat, 6 Feb 2016 20:58:23 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <20160207124404.186b395f@X220.alogt.com> References: <20160207050149.39f7e280@X220.alogt.com> <20160207095721.57fc3502@X220.alogt.com> <20160207124404.186b395f@X220.alogt.com> Date: Sat, 6 Feb 2016 21:58:23 -0700 X-Google-Sender-Auth: WdwO3Hb2aa_Vqw2VJPLL2GZKxLg Message-ID: Subject: Re: clang++: error: the clang compiler does not support '-march=native' From: Warner Losh To: Erich Dollansky Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 04:58:24 -0000 On Sat, Feb 6, 2016 at 9:44 PM, Erich Dollansky wrote: > Hi, > > On Sat, 6 Feb 2016 21:01:13 -0700 > Warner Losh wrote: > > > On Sat, Feb 6, 2016 at 6:57 PM, Erich Dollansky > > > > wrote: > > > > > On Sat, 6 Feb 2016 15:49:14 -0700 > > > Warner Losh wrote: > > > > > > > On Sat, Feb 6, 2016 at 2:01 PM, Erich Dollansky > > > > > > > > wrote: > > > > > > > > > compiling on a Raspberry Pi B 2 on FreeBSD 11 gives me above's > > > > > error message. > > > > > > > > > > A Internet search shows that this message does not exist. > > > > > > > > > > The program compiles using the same make file on FreeBSD 10 > > > > > both on x86 and an Raspberry Pi B using the default compilers. > > > > > > > > > > Did support for 'march' get removed? > > > > > > > > > > > > > As far as I can tell, it has never worked for either gcc or clang. > > > > > > > this is what I would have liked to find out. Intel claims speed > > > gains of some 40% on their CPUs depending on the work load using > > > gcc. > > > > > > Getting a few per cent on a Raspberry for free would make a real > > > difference. > > > > > > > Well, the -march= args work, just not -march=native. > > The exact details of the core aren't exported from the kernel, so the > > compiler can't easily query them to guess at the best code generation > > to use. I think it would be a useful feature, but it just isn't one > > we have yet. > > > > There are some -march values that get so aggressive about optimization > > that they reveal some alignment issues. However, I think we've kill > > them all. If not, we'd love to hear about it. > > > > I know that the -march=arm1176 works well for the RPi B. Last time I > > tried it, the -march=cortex-a7 had some alignment issues. Since then > > I've seen fixes go into the tree and I haven't tried again. Reports > > from elsewhere indicate that this will give tens of percent in > > improvement depending on the workload. > > > ok, I will try this then. > > Is there a list of working architectures somewhere which really > applies for clang? I found only random information. TARGET_CPUTYPE is how you can buildworld with this flag set. Valid values can be found in bsd.cpus.mk # Common values for FreeBSD # arm: # arm920t, arm926ej-s, marvell-pj4, fa526, fa626, # fa606te, fa626te, fa726te # armv6: # arm1176jzf-s, generic-armv7-a, cortex-a5, cortex-a7, cortex-a8, # cortex-a9, cortex-a12, cortex-a15, cortex-a17, cortex-a53, cortex-a57, # cortex-a72, exynos-m1 I've not tried all of them, but the system at least builds with cortex-a7, arm926ej-s, arm1176jzf-s. Warner From owner-freebsd-arm@freebsd.org Sun Feb 7 18:10:03 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0494AAA0DF0 for ; Sun, 7 Feb 2016 18:10:03 +0000 (UTC) (envelope-from sig6247@openmailbox.org) Received: from smtp17.openmailbox.org (smtp17.openmailbox.org [62.4.1.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE9878F7 for ; Sun, 7 Feb 2016 18:10:02 +0000 (UTC) (envelope-from sig6247@openmailbox.org) Received: by mail2.openmailbox.org (Postfix, from userid 1002) id 172DF7CBD04; Sun, 7 Feb 2016 15:33:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1454855626; bh=rAfsIp61sg49A12eEeOklt5j3N1PpKVerzXdDwElkvY=; h=Date:From:To:Subject:From; b=sz8e3++jsZGJrJ/89pFWotKSpQWUzNqksLmNsIDSN4xXneDTrKCo/adFCf4jzh0YX 7ZGdznkwYJ2qCKXMXxjz+Wr9iCvEoUAxSPCJB1b8iFKmsPjglMqFug5PZl7b1+QvTi kS1AO/5oGxHXWwh/PYLasQPm3lMbWaUEORqnlf6g= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on openmailbox-b1 X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MISSING_MID,NO_RECEIVED,NO_RELAYS autolearn=no autolearn_force=no version=3.4.0 Date: Sun, 07 Feb 2016 14:33:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1454855625; bh=rAfsIp61sg49A12eEeOklt5j3N1PpKVerzXdDwElkvY=; h=Date:From:To:Subject:From; b=XeqfqzIzlSMXFAgwRSXt1u5V1eftI0jwmZ5M9KTCa3vhu+bDrXOkPC/QjallVsRvr 5owLqQFyhWAHZFHmTH7yP0URRLPASupaMLx6eTIRCpahp4bnZa0pTpL1UGsWcVbutk 87TNhEiU06D28qHIVjwYI/sxTH+Ucvx2G/dGi+RI= From: sig6247 To: freebsd-arm@freebsd.org Subject: BananaPi hangs with ARM_INTRNG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <20160207143346.172DF7CBD04@mail2.openmailbox.org> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 18:10:03 -0000 Hi, I'm running 11.0-CURRENT r295349 on a BananaPi M1 with the kernel config file A20. It just hangs on boot: crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 procfs registered Timecounters tick every 10.000 msec tcp_init: net.inet.tcp.tcbhashsize auto tuned to 8192 IPsec: Initialized Security Association Processing. lo0: bpf attached mmc0: Probing bus usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ahcich0: AHCI reset... ahcich0: SATA connect time=100us status=00000123 ahcich0: AHCI reset: device found ahcich0: AHCI reset: device ready after 0ms After commenting out "options ARM_INTRNG", everything works again. crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 procfs registered Timecounters tick every 10.000 msec tcp_init: net.inet.tcp.tcbhashsize auto tuned to 8192 usbus0: 480Mbps High Speed USB v2.0p IPsec: Initialized Security Association Processing. lo0: bpf attached mmc0: Probing bus usbus1: 480Mbps High Speed USB v2.0 ahcich0: AHCI reset... ahcich0: SATA connect time=100us status=00000123 ahcich0: AHCI reset: device found ugen1.1: at usbus1 uhub0: on usbus1 ugen0.1: at usbus0 uhub1: on usbus0 ahcich0: AHCI reset: device ready after 0ms mmc0: SD 2.0 interface conditions: OK mmc0: SD probe: OK (OCR: 0x40ff8000) mmc0: Current OCR: 0x00ff8000 ... Thanks, From owner-freebsd-arm@freebsd.org Mon Feb 8 05:52:49 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26016AA0491; Mon, 8 Feb 2016 05:52:49 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D1F4A36; Mon, 8 Feb 2016 05:52:47 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 4630dc2f; Mon, 8 Feb 2016 06:52:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; s=mail; bh=fCsgUo /kqxCd4aivt0SwhMuiBsk=; b=h5BGsXscY4Xrkn/JDeGGS8kR1GQGTXy6vJTFJa wbVPfLlDyWkyEoAZ2fESTaLf2/NLW3fwGaz+6U0SXX0kcP+vKMx2KDTte8kj5s1K iqXUrzQqiSS6LWyCeOQnZjf0QXLQ+QJsQrUyfiS7AcxJjpifH0yS+nSELSqULXeV ViSXI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; q=dns; s=mail; b= l+7fSQ6r98trUVqw9ZQpjoB0o9ptXAM2YSmqmG2Veip1WkL+yMtS8pmImK/5thC4 o9fUTszGdwG1ow9cdw/69FUjFUbTv/d7rdU3F2StDcZRGapgxlnfK9h6v1JDEYrK azr1z0fedRqsgf+8ngt3peYQI240MO4Lcw/6Rl2IdSU= Received: from webmail.megadrive.org (www1.blih.net [212.83.177.180]) by mail.blih.net (OpenSMTPD) with ESMTP id ecbdce62; Mon, 8 Feb 2016 06:52:38 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 08 Feb 2016 06:52:38 +0100 From: Emmanuel Vadot To: sig6247 Cc: freebsd-arm@freebsd.org, owner-freebsd-arm@freebsd.org Subject: Re: BananaPi hangs with ARM_INTRNG Organization: Bidouilliste In-Reply-To: <20160207143346.172DF7CBD04@mail2.openmailbox.org> References: <20160207143346.172DF7CBD04@mail2.openmailbox.org> Message-ID: X-Sender: manu@bidouilliste.com User-Agent: Roundcube Webmail/1.1.1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 05:52:49 -0000 Hi, Could you do a boot -v at ubldr stage and post the full boot log please ? Thanks, On 2016-02-07 15:33, sig6247 wrote: > Hi, > > I'm running 11.0-CURRENT r295349 on a BananaPi M1 with the kernel > config file A20. It just hangs on boot: > > crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 > random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 > procfs registered > Timecounters tick every 10.000 msec > tcp_init: net.inet.tcp.tcbhashsize auto tuned to 8192 > IPsec: Initialized Security Association Processing. > lo0: bpf attached > mmc0: Probing bus > usbus0: 480Mbps High Speed USB v2.0 > usbus1: 480Mbps High Speed USB v2.0 > ahcich0: AHCI reset... > ahcich0: SATA connect time=100us status=00000123 > ahcich0: AHCI reset: device found > ahcich0: AHCI reset: device ready after 0ms > > After commenting out "options ARM_INTRNG", everything works again. > > crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 > random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 > procfs registered > Timecounters tick every 10.000 msec > tcp_init: net.inet.tcp.tcbhashsize auto tuned to 8192 > usbus0: 480Mbps High Speed USB v2.0p > IPsec: Initialized Security Association Processing. > lo0: bpf attached > mmc0: Probing bus > usbus1: 480Mbps High Speed USB v2.0 > ahcich0: AHCI reset... > ahcich0: SATA connect time=100us status=00000123 > ahcich0: AHCI reset: device found > ugen1.1: at usbus1 > uhub0: on > usbus1 > ugen0.1: at usbus0 > uhub1: on > usbus0 > ahcich0: AHCI reset: device ready after 0ms > mmc0: SD 2.0 interface conditions: OK > mmc0: SD probe: OK (OCR: 0x40ff8000) > mmc0: Current OCR: 0x00ff8000 > ... > > Thanks, > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Feb 8 06:53:08 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77877AA1D3D for ; Mon, 8 Feb 2016 06:53:08 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FDAC1CDD for ; Mon, 8 Feb 2016 06:53:08 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id e185so89373326vkb.1 for ; Sun, 07 Feb 2016 22:53:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7TQSq0/LwBftI+1EzEHK2NWqOCjvhgB+XXqd827s//0=; b=luLVPsx5kK/Nmh5wgLbQTLR62u0CD3MQwRsEueiVflQ7KZE/WZ4AB9fItCmkfh+YiS J8hE9E7UwHHZNvQKTO3RjS4YqDKrWe5W83JDo5PeUYGMz/Ff49SNcK+Zg1tCWSw6dEoB jUosAj4RrvLIcZ238TF/1993NRvhfuLZaIzd/Q8jWrXm+KtjruCvaQRyiMldV1fVWyrg oKaCwNJh+5yLxBxfzQfODUe20jJZkVG5tFHQT04ZSpnij9dgxi5CBaVIx52/k/npb89h Ob1hFMHG7UATHx8P4cT7IqMM3E4AmWZOX0zpAVhpJ9OAewRnAgLmbcQ6nzzRt3GSs3V+ 1KZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=7TQSq0/LwBftI+1EzEHK2NWqOCjvhgB+XXqd827s//0=; b=RWLxDVss67HHCnFEaremng+ObJeqPsfHr6YSCM5Z4rPj3Xk3lHbrptYIV9t9/dWBrR WaVTY4/71XAqvBJX+tLfjgJfr4oLlrzsFigAK21ntv/nmklz27QKaC2E7pmXrXpqMLSv 1IAOL78ib4hkDYFKQF9CKGa4BbuJCFPBf9PGld4bOCIaqni9L7Sx0AaE3uLs8slvgMm2 B211wdn/faW7IAabDzBYdY16aMNG3Q9qcWjnJtogVjn7tdnWPk62fEO3knwf/KcVnwTv cZuSrhaCl/Bx3QLoA52IjKAWjo2zrM72RDyz4ZE+PIDWjr2gzmnUBrhSKY0x9xcQUW58 UIkQ== X-Gm-Message-State: AG10YOTLmM+oWcqyPGMsmhfpR+yYjG7lZkg6P8rCpBE5DmDBE+iHd9MacajGuKPV5WBKSnvQ2WoJOk8iWyXHdw== MIME-Version: 1.0 X-Received: by 10.31.159.136 with SMTP id i130mr19204166vke.144.1454914387251; Sun, 07 Feb 2016 22:53:07 -0800 (PST) Received: by 10.31.54.13 with HTTP; Sun, 7 Feb 2016 22:53:07 -0800 (PST) Date: Sun, 7 Feb 2016 22:53:07 -0800 Message-ID: Subject: ZFS Boot Environments on Arm Platforms From: Russell Haley To: freebsd-arm Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 06:53:08 -0000 Hi, Ian had indicated in a prior thread that ZFS has been known to work on the Arm platform. Does the recent addition of support for boot environments in the FreeBSD loader translate to arm, u-boot and ublr? I don't know much about loading ZFS BEs yet so ANY information on the subject would be greatly appreciated. Thanks Russ From owner-freebsd-arm@freebsd.org Tue Feb 9 02:41:32 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2215FAA2F6C for ; Tue, 9 Feb 2016 02:41:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 001B31EB1 for ; Tue, 9 Feb 2016 02:41:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.14.9/8.14.5) with ESMTP id u192fPEc017541; Mon, 8 Feb 2016 18:41:25 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.14.9/8.14.5/Submit) id u192fPah017540; Mon, 8 Feb 2016 18:41:25 -0800 (PST) (envelope-from fbsd) Date: Mon, 8 Feb 2016 18:41:24 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Savecore can't find matching kernel Message-ID: <20160209024124.GC150@www.zefox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 02:41:32 -0000 Hi all, [system is 11-CURRENT, updated last night, on RPI2] During a recent reboot following a crash the following message appeared on the console: Creating and/or trimming log files. Starting syslogd. savecore: reboot after panic: PGA_WRITEABLE on unmanaged page Feb 8 08:26:00 www savecore: reboot after panic: PGA_WRITEABLE on unmanaged page savecore: writing core to /var/crash/vmcore.2 Unable to find matching kernel for /var/crash/vmcore.2 Setting date via ntp. The no matching kernel warning has appeared at least once before as well. The core was generated manually with the "dump" command at the debugger prompt, is some additional action required? Along similar lines, where do debugging scripts go for the default configuration on an RPI2 ? I've tried adding them to /etc/ddb.conf but they're not found. /etc/defaults/rc.conf has script loading turned off by default, turning it on generates warnings, but obviously some scripts get loaded and run during some crashes. Seeming I'm looking in the wrong place.... Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Tue Feb 9 11:28:27 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E64DAA2333 for ; Tue, 9 Feb 2016 11:28:27 +0000 (UTC) (envelope-from export@vascofilters.eu) Received: from karieraserlg.nazwa.pl (aju23.rev.netart.pl [77.55.254.23]) by mx1.freebsd.org (Postfix) with ESMTP id 83A14C39 for ; Tue, 9 Feb 2016 11:28:26 +0000 (UTC) (envelope-from export@vascofilters.eu) Received: from pc (unknown [194.33.77.155]) by karieraserlg.nazwa.pl (Postfix) with ESMTPA id 253483CE18C2 for ; Tue, 9 Feb 2016 12:28:25 +0100 (CET) From: "=?iso-8859-2?Q?Marcin_Tomzi=F1ski?=" To: "freebsd-arm" Subject: cooperation Message-ID: <4F933069B27ADF09BE2F9447DDEF5766@pc> Date: Tue, 9 Feb 2016 12:28:33 +0100 Organization: AnoMail - oprogramowanie do emailingow X-Priority: 3 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 11:28:27 -0000 =20 Are you looking for a new automotive parts brand to be different from your = competitors?=20 Do you want to be a direct importer?=20 Are you looking for high quality products at fair and individual quotation?= =20 Fed up with late deliveries and low availability from the stock?=20 Do you want to join young and effective organisation?=20 Do you need fast orders handling and flexibility in market approach? We have a great proposal for your business! =20 Our products range consists of more than 1500 references under 4 brands - VASCO FILTERS (oil, fuel air and cabin filters) - FLUXAR FILTERS (red line) - PEXA WIPERS (universal and dedicated sets of wipers) - BREYKO (brake pads)=20 We are expanding our business in your country and looking for direct import= ers.=20 Join our Team! More info on web page: www.vascofilters.com or facebook = =20 If you have any questions do not hesitate to contact us, we speak English, = French and Spanish. Marketing and Operations Manager Olaf Tomzi=F1ski If you do not wish to receive further information. From owner-freebsd-arm@freebsd.org Tue Feb 9 16:46:37 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CC6DAA2C68 for ; Tue, 9 Feb 2016 16:46:37 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from kif.fubar.geek.nz (kif.fubar.geek.nz [178.62.119.249]) by mx1.freebsd.org (Postfix) with ESMTP id 600B71C85 for ; Tue, 9 Feb 2016 16:46:37 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from zapp.Home (global-5-143.nat-2.net.cam.ac.uk [131.111.5.143]) by kif.fubar.geek.nz (Postfix) with ESMTPSA id 749DAD78FE for ; Tue, 9 Feb 2016 16:46:00 +0000 (UTC) Date: Tue, 9 Feb 2016 16:45:59 +0000 From: Andrew Turner To: freebsd-arm@freebsd.org Subject: HEADS UP: New gnu dts files Message-ID: <20160209164559.5fdf6efe@zapp.Home> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 16:46:37 -0000 I've just updated our gnu device tree sources. I've tested them where I can, but if you find issues, e.g. devices not attaching or the kernel failing to boot, please report them so we can fix them for 11-RELEASE. Andrew From owner-freebsd-arm@freebsd.org Tue Feb 9 17:18:22 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3853FAA3CB4 for ; Tue, 9 Feb 2016 17:18:22 +0000 (UTC) (envelope-from sig6247@openmailbox.org) Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF92D17A8 for ; Tue, 9 Feb 2016 17:18:21 +0000 (UTC) (envelope-from sig6247@openmailbox.org) Received: by mail2.openmailbox.org (Postfix, from userid 1004) id 47F0A2AC618A; Tue, 9 Feb 2016 18:11:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1455037906; bh=T5R9dOLc0PWYPmYTfjEzjP9SkI3BMAqRYFWE4fK2k2I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=0krqlfggm2W/rCR6JIziLdSURv0aNJaH+mZit9Vf+yKlk/8hraknbn9rHBVrf06wy xWHgQPENqT7sIEa2mZi6/05xMVaY4j6+vmL0DElOUOibWBzi9gEnZKlOF87JUJPuSN Fgq+h74f8XdQCMKZYsqNmdKs4/Ns1frKbPK5KYBM= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on openmailbox-b2 X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MISSING_MID,NO_RECEIVED,NO_RELAYS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Date: Tue, 09 Feb 2016 17:11:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1455037896; bh=T5R9dOLc0PWYPmYTfjEzjP9SkI3BMAqRYFWE4fK2k2I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=gJfqRiIn5QlsFtnaQd19J3lL2P22oAZ6v2znqAhuw/g0N1xcHviL2VBnbCa2nacB0 Q4u+HQYaIX6Djo+jEbRq3DcP4i0Vp27rIytrOsR0P9SW5U9hLY+0TU7c49YvCv/+N8 fwxtxbfnDDyqk7XWcQmmEwpt4SQvoskY5QDfnfQs= From: sig6247 To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org Subject: Re: BananaPi hangs with ARM_INTRNG In-Reply-To: (Emmanuel Vadot's message of "Mon, 08 Feb 2016 06:52:38 +0100") References: <20160207143346.172DF7CBD04@mail2.openmailbox.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <20160209171146.47F0A2AC618A@mail2.openmailbox.org> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 17:18:22 -0000 On Mon, 08 Feb 2016 06:52:38 +0100, Emmanuel Vadot wrote: > Hi, > > Could you do a boot -v at ubldr stage and post the full boot log please > ? Sure. Here's the boot log of a kernel with ARM_INTRNG it just hangs at the line "ahcich0: AHCI reset: device ready after 0ms". /boot/dtb/bananapi.dtb size=0xf56 Loaded DTB from file 'bananapi.dtb'. Kernel entry at 0x42200100... Kernel args: -v KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #0 r295368: Tue Feb 9 10:20:05 UTC 2016 root@bpi.localhost:/usr/obj/usr/src/sys/A20 arm FreeBSD clang version 3.7.1 (tags/RELEASE_371/final 255217) 20151225 WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc0941000. Preloaded dtb "/boot/dtb/bananapi.dtb" at 0xc0941704. CPU: Cortex A7 rev 4 (Cortex-A core) Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext WB enabled LABT branch prediction disabled LoUU:2 LoC:3 LoUIS:2 Cache level 1: 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc 32KB/32B 2-way instruction cache Read-Alloc Cache level 2: 256KB/64B 8-way unified cache WB Read-Alloc Write-Alloc real memory = 1073741824 (1024 MB) avail memory = 1037066240 (989 MB) Physical memory chunk(s): 0x40000000 - 0x7fffffff, 1024 MB ( 262144 pages) Excluded memory regions: 0x42200000 - 0x42a53fff, 8 MB ( 2132 pages) NoAlloc Static device mappings: 0x01c00000 - 0x01ffffff mapped at VA 0xffb00000 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs ULE: setup cpu 0 ULE: setup cpu 1 random: entropy device external interface null: openfirm: mem: nfslock: pseudo-device crypto: random: harvesting attach, 8 bytes (4 bits) from nexus0 ofwbus0: simplebus0: on ofwbus0 random: harvesting attach, 8 bytes (4 bits) from simplebus0 random: harvesting attach, 8 bytes (4 bits) from ofwbus0 gic0: mem 0x1c81000-0x1c81fff,0x1c82000-0x1c820ff on simplebus0 simplebus0: no default resources for rid = 0, type = 1 gic0: pn 0x10, arch 0x2, rev 0x1, implementer 0x43b irqs 160 random: harvesting attach, 8 bytes (4 bits) from gic0 a10_sramc0: mem 0x1c00000-0x1c00fff on simplebus0 random: harvesting attach, 8 bytes (4 bits) from a10_sramc0 a20_cpu_cfg0: mem 0x1c25c00-0x1c25fff on simplebus0 random: harvesting attach, 8 bytes (4 bits) from a20_cpu_cfg0 a10_ccm0: mem 0x1c20000-0x1c203ff on simplebus0 random: harvesting attach, 8 bytes (4 bits) from a10_ccm0 a10_timer0: mem 0x1c20c00-0x1c20c8f irq 0 on simplebus0 Event timer "a10_timer Eventtimer" frequency 24000000 Hz quality 1000 Timecounter "a10_timer timer0" frequency 24000000 Hz quality 1000 a10_timer0: clock: hz=100 stathz = 0 a10_timer0: event timer clock frequency 24000000 a10_timer0: timecounter clock frequency 24000000 random: harvesting attach, 8 bytes (4 bits) from a10_timer0 a10wd0: mem 0x1c20c90-0x1c20c9f on simplebus0 random: harvesting attach, 8 bytes (4 bits) from a10wd0 gpio0: mem 0x1c20800-0x1c20bff irq 1 on simplebus0 gpiobus0: on gpio0 gpioled0: at pin 248 on gpiobus0 random: harvesting attach, 8 bytes (4 bits) from gpioled0 random: harvesting attach, 8 bytes (4 bits) from gpiobus0 gpioc0: on gpio0 random: harvesting attach, 8 bytes (4 bits) from gpioc0 random: harvesting attach, 8 bytes (4 bits) from gpio0 ehci0: mem 0x1c14000-0x1c14fff irq 2 on simplebus0 usbus0: EHCI version 1.0 usbus0 on ehci0 ehci0: usbpf: Attached random: harvesting attach, 8 bytes (4 bits) from usbus0 random: harvesting attach, 8 bytes (4 bits) from ehci0 ehci1: mem 0x1c1c000-0x1c1cfff irq 3 on simplebus0 usbus1: EHCI version 1.0 usbus1 on ehci1 ehci1: usbpf: Attached random: harvesting attach, 8 bytes (4 bits) from usbus1 random: harvesting attach, 8 bytes (4 bits) from ehci1 a10_mmc0: mem 0x1c0f000-0x1c0ffff irq 4 on simplebus0 a10_mmc0: DMA status: enabled mmc0: on a10_mmc0 random: harvesting attach, 8 bytes (4 bits) from mmc0 random: harvesting attach, 8 bytes (4 bits) from a10_mmc0 ahci0: mem 0x1c18000-0x1c18fff irq 5 on simplebus0 ahci0: AHCI v1.10 with 1 3Gbps ports, Port Multiplier not supported ahci0: quirks=0x2 ahci0: Caps: NCQ SNTF SS ALP AL CLO 3Gbps PMD SSC PSC 32cmd CCC 1ports ahcich0: at channel 0 on ahci0 ahcich0: Caps: random: harvesting attach, 8 bytes (4 bits) from ahcich0 random: harvesting attach, 8 bytes (4 bits) from ahci0 uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 6 on simplebus0 uart0: console (115200,n,8,1) uart0: fast interrupt uart0: PPS capture mode: DCDinvalid random: harvesting attach, 8 bytes (4 bits) from uart0 simplebus0: mem 0x1c0b000-0x1c0bfff irq 7 disabled compat allwinner,sun4i-emac (no driver attached) dwc0: mem 0x1c50000-0x1c5ffff irq 8 on simplebus0 miibus0: on dwc0 rgephy0: PHY 0 on miibus0 rgephy0: OUI 0x00e04c, model 0x0011, rev. 5 rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto random: harvesting attach, 8 bytes (4 bits) from rgephy0 rgephy1: PHY 1 on miibus0 rgephy1: OUI 0x00e04c, model 0x0011, rev. 5 rgephy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto random: harvesting attach, 8 bytes (4 bits) from rgephy1 random: harvesting attach, 8 bytes (4 bits) from miibus0 dwc0: bpf attached dwc0: Ethernet address: 02:86:0b:02:2d:7a random: harvesting attach, 8 bytes (4 bits) from dwc0 ofwbus0: compat gpio-leds (no driver attached) cryptosoft0: crypto: assign cryptosoft0 driver id 0, flags 100663296 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 22 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 23 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 25 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 24 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 26 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 27 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 28 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 procfs registered Timecounters tick every 10.000 msec tcp_init: net.inet.tcp.tcbhashsize auto tuned to 8192 IPsec: Initialized Security Association Processing. lo0: bpf attached mmc0: Probing bus usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ahcich0: AHCI reset... ahcich0: SATA connect time=100us status=00000123 ahcich0: AHCI reset: device found ahcich0: AHCI reset: device ready after 0ms Thanks, From owner-freebsd-arm@freebsd.org Tue Feb 9 20:56:40 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BB86AA263D; Tue, 9 Feb 2016 20:56:40 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DF11418F8; Tue, 9 Feb 2016 20:56:38 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 6deecc54; Tue, 9 Feb 2016 21:56:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; s=mail; bh=urf9KM jf0MOEzea1tZ5vAv5ZT14=; b=fLQJocbd60WOklKsXNLImt/8PhA7uQ+f7QLRwY sfKbOne3J57Cj27VZV5o73GHwdC/a9CCjGDpa1yif7YJYuigzN2Jef9DZxCTTtX5 png+fXs94Zov+tsQvdK5creP731HlNGo5pFdJVDcXV9Qb+JAh9pgyRynC/qStTGn suedE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; q=dns; s=mail; b= EfClOv8jOYL4GqNCHaefySzDyiEQhWKlfnX5NOKVKZujz7Fbo5+zIo3RHZR1yY/U QMuH0sn33uZIlZd1MpPy2m2Hx2Wmi2gyHiHY2BUDMduiiMs6XkQiF7a9AwSs0a6u 45MmqfrDpU1l6SA0g1hYRIfB9TH/QKA+VENnfZvvG6s= Received: from webmail.megadrive.org (www1.blih.net [212.83.177.180]) by mail.blih.net (OpenSMTPD) with ESMTP id 71665982; Tue, 9 Feb 2016 21:56:29 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 09 Feb 2016 21:56:29 +0100 From: Emmanuel Vadot To: sig6247 Cc: freebsd-arm@freebsd.org, owner-freebsd-arm@freebsd.org Subject: Re: BananaPi hangs with ARM_INTRNG Organization: Bidouilliste In-Reply-To: <20160209171146.47F0A2AC618A@mail2.openmailbox.org> References: <20160207143346.172DF7CBD04@mail2.openmailbox.org> <20160209171146.47F0A2AC618A@mail2.openmailbox.org> Message-ID: <262fb88021ac6915004d6b697af75ddd@megadrive.org> X-Sender: manu@bidouilliste.com User-Agent: Roundcube Webmail/1.1.1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 20:56:40 -0000 Ok that's what I thought, our current A20 dts doesn't have all the info for the gic with ARM_INTRNG. This was commited because I split a review in half and I didn't realise that it would cause a problem. The rest of the review (https://reviews.freebsd.org/D4792) have been accepted so just wait a bit till it's commited or just patch locally your source tree. Sorry for breaking bananapi. On 2016-02-09 18:11, sig6247 wrote: > On Mon, 08 Feb 2016 06:52:38 +0100, Emmanuel Vadot > wrote: > >> Hi, >> >> Could you do a boot -v at ubldr stage and post the full boot log >> please >> ? > > Sure. Here's the boot log of a kernel with ARM_INTRNG > it just hangs at the line "ahcich0: AHCI reset: device ready after > 0ms". > > /boot/dtb/bananapi.dtb size=0xf56 > Loaded DTB from file 'bananapi.dtb'. > Kernel entry at 0x42200100... > Kernel args: -v > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-CURRENT #0 r295368: Tue Feb 9 10:20:05 UTC 2016 > root@bpi.localhost:/usr/obj/usr/src/sys/A20 arm > FreeBSD clang version 3.7.1 (tags/RELEASE_371/final 255217) 20151225 > WARNING: WITNESS option enabled, expect reduced performance. > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0941000. > Preloaded dtb "/boot/dtb/bananapi.dtb" at 0xc0941704. > CPU: Cortex A7 rev 4 (Cortex-A core) > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext > WB enabled LABT branch prediction disabled > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: > 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc > 32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: > 256KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory = 1073741824 (1024 MB) > avail memory = 1037066240 (989 MB) > Physical memory chunk(s): > 0x40000000 - 0x7fffffff, 1024 MB ( 262144 pages) > Excluded memory regions: > 0x42200000 - 0x42a53fff, 8 MB ( 2132 pages) NoAlloc > Static device mappings: > 0x01c00000 - 0x01ffffff mapped at VA 0xffb00000 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > ULE: setup cpu 0 > ULE: setup cpu 1 > random: entropy device external interface > null: > openfirm: > mem: > nfslock: pseudo-device > crypto: > random: harvesting attach, 8 bytes (4 bits) from nexus0 > ofwbus0: > simplebus0: on ofwbus0 > random: harvesting attach, 8 bytes (4 bits) from simplebus0 > random: harvesting attach, 8 bytes (4 bits) from ofwbus0 > gic0: mem > 0x1c81000-0x1c81fff,0x1c82000-0x1c820ff on simplebus0 > simplebus0: no default resources for rid = 0, type = 1 > gic0: pn 0x10, arch 0x2, rev 0x1, implementer 0x43b irqs 160 > random: harvesting attach, 8 bytes (4 bits) from gic0 > a10_sramc0: mem 0x1c00000-0x1c00fff on > simplebus0 > random: harvesting attach, 8 bytes (4 bits) from a10_sramc0 > a20_cpu_cfg0: mem 0x1c25c00-0x1c25fff > on simplebus0 > random: harvesting attach, 8 bytes (4 bits) from a20_cpu_cfg0 > a10_ccm0: mem 0x1c20000-0x1c203ff on > simplebus0 > random: harvesting attach, 8 bytes (4 bits) from a10_ccm0 > a10_timer0: mem 0x1c20c00-0x1c20c8f irq 0 on > simplebus0 > Event timer "a10_timer Eventtimer" frequency 24000000 Hz quality 1000 > Timecounter "a10_timer timer0" frequency 24000000 Hz quality 1000 > a10_timer0: clock: hz=100 stathz = 0 > a10_timer0: event timer clock frequency 24000000 > a10_timer0: timecounter clock frequency 24000000 > random: harvesting attach, 8 bytes (4 bits) from a10_timer0 > a10wd0: mem 0x1c20c90-0x1c20c9f on simplebus0 > random: harvesting attach, 8 bytes (4 bits) from a10wd0 > gpio0: mem 0x1c20800-0x1c20bff irq 1 on > simplebus0 > gpiobus0: on gpio0 > gpioled0: at pin 248 on gpiobus0 > random: harvesting attach, 8 bytes (4 bits) from gpioled0 > random: harvesting attach, 8 bytes (4 bits) from gpiobus0 > gpioc0: on gpio0 > random: harvesting attach, 8 bytes (4 bits) from gpioc0 > random: harvesting attach, 8 bytes (4 bits) from gpio0 > ehci0: mem > 0x1c14000-0x1c14fff irq 2 on simplebus0 > usbus0: EHCI version 1.0 > usbus0 on ehci0 > ehci0: usbpf: Attached > random: harvesting attach, 8 bytes (4 bits) from usbus0 > random: harvesting attach, 8 bytes (4 bits) from ehci0 > ehci1: mem > 0x1c1c000-0x1c1cfff irq 3 on simplebus0 > usbus1: EHCI version 1.0 > usbus1 on ehci1 > ehci1: usbpf: Attached > random: harvesting attach, 8 bytes (4 bits) from usbus1 > random: harvesting attach, 8 bytes (4 bits) from ehci1 > a10_mmc0: mem > 0x1c0f000-0x1c0ffff irq 4 on simplebus0 > a10_mmc0: DMA status: enabled > mmc0: on a10_mmc0 > random: harvesting attach, 8 bytes (4 bits) from mmc0 > random: harvesting attach, 8 bytes (4 bits) from a10_mmc0 > ahci0: mem 0x1c18000-0x1c18fff > irq 5 on simplebus0 > ahci0: AHCI v1.10 with 1 3Gbps ports, Port Multiplier not supported > ahci0: quirks=0x2 > ahci0: Caps: NCQ SNTF SS ALP AL CLO 3Gbps PMD SSC PSC 32cmd CCC 1ports > ahcich0: at channel 0 on ahci0 > ahcich0: Caps: > random: harvesting attach, 8 bytes (4 bits) from ahcich0 > random: harvesting attach, 8 bytes (4 bits) from ahci0 > uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 6 on > simplebus0 > uart0: console (115200,n,8,1) > uart0: fast interrupt > uart0: PPS capture mode: DCDinvalid > random: harvesting attach, 8 bytes (4 bits) from uart0 > simplebus0: mem 0x1c0b000-0x1c0bfff irq 7 disabled > compat allwinner,sun4i-emac (no driver attached) > dwc0: mem 0x1c50000-0x1c5ffff irq 8 > on simplebus0 > miibus0: on dwc0 > rgephy0: PHY 0 on > miibus0 > rgephy0: OUI 0x00e04c, model 0x0011, rev. 5 > rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto > random: harvesting attach, 8 bytes (4 bits) from rgephy0 > rgephy1: PHY 1 on > miibus0 > rgephy1: OUI 0x00e04c, model 0x0011, rev. 5 > rgephy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto > random: harvesting attach, 8 bytes (4 bits) from rgephy1 > random: harvesting attach, 8 bytes (4 bits) from miibus0 > dwc0: bpf attached > dwc0: Ethernet address: 02:86:0b:02:2d:7a > random: harvesting attach, 8 bytes (4 bits) from dwc0 > ofwbus0: compat gpio-leds (no driver attached) > cryptosoft0: > crypto: assign cryptosoft0 driver id 0, flags 100663296 > crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 22 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 23 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 25 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 24 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 26 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 27 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 28 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0 > crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 > random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 > procfs registered > Timecounters tick every 10.000 msec > tcp_init: net.inet.tcp.tcbhashsize auto tuned to 8192 > IPsec: Initialized Security Association Processing. > lo0: bpf attached > mmc0: Probing bus > usbus0: 480Mbps High Speed USB v2.0 > usbus1: 480Mbps High Speed USB v2.0 > ahcich0: AHCI reset... > ahcich0: SATA connect time=100us status=00000123 > ahcich0: AHCI reset: device found > ahcich0: AHCI reset: device ready after 0ms > > Thanks, > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Feb 10 21:54:40 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03311AA5630 for ; Wed, 10 Feb 2016 21:54:40 +0000 (UTC) (envelope-from freebsd@mikej.com) Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com [216.26.158.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.paymentallianceintl.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8A9A1784 for ; Wed, 10 Feb 2016 21:54:39 +0000 (UTC) (envelope-from freebsd@mikej.com) Received: from firewall.mikej.com (162-230-214-65.lightspeed.lsvlky.sbcglobal.net [162.230.214.65]) by mx2.paymentallianceintl.com (8.15.1/8.15.1) with ESMTPS id u1ALsb7w034294 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 10 Feb 2016 16:54:38 -0500 (EST) (envelope-from freebsd@mikej.com) X-Authentication-Warning: mx2.paymentallianceintl.com: Host 162-230-214-65.lightspeed.lsvlky.sbcglobal.net [162.230.214.65] claimed to be firewall.mikej.com Received: from 192.168.6.63 (firewall.mikej.com [192.168.6.63]) by firewall.mikej.com (8.15.2/8.15.2) with ESMTP id u1ALsNkm092842 for ; Wed, 10 Feb 2016 16:54:24 -0500 (EST) (envelope-from freebsd@mikej.com) DMARC-Filter: OpenDMARC Filter v1.3.1 firewall.mikej.com u1ALsNkm092842 Authentication-Results: mail.mikej.com; dmarc=none header.from=mikej.com DKIM-Filter: OpenDKIM Filter v2.10.3 firewall.mikej.com u1ALsNkm092842 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mikej.com; s=mail; t=1455141264; bh=iY4tuJ/dT8sbH2MBn0pj48kTsYWPhEIi5/mwNW+Nunw=; h=Date:From:To:Subject; b=ARaXiUWiIDCpNqrM1L3LwRFvOkOLjtH08da1mI0CCcDwjzhj/nL3ke3zcEvxKkMRU opsoBs3SgR6HP8TDS6NYiVfhNHCFCSjmj9cxqzMHoxpcQLPf0MvU4s5k95mnTItIP3 gz11FICjiMbqjsGqwlmu6bJ6dbX41r5QolT7tm5z7xUtrM8WW+2mft10szYtYolYfw DdgNUM2c4sfwkuNGpBOn8ZYytEJ3pDs/Zp3W10KZzn88/CfuTDn+T1SqdX+lggz76l Wx48H+FNLuVudrtwiFSKeMin16cloRZikKeXxM+PB0TU/X0j2ushgopNkublqqEMSR 2v7k540/1Crrg== X-Authentication-Warning: firewall.mikej.com: Host firewall.mikej.com [192.168.6.63] claimed to be 192.168.6.63 MIME-Version: 1.0 Date: Wed, 10 Feb 2016 16:54:23 -0500 From: Michael Jung To: freebsd-arm@freebsd.org Subject: Pine 64 support Message-ID: <29c61e45e2755017f4b3ebabfeaae268@192.168.6.63> X-Sender: freebsd@mikej.com User-Agent: Roundcube Webmail/1.1.4 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 21:54:40 -0000 Are there any plans in supporting the Allwiner A64 SOC? http://wiki.pine64.org/index.php/Main_Page Please CC me, I've had issues getting subscribed to freebsd-arm@ which I have reported to the moderator. --mikej From owner-freebsd-arm@freebsd.org Thu Feb 11 00:16:13 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CD86AA36CB for ; Thu, 11 Feb 2016 00:16:13 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from newton2.metanet.ch (newton2.metanet.ch [80.74.158.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.metanet.ch", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AA4D95A for ; Thu, 11 Feb 2016 00:16:13 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from qubik.local (cpe-76-173-9-214.hawaii.res.rr.com [76.173.9.214]) by newton2.metanet.ch (Postfix) with ESMTPSA id 8B7AB33809B2 for ; Thu, 11 Feb 2016 01:07:14 +0100 (CET) Reply-To: werner@thieprojects.ch To: freebsd-arm@freebsd.org From: Werner Thie Subject: FreeBSD on the $9 C.H.I.P Organization: Thie & Co Projects Message-ID: <56BBD0B0.7040407@thieprojects.ch> Date: Wed, 10 Feb 2016 14:07:12 -1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 00:16:13 -0000 Hi all is there any interest or work going on making FreeBSD available on the $9 CHIP from nextthing.co? Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash and a slew of peripherals, the datasheet can be found on https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf Werner From owner-freebsd-arm@freebsd.org Thu Feb 11 00:48:55 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A315EAA47E2 for ; Thu, 11 Feb 2016 00:48:55 +0000 (UTC) (envelope-from krisb@interia.eu) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.156]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6392B1AA4 for ; Thu, 11 Feb 2016 00:48:55 +0000 (UTC) (envelope-from krisb@interia.eu) X-Interia-R: Interia X-Interia-R-IP: 178.183.176.58 X-Interia-R-Helo: <[192.168.20.162]> Received: from [192.168.20.162] (178.183.176.58.dsl.dynamic.t-mobile.pl [178.183.176.58]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by interia.eu (INTERIA.PL) with ESMTPSA; Thu, 11 Feb 2016 01:32:57 +0100 (CET) Subject: Re: FreeBSD on the $9 C.H.I.P To: werner@thieprojects.ch, freebsd-arm@freebsd.org References: <56BBD0B0.7040407@thieprojects.ch> From: Kris X-Enigmail-Draft-Status: N1110 Message-ID: <56BBD6B9.3090703@interia.eu> Date: Thu, 11 Feb 2016 01:32:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56BBD0B0.7040407@thieprojects.ch> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Interia-Antivirus: OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1455150779; bh=bOOGwhi6MpRbXIYXP7B1rRT5knlFP2Iusrdrr1YhicE=; h=X-Interia-R:X-Interia-R-IP:X-Interia-R-Helo:Subject:To:References: From:X-Enigmail-Draft-Status:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding: X-Interia-Antivirus; b=RH+m5AHlzq47tIlM8YhERaNAUJa2IUo4Fmr9V56Dd2tXuq4jfR2VojVO7WUBN9dA5 fseRDuvzNpMzjuXv6Xy0rmtvGvTVUh4to8z1ByWkHJFwKcaDh5BlSM2oeE6nMbb6lF aZhQOFcgEhPzvRZ7vDPu6AmER0cflBB+w95+O3Hk= X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 00:48:55 -0000 Hi Werner, Basically there is interest (I am waiting for x2 CHIP boards, they are due in March, but I think they will be slightly delayed). Before I get boards the only reasonable thing for me to do is to get as much out of existing tree to see how it can be ported, but no actual work. Please be careful - there is no such a thing like Cortex A13. A13 is just a marketing name Allwinner gave to their product. And I believe CHIP put Allwinner R8 on their board (normally in ARM nomenclature, R=for deeply embedded devices, A=for applications, but again, it is Allwinner so you can expect anything from their naming convention). However R8 is indeed equipped with Cortex A8 core, for which I believe some work has been done - see Allwinner A20 in repo - it has the same core if my memory serves right (it is even pin compatible with single core Allwinner A10 -> again Cortex A8 :) Kris On 02/11/16 01:07, Werner Thie wrote: > Hi all > > is there any interest or work going on making FreeBSD available on the > $9 CHIP from nextthing.co? > > Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash > and a slew of peripherals, the datasheet can be found on > > https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf > > Werner > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu Feb 11 01:43:36 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3E4EAA06D9 for ; Thu, 11 Feb 2016 01:43:36 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from newton2.metanet.ch (newton2.metanet.ch [80.74.158.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.metanet.ch", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F8931CEE for ; Thu, 11 Feb 2016 01:43:36 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from qubik.local (cpe-76-173-9-214.hawaii.res.rr.com [76.173.9.214]) by newton2.metanet.ch (Postfix) with ESMTPSA id 759CC3380887; Thu, 11 Feb 2016 02:43:31 +0100 (CET) Reply-To: werner@thieprojects.ch Subject: Re: FreeBSD on the $9 C.H.I.P References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> To: Kris , freebsd-arm@freebsd.org From: Werner Thie Organization: Thie & Co Projects Message-ID: <56BBE741.4010708@thieprojects.ch> Date: Wed, 10 Feb 2016 15:43:29 -1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56BBD6B9.3090703@interia.eu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 01:43:36 -0000 Hi Kris I have a board which did not boot when it arrived, but I was able to make it start up by going through their complete reflashing procedure. It's now running a headless version of Debian. Apparently a lot of chips have been sent out which did not boot at all, but with re-flashing it seems to be possible to navigate around the bad blocks issue on the NAND flash. I didn't look too deep into the re-flashing but it seemed to me quite a stable and re-doable action. So, basically it's looking at uboot, how the DTB would have to look like and then we would end up with a booting kernel and a few drivers missing, you seem to know more about that than I do. Werner On 2/10/16 2:32 PM, Kris wrote: > Hi Werner, > Basically there is interest (I am waiting for x2 CHIP boards, they are > due in March, but I think they will be slightly delayed). > Before I get boards the only reasonable thing for me to do is to get as > much out of existing tree to see how it can be ported, but no actual work. > > Please be careful - there is no such a thing like Cortex A13. A13 is > just a marketing name Allwinner gave to their product. And I believe > CHIP put Allwinner R8 on their board (normally in ARM nomenclature, > R=for deeply embedded devices, A=for applications, but again, it is > Allwinner so you can expect anything from their naming convention). > However R8 is indeed equipped with Cortex A8 core, for which I believe > some work has been done - see Allwinner A20 in repo - it has the same > core if my memory serves right (it is even pin compatible with single > core Allwinner A10 -> again Cortex A8 :) > > Kris > > On 02/11/16 01:07, Werner Thie wrote: >> Hi all >> >> is there any interest or work going on making FreeBSD available on the >> $9 CHIP from nextthing.co? >> >> Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash >> and a slew of peripherals, the datasheet can be found on >> >> https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf >> >> Werner >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Thu Feb 11 02:17:39 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE193AA1746 for ; Thu, 11 Feb 2016 02:17:38 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DDE9A94 for ; Thu, 11 Feb 2016 02:17:38 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-qk0-x233.google.com with SMTP id o6so14394395qkc.2 for ; Wed, 10 Feb 2016 18:17:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6xz2XCFYE+6bAQK0zamaWgJaLy41nfCOxflz9voOnRI=; b=L0L5zLcf2XjsGZ4bV3G3hv+Sb0tt3hWO9+17HFOBBXOtnmoov9MfP9Cjbp23e9ZGja BGP4Hx5Lg2eXdxSuUK3zfKZRGAbj6i3ciBRz+1r7qSGigrSbxqQd65KXoq/Tc1SqRooH dPtBJgAMhPooPg/kMHSwrRqDgsI7EIJNCtIeNRUqv8/fBCsKfx+iGSASCEvL4YcMcTG0 bdJ+qa2X16jPsSA68OhBJbPbdk7sRLioCw14xQt6+/Rfj+8Kc+32EG7JYA2QLLzyqlS0 eYy5F2DOitvjAEGsLlEIxtx0CMHWxXE8B4KP6QA+u+Na5liAa5PPT6/O0CH+6TT7DVO8 PbsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=6xz2XCFYE+6bAQK0zamaWgJaLy41nfCOxflz9voOnRI=; b=OYJzHYalsRc/fvG9oVHXMssKnWVzwySCp5E7ohhFFwE19tnnEB4T3FKDYPegxyD7yA 7mnm+FbRdMWyFovshHs5K6DBB/DWHEWjmLflUKOwaNpb6krdyLcFPwTr3yd8Jvpq4r7T /lQ/VFw1/QZrqX/BLFpUrml4HycPwIoGNlS1bzHTRY8vM250gl5PZIlrUZiBRw2FMEzL M+SXA8omEHMpGtg/yH8b/Zc2qIuS4bcR0RcPhptr0N0mj8uwi9FBR8zeGJ8jzUFZC/uy BedNQlWOP886CH+V8HfPCvQhzfQvRptqS/IRlV2bBuRLnbb05W4WR6BeLb1Q7djfdk7+ osLQ== X-Gm-Message-State: AG10YOTWeZwHWF99hUY6wCaRsJMwmCSY8bjOOlYXWm8Ct/t89cHvQhIZ2Eeogz3Y4SC1Psc9yYW7ukSIFqDuKq2FbKYnpXeel2O4mI9DrHaDnHYRZTrhN6wpirCEqMBg/nkxph14tyzuvymX1iPy/Q== X-Received: by 10.55.41.160 with SMTP id p32mr47742065qkp.69.1455157056884; Wed, 10 Feb 2016 18:17:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.45.71 with HTTP; Wed, 10 Feb 2016 18:17:22 -0800 (PST) In-Reply-To: <5688F015.4090002@bakulin.de> References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> From: "Lundberg, Johannes" Date: Wed, 10 Feb 2016 18:17:22 -0800 Message-ID: Subject: Re: MMC/SDIO stack under CAM To: Ilya Bakulin Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Alexander Motin , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 02:17:39 -0000 Hi Ilya This is great! I've got a Tronsmart ARA X5 and just purchased a few UP boards and it would be really nice if I could utilize the onboard eMMC. These are all Intel Cherrytrail platforms. Please let me know if there's anything (testing?) I can do to speed up the process. -- Name: Johannes Lundberg Position: Mirama project leader Phone: +1-408-636-2161 Skype: brilliantjohannes Online: LinkedIn Facebook Reddit Twitter GitHub GitLab Company: Mirama Brilliantservice US Brilliantservice JP On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: > So, more than one year has passed, and I'd like to resurrect this work > and move forward. > > I have uploaded a new diff and created a completely new revision to > track the development: https://reviews.freebsd.org/D4761 > > What it is able to do now: > > * Read/write on SD/SDHC/MMC cards! > * Detect SDIO cards and create devices that correspond to SDIO functions > > This all works only on BeagleBone currently, because some changes need > to be done in each SDHCI-compliant driver to make it interact with CAM. > I have purchased a Wandboard Quad that has an integrated SDIO WiFi chip, > so I hope to tweak its SDHCI driver as well. > > I haven't profiled the stack because: > * Now we have only SD/MMC cards that are slow anyway; > * I don't know how to do it in FreeBSD :-) > > Please review this diff and tell what you think! > > On 01/03/14 18:05, Adrian Chadd wrote: > > On 1 March 2014 08:46, Ilya Bakulin wrote: > >> Hi Adrian, > >> > >> On 24.02.14, 16:59, Adrian Chadd wrote: > >>> hi, > >>> > >>> Let me just reiterate some .. well, experience doing this stuff at QC= A. > >>> > >>> You really, absolutely don't want too much overhead in the MMC/SDIO > >>> path between whatever is issuing things and the network driver. > >>> > >>> There was significant performance work done at QCA on a local MMC/SDI= O > >>> driver and bus to get extremely low latency and CPU utilisation when > >>> pushing around small transactions. The current CAM locking model is > >>> not geared towards getting to high transaction rates. > >> So here you mean some work done on Linux MMC/SDIO stack by QCA > >> which made it far better than current Linux MMC stack in terms of > >> high SDIO I/O rates? > > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at small > > transactions to sustain the wifi speeds customers required. > > > >>> You may think this is a very architecturally pretty solution and it > >>> indeed may be. But if it doesn't perform as well as the existing loca= l > >>> hacks that vendors have done, no company deploying this hardware is > >>> going to want to use it. They'll end up realising there's this massiv= e > >>> CAM storage layer in between and either have to sit down to rip it up > >>> and replace it with something lightweight, or they'll say "screw it" > >>> and go back to the vendor supplied hacked up Linux solution. > >> I think that if the "architecturally pretty solution" behaves worse th= an > >> some ugly hacks, then it may be not so pretty or the architecture is > >> just broken > >> by design. > >> > >>> So I highly recommend you profile things - and profile things with > >>> lots of small transactions. If the CAM overhead is more than a tiny, > >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. :-) > >> I don't really know what to compare with. For MMC/SD cards it is prett= y > >> obvious, but then these cards will be likely the bottleneck, not the > stack. > >> And the only goal would be to not make the stack slower than it is now= . > >> But, as ATA devices are much faster than MMC/SD, I don't think this wi= ll > >> be a problem. > >> > >> For SDIO things are different. But we don't have any drivers (yet), > except > >> mv_sdiowl that I'm writing, to test on. So I have to bring the SDIO > >> stack on CAM, > >> than bring mv_sdiowl to the state when it can actually transmit the > >> data, and then > >> compare performance with the vendor-supplied Linux driver. > >> We'll see then if there is a room for improvement... > > That sounds like a plan. > > > > Just note that although storage looks like it's doing much more > > throughput, the IO size also matters. As I said above, it's not > > uncommon to have > 1000 receive frames a second on 802.11n; and that > > can peak much higher than that. That's not the kind of IO rate you see > > on SD cards. :-) > > > > > > > > -a > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > > > > > -- > Regards, > Ilya Bakulin > > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-arm@freebsd.org Thu Feb 11 02:35:24 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1C6FAA4351 for ; Thu, 11 Feb 2016 02:35:24 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-1.reflexion.net [208.70.210.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 782B11206 for ; Thu, 11 Feb 2016 02:35:23 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 11235 invoked from network); 11 Feb 2016 02:35:14 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 11 Feb 2016 02:35:14 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Wed, 10 Feb 2016 21:35:19 -0500 (EST) Received: (qmail 4450 invoked from network); 11 Feb 2016 02:35:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 11 Feb 2016 02:35:18 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 3154A1C43B3 for ; Wed, 10 Feb 2016 18:35:10 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: archivers/lzo2 on arm cortex-a7 (rpi2b) : ./lzotest/lzotest -mlzo -n2 -q ./COPYING gets "Signal 10" and stops the build Message-Id: <549E3A9E-302B-4412-B7FE-650E3986EFAD@dsl-only.net> Date: Wed, 10 Feb 2016 18:35:14 -0800 To: freebsd-arm Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 02:35:24 -0000 [Context basics: projects/clang380-import -r295351 for = buildworld/buildkernel that targeted an rpi2 (armv7-a/cortex-a7). This = context requires strict alignment: FreeBSD 11.0-CURRNET has SCTLR = bit[1]=3D=3D1 for such contexts.] When I attempt portinstall/portmaster builds for an arm rpi2 context = that depend on lzo2 I get the following. . . . LZO configuration summary ------------------------- LZO version : 2.09 configured for host : armv6-portbld-freebsd11.0 source code location : . compiler : /usr/bin/clang preprocessor definitions : -DLZO_HAVE_CONFIG_H=3D1 preprocessor flags :=20 compiler flags : -O -pipe -target = armv6--freebsd11.0-gnueabi -march=3Darmv7-a -mcpu=3Dcortex-a7 = -mfloat-abi=3Dsoftfp -mno-unaligned-access -mfloat-abi=3Dsoftfp = -fno-strict-aliasing build static library : yes build shared library : yes enable i386 assembly code : no . . . =3D=3D=3D> Running self-tests for lzo2-2.09 (can take a few minutes) cd /usr/obj/portswork/usr/ports/archivers/lzo2/work/lzo-2.09 && = /usr/bin/env MALLOC_OPTIONS=3Djz make check test SHELL=3D"/bin/sh -x" make check-local ./lzotest/lzotest -mlzo -n2 -q ./COPYING *** Signal 10 Stop. make[3]: stopped in = /usr/obj/portswork/usr/ports/archivers/lzo2/work/lzo-2.09 *** Error code 1 . . . I have submitted Bug 207096 for this misalignment problem. It has some = more supporting detail in its description. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Thu Feb 11 09:45:45 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DD73AA4970 for ; Thu, 11 Feb 2016 09:45:45 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DB6EE1386 for ; Thu, 11 Feb 2016 09:45:44 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 6d643be5; Thu, 11 Feb 2016 10:45:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=Vgsfjdq7DYKpwYzwX6jEVbCrtxM=; b=WktKHRZe/MaVZLpHZoG1wav6ojma lTpkXJkkYuLOZCSYX0Aqx91/a5KxdbVLM5sSHNavtIJlDgLmm2BSvOUbYadZ1MM5 zzeuUdHeOH+GLx2zZLHRJT5eT8+I0dDKS7eTRmw+Gc5mZn/WkNxOG0n6yajzanmv m9fg5SXqEFNXDMI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=SLsiV3tIF7Nhr/VTllsCpws+vqCuxy9XptgQJ22cWIje8MEAQi2VqXCd lmS0SX1E3HU2aAGvbM2d6eaNDCRQ1Auiyfb84dHqCpeIJ7Ko8fcYXI9NS0JW7Eo6 EDzDiq9Or75ljkBOQuxDmYZDSzCcXAq+PQAC5aVn3Uc7GeXTNys= Received: from atlantis.staff.bocal.org (163.5.250.239 [163.5.250.239]) by mail.blih.net (OpenSMTPD) with ESMTPSA id fd8840bb TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 11 Feb 2016 10:45:35 +0100 (CET) Date: Thu, 11 Feb 2016 10:45:34 +0100 From: Emmanuel Vadot To: Kris Cc: werner@thieprojects.ch, freebsd-arm@freebsd.org Subject: Re: FreeBSD on the $9 C.H.I.P Message-Id: <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> In-Reply-To: <56BBD6B9.3090703@interia.eu> References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 09:45:45 -0000 The R here does not stand for the RealTime profile from ARM, it's just one Allwinner chip line. The R8 is basically an A13 which is basically an A10 which FreeBSD support, so it should be easy to port FreeBSD on the R8. On Thu, 11 Feb 2016 01:32:57 +0100 Kris wrote: > Hi Werner, > Basically there is interest (I am waiting for x2 CHIP boards, they are > due in March, but I think they will be slightly delayed). > Before I get boards the only reasonable thing for me to do is to get as > much out of existing tree to see how it can be ported, but no actual work. > > Please be careful - there is no such a thing like Cortex A13. A13 is > just a marketing name Allwinner gave to their product. And I believe > CHIP put Allwinner R8 on their board (normally in ARM nomenclature, > R=for deeply embedded devices, A=for applications, but again, it is > Allwinner so you can expect anything from their naming convention). > However R8 is indeed equipped with Cortex A8 core, for which I believe > some work has been done - see Allwinner A20 in repo - it has the same > core if my memory serves right (it is even pin compatible with single > core Allwinner A10 -> again Cortex A8 :) > > Kris > > On 02/11/16 01:07, Werner Thie wrote: > > Hi all > > > > is there any interest or work going on making FreeBSD available on the > > $9 CHIP from nextthing.co? > > > > Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash > > and a slew of peripherals, the datasheet can be found on > > > > https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf > > > > Werner > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Feb 11 10:54:30 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5EF43AA4FEC for ; Thu, 11 Feb 2016 10:54:30 +0000 (UTC) (envelope-from export@vascofilters.eu) Received: from karieraserlg.nazwa.pl (aju23.rev.netart.pl [77.55.254.23]) by mx1.freebsd.org (Postfix) with ESMTP id 917DF1893 for ; Thu, 11 Feb 2016 10:54:29 +0000 (UTC) (envelope-from export@vascofilters.eu) Received: from pc (unknown [194.33.77.155]) by karieraserlg.nazwa.pl (Postfix) with ESMTPA id B1B833CE1A98 for ; Thu, 11 Feb 2016 11:54:28 +0100 (CET) From: "=?iso-8859-2?Q?Marcin_Tomzi=F1ski?=" To: "freebsd-arm" Subject: cooperation Message-ID: <7A3A6B6FC9EBB35140063A3F7E36BB4F@pc> Date: Thu, 11 Feb 2016 11:54:31 +0100 Organization: AnoMail - oprogramowanie do emailingow X-Priority: 3 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 10:54:30 -0000 =20 Are you looking for a new automotive parts brand to be different from your = competitors?=20 Do you want to be a direct importer?=20 Are you looking for high quality products at fair and individual quotation?= =20 Fed up with late deliveries and low availability from the stock?=20 Do you want to join young and effective organisation?=20 Do you need fast orders handling and flexibility in market approach? We have a great proposal for your business! =20 Our products range consists of more than 1500 references under 4 brands - VASCO FILTERS (oil, fuel air and cabin filters) - FLUXAR FILTERS (red line) - PEXA WIPERS (universal and dedicated sets of wipers) - BREYKO (brake pads)=20 We are expanding our business in your country and looking for direct import= ers.=20 Join our Team! More info on web page: www.vascofilters.com or facebook = =20 If you have any questions do not hesitate to contact us, we speak English, = French and Spanish. Marketing and Operations Manager Olaf Tomzi=F1ski If you do not wish to receive further information. From owner-freebsd-arm@freebsd.org Thu Feb 11 12:24:32 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24AADAA45DC for ; Thu, 11 Feb 2016 12:24:32 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E40741B24 for ; Thu, 11 Feb 2016 12:24:31 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aTqIE-0003YB-2y for freebsd-arm@freebsd.org; Thu, 11 Feb 2016 13:24:23 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Date: Thu, 11 Feb 2016 13:24:16 +0100 Subject: gpio device not available MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: -- X-Spam-Score: -2.9 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=disabled version=3.4.0 X-Scan-Signature: 38b42a75504d14ed68437fa295b89bc6 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 12:24:32 -0000 Hello, Running this beast of a machine. :-) FreeBSD 11.0-CURRENT #15 r294908M: Wed Jan 27 18:46:10 CET 2016 root@sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG arm I see gpio0 in dmesg: gpio0: mem 0x10100-0x1011f irq 35,36,37,38,39,40,41 on simplebus0 But no /dev/gpio* thingy. Is it possible to do anything with this gpio on my Sheevaplug? Regards, Ronald. From owner-freebsd-arm@freebsd.org Thu Feb 11 12:29:07 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A765AA471C for ; Thu, 11 Feb 2016 12:29:07 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ECB3F1C15 for ; Thu, 11 Feb 2016 12:29:06 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id B4F7F1FE023; Thu, 11 Feb 2016 13:29:04 +0100 (CET) Subject: Re: gpio device not available To: Ronald Klop , freebsd-arm@freebsd.org References: From: Hans Petter Selasky Message-ID: <56BC7F1D.5040809@selasky.org> Date: Thu, 11 Feb 2016 13:31:25 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 12:29:07 -0000 On 02/11/16 13:24, Ronald Klop wrote: > Hello, > > Running this beast of a machine. :-) > FreeBSD 11.0-CURRENT #15 r294908M: Wed Jan 27 18:46:10 CET 2016 > root@sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG > arm > > I see gpio0 in dmesg: > gpio0: mem 0x10100-0x1011f irq > 35,36,37,38,39,40,41 on simplebus0 > > But no /dev/gpio* thingy. > > Is it possible to do anything with this gpio on my Sheevaplug? > Hi, kldload gpiobus ??? --HPS From owner-freebsd-arm@freebsd.org Thu Feb 11 12:54:25 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C8AFAA5552 for ; Thu, 11 Feb 2016 12:54:25 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 575269AF for ; Thu, 11 Feb 2016 12:54:25 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aTqlF-0000kT-O5 for freebsd-arm@freebsd.org; Thu, 11 Feb 2016 13:54:22 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Subject: Re: gpio device not available References: <56BC7F1D.5040809@selasky.org> Date: Thu, 11 Feb 2016 13:54:16 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <56BC7F1D.5040809@selasky.org> User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: -- X-Spam-Score: -2.9 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=disabled version=3.4.0 X-Scan-Signature: 76f3589a93270604ea078d468a2051b3 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 12:54:25 -0000 On Thu, 11 Feb 2016 13:31:25 +0100, Hans Petter Selasky wrote: > On 02/11/16 13:24, Ronald Klop wrote: >> Hello, >> >> Running this beast of a machine. :-) >> FreeBSD 11.0-CURRENT #15 r294908M: Wed Jan 27 18:46:10 CET 2016 >> root@sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG >> arm >> >> I see gpio0 in dmesg: >> gpio0: mem 0x10100-0x1011f irq >> 35,36,37,38,39,40,41 on simplebus0 >> >> But no /dev/gpio* thingy. >> >> Is it possible to do anything with this gpio on my Sheevaplug? >> > > Hi, > > kldload gpiobus > > ??? > > --HPS > # kldstat -v | grep gpio 13 gpio/ofw_gpiobus 80 simplebus/gpio 12 gpio/gpioc 11 gpio/gpiobus Looks like it is embedded in the kernel. Regards, Ronald. From owner-freebsd-arm@freebsd.org Thu Feb 11 13:12:12 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A092CAA5C80 for ; Thu, 11 Feb 2016 13:12:12 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 12E741000 for ; Thu, 11 Feb 2016 13:12:11 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 96193917; Thu, 11 Feb 2016 14:12:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=5v8v5JOCjbIiULPgosCBJF3LbFs=; b=PTB5EcWU5g5I4g0AVQyS2TXfHCYc rKBPT/Oytl6OocQX29MtXwMqwKY4AWuNSuLqLILO6TLIBnnxgr63sY52YeYOqYys vPWyiUjSMRf3FU3f12y3tn86oxy4LDMURfmm8IjsACrYxHPC+PcrAzymN2VOp6Yy qWkSK1sFSHqBrKo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=giqK5aMP/cxjyZ0O8/c90UKFRpGv1Hj5/85zmHuzLzW7Cr34RSbvGDH3 62/+Y1yLlu4F/WAoZLRwC5IgEpcFGFsnet7UeHXbvWtjOSXRgMBHOQKPCVhNkT6Z yRngv1MSieQ7Fe5hy7AA+Dlaq9a3NWMUkYLRW3NiopvCwJpctx0= Received: from atlantis.staff.bocal.org (163.5.250.239 [163.5.250.239]) by mail.blih.net (OpenSMTPD) with ESMTPSA id b36eb6d1 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 11 Feb 2016 14:12:08 +0100 (CET) Date: Thu, 11 Feb 2016 14:12:07 +0100 From: Emmanuel Vadot To: "Ronald Klop" Cc: freebsd-arm@freebsd.org Subject: Re: gpio device not available Message-Id: <20160211141207.3777d527a270bc9902301a39@bidouilliste.com> In-Reply-To: References: <56BC7F1D.5040809@selasky.org> X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 13:12:12 -0000 The gpio controller doesn't seems to attach to the gpiobus so there is nothing you can do from userland. On Thu, 11 Feb 2016 13:54:16 +0100 "Ronald Klop" wrote: > On Thu, 11 Feb 2016 13:31:25 +0100, Hans Petter Selasky > wrote: > > > On 02/11/16 13:24, Ronald Klop wrote: > >> Hello, > >> > >> Running this beast of a machine. :-) > >> FreeBSD 11.0-CURRENT #15 r294908M: Wed Jan 27 18:46:10 CET 2016 > >> root@sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG > >> arm > >> > >> I see gpio0 in dmesg: > >> gpio0: mem 0x10100-0x1011f irq > >> 35,36,37,38,39,40,41 on simplebus0 > >> > >> But no /dev/gpio* thingy. > >> > >> Is it possible to do anything with this gpio on my Sheevaplug? > >> > > > > Hi, > > > > kldload gpiobus > > > > ??? > > > > --HPS > > > > # kldstat -v | grep gpio > 13 gpio/ofw_gpiobus > 80 simplebus/gpio > 12 gpio/gpioc > 11 gpio/gpiobus > > Looks like it is embedded in the kernel. > > Regards, > Ronald. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Thu Feb 11 18:04:42 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1324AAA4FEE for ; Thu, 11 Feb 2016 18:04:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0DFF12E9 for ; Thu, 11 Feb 2016 18:04:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qg0-x22f.google.com with SMTP id b35so43913926qge.0 for ; Thu, 11 Feb 2016 10:04:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JDMSVZsWLF0lt2kZj5fotNtsrJfcb1lh+O5tSkmuLHo=; b=DcoqqHBnAu875OJpuPILqbhP6LUsAR6AuKTC65V/T0kP1ARZye2FQN42dX1ASgm8eQ C7VxdULbzPAuZL/TdPflJlKrU01mLRPMlldhN64F8p8sV7q5bom3CCF7DDP0IVB0xZcG c0MixBDNpya6B6SN+C4XOjr7DAOU5Gcka+ZyTeb9sxg+XRFNWVisiepKbAgjSLz56WKh t4ss2tRrgZDO1F9Qyh9hsNs3Fne/sTqR4tx/uIj0RvNwb1YKQ09N7ecSCako9UWfY86H lS4qLqRVvbtKxAO2ezS2DccPPBXGVxYrgQNo84Ig/a2IG+lOUnGnPakDm9j5Jk6smbeX LJ7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JDMSVZsWLF0lt2kZj5fotNtsrJfcb1lh+O5tSkmuLHo=; b=C7hnQ0uXQWAz9uJOVLDBpVH7Ws+6MACbvNtm9cGr5M2btJ/4roF6C3+/SykANvAWjW I81EBsOm88F88geYIv9x9uQgWU0OaKtxV+gGuRpJYezTgQygtzOWfYlwJn6f9blZELw+ Z+LIL5N20mUS6fXFL0KTVSBNVUqcuCPayqpdAQERN7yFJT4n9PDuMFMMR5zpJr0Ee1pH IkH9jz4fF5lmzr5YVdTMEpjg5V1sSlHrnjSysoO5EWXTEg1DsuuGWUTslPKtnb4JMAxP EBvWHPlwb0oiY+OlDM2Ygp8iqldeXRBJyg45uMc+fKs/inMvpHfnikwd6G0x0GwTjiV7 FGtQ== X-Gm-Message-State: AG10YOSJBRQb5A40ObDBK6Iat/5Oc5wum7FigBxFlQBr8pW2SbJGDRz4QQsqZrOUA8aHG/MOpg4P+EbOMVe0Ww== MIME-Version: 1.0 X-Received: by 10.140.135.147 with SMTP id 141mr40764425qhh.74.1455213880710; Thu, 11 Feb 2016 10:04:40 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.30.166 with HTTP; Thu, 11 Feb 2016 10:04:40 -0800 (PST) X-Originating-IP: [69.53.245.22] In-Reply-To: <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> Date: Thu, 11 Feb 2016 11:04:40 -0700 X-Google-Sender-Auth: 7EIrHYhx5GaYt-cfGX02s7i8vxE Message-ID: Subject: Re: FreeBSD on the $9 C.H.I.P From: Warner Losh To: Emmanuel Vadot Cc: Kris , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 18:04:42 -0000 I have one of these too that I was handed a little bit ago. The initial issue that I saw was NAND support... Other than that, though, it didn't look terrible. Warner On Thu, Feb 11, 2016 at 2:45 AM, Emmanuel Vadot wrote: > > The R here does not stand for the RealTime profile from ARM, it's just > one Allwinner chip line. > > The R8 is basically an A13 which is basically an A10 which FreeBSD > support, so it should be easy to port FreeBSD on the R8. > > On Thu, 11 Feb 2016 01:32:57 +0100 > Kris wrote: > > > Hi Werner, > > Basically there is interest (I am waiting for x2 CHIP boards, they are > > due in March, but I think they will be slightly delayed). > > Before I get boards the only reasonable thing for me to do is to get as > > much out of existing tree to see how it can be ported, but no actual > work. > > > > Please be careful - there is no such a thing like Cortex A13. A13 is > > just a marketing name Allwinner gave to their product. And I believe > > CHIP put Allwinner R8 on their board (normally in ARM nomenclature, > > R=for deeply embedded devices, A=for applications, but again, it is > > Allwinner so you can expect anything from their naming convention). > > However R8 is indeed equipped with Cortex A8 core, for which I believe > > some work has been done - see Allwinner A20 in repo - it has the same > > core if my memory serves right (it is even pin compatible with single > > core Allwinner A10 -> again Cortex A8 :) > > > > Kris > > > > On 02/11/16 01:07, Werner Thie wrote: > > > Hi all > > > > > > is there any interest or work going on making FreeBSD available on the > > > $9 CHIP from nextthing.co? > > > > > > Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash > > > and a slew of peripherals, the datasheet can be found on > > > > > > https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf > > > > > > Werner > > > _______________________________________________ > > > freebsd-arm@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > -- > Emmanuel Vadot > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Thu Feb 11 18:42:56 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39FE3AA61BA for ; Thu, 11 Feb 2016 18:42:56 +0000 (UTC) (envelope-from krisb@interia.eu) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.156]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3ADF8FB for ; Thu, 11 Feb 2016 18:42:55 +0000 (UTC) (envelope-from krisb@interia.eu) X-Interia-R: Interia X-Interia-R-IP: 178.183.177.182 X-Interia-R-Helo: <[192.168.20.162]> Received: from [192.168.20.162] (178.183.177.182.dsl.dynamic.t-mobile.pl [178.183.177.182]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by interia.eu (INTERIA.PL) with ESMTPSA; Thu, 11 Feb 2016 19:42:50 +0100 (CET) Subject: Re: FreeBSD on the $9 C.H.I.P To: Emmanuel Vadot References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> Cc: werner@thieprojects.ch, freebsd-arm@freebsd.org From: Kris X-Enigmail-Draft-Status: N1110 Message-ID: <56BCD629.3040209@interia.eu> Date: Thu, 11 Feb 2016 19:42:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Interia-Antivirus: OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1455216172; bh=sSUe89R6za1gwcWogPh69GL0oi2KWyCzbExYbUNscUY=; h=X-Interia-R:X-Interia-R-IP:X-Interia-R-Helo:Subject:To:References: Cc:From:X-Enigmail-Draft-Status:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding: X-Interia-Antivirus; b=XyWSfKaW4Rc2zW6EqhYu6GjUMQHCx779mNPjYMLJeWgS6vYTYPvAwJ1MPg6XPEIbC sWEPjd1aRbxZhCU9RDQEWVD831ITTwxJ1WuDnWmh982GCIFNjOMzZ7OZ+73ditikMl BTqj0Dr8l5WR8hGKjTsLBBwMX8RjKjHSoRtWtBxI= X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 18:42:56 -0000 Yep, that's what I meant. As long as we distinguish Allwinner naming convention from what is inside we shall be fine (although Allwinner tries hard to confuse people... as if ARM had not done enough :) ) That being said I think support for Allwinner chips is worth being continued. They are cheap, quite robust, quite popular, and documentation is reasonably available (credits go to sunxi I must admit) So enough talking, time to go down to basement, disconnect my old Olimex-A10-Lime and try to put FreeBSD on it. I do expect troubles as I am not convinced it will work out of the box (e.g. it is A10 but I can see there is A20_cpu_cfg (dual core) among files.allwinner, which does not sound right to me...). However I also see that some good soul put more sources in compare to 10.2 tree. On 02/11/16 10:45, Emmanuel Vadot wrote: > The R here does not stand for the RealTime profile from ARM, it's just one Allwinner chip line. > > The R8 is basically an A13 which is basically an A10 which FreeBSD support, so it should be easy to port FreeBSD on the R8. > > On Thu, 11 Feb 2016 01:32:57 +0100 > Kris wrote: > >> Hi Werner, >> Basically there is interest (I am waiting for x2 CHIP boards, they are >> due in March, but I think they will be slightly delayed). >> Before I get boards the only reasonable thing for me to do is to get as >> much out of existing tree to see how it can be ported, but no actual work. >> >> Please be careful - there is no such a thing like Cortex A13. A13 is >> just a marketing name Allwinner gave to their product. And I believe >> CHIP put Allwinner R8 on their board (normally in ARM nomenclature, >> R=for deeply embedded devices, A=for applications, but again, it is >> Allwinner so you can expect anything from their naming convention). >> However R8 is indeed equipped with Cortex A8 core, for which I believe >> some work has been done - see Allwinner A20 in repo - it has the same >> core if my memory serves right (it is even pin compatible with single >> core Allwinner A10 -> again Cortex A8 :) >> >> Kris >> >> On 02/11/16 01:07, Werner Thie wrote: >>> Hi all >>> >>> is there any interest or work going on making FreeBSD available on the >>> $9 CHIP from nextthing.co? >>> >>> Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash >>> and a slew of peripherals, the datasheet can be found on >>> >>> https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf >>> >>> Werner >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Thu Feb 11 18:43:15 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0357EAA6210; Thu, 11 Feb 2016 18:43:15 +0000 (UTC) (envelope-from ilya@bakulin.de) Received: from olymp.kibab.com (olymp6.kibab.com [IPv6:2a01:4f8:160:84c1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6513794B; Thu, 11 Feb 2016 18:43:13 +0000 (UTC) (envelope-from ilya@bakulin.de) DKIM-Filter: OpenDKIM Filter v2.10.3 olymp.kibab.com 405134E679 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bakulin.de; s=default; t=1455216191; bh=XZ4eNKXf4QhM5JSmcSdX3bTOAM/fCSgWxsTz8dzeGGI=; h=In-Reply-To:References:Subject:From:Date:To:CC; b=lsiNR3Hpc5M0n7LWFYnQPbhUyD01yXMgGUz2VffBdio7JCjmnUqAGvQ8jLMPT+6+n sD7FDJd2SKHfeBWYzPX1rvgRuB94355qNcy8cYYYUXe0z1wuMJj4LNOKlmYTbZynpl 2uJEgLutMK0zBFHIEx/DBS1TIgFy1vW4PIlbLGj0= In-Reply-To: References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> MIME-Version: 1.0 Subject: Re: MMC/SDIO stack under CAM From: Ilya Bakulin Date: Thu, 11 Feb 2016 19:42:57 +0100 To: "Lundberg, Johannes" CC: "freebsd-hackers@freebsd.org" , Adrian Chadd , Alexander Motin , "freebsd-arm@freebsd.org" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 18:43:15 -0000 Hi Johannes, My work doesn't include writing drivers for SDHCI controllers. But if the controller on your new boards is supported by FreeBSD, then you can really test the new stack! Especially if the controller driver for your board is based on dev/sdhci, adapting it to work with the new stack is trivial. For example, iMX6 SDHCI needed only a couple of lines: https://github.com/kibab/freebsd/commit/df6d8d534740aa3633979da0a9d0ca00b60db0e9 Please let me know when you get the new boards and we will figure out what we need. On February 11, 2016 3:17:22 AM GMT+01:00, "Lundberg, Johannes" wrote: >Hi Ilya > >This is great! > >I've got a Tronsmart ARA X5 and just purchased a few UP > >boards >and it would be really nice if I could utilize the onboard eMMC. These >are >all Intel Cherrytrail platforms. > >Please let me know if there's anything (testing?) I can do to speed up >the >process. > > > >-- >Name: Johannes Lundberg >Position: Mirama project leader >Phone: +1-408-636-2161 >Skype: brilliantjohannes >Online: LinkedIn >Facebook > Reddit > Twitter > GitHub > >GitLab >Company: Mirama Brilliantservice US > Brilliantservice JP > > >On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: > >> So, more than one year has passed, and I'd like to resurrect this >work >> and move forward. >> >> I have uploaded a new diff and created a completely new revision to >> track the development: https://reviews.freebsd.org/D4761 >> >> What it is able to do now: >> >> * Read/write on SD/SDHC/MMC cards! >> * Detect SDIO cards and create devices that correspond to SDIO >functions >> >> This all works only on BeagleBone currently, because some changes >need >> to be done in each SDHCI-compliant driver to make it interact with >CAM. >> I have purchased a Wandboard Quad that has an integrated SDIO WiFi >chip, >> so I hope to tweak its SDHCI driver as well. >> >> I haven't profiled the stack because: >> * Now we have only SD/MMC cards that are slow anyway; >> * I don't know how to do it in FreeBSD :-) >> >> Please review this diff and tell what you think! >> >> On 01/03/14 18:05, Adrian Chadd wrote: >> > On 1 March 2014 08:46, Ilya Bakulin wrote: >> >> Hi Adrian, >> >> >> >> On 24.02.14, 16:59, Adrian Chadd wrote: >> >>> hi, >> >>> >> >>> Let me just reiterate some .. well, experience doing this stuff >at QCA. >> >>> >> >>> You really, absolutely don't want too much overhead in the >MMC/SDIO >> >>> path between whatever is issuing things and the network driver. >> >>> >> >>> There was significant performance work done at QCA on a local >MMC/SDIO >> >>> driver and bus to get extremely low latency and CPU utilisation >when >> >>> pushing around small transactions. The current CAM locking model >is >> >>> not geared towards getting to high transaction rates. >> >> So here you mean some work done on Linux MMC/SDIO stack by QCA >> >> which made it far better than current Linux MMC stack in terms of >> >> high SDIO I/O rates? >> > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at >small >> > transactions to sustain the wifi speeds customers required. >> > >> >>> You may think this is a very architecturally pretty solution and >it >> >>> indeed may be. But if it doesn't perform as well as the existing >local >> >>> hacks that vendors have done, no company deploying this hardware >is >> >>> going to want to use it. They'll end up realising there's this >massive >> >>> CAM storage layer in between and either have to sit down to rip >it up >> >>> and replace it with something lightweight, or they'll say "screw >it" >> >>> and go back to the vendor supplied hacked up Linux solution. >> >> I think that if the "architecturally pretty solution" behaves >worse than >> >> some ugly hacks, then it may be not so pretty or the architecture >is >> >> just broken >> >> by design. >> >> >> >>> So I highly recommend you profile things - and profile things >with >> >>> lots of small transactions. If the CAM overhead is more than a >tiny, >> >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. >:-) >> >> I don't really know what to compare with. For MMC/SD cards it is >pretty >> >> obvious, but then these cards will be likely the bottleneck, not >the >> stack. >> >> And the only goal would be to not make the stack slower than it is >now. >> >> But, as ATA devices are much faster than MMC/SD, I don't think >this will >> >> be a problem. >> >> >> >> For SDIO things are different. But we don't have any drivers >(yet), >> except >> >> mv_sdiowl that I'm writing, to test on. So I have to bring the >SDIO >> >> stack on CAM, >> >> than bring mv_sdiowl to the state when it can actually transmit >the >> >> data, and then >> >> compare performance with the vendor-supplied Linux driver. >> >> We'll see then if there is a room for improvement... >> > That sounds like a plan. >> > >> > Just note that although storage looks like it's doing much more >> > throughput, the IO size also matters. As I said above, it's not >> > uncommon to have > 1000 receive frames a second on 802.11n; and >that >> > can peak much higher than that. That's not the kind of IO rate you >see >> > on SD cards. :-) >> > >> > >> > >> > -a >> > _______________________________________________ >> > freebsd-hackers@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> > To unsubscribe, send any mail to " >> freebsd-hackers-unsubscribe@freebsd.org" >> > >> >> >> -- >> Regards, >> Ilya Bakulin >> >> >> > >-- >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 >もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 >複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 >--- >CONFIDENTIALITY NOTE: The information in this email is confidential >and intended solely for the addressee. >Disclosure, copying, distribution or any other action of use of this >email by person other than intended recipient, is prohibited. >If you are not the intended recipient and have received this email in >error, please destroy the original message. -- Простите за краткость, создано в K-9 Mail. From owner-freebsd-arm@freebsd.org Thu Feb 11 18:47:27 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04C16AA63D6; Thu, 11 Feb 2016 18:47:27 +0000 (UTC) (envelope-from ilya@bakulin.de) Received: from olymp.kibab.com (olymp6.kibab.com [IPv6:2a01:4f8:160:84c1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 67BB7BC7; Thu, 11 Feb 2016 18:47:25 +0000 (UTC) (envelope-from ilya@bakulin.de) DKIM-Filter: OpenDKIM Filter v2.10.3 olymp.kibab.com 957324E674 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bakulin.de; s=default; t=1455216445; bh=tRMeB9fG5vJN/yPGo7dqSSA4P1vEcY/rDAYmT+8+LtQ=; h=In-Reply-To:References:Subject:From:Date:To:CC; b=pOW+ovNQ3aNiRD7U0ZG0lNWj3Pc6o6fFlMGUIPBynsJjBX/X9r3HnWZm1L5jV8nDU o7UeNUKeEUZ3D8UWYSXRPIECV6BbfNVQloI6YdEUiQaJZtR3Bv84ywb2C7L8eqwGcY wDhC7ELzEtkjTLG/1/DgzHqF7QAriJRaYhPKq0sc= In-Reply-To: References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> MIME-Version: 1.0 Subject: Re: MMC/SDIO stack under CAM From: Ilya Bakulin Date: Thu, 11 Feb 2016 19:47:09 +0100 To: "Lundberg, Johannes" CC: "freebsd-hackers@freebsd.org" , Adrian Chadd , Alexander Motin , "freebsd-arm@freebsd.org" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 18:47:27 -0000 I'll use an excellent opportunity to post a small status update about my work :-) * SDHC controller on Wandboard now works with the new stack; * SDIO block read now works! * camcontrol userland app is extended to support "mmcsdcmd" command that allows to send MMC commands from userland apps directly to the card via pass(4) device -- now we can write WLAN driver in userland :-D On February 11, 2016 3:17:22 AM GMT+01:00, "Lundberg, Johannes" wrote: >Hi Ilya > >This is great! > >I've got a Tronsmart ARA X5 and just purchased a few UP > >boards >and it would be really nice if I could utilize the onboard eMMC. These >are >all Intel Cherrytrail platforms. > >Please let me know if there's anything (testing?) I can do to speed up >the >process. > > > >-- >Name: Johannes Lundberg >Position: Mirama project leader >Phone: +1-408-636-2161 >Skype: brilliantjohannes >Online: LinkedIn >Facebook > Reddit > Twitter > GitHub > >GitLab >Company: Mirama Brilliantservice US > Brilliantservice JP > > >On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: > >> So, more than one year has passed, and I'd like to resurrect this >work >> and move forward. >> >> I have uploaded a new diff and created a completely new revision to >> track the development: https://reviews.freebsd.org/D4761 >> >> What it is able to do now: >> >> * Read/write on SD/SDHC/MMC cards! >> * Detect SDIO cards and create devices that correspond to SDIO >functions >> >> This all works only on BeagleBone currently, because some changes >need >> to be done in each SDHCI-compliant driver to make it interact with >CAM. >> I have purchased a Wandboard Quad that has an integrated SDIO WiFi >chip, >> so I hope to tweak its SDHCI driver as well. >> >> I haven't profiled the stack because: >> * Now we have only SD/MMC cards that are slow anyway; >> * I don't know how to do it in FreeBSD :-) >> >> Please review this diff and tell what you think! >> >> On 01/03/14 18:05, Adrian Chadd wrote: >> > On 1 March 2014 08:46, Ilya Bakulin wrote: >> >> Hi Adrian, >> >> >> >> On 24.02.14, 16:59, Adrian Chadd wrote: >> >>> hi, >> >>> >> >>> Let me just reiterate some .. well, experience doing this stuff >at QCA. >> >>> >> >>> You really, absolutely don't want too much overhead in the >MMC/SDIO >> >>> path between whatever is issuing things and the network driver. >> >>> >> >>> There was significant performance work done at QCA on a local >MMC/SDIO >> >>> driver and bus to get extremely low latency and CPU utilisation >when >> >>> pushing around small transactions. The current CAM locking model >is >> >>> not geared towards getting to high transaction rates. >> >> So here you mean some work done on Linux MMC/SDIO stack by QCA >> >> which made it far better than current Linux MMC stack in terms of >> >> high SDIO I/O rates? >> > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at >small >> > transactions to sustain the wifi speeds customers required. >> > >> >>> You may think this is a very architecturally pretty solution and >it >> >>> indeed may be. But if it doesn't perform as well as the existing >local >> >>> hacks that vendors have done, no company deploying this hardware >is >> >>> going to want to use it. They'll end up realising there's this >massive >> >>> CAM storage layer in between and either have to sit down to rip >it up >> >>> and replace it with something lightweight, or they'll say "screw >it" >> >>> and go back to the vendor supplied hacked up Linux solution. >> >> I think that if the "architecturally pretty solution" behaves >worse than >> >> some ugly hacks, then it may be not so pretty or the architecture >is >> >> just broken >> >> by design. >> >> >> >>> So I highly recommend you profile things - and profile things >with >> >>> lots of small transactions. If the CAM overhead is more than a >tiny, >> >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. >:-) >> >> I don't really know what to compare with. For MMC/SD cards it is >pretty >> >> obvious, but then these cards will be likely the bottleneck, not >the >> stack. >> >> And the only goal would be to not make the stack slower than it is >now. >> >> But, as ATA devices are much faster than MMC/SD, I don't think >this will >> >> be a problem. >> >> >> >> For SDIO things are different. But we don't have any drivers >(yet), >> except >> >> mv_sdiowl that I'm writing, to test on. So I have to bring the >SDIO >> >> stack on CAM, >> >> than bring mv_sdiowl to the state when it can actually transmit >the >> >> data, and then >> >> compare performance with the vendor-supplied Linux driver. >> >> We'll see then if there is a room for improvement... >> > That sounds like a plan. >> > >> > Just note that although storage looks like it's doing much more >> > throughput, the IO size also matters. As I said above, it's not >> > uncommon to have > 1000 receive frames a second on 802.11n; and >that >> > can peak much higher than that. That's not the kind of IO rate you >see >> > on SD cards. :-) >> > >> > >> > >> > -a >> > _______________________________________________ >> > freebsd-hackers@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> > To unsubscribe, send any mail to " >> freebsd-hackers-unsubscribe@freebsd.org" >> > >> >> >> -- >> Regards, >> Ilya Bakulin >> >> >> > >-- >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 >もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 >複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 >--- >CONFIDENTIALITY NOTE: The information in this email is confidential >and intended solely for the addressee. >Disclosure, copying, distribution or any other action of use of this >email by person other than intended recipient, is prohibited. >If you are not the intended recipient and have received this email in >error, please destroy the original message. -- Простите за краткость, создано в K-9 Mail. From owner-freebsd-arm@freebsd.org Thu Feb 11 18:54:21 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97764AA68A4; Thu, 11 Feb 2016 18:54:21 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (mx0.deglitch.com [IPv6:2a00:13c0:63:7194:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5B967119E; Thu, 11 Feb 2016 18:54:21 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [192.168.11.14] (unknown [98.248.95.7]) by mx0.deglitch.com (Postfix) with ESMTPSA id 0DF598FC0A; Thu, 11 Feb 2016 10:54:15 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: MMC/SDIO stack under CAM From: Stanislav Sedov In-Reply-To: Date: Thu, 11 Feb 2016 10:54:12 -0800 Cc: "Lundberg, Johannes" , Adrian Chadd , "freebsd-hackers@freebsd.org" , Alexander Motin , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <6942A46B-110B-4E1F-9DA1-F965009E8E92@FreeBSD.org> References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> To: Ilya Bakulin X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 18:54:21 -0000 > On Feb 11, 2016, at 10:47 AM, Ilya Bakulin wrote: >=20 > I'll use an excellent opportunity to post a small status update about = my work :-) > * SDHC controller on Wandboard now works with the new stack; > * SDIO block read now works! > * camcontrol userland app is extended to support "mmcsdcmd" command = that allows to send MMC commands from userland apps directly to the card = via pass(4) device -- now we can write WLAN driver in userland :-D Great news, userspace drivers are the best!:) So what are the remaining pieces that prevent this work from hitting the = HEAD? -- Stanislav Sedov ST4096-RIPE From owner-freebsd-arm@freebsd.org Thu Feb 11 18:55:27 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BE70AA696A for ; Thu, 11 Feb 2016 18:55:27 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F6B51300 for ; Thu, 11 Feb 2016 18:55:27 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-qg0-x22f.google.com with SMTP id y9so45519658qgd.3 for ; Thu, 11 Feb 2016 10:55:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4R5xfqx5Argp9EYfrvegPansNCf5hMjmT0eLGR8/rxg=; b=iDIhbqFd8Ky6YDXnqFIsGiZGiNDUA6PlxoCr0FCAj2fk5xfjCR6O02FA+9vForAuDa bKLFJbpi7Uae1VjdZkVgqSWHJcIduDUPryDvmgSi2b1wPQGEI6P5KILswrFiTMqx2x0D qv0rDn2Z012do9tX2sVBnNbgBuwfJHuAjLwuJXBjPLzM0vSKlLEDNV5nbNUfJdFM9Mww dOXzQTBXhxNSptwIO+EvT0CMzYlpleEbpapqfz1iEvD5AfAm0eXe0pmY7H8OjGXLqokc +pvVodaHv/HTUwQTzf6NYVUfLyy3oi2awFfsUwMksmVnHM85dqLe9AcwXJYsfzN2UjnB KlEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=4R5xfqx5Argp9EYfrvegPansNCf5hMjmT0eLGR8/rxg=; b=ceeC/1Ip56lqLEh3uHeLCUczeCyZT+B6dc7x6aCZwNNavGlmqLQ9h5t+am7IH3SJnq sDhGtZphDUpVCvuatVDssVAlFrY6Nzc2XCX9cnPe6F1vHybDojcYCacwqs/aqsVJTAZL /1+LR1mWnioltf/mPIqlFa10aDfBlNhD8v8Hvk2N9Nuo/nJ73woB47dyyquBJ8xBksEe 3qOkYaYmCtdJlCy/G3VUuKkY7JAslU6PvFQwrLDxsX57+mBxFMUz0TzWG/BzZlYm2orG dx+rR3dekOZTaAQI6rsF32X4oPFWVvKHCJAmOWY4QFSXTe+094dW9mCYIoAAgwf6OtNP iJ8Q== X-Gm-Message-State: AG10YOTLIgzcmrYbd5ZszO+NNnBXVqYbHRFfxOx5O+Eb56kaFPVi+UDaRB7/7yGARj1svEinJihzD7SlMjLBDuoGPO9tCWzl3YtUP7jCJ/FnlasOJy55xym6aZ+toHKAcm5l6d4nNedZHnOusX3wqA== X-Received: by 10.140.40.37 with SMTP id w34mr58162699qgw.85.1455216925862; Thu, 11 Feb 2016 10:55:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.45.71 with HTTP; Thu, 11 Feb 2016 10:55:11 -0800 (PST) In-Reply-To: References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> From: "Lundberg, Johannes" Date: Thu, 11 Feb 2016 10:55:11 -0800 Message-ID: Subject: Re: MMC/SDIO stack under CAM To: Ilya Bakulin Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Alexander Motin , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 18:55:27 -0000 Hi Ilya The controller is Intel, https://pci-ids.ucw.cz/read/PC/8086/0f14 It was added in Linux some time ago http://lxr.free-electrons.com/source/drivers/mmc/host/sdhci-acpi.c I'm not sure how much work is needed to get the controller working...? I'm kind of new to device driver development. -- Name: Johannes Lundberg Position: Mirama project leader Phone: +1-408-636-2161 Skype: brilliantjohannes Online: LinkedIn Facebook Reddit Twitter GitHub GitLab Company: Mirama Brilliantservice US Brilliantservice JP On Thu, Feb 11, 2016 at 10:42 AM, Ilya Bakulin wrote: > Hi Johannes, > > My work doesn't include writing drivers for SDHCI controllers. But if the > controller on your new boards is supported by FreeBSD, then you can reall= y > test the new stack! Especially if the controller driver for your board is > based on dev/sdhci, adapting it to work with the new stack is trivial. Fo= r > example, iMX6 SDHCI needed only a couple of lines: > https://github.com/kibab/freebsd/commit/df6d8d534740aa3633979da0a9d0ca00b= 60db0e9 > > Please let me know when you get the new boards and we will figure out wha= t > we need. > > On February 11, 2016 3:17:22 AM GMT+01:00, "Lundberg, Johannes" < > johannes@brilliantservice.co.jp> wrote: > >> Hi Ilya >> >> This is great! >> >> I've got a Tronsmart ARA X5 and just purchased a few UP >> >> boards and it would be really nice if I could utilize the onboard eMMC. >> These are all Intel Cherrytrail platforms. >> >> Please let me know if there's anything (testing?) I can do to speed up >> the process. >> >> >> >> -- >> Name: Johannes Lundberg >> Position: Mirama project leader >> Phone: +1-408-636-2161 >> Skype: brilliantjohannes >> Online: LinkedIn Facebook >> Reddit >> Twitter >> GitHub >> GitLab >> >> Company: Mirama Brilliantservice US >> Brilliantservice JP >> >> >> On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: >> >>> So, more than one year has passed, and I'd like to resurrect this work >>> and move forward. >>> >>> I have uploaded a new diff and created a completely new revision to >>> track the development: https://reviews.freebsd.org/D4761 >>> >>> What it is able to do now: >>> >>> * Read/write on SD/SDHC/MMC cards! >>> * Detect SDIO cards and create devices that correspond to SDIO function= s >>> >>> This all works only on BeagleBone currently, because some changes need >>> to be done in each SDHCI-compliant driver to make it interact with CAM. >>> I have purchased a Wandboard Quad that has an integrated SDIO WiFi chip= , >>> so I hope to tweak its SDHCI driver as well. >>> >>> I haven't profiled the stack because: >>> * Now we have only SD/MMC cards that are slow anyway; >>> * I don't know how to do it in FreeBSD :-) >>> >>> Please review this diff and tell what you think! >>> >>> On 01/03/14 18:05, Adrian Chadd wrote: >>> > On 1 March 2014 08:46, Ilya Bakulin wrote: >>> >> Hi Adrian, >>> >> >>> >> On 24.02.14, 16:59, Adrian Chadd wrote: >>> >>> hi, >>> >>> >>> >>> Let me just reiterate some .. well, experience doing this stuff at >>> QCA. >>> >>> >>> >>> You really, absolutely don't want too much overhead in the MMC/SDIO >>> >>> path between whatever is issuing things and the network driver. >>> >>> >>> >>> There was significant performance work done at QCA on a local >>> MMC/SDIO >>> >>> driver and bus to get extremely low latency and CPU utilisation whe= n >>> >>> pushing around small transactions. The current CAM locking model is >>> >>> not geared towards getting to high transaction rates. >>> >> So here you mean some work done on Linux MMC/SDIO stack by QCA >>> >> which made it far better than current Linux MMC stack in terms of >>> >> high SDIO I/O rates? >>> > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at smal= l >>> > transactions to sustain the wifi speeds customers required. >>> > >>> >>> You may think this is a very architecturally pretty solution and it >>> >>> indeed may be. But if it doesn't perform as well as the existing >>> local >>> >>> hacks that vendors have done, no company deploying this hardware is >>> >>> going to want to use it. They'll end up realising there's this >>> massive >>> >>> CAM storage layer in between and either have to sit down to rip it = up >>> >>> and replace it with something lightweight, or they'll say "screw it= " >>> >>> and go back to the vendor supplied hacked up Linux solution. >>> >> I think that if the "architecturally pretty solution" behaves worse >>> than >>> >> some ugly hacks, then it may be not so pretty or the architecture is >>> >> just broken >>> >> by design. >>> >> >>> >>> So I highly recommend you profile things - and profile things with >>> >>> lots of small transactions. If the CAM overhead is more than a tiny= , >>> >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. :-) >>> >> I don't really know what to compare with. For MMC/SD cards it is >>> pretty >>> >> obvious, but then these cards will be likely the bottleneck, not the >>> stack. >>> >> And the only goal would be to not make the stack slower than it is >>> now. >>> >> But, as ATA devices are much faster than MMC/SD, I don't think this >>> will >>> >> be a problem. >>> >> >>> >> For SDIO things are different. But we don't have any drivers (yet), >>> except >>> >> mv_sdiowl that I'm writing, to test on. So I have to bring the SDIO >>> >> stack on CAM, >>> >> than bring mv_sdiowl to the state when it can actually transmit the >>> >> data, and then >>> >> compare performance with the vendor-supplied Linux driver. >>> >> We'll see then if there is a room for improvement... >>> > That sounds like a plan. >>> > >>> > Just note that although storage looks like it's doing much more >>> > throughput, the IO size also matters. As I said above, it's not >>> > uncommon to have > 1000 receive frames a second on 802.11n; and that >>> > can peak much higher than that. That's not the kind of IO rate you se= e >>> > on SD cards. :-) >>> > >>> > >>> > >>> > -a >>> > _______________________________________________ >>> > freebsd-hackers@freebsd.org mailing list >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> > To unsubscribe, send any mail to " >>> freebsd-hackers-unsubscribe@freebsd.org" >>> > >>> >>> >>> -- >>> Regards, >>> Ilya Bakulin >>> >>> >>> >> >> =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- >> =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 >> =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 >> =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 >> --- >> CONFIDENTIALITY NOTE: The information in this email is confidential >> and intended solely for the addressee. >> Disclosure, copying, distribution or any other action of use of this >> email by person other than intended recipient, is prohibited. >> If you are not the intended recipient and have received this email in >> error, please destroy the original message. > > > -- > =D0=9F=D1=80=D0=BE=D1=81=D1=82=D0=B8=D1=82=D0=B5 =D0=B7=D0=B0 =D0=BA=D1= =80=D0=B0=D1=82=D0=BA=D0=BE=D1=81=D1=82=D1=8C, =D1=81=D0=BE=D0=B7=D0=B4=D0= =B0=D0=BD=D0=BE =D0=B2 K-9 Mail. > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-arm@freebsd.org Thu Feb 11 21:36:53 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65DB9AA59EA for ; Thu, 11 Feb 2016 21:36:53 +0000 (UTC) (envelope-from alexander.fedorov@rtlservice.com) Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FE56107B for ; Thu, 11 Feb 2016 21:36:52 +0000 (UTC) (envelope-from alexander.fedorov@rtlservice.com) Received: by mail-yk0-x230.google.com with SMTP id z7so26707867yka.3 for ; Thu, 11 Feb 2016 13:36:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtlservice-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WP3CAVXki4ipEwFDaYNCxtUFIHerUnim8KL5yXL3YWs=; b=PUfOLdfqqVWwYI5+YK4u5kBis56LTImxeFUNFf/tBJddwGMgtO/CmLBQoEKYfAdquI R+FgxUiMAzL1YkydOKYvrDon7hzskGbIArRmS/7M7ZkHnEapNKFvNAYScnyD6674CEK4 EVRO01aKXrgrLflHhyP6CuaxPbuZ/wP4t4vM2SW4CQZff6U9cKGcSFb/blo9LR9Abkvb cQsqmywv+QsKSfJf+c9ehk6O2dPMAtsZWZroPmU417DMItdXz3zA6Z/neY4M0doUCm9N xy9cehnBoDytjJOmyw/dU40O9kL8hZz/gjX+K4hBpQTo8UnPzJatYiruyHqoEDk6jbzQ 7vLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WP3CAVXki4ipEwFDaYNCxtUFIHerUnim8KL5yXL3YWs=; b=aqe+yd0SikLG4wn2JSguVADAZ+jqJ00GAGx9P+24+FBq9W3NxjePzWTELFBbDS8uOS WcktdXxojukZVdnqcCKmSEwfiHXLZFiksdnEqdQdfD12FBNRuNgKypBgEmz4A6C5wOgW kYamugakLDINMbwEe6DL0JwLuvEspQCE00Aw97jtMLxrZeJk/c/rugiE9gN0yi2ao7V6 bqXSCOyxiUhTS7FYb4cpChlTQ5sShnjebzcAkm9AakA6h5vbS9cfPYOH+kbcVUTEIRtx pbQfkJSHgD8mp+fMZDF60dz6ZsmUlp9y5CpnfwBZD7iDSWoKY06QpDGCirZDFlvdFQDI gPLw== X-Gm-Message-State: AG10YOQWvWeKWiQCKVKqWHr3YPRtbaE8yc1Ez9jmBcJfzIbTigq6ndI7HggjyM7IU3USDHHP1w7QBCRansIi/4E6 MIME-Version: 1.0 X-Received: by 10.37.94.198 with SMTP id s189mr467329ybb.62.1455226611422; Thu, 11 Feb 2016 13:36:51 -0800 (PST) Received: by 10.13.195.71 with HTTP; Thu, 11 Feb 2016 13:36:51 -0800 (PST) In-Reply-To: References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> Date: Fri, 12 Feb 2016 00:36:51 +0300 Message-ID: Subject: Re: FreeBSD on the $9 C.H.I.P From: "Fedorov, Alexander" To: Warner Losh Cc: Emmanuel Vadot , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2016 21:36:53 -0000 It's seems, that many other things are not supported, what about: https://reviews.freebsd.org/D5202 https://reviews.freebsd.org/D5050 https://reviews.freebsd.org/D5050 https://reviews.freebsd.org/D4846 2016-02-11 21:04 GMT+03:00 Warner Losh : > I have one of these too that I was handed a little bit ago. The initial > issue that I saw > was NAND support... Other than that, though, it didn't look terrible. > > Warner > > > > On Thu, Feb 11, 2016 at 2:45 AM, Emmanuel Vadot > wrote: > >> >> The R here does not stand for the RealTime profile from ARM, it's just >> one Allwinner chip line. >> >> The R8 is basically an A13 which is basically an A10 which FreeBSD >> support, so it should be easy to port FreeBSD on the R8. >> >> On Thu, 11 Feb 2016 01:32:57 +0100 >> Kris wrote: >> >> > Hi Werner, >> > Basically there is interest (I am waiting for x2 CHIP boards, they are >> > due in March, but I think they will be slightly delayed). >> > Before I get boards the only reasonable thing for me to do is to get as >> > much out of existing tree to see how it can be ported, but no actual >> work. >> > >> > Please be careful - there is no such a thing like Cortex A13. A13 is >> > just a marketing name Allwinner gave to their product. And I believe >> > CHIP put Allwinner R8 on their board (normally in ARM nomenclature, >> > R=for deeply embedded devices, A=for applications, but again, it is >> > Allwinner so you can expect anything from their naming convention). >> > However R8 is indeed equipped with Cortex A8 core, for which I believe >> > some work has been done - see Allwinner A20 in repo - it has the same >> > core if my memory serves right (it is even pin compatible with single >> > core Allwinner A10 -> again Cortex A8 :) >> > >> > Kris >> > >> > On 02/11/16 01:07, Werner Thie wrote: >> > > Hi all >> > > >> > > is there any interest or work going on making FreeBSD available on the >> > > $9 CHIP from nextthing.co? >> > > >> > > Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash >> > > and a slew of peripherals, the datasheet can be found on >> > > >> > > https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf >> > > >> > > Werner >> > > _______________________________________________ >> > > freebsd-arm@freebsd.org mailing list >> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > >> > _______________________________________________ >> > freebsd-arm@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >> >> -- >> Emmanuel Vadot >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Fri Feb 12 11:32:47 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41104AA4970 for ; Fri, 12 Feb 2016 11:32:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from smtp.hungerhost.com (smtp.hungerhost.com [216.38.51.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1FD6C1B7F for ; Fri, 12 Feb 2016 11:32:46 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from global-5-13.nat-1.net.cam.ac.uk ([131.111.5.13]:64634 helo=[10.240.98.110]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from ) id 1aUBxt-0004MV-Fg; Fri, 12 Feb 2016 06:32:45 -0500 From: "George Neville-Neil" To: "Michael Jung" Cc: freebsd-arm@freebsd.org Subject: Re: Pine 64 support Date: Fri, 12 Feb 2016 11:32:44 +0000 Message-ID: <0116C790-553F-433B-BDFD-55CEEB5D7E12@neville-neil.com> In-Reply-To: <29c61e45e2755017f4b3ebabfeaae268@192.168.6.63> References: <29c61e45e2755017f4b3ebabfeaae268@192.168.6.63> MIME-Version: 1.0 X-Mailer: MailMate (1.9.4r5213) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com X-Authenticated-Sender: vps.hungerhost.com: gnn@neville-neil.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2016 11:32:47 -0000 > Are there any plans in supporting the Allwiner A64 SOC? > > http://wiki.pine64.org/index.php/Main_Page > I'm waiting on one, as I am sure are others. Best, George From owner-freebsd-arm@freebsd.org Fri Feb 12 16:13:45 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DC3FAA6B70 for ; Fri, 12 Feb 2016 16:13:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48B3BEF8 for ; Fri, 12 Feb 2016 16:13:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x22c.google.com with SMTP id y8so13440306igp.1 for ; Fri, 12 Feb 2016 08:13:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jwZ1NzcbTH2A0N3rUnw6Mq3G4FKaATzPYOW7Uuerppk=; b=pOwLvXiby9AYdVFI68ir7XRiufqpuzXr3ATLFCRbWvQPLedXGzfJCBtstITl/TA5yp B2xFK9qd1Nh79Bz3z1XHX4u4WfxbZYbP3bn8RyNyeUo+40J8buIrZ+4b5Y07hPyTGKXv lXNjvAVCeWS51r7Z1DwerkIIUp8RnTV+JK8UBdpQXyKfoIHE5Z8771s/kJtCuntE0sud 3M2uu5MZd6YK8Nh2KWMF6rxRIGK1qMWo5yiqAimnx+S+RBhpljkUDjuxukquo8EBQPU0 gpYxuk/+U8lDlPOKoPXkywr08oP3sua15B9Yoj7udzhpeBMbKB/jr48tecwskXmX0VuG CMMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jwZ1NzcbTH2A0N3rUnw6Mq3G4FKaATzPYOW7Uuerppk=; b=D7VSsPgTEp1ka82QOy7hSqWyzRXSUHmweZx6TWPEwlzY5jYXzWJoL4JUpPJNMnMuA2 e5dyx0ztpdgCafp/6EV3bBRtrZOw4Bn8IrA4HEKGsFLA3meegvhzgMuU50bWH4UEXQAM 4qxgZPL4ahgu/FAWerWtIPZ4/0MANK3DING8qpHfeGwodGd6LwFuvHznZLFdZhMUeNM4 KBGPipHC9nXGJOPVq5EhOCL2/Pe5uxTlQNISW6r65UWWHmX9NUUC1CgLa2KY/j3+5zzI qreSZI8EL0upFK8wOxKT6YZn17YOd2R1Nv/b9KeohjhLZnde5x/4UQGTnwWSbh0ZPmKE dxAQ== X-Gm-Message-State: AG10YOQSe5ySYAlhdGaQAvKRnJk0Fft6XM3apDTSS9sQw8++rhWDZ8C8YNHrBH1zaP9kRnieHhggjoYhC5sg6w== MIME-Version: 1.0 X-Received: by 10.50.93.36 with SMTP id cr4mr3702909igb.22.1455293624441; Fri, 12 Feb 2016 08:13:44 -0800 (PST) Received: by 10.36.14.19 with HTTP; Fri, 12 Feb 2016 08:13:44 -0800 (PST) In-Reply-To: References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> Date: Fri, 12 Feb 2016 08:13:44 -0800 Message-ID: Subject: Re: FreeBSD on the $9 C.H.I.P From: Adrian Chadd To: "Fedorov, Alexander" Cc: Warner Losh , "freebsd-arm@freebsd.org" , Emmanuel Vadot Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2016 16:13:45 -0000 On 11 February 2016 at 13:36, Fedorov, Alexander wrote: > It's seems, that many other things are not supported, what about: > https://reviews.freebsd.org/D5202 > https://reviews.freebsd.org/D5050 > https://reviews.freebsd.org/D5050 > https://reviews.freebsd.org/D4846 Hopefully those can go into -HEAD next week.. :) -adrian > > > > 2016-02-11 21:04 GMT+03:00 Warner Losh : >> I have one of these too that I was handed a little bit ago. The initial >> issue that I saw >> was NAND support... Other than that, though, it didn't look terrible. >> >> Warner >> >> >> >> On Thu, Feb 11, 2016 at 2:45 AM, Emmanuel Vadot >> wrote: >> >>> >>> The R here does not stand for the RealTime profile from ARM, it's just >>> one Allwinner chip line. >>> >>> The R8 is basically an A13 which is basically an A10 which FreeBSD >>> support, so it should be easy to port FreeBSD on the R8. >>> >>> On Thu, 11 Feb 2016 01:32:57 +0100 >>> Kris wrote: >>> >>> > Hi Werner, >>> > Basically there is interest (I am waiting for x2 CHIP boards, they are >>> > due in March, but I think they will be slightly delayed). >>> > Before I get boards the only reasonable thing for me to do is to get as >>> > much out of existing tree to see how it can be ported, but no actual >>> work. >>> > >>> > Please be careful - there is no such a thing like Cortex A13. A13 is >>> > just a marketing name Allwinner gave to their product. And I believe >>> > CHIP put Allwinner R8 on their board (normally in ARM nomenclature, >>> > R=for deeply embedded devices, A=for applications, but again, it is >>> > Allwinner so you can expect anything from their naming convention). >>> > However R8 is indeed equipped with Cortex A8 core, for which I believe >>> > some work has been done - see Allwinner A20 in repo - it has the same >>> > core if my memory serves right (it is even pin compatible with single >>> > core Allwinner A10 -> again Cortex A8 :) >>> > >>> > Kris >>> > >>> > On 02/11/16 01:07, Werner Thie wrote: >>> > > Hi all >>> > > >>> > > is there any interest or work going on making FreeBSD available on the >>> > > $9 CHIP from nextthing.co? >>> > > >>> > > Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash >>> > > and a slew of peripherals, the datasheet can be found on >>> > > >>> > > https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf >>> > > >>> > > Werner >>> > > _______________________________________________ >>> > > freebsd-arm@freebsd.org mailing list >>> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> > >>> > _______________________________________________ >>> > freebsd-arm@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> >>> >>> -- >>> Emmanuel Vadot >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Fri Feb 12 16:38:29 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 522E1AA659B; Fri, 12 Feb 2016 16:38:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 734A11A26; Fri, 12 Feb 2016 16:38:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 0232d430; Fri, 12 Feb 2016 17:38:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; s=mail; bh=85dVJn U4kgiMDPdQ3x7HvOAcnvQ=; b=OefTTB83oGaQe7W5EAA7eMKn/id91anVpX7GnR i0mDBauT+6P8dAsz/KBL3dlvF93RFy+vpK6+/PA+lqSOdtjSfwvbwCc8bnOhMMsf kgbI8w8fo3fdB/g39gOsQCcdn5QYIsZGs0nFTU3yfkaXnDJS/FK/7dbNFYBJ9cUS Jd898= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; q=dns; s=mail; b= sBRPvfvOJUklYcMk9iPp8+wkrlbhaYAHXXKmGx0Dfv9hOBCw1vW+L51pzXdDJccR xv/tw7Lf4X3I/DiMWnO+v7nxs63/0y3GgImt5gx2qwQRfmC4++wUZnbCGG28DgMx HsW27u7sg97Xjr3r5f2yrHmzK9FcrwPP7YWX4HTlEyo= Received: from webmail.megadrive.org (www1.blih.net [212.83.177.180]) by mail.blih.net (OpenSMTPD) with ESMTP id a245ae68; Fri, 12 Feb 2016 17:38:18 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 12 Feb 2016 17:38:18 +0100 From: Emmanuel Vadot To: Kris Cc: freebsd-arm@freebsd.org, owner-freebsd-arm@freebsd.org Subject: Re: FreeBSD on the $9 C.H.I.P Organization: Bidouilliste In-Reply-To: <56BCD629.3040209@interia.eu> References: <56BBD0B0.7040407@thieprojects.ch> <56BBD6B9.3090703@interia.eu> <20160211104534.5c18d1d32b3b55fdc458f6a5@bidouilliste.com> <56BCD629.3040209@interia.eu> Message-ID: <6b8f30ec50bc857e9edc180e6bb0a4aa@megadrive.org> X-Sender: manu@bidouilliste.com User-Agent: Roundcube Webmail/1.1.1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2016 16:38:29 -0000 Olinuxino-a10-lime works out of the box with -HEAD, this is the board I use almost everyday to work on A10. On 2016-02-11 19:42, Kris wrote: > Yep, that's what I meant. As long as we distinguish Allwinner naming > convention from what is inside we shall be fine (although Allwinner > tries hard to confuse people... as if ARM had not done enough :) ) > That being said I think support for Allwinner chips is worth being > continued. They are cheap, quite robust, quite popular, and > documentation is reasonably available (credits go to sunxi I must > admit) > So enough talking, time to go down to basement, disconnect my old > Olimex-A10-Lime and try to put FreeBSD on it. > I do expect troubles as I am not convinced it will work out of the box > (e.g. it is A10 but I can see there is A20_cpu_cfg (dual core) among > files.allwinner, which does not sound right to me...). However I also > see that some good soul put more sources in compare to 10.2 tree. > > > On 02/11/16 10:45, Emmanuel Vadot wrote: >> The R here does not stand for the RealTime profile from ARM, it's >> just one Allwinner chip line. >> >> The R8 is basically an A13 which is basically an A10 which FreeBSD >> support, so it should be easy to port FreeBSD on the R8. >> >> On Thu, 11 Feb 2016 01:32:57 +0100 >> Kris wrote: >> >>> Hi Werner, >>> Basically there is interest (I am waiting for x2 CHIP boards, they >>> are >>> due in March, but I think they will be slightly delayed). >>> Before I get boards the only reasonable thing for me to do is to get >>> as >>> much out of existing tree to see how it can be ported, but no actual >>> work. >>> >>> Please be careful - there is no such a thing like Cortex A13. A13 is >>> just a marketing name Allwinner gave to their product. And I believe >>> CHIP put Allwinner R8 on their board (normally in ARM nomenclature, >>> R=for deeply embedded devices, A=for applications, but again, it is >>> Allwinner so you can expect anything from their naming convention). >>> However R8 is indeed equipped with Cortex A8 core, for which I >>> believe >>> some work has been done - see Allwinner A20 in repo - it has the same >>> core if my memory serves right (it is even pin compatible with single >>> core Allwinner A10 -> again Cortex A8 :) >>> >>> Kris >>> >>> On 02/11/16 01:07, Werner Thie wrote: >>>> Hi all >>>> >>>> is there any interest or work going on making FreeBSD available on >>>> the >>>> $9 CHIP from nextthing.co? >>>> >>>> Basically it's a Cortex A13, 1GHz ARM V7A with 512MB RAM, NAND flash >>>> and a slew of peripherals, the datasheet can be found on >>>> >>>> https://linux-sunxi.org/images/e/eb/A13_Datasheet.pdf >>>> >>>> Werner >>>> _______________________________________________ >>>> freebsd-arm@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>>> To unsubscribe, send any mail to >>>> "freebsd-arm-unsubscribe@freebsd.org" >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to >>> "freebsd-arm-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Fri Feb 12 21:38:53 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 689E4AA68F1 for ; Fri, 12 Feb 2016 21:38:53 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22EB8F2E for ; Fri, 12 Feb 2016 21:38:53 +0000 (UTC) (envelope-from peter.garshtja@ambient-md.com) Received: by mail-wm0-x235.google.com with SMTP id g62so36346051wme.0 for ; Fri, 12 Feb 2016 13:38:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ambient-md-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=Tq3y6AjXLa9Zx3FX5ctvoz1hUjUnbpruBjMXo3Bd8+I=; b=f/wT2cXix2QJCVse/6snWrI4klBviX9OoVDqLrepdbID3qAWgcrqqdTTsXvvZyo4PW cK8NbaCq2WTS3w+wZQ1/1uczXqWdokEmkW3zSOZLsRVfyuDieNeGPO1z58ANpU/eduSV mL7l5tBr3NynJoCBZBxZoOB10FaXf/JddNYYIVoC7299iBoy5zcjSi2nf4mHJyeZNd0K yfn5/czK6KTWn/FKFh+uBttQR3u7hxRMT8TWG2s4TZZ+k09IY6/bbFUYYC1q9CUiAV2S dgSpT6DPZd2mDqt8wEcrJ8PalEMrH1GFh9UHr8YZuNxE1HrkVNFRd209UChtTXprczjH 4gtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=Tq3y6AjXLa9Zx3FX5ctvoz1hUjUnbpruBjMXo3Bd8+I=; b=lQvrFZK3uCU8K5J8jGBDg5aTD3vts1klW0e/LAJASeM6PsprM0ecQuEDH15Oy7URpK u3E11VPpHsrlZMIdrtfcCzfi7Xv+3sy937unJDU+10vfo1xB2GcwmqouzMfaNO37BWtn heXw7emBzeY800IWj117GQsCUEewvvS3ZNVYOsTPa1S9b5xbM75Onb8cz4RVRV8DGHx7 WJ0P2aCfkknZUJJFt3AsWVLEjrZluj87A9mQ5bWsPXU3Oi22QeqbeFu78GygZ4Gi2alz NrdnxOIsr269h7Qt8rlBHNzYR7DUucdqB9FCC31cwMmRPevpELdypx8hcBM59KgCbhMk ZhZg== X-Gm-Message-State: AG10YOQh2QwTDDGJ2REE+23YveGiWuNW5oI3wwLR9TDrLMIL6wRFVOMGTNTp8xj+5uscw3ZITrJ3N8hZlk8DjA== MIME-Version: 1.0 X-Received: by 10.28.184.78 with SMTP id i75mr47725wmf.22.1455313131051; Fri, 12 Feb 2016 13:38:51 -0800 (PST) Received: by 10.27.0.215 with HTTP; Fri, 12 Feb 2016 13:38:51 -0800 (PST) X-Originating-IP: [207.96.192.66] Date: Fri, 12 Feb 2016 16:38:51 -0500 Message-ID: Subject: arm repositories From: peter garshtja To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2016 21:38:53 -0000 Hi, I was able to install packages from official freebsd repositories. I believe that was implemented recently, That is fantastic. Great work. Most applications that i installed works, just pftop crashes. Thanks, Peter From owner-freebsd-arm@freebsd.org Sat Feb 13 03:58:10 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36AC5AA5AA3; Sat, 13 Feb 2016 03:58:10 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05AC81CF3; Sat, 13 Feb 2016 03:58:09 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-io0-x234.google.com with SMTP id l127so110741344iof.3; Fri, 12 Feb 2016 19:58:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:content-transfer-encoding:message-id:date :subject:from:in-reply-to:references:to:cc; bh=Xp55/YuHn5rPNs5/9VbDhKFAh+fvTyFLgu2rKstmg2U=; b=Szwgu/DCHIdoILcZO8a85wOtTGgndY3J4YFxLY0elVoa0IuTvCJN3cAgL4sjw66SlM 8EycPnbHfSc7X7k1WIkBRPBwjKMRTB3/zOFL/4BlbW+IRC3x0gRZS3gzL7qztzUWT8v3 ZrNG7HNsRq+Hy+jRw6q8xHMDaYwrG4BwwSzItmC1rMt9yUFnMkWbLF7QGKo6KUMMqf0z nC65PieLV5jrZbop9NAmONQRuzUFD3FXyUzLxQ9Z53HDVlsg4FaWytDXFa135KZ2dEzY DkCRLNBT0QCYsUJsHQd6/rPrXSQN1OviuiUaH0m198Gpvd9hj3nEUrNejFBsL1Jv41dP v/sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version :content-transfer-encoding:message-id:date:subject:from:in-reply-to :references:to:cc; bh=Xp55/YuHn5rPNs5/9VbDhKFAh+fvTyFLgu2rKstmg2U=; b=aPfheEiNSCzHUmjg2niPlrhMaAUAvW2+s+gD1mv98qmPXg7YzSvb08c+8sFfEjtg1u 0XAYcImzn0RdMU74Tfn4nhHLpBt+ukMslBzTUw7RMD6U4znJKa0CP49+ZsirpXLj/+aa 7O1aDg50MplwSdUuVE9CIdUB/EzoeJftSCEwd30R7Bs5R/VSiw2n2j9phwB+YQ7yk/HO wx5W8KjUDGlI3ixVFbgKwsPD6T2zTzxK2WrLYgeXDpfheYVJLphdKWxB5IC6EJKlhXc0 ryw0/Q2seYinAVgXsVJFhyIwSgAThYwF5YN7rQ4B2zGapuZEfs3fsXKYeXDfPi5OWOs+ QMPA== X-Gm-Message-State: AG10YOQCBN9J/Zy78AN4Amf8gD/Kf+vI49P7umawswJUT5tHx9KO3vqz4AcqbRk7QMdUIA== X-Received: by 10.107.152.142 with SMTP id a136mr6721597ioe.84.1455335889108; Fri, 12 Feb 2016 19:58:09 -0800 (PST) Received: from [127.0.0.1] ([209.52.88.27]) by smtp.gmail.com with ESMTPSA id v68sm7511666ioi.23.2016.02.12.19.58.06 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 12 Feb 2016 19:58:08 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20160213035806.4403283.12124.2928@gmail.com> Date: Fri, 12 Feb 2016 19:58:06 -0800 Subject: Re: MMC/SDIO stack under CAM From: Russell Haley In-Reply-To: References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> To: Ilya Bakulin , "Lundberg, Johannes" Cc: Adrian Chadd , freebsd-hackers@freebsd.org, Alexander Motin , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2016 03:58:10 -0000 Hi Ilya, so does that mean I can take a linux driver for an SDIO wifi card = and build it using a reference to your library and everything should "just = work"? Thanks, Russ Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A010=C2=A0smartphone=C2=A0on=C2= =A0the=C2=A0Koodo=C2=A0network. =C2=A0 Original Message =C2=A0 From: Ilya Bakulin Sent: Thursday, February 11, 2016 10:43 AM To: Lundberg, Johannes Cc: Adrian Chadd; freebsd-hackers@freebsd.org; Alexander Motin; freebsd-arm= @freebsd.org Subject: Re: MMC/SDIO stack under CAM Hi Johannes, My work doesn't include writing drivers for SDHCI controllers. But if the c= ontroller on your new boards is supported by FreeBSD, then you can really t= est the new stack! Especially if the controller driver for your board is ba= sed on dev/sdhci, adapting it to work with the new stack is trivial. For ex= ample, iMX6 SDHCI needed only a couple of lines: https://github.com/kibab/f= reebsd/commit/df6d8d534740aa3633979da0a9d0ca00b60db0e9 Please let me know when you get the new boards and we will figure out what = we need. On February 11, 2016 3:17:22 AM GMT+01:00, "Lundberg, Johannes" wrote: >Hi Ilya > >This is great! > >I've got a Tronsmart ARA X5 and just purchased a few UP > >boards >and it would be really nice if I could utilize the onboard eMMC. These >are >all Intel Cherrytrail platforms. > >Please let me know if there's anything (testing?) I can do to speed up >the >process. > > > >-- >Name: Johannes Lundberg >Position: Mirama project leader >Phone: +1-408-636-2161 >Skype: brilliantjohannes >Online: LinkedIn >Facebook > Reddit > Twitter > GitHub > >GitLab >Company: Mirama Brilliantservice US > Brilliantservice JP > > >On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: > >> So, more than one year has passed, and I'd like to resurrect this >work >> and move forward. >> >> I have uploaded a new diff and created a completely new revision to >> track the development: https://reviews.freebsd.org/D4761 >> >> What it is able to do now: >> >> * Read/write on SD/SDHC/MMC cards! >> * Detect SDIO cards and create devices that correspond to SDIO >functions >> >> This all works only on BeagleBone currently, because some changes >need >> to be done in each SDHCI-compliant driver to make it interact with >CAM. >> I have purchased a Wandboard Quad that has an integrated SDIO WiFi >chip, >> so I hope to tweak its SDHCI driver as well. >> >> I haven't profiled the stack because: >> * Now we have only SD/MMC cards that are slow anyway; >> * I don't know how to do it in FreeBSD :-) >> >> Please review this diff and tell what you think! >> >> On 01/03/14 18:05, Adrian Chadd wrote: >> > On 1 March 2014 08:46, Ilya Bakulin wrote: >> >> Hi Adrian, >> >> >> >> On 24.02.14, 16:59, Adrian Chadd wrote: >> >>> hi, >> >>> >> >>> Let me just reiterate some .. well, experience doing this stuff >at QCA. >> >>> >> >>> You really, absolutely don't want too much overhead in the >MMC/SDIO >> >>> path between whatever is issuing things and the network driver. >> >>> >> >>> There was significant performance work done at QCA on a local >MMC/SDIO >> >>> driver and bus to get extremely low latency and CPU utilisation >when >> >>> pushing around small transactions. The current CAM locking model >is >> >>> not geared towards getting to high transaction rates. >> >> So here you mean some work done on Linux MMC/SDIO stack by QCA >> >> which made it far better than current Linux MMC stack in terms of >> >> high SDIO I/O rates? >> > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at >small >> > transactions to sustain the wifi speeds customers required. >> > >> >>> You may think this is a very architecturally pretty solution and >it >> >>> indeed may be. But if it doesn't perform as well as the existing >local >> >>> hacks that vendors have done, no company deploying this hardware >is >> >>> going to want to use it. They'll end up realising there's this >massive >> >>> CAM storage layer in between and either have to sit down to rip >it up >> >>> and replace it with something lightweight, or they'll say "screw >it" >> >>> and go back to the vendor supplied hacked up Linux solution. >> >> I think that if the "architecturally pretty solution" behaves >worse than >> >> some ugly hacks, then it may be not so pretty or the architecture >is >> >> just broken >> >> by design. >> >> >> >>> So I highly recommend you profile things - and profile things >with >> >>> lots of small transactions. If the CAM overhead is more than a >tiny, >> >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. >:-) >> >> I don't really know what to compare with. For MMC/SD cards it is >pretty >> >> obvious, but then these cards will be likely the bottleneck, not >the >> stack. >> >> And the only goal would be to not make the stack slower than it is >now. >> >> But, as ATA devices are much faster than MMC/SD, I don't think >this will >> >> be a problem. >> >> >> >> For SDIO things are different. But we don't have any drivers >(yet), >> except >> >> mv_sdiowl that I'm writing, to test on. So I have to bring the >SDIO >> >> stack on CAM, >> >> than bring mv_sdiowl to the state when it can actually transmit >the >> >> data, and then >> >> compare performance with the vendor-supplied Linux driver. >> >> We'll see then if there is a room for improvement... >> > That sounds like a plan. >> > >> > Just note that although storage looks like it's doing much more >> > throughput, the IO size also matters. As I said above, it's not >> > uncommon to have > 1000 receive frames a second on 802.11n; and >that >> > can peak much higher than that. That's not the kind of IO rate you >see >> > on SD cards. :-) >> > >> > >> > >> > -a >> > _______________________________________________ >> > freebsd-hackers@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> > To unsubscribe, send any mail to " >> freebsd-hackers-unsubscribe@freebsd.org" >> > >> >> >> -- >> Regards, >> Ilya Bakulin >> >> >> > >--=20 >=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- >=E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 >=E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 >=E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 >--- >CONFIDENTIALITY NOTE: The information in this email is confidential >and intended solely for the addressee. >Disclosure, copying, distribution or any other action of use of this >email by person other than intended recipient, is prohibited. >If you are not the intended recipient and have received this email in >error, please destroy the original message. --=20 =D0=9F=D1=80=D0=BE=D1=81=D1=82=D0=B8=D1=82=D0=B5 =D0=B7=D0=B0 =D0=BA=D1=80= =D0=B0=D1=82=D0=BA=D0=BE=D1=81=D1=82=D1=8C, =D1=81=D0=BE=D0=B7=D0=B4=D0=B0= =D0=BD=D0=BE =D0=B2 K-9 Mail. _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Feb 13 04:16:37 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FC22AA6384; Sat, 13 Feb 2016 04:16:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA7841607; Sat, 13 Feb 2016 04:16:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x236.google.com with SMTP id 9so111844146iom.1; Fri, 12 Feb 2016 20:16:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=vcOrlLoAn6QFPzuuCllbvcj58RaWF8FD+s/5aCGCLpk=; b=X3mgSkbNi2QGVqhg1bgKVbi4p7h3Cj12YlExL/VdqbEtJlp+Q6ML3PoUlF7QTVHPtg TJx7wwsnS+UmOz9NAQH7fFD40f1UgGwot5tfCYxQvPyPKvOFX7+z6btaWiMy7niR2vGb 2jvoFN+uAafbWX5SysvmbgfF0teSfIKPDGck1kW5O6J1EZMMqEgRnee6FU6WAEszz91V /dq6EZrW6vg24Wh22MmJCRe3Vez4jkjWU+7O5EmPN1PA4CMRY53xucFgn2dUrTSphVAj A8bCiP9zwDpA7lFqTt5s/zE1PnvTCBAfY1ojWOaRoMl5h2bc1JFeMXZTYaou14DzYFQh ymvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vcOrlLoAn6QFPzuuCllbvcj58RaWF8FD+s/5aCGCLpk=; b=DtNaTZn1m40ThCUth8CYgbf7DIgO/ABTWHgbHSGT4LUBNRhkUILpCqIJi9oWg5JFsd mzJOhVhnohVcQFUUHTosHvC9sxiocIKW4kj/QpAFfHeFsY1GnUDZYJKAatKQqIb/xUcv FCsAngvVsQfGpx3MbJytcU35sBTcnCWLqDNApHQnOuW4nyJ+A51PwBrPGR+sCKO8pmR0 upXLw66wVjU7Eg166tvCyKAoKgNvLaQ16BnuZJnoahuESFtES9qgTp1/X7yc9YEYrwI6 A8uuO+rhqETp06uyfbu8OBYJvJTFrMJO8TCRtdmOGLvd6ISOecvC3yuCVldzc1pIDlYE UMmQ== X-Gm-Message-State: AG10YOTpANgNHh7xnsy6fhoDZWh83Se/m4fdopPafGmMd1kXtT/qiBasMcc2UtonrYlalcJMMfCHDcgkIpkUcg== MIME-Version: 1.0 X-Received: by 10.107.162.146 with SMTP id l140mr6256204ioe.123.1455336996190; Fri, 12 Feb 2016 20:16:36 -0800 (PST) Received: by 10.36.14.19 with HTTP; Fri, 12 Feb 2016 20:16:36 -0800 (PST) In-Reply-To: <20160213035806.4403283.12124.2928@gmail.com> References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> <20160213035806.4403283.12124.2928@gmail.com> Date: Fri, 12 Feb 2016 20:16:36 -0800 Message-ID: Subject: Re: MMC/SDIO stack under CAM From: Adrian Chadd To: Russell Haley Cc: Ilya Bakulin , "Lundberg, Johannes" , "freebsd-hackers@freebsd.org" , Alexander Motin , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2016 04:16:37 -0000 On 12 February 2016 at 19:58, Russell Haley wrote: > Hi Ilya, so does that mean I can take a linux driver for an SDIO wifi car= d and build it using a reference to your library and everything should "jus= t work"? nope. there's a lot more to it than that. But it's a good start - getting the driver up and doing IO to the card is a big step. -a > Thanks, > Russ > > Sent from my BlackBerry 10 smartphone on the Koodo network. > Original Message > From: Ilya Bakulin > Sent: Thursday, February 11, 2016 10:43 AM > To: Lundberg, Johannes > Cc: Adrian Chadd; freebsd-hackers@freebsd.org; Alexander Motin; freebsd-a= rm@freebsd.org > Subject: Re: MMC/SDIO stack under CAM > > Hi Johannes, > > My work doesn't include writing drivers for SDHCI controllers. But if the= controller on your new boards is supported by FreeBSD, then you can really= test the new stack! Especially if the controller driver for your board is = based on dev/sdhci, adapting it to work with the new stack is trivial. For = example, iMX6 SDHCI needed only a couple of lines: https://github.com/kibab= /freebsd/commit/df6d8d534740aa3633979da0a9d0ca00b60db0e9 > > Please let me know when you get the new boards and we will figure out wha= t we need. > > On February 11, 2016 3:17:22 AM GMT+01:00, "Lundberg, Johannes" wrote: >>Hi Ilya >> >>This is great! >> >>I've got a Tronsmart ARA X5 and just purchased a few UP >> >>boards >>and it would be really nice if I could utilize the onboard eMMC. These >>are >>all Intel Cherrytrail platforms. >> >>Please let me know if there's anything (testing?) I can do to speed up >>the >>process. >> >> >> >>-- >>Name: Johannes Lundberg >>Position: Mirama project leader >>Phone: +1-408-636-2161 >>Skype: brilliantjohannes >>Online: LinkedIn >>Facebook >> Reddit >> Twitter >> GitHub >> >>GitLab >>Company: Mirama Brilliantservice US >> Brilliantservice JP >> >> >>On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: >> >>> So, more than one year has passed, and I'd like to resurrect this >>work >>> and move forward. >>> >>> I have uploaded a new diff and created a completely new revision to >>> track the development: https://reviews.freebsd.org/D4761 >>> >>> What it is able to do now: >>> >>> * Read/write on SD/SDHC/MMC cards! >>> * Detect SDIO cards and create devices that correspond to SDIO >>functions >>> >>> This all works only on BeagleBone currently, because some changes >>need >>> to be done in each SDHCI-compliant driver to make it interact with >>CAM. >>> I have purchased a Wandboard Quad that has an integrated SDIO WiFi >>chip, >>> so I hope to tweak its SDHCI driver as well. >>> >>> I haven't profiled the stack because: >>> * Now we have only SD/MMC cards that are slow anyway; >>> * I don't know how to do it in FreeBSD :-) >>> >>> Please review this diff and tell what you think! >>> >>> On 01/03/14 18:05, Adrian Chadd wrote: >>> > On 1 March 2014 08:46, Ilya Bakulin wrote: >>> >> Hi Adrian, >>> >> >>> >> On 24.02.14, 16:59, Adrian Chadd wrote: >>> >>> hi, >>> >>> >>> >>> Let me just reiterate some .. well, experience doing this stuff >>at QCA. >>> >>> >>> >>> You really, absolutely don't want too much overhead in the >>MMC/SDIO >>> >>> path between whatever is issuing things and the network driver. >>> >>> >>> >>> There was significant performance work done at QCA on a local >>MMC/SDIO >>> >>> driver and bus to get extremely low latency and CPU utilisation >>when >>> >>> pushing around small transactions. The current CAM locking model >>is >>> >>> not geared towards getting to high transaction rates. >>> >> So here you mean some work done on Linux MMC/SDIO stack by QCA >>> >> which made it far better than current Linux MMC stack in terms of >>> >> high SDIO I/O rates? >>> > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at >>small >>> > transactions to sustain the wifi speeds customers required. >>> > >>> >>> You may think this is a very architecturally pretty solution and >>it >>> >>> indeed may be. But if it doesn't perform as well as the existing >>local >>> >>> hacks that vendors have done, no company deploying this hardware >>is >>> >>> going to want to use it. They'll end up realising there's this >>massive >>> >>> CAM storage layer in between and either have to sit down to rip >>it up >>> >>> and replace it with something lightweight, or they'll say "screw >>it" >>> >>> and go back to the vendor supplied hacked up Linux solution. >>> >> I think that if the "architecturally pretty solution" behaves >>worse than >>> >> some ugly hacks, then it may be not so pretty or the architecture >>is >>> >> just broken >>> >> by design. >>> >> >>> >>> So I highly recommend you profile things - and profile things >>with >>> >>> lots of small transactions. If the CAM overhead is more than a >>tiny, >>> >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. >>:-) >>> >> I don't really know what to compare with. For MMC/SD cards it is >>pretty >>> >> obvious, but then these cards will be likely the bottleneck, not >>the >>> stack. >>> >> And the only goal would be to not make the stack slower than it is >>now. >>> >> But, as ATA devices are much faster than MMC/SD, I don't think >>this will >>> >> be a problem. >>> >> >>> >> For SDIO things are different. But we don't have any drivers >>(yet), >>> except >>> >> mv_sdiowl that I'm writing, to test on. So I have to bring the >>SDIO >>> >> stack on CAM, >>> >> than bring mv_sdiowl to the state when it can actually transmit >>the >>> >> data, and then >>> >> compare performance with the vendor-supplied Linux driver. >>> >> We'll see then if there is a room for improvement... >>> > That sounds like a plan. >>> > >>> > Just note that although storage looks like it's doing much more >>> > throughput, the IO size also matters. As I said above, it's not >>> > uncommon to have > 1000 receive frames a second on 802.11n; and >>that >>> > can peak much higher than that. That's not the kind of IO rate you >>see >>> > on SD cards. :-) >>> > >>> > >>> > >>> > -a >>> > _______________________________________________ >>> > freebsd-hackers@freebsd.org mailing list >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> > To unsubscribe, send any mail to " >>> freebsd-hackers-unsubscribe@freebsd.org" >>> > >>> >>> >>> -- >>> Regards, >>> Ilya Bakulin >>> >>> >>> >> >>-- >>=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- >>=E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 >>=E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 >>=E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 >>--- >>CONFIDENTIALITY NOTE: The information in this email is confidential >>and intended solely for the addressee. >>Disclosure, copying, distribution or any other action of use of this >>email by person other than intended recipient, is prohibited. >>If you are not the intended recipient and have received this email in >>error, please destroy the original message. > > -- > =D0=9F=D1=80=D0=BE=D1=81=D1=82=D0=B8=D1=82=D0=B5 =D0=B7=D0=B0 =D0=BA=D1= =80=D0=B0=D1=82=D0=BA=D0=BE=D1=81=D1=82=D1=8C, =D1=81=D0=BE=D0=B7=D0=B4=D0= =B0=D0=BD=D0=BE =D0=B2 K-9 Mail. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Feb 13 06:48:54 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 331EFAA7103; Sat, 13 Feb 2016 06:48:54 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD955153B; Sat, 13 Feb 2016 06:48:53 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x22b.google.com with SMTP id e6so75786768vkh.2; Fri, 12 Feb 2016 22:48:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=m3AzWaJZdo4EeQPmjIX7g0XTjqjARbpfhMZOkTZLWWI=; b=HV0IWoy6lWkcB1VcSEy+3KX/Vx5Q5hNudo+L+3gHhFeEA0d7tMrrFe1j/TZ7JI0Nf2 p/rbD7uvs0ACZh+I2ZYZ8Ip79pvILAgg5Sglga4cqmL2hqcgumdK1PedC3JIeTj+fVGr o6evyaRQlo3USZKEKV3CH4getv3VrFBhivA8OImUu8HLvy7yyQ5+pEuJkExZhL4cp8SH hnzZ+gnFq1t2/59ZO+gUcNfVAbKIxLb8ysfOBTv8xEfIdEtd/oPp4Ub5oQzfjH+tkOXF zRq9HbyHYuqdevL5gH1SLsoabA0EpNKUewStqsGLEThGlZoM2UKyz8wLNeJ49CwQddVI /LAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=m3AzWaJZdo4EeQPmjIX7g0XTjqjARbpfhMZOkTZLWWI=; b=h+Evb/AceOELJxDMOI/o3Qi03D2Y35EvSVK9px2jRMz6EDZ3JedCJQqON/cpgpGir0 ilKmv79ygrBqFc88c4EB69u3fus8xXO/Y++wnIfg+90xUbc5/rl8uqxlM4X2chURww/J n1UZkitR9yuIoRdJXce3LULtokWcTXk3oLkbO9AmJXF1d5CbTrPlQnL3teSLXxJhfWt6 Oc3Yhyq1g5R8O1NCgnNnxoqZMho/2ZndOggcDPcMVy59w4Sg7G7poTIAYJ+WEGcrT2a6 d9OxyhSSfFfwJ/ygicVp69KEN9Y41vyj81EAM0XTMpQ6Q8Grv3rHOKfEPPcfUexipEsI JAKQ== X-Gm-Message-State: AG10YOTrL2blwKkWw7OVEiJUkc8IvZoZc1oqcY5xpvrqx56smPgYQC+YnEuhvDign786xQ87usIO6NKMuhnwzA== MIME-Version: 1.0 X-Received: by 10.31.8.72 with SMTP id 69mr4669253vki.145.1455346132868; Fri, 12 Feb 2016 22:48:52 -0800 (PST) Received: by 10.31.54.13 with HTTP; Fri, 12 Feb 2016 22:48:52 -0800 (PST) In-Reply-To: References: <20140216111153.GA74858@olymp.kibab.com> <5C2CF572-360D-4CA0-81C7-18A5C455AED5@bsdimp.com> <20140224142642.GA32538@olymp.kibab.com> <53120EE8.1080600@bakulin.de> <5688F015.4090002@bakulin.de> <20160213035806.4403283.12124.2928@gmail.com> Date: Fri, 12 Feb 2016 22:48:52 -0800 Message-ID: Subject: Re: MMC/SDIO stack under CAM From: Russell Haley To: Adrian Chadd Cc: Ilya Bakulin , "Lundberg, Johannes" , "freebsd-hackers@freebsd.org" , Alexander Motin , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2016 06:48:54 -0000 On Fri, Feb 12, 2016 at 8:16 PM, Adrian Chadd wrot= e: > On 12 February 2016 at 19:58, Russell Haley wrote: >> Hi Ilya, so does that mean I can take a linux driver for an SDIO wifi ca= rd and build it using a reference to your library and everything should "ju= st work"? > > nope. there's a lot more to it than that. But it's a good start - > getting the driver up and doing IO to the card is a big step. > > > > -a > Okay, thanks. But if I include his CAM driver and then use the patch below for IMX6 on my Hummingboard, I would be able to test the driver? Will a simple kldstat be enough to verify I am using his driver or is there something more direct in dtrace? Thanks, Russ >> Thanks, >> Russ >> >> Sent from my BlackBerry 10 smartphone on the Koodo network. >> Original Message >> From: Ilya Bakulin >> Sent: Thursday, February 11, 2016 10:43 AM >> To: Lundberg, Johannes >> Cc: Adrian Chadd; freebsd-hackers@freebsd.org; Alexander Motin; freebsd-= arm@freebsd.org >> Subject: Re: MMC/SDIO stack under CAM >> >> Hi Johannes, >> >> My work doesn't include writing drivers for SDHCI controllers. But if th= e controller on your new boards is supported by FreeBSD, then you can reall= y test the new stack! Especially if the controller driver for your board is= based on dev/sdhci, adapting it to work with the new stack is trivial. For= example, iMX6 SDHCI needed only a couple of lines: https://github.com/kiba= b/freebsd/commit/df6d8d534740aa3633979da0a9d0ca00b60db0e9 >> >> Please let me know when you get the new boards and we will figure out wh= at we need. >> >> On February 11, 2016 3:17:22 AM GMT+01:00, "Lundberg, Johannes" wrote: >>>Hi Ilya >>> >>>This is great! >>> >>>I've got a Tronsmart ARA X5 and just purchased a few UP >>> >>>boards >>>and it would be really nice if I could utilize the onboard eMMC. These >>>are >>>all Intel Cherrytrail platforms. >>> >>>Please let me know if there's anything (testing?) I can do to speed up >>>the >>>process. >>> >>> >>> >>>-- >>>Name: Johannes Lundberg >>>Position: Mirama project leader >>>Phone: +1-408-636-2161 >>>Skype: brilliantjohannes >>>Online: LinkedIn >>>Facebook >>> Reddit >>> Twitter >>> GitHub >>> >>>GitLab >>>Company: Mirama Brilliantservice US >>> Brilliantservice JP >>> >>> >>>On Sun, Jan 3, 2016 at 1:55 AM, Ilya Bakulin wrote: >>> >>>> So, more than one year has passed, and I'd like to resurrect this >>>work >>>> and move forward. >>>> >>>> I have uploaded a new diff and created a completely new revision to >>>> track the development: https://reviews.freebsd.org/D4761 >>>> >>>> What it is able to do now: >>>> >>>> * Read/write on SD/SDHC/MMC cards! >>>> * Detect SDIO cards and create devices that correspond to SDIO >>>functions >>>> >>>> This all works only on BeagleBone currently, because some changes >>>need >>>> to be done in each SDHCI-compliant driver to make it interact with >>>CAM. >>>> I have purchased a Wandboard Quad that has an integrated SDIO WiFi >>>chip, >>>> so I hope to tweak its SDHCI driver as well. >>>> >>>> I haven't profiled the stack because: >>>> * Now we have only SD/MMC cards that are slow anyway; >>>> * I don't know how to do it in FreeBSD :-) >>>> >>>> Please review this diff and tell what you think! >>>> >>>> On 01/03/14 18:05, Adrian Chadd wrote: >>>> > On 1 March 2014 08:46, Ilya Bakulin wrote: >>>> >> Hi Adrian, >>>> >> >>>> >> On 24.02.14, 16:59, Adrian Chadd wrote: >>>> >>> hi, >>>> >>> >>>> >>> Let me just reiterate some .. well, experience doing this stuff >>>at QCA. >>>> >>> >>>> >>> You really, absolutely don't want too much overhead in the >>>MMC/SDIO >>>> >>> path between whatever is issuing things and the network driver. >>>> >>> >>>> >>> There was significant performance work done at QCA on a local >>>MMC/SDIO >>>> >>> driver and bus to get extremely low latency and CPU utilisation >>>when >>>> >>> pushing around small transactions. The current CAM locking model >>>is >>>> >>> not geared towards getting to high transaction rates. >>>> >> So here you mean some work done on Linux MMC/SDIO stack by QCA >>>> >> which made it far better than current Linux MMC stack in terms of >>>> >> high SDIO I/O rates? >>>> > Yup. The stock MMC stack/driver in Linux wasn't "fast" enough at >>>small >>>> > transactions to sustain the wifi speeds customers required. >>>> > >>>> >>> You may think this is a very architecturally pretty solution and >>>it >>>> >>> indeed may be. But if it doesn't perform as well as the existing >>>local >>>> >>> hacks that vendors have done, no company deploying this hardware >>>is >>>> >>> going to want to use it. They'll end up realising there's this >>>massive >>>> >>> CAM storage layer in between and either have to sit down to rip >>>it up >>>> >>> and replace it with something lightweight, or they'll say "screw >>>it" >>>> >>> and go back to the vendor supplied hacked up Linux solution. >>>> >> I think that if the "architecturally pretty solution" behaves >>>worse than >>>> >> some ugly hacks, then it may be not so pretty or the architecture >>>is >>>> >> just broken >>>> >> by design. >>>> >> >>>> >>> So I highly recommend you profile things - and profile things >>>with >>>> >>> lots of small transactions. If the CAM overhead is more than a >>>tiny, >>>> >>> tiny fraction of CPU at 25,000 pps, your solution won't scale. >>>:-) >>>> >> I don't really know what to compare with. For MMC/SD cards it is >>>pretty >>>> >> obvious, but then these cards will be likely the bottleneck, not >>>the >>>> stack. >>>> >> And the only goal would be to not make the stack slower than it is >>>now. >>>> >> But, as ATA devices are much faster than MMC/SD, I don't think >>>this will >>>> >> be a problem. >>>> >> >>>> >> For SDIO things are different. But we don't have any drivers >>>(yet), >>>> except >>>> >> mv_sdiowl that I'm writing, to test on. So I have to bring the >>>SDIO >>>> >> stack on CAM, >>>> >> than bring mv_sdiowl to the state when it can actually transmit >>>the >>>> >> data, and then >>>> >> compare performance with the vendor-supplied Linux driver. >>>> >> We'll see then if there is a room for improvement... >>>> > That sounds like a plan. >>>> > >>>> > Just note that although storage looks like it's doing much more >>>> > throughput, the IO size also matters. As I said above, it's not >>>> > uncommon to have > 1000 receive frames a second on 802.11n; and >>>that >>>> > can peak much higher than that. That's not the kind of IO rate you >>>see >>>> > on SD cards. :-) >>>> > >>>> > >>>> > >>>> > -a >>>> > _______________________________________________ >>>> > freebsd-hackers@freebsd.org mailing list >>>> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> > To unsubscribe, send any mail to " >>>> freebsd-hackers-unsubscribe@freebsd.org" >>>> > >>>> >>>> >>>> -- >>>> Regards, >>>> Ilya Bakulin >>>> >>>> >>>> >>> >>>-- >>>=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- >>>=E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 >>>=E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 >>>=E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 >>>--- >>>CONFIDENTIALITY NOTE: The information in this email is confidential >>>and intended solely for the addressee. >>>Disclosure, copying, distribution or any other action of use of this >>>email by person other than intended recipient, is prohibited. >>>If you are not the intended recipient and have received this email in >>>error, please destroy the original message. >> >> -- >> =D0=9F=D1=80=D0=BE=D1=81=D1=82=D0=B8=D1=82=D0=B5 =D0=B7=D0=B0 =D0=BA=D1= =80=D0=B0=D1=82=D0=BA=D0=BE=D1=81=D1=82=D1=8C, =D1=81=D0=BE=D0=B7=D0=B4=D0= =B0=D0=BD=D0=BE =D0=B2 K-9 Mail. >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Feb 13 12:56:58 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAC54AA6DEF; Sat, 13 Feb 2016 12:56:58 +0000 (UTC) (envelope-from freebsd@mikej.com) Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com [216.26.158.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.paymentallianceintl.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E3751486; Sat, 13 Feb 2016 12:56:58 +0000 (UTC) (envelope-from freebsd@mikej.com) Received: from firewall.mikej.com (162-230-214-65.lightspeed.lsvlky.sbcglobal.net [162.230.214.65]) by mx2.paymentallianceintl.com (8.15.1/8.15.1) with ESMTPS id u1DCuth5009088 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 13 Feb 2016 07:56:56 -0500 (EST) (envelope-from freebsd@mikej.com) X-Authentication-Warning: mx2.paymentallianceintl.com: Host 162-230-214-65.lightspeed.lsvlky.sbcglobal.net [162.230.214.65] claimed to be firewall.mikej.com Received: from mail.mikej.com (firewall.mikej.com [192.168.6.63]) by firewall.mikej.com (8.15.2/8.15.2) with ESMTP id u1DCuWoG059294; Sat, 13 Feb 2016 07:56:33 -0500 (EST) (envelope-from freebsd@mikej.com) DMARC-Filter: OpenDMARC Filter v1.3.1 firewall.mikej.com u1DCuWoG059294 Authentication-Results: mail.mikej.com; dmarc=none header.from=mikej.com DKIM-Filter: OpenDKIM Filter v2.10.3 firewall.mikej.com u1DCuWoG059294 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mikej.com; s=mail; t=1455368193; bh=wlhxzHjNy//ydaNJzXq+Grx0641Yha14o8L5Dp9lEWk=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=E5zh8BKnHafaQ60tHKNOrPWdwAQZtigfIKsuC1metJogCwwmDD+R4EhlYf6XTTWBP gL0E7gXdyM4A4wankSWO06sw849IVVM/0WgaXYkGgTxP856aRhZbuCVfDJcIxk2Q5m 1Qf/GuoStgJ/ejwbsG6cbOVsQ8DXNO5oivkvlb2N+2cekxLEbux98XEwkzCMwMkhiV fmRmuzAUKnjSdBOgA2g5W3wQ6lHPIjHrtPskePxqgT4uEj6W2kBn9PqPwBf1b1q+71 cdGaiv2qa93EUAOQ1/EWQ5OGCkXYJEukKKOn74uZtCK6TEFoIIQUqCSS4809pcWUvE 8YXyMF28ugqGA== X-Authentication-Warning: firewall.mikej.com: Host firewall.mikej.com [192.168.6.63] claimed to be mail.mikej.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 13 Feb 2016 07:56:32 -0500 From: Michael Jung To: George Neville-Neil Cc: freebsd-arm@freebsd.org, owner-freebsd-arm@freebsd.org Subject: Re: Pine 64 support In-Reply-To: <0116C790-553F-433B-BDFD-55CEEB5D7E12@neville-neil.com> References: <29c61e45e2755017f4b3ebabfeaae268@192.168.6.63> <0116C790-553F-433B-BDFD-55CEEB5D7E12@neville-neil.com> Message-ID: <89a79a3b0cd08f26b2473cc75aa542da@mail.mikej.com> X-Sender: freebsd@mikej.com User-Agent: Roundcube Webmail/1.1.4 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2016 12:56:59 -0000 On 2016-02-12 06:32, George Neville-Neil wrote: >> Are there any plans in supporting the Allwiner A64 SOC? >> >> http://wiki.pine64.org/index.php/Main_Page >> > > I'm waiting on one, as I am sure are others. > > Best, > George > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" I'm waiting on mine also. I am *NOT* a kernel person, what is the likely hood of HDMI and H264/H265 hardware support in FreeBSD or is it simply too early to say? I ordered mine just for something to play with. I know there are other OS options... but I will a SD card just for FreeBSD. I did have some FreeBSD servers on 4 Proc Alpha 4100's way back when. And it's fun to tinker with other platforms. Heck I still have a S-100 Northstar that works... although not running FreeBSD ;-) Thanks! --mikej