From owner-freebsd-arch@FreeBSD.ORG Sun Oct 16 01:48:27 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4325106566B for ; Sun, 16 Oct 2011 01:48:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f177.google.com (mail-yx0-f177.google.com [209.85.213.177]) by mx1.freebsd.org (Postfix) with ESMTP id A9D868FC0C for ; Sun, 16 Oct 2011 01:48:27 +0000 (UTC) Received: by mail-yx0-f177.google.com with SMTP id 36so2552719yxk.8 for ; Sat, 15 Oct 2011 18:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=mNuiRtPHawLPNvk73unSZIi990alq8tObq9CXM0Gfeg=; b=YBiwNBoi3hDBBKAoBtathTXpqGK4XvyjoXJ/sWhRyyFtYAGrurq8cYq4OJS4O/NVwl B8RVZ3Ft79X38Nx9XD4BwNfczuC1clpIQJ5Rr3TkekmF87RO6LwVWXz0fJnJvZHIbXgV faSn09qR2Pvi0C1sztdrz4mG3OFs0fp0PnuwU= MIME-Version: 1.0 Received: by 10.236.175.195 with SMTP id z43mr19630812yhl.66.1318729707321; Sat, 15 Oct 2011 18:48:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.95.147 with HTTP; Sat, 15 Oct 2011 18:48:27 -0700 (PDT) Date: Sun, 16 Oct 2011 09:48:27 +0800 X-Google-Sender-Auth: 11XRBFbn1E0UC797-CQNBVkv_ag Message-ID: From: Adrian Chadd To: freebsd-arch@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: newbus bus access routines and bus_space_barrier() X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2011 01:48:28 -0000 Hi all, I'm not clued up on the way of the bus API, so please excuse the newbie questions. Nathan and I found that ath(4) wasn't working for a user because of a missing bus barrier. Ath trips it up because it does lots of loops of register reads/writes through the bus stream API rather than the normal bus API. It does this because it handles the register value swapping in hardware rather than in software. The correct fix is to teach ath(4) to use bus_space_barrier() calls when doing stream calls, which I can do, but the newbus documentation points out that both normal and stream bus access doesn't enforce ordering, and barrier calls are needed. But I don't see lots of bus_space_barrier() calls everywhere. Why's that? Thanks, Adrian From owner-freebsd-arch@FreeBSD.ORG Sun Oct 16 03:45:41 2011 Return-Path: Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 761201065670; Sun, 16 Oct 2011 03:45:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 06D718FC12; Sun, 16 Oct 2011 03:45:34 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p9G3jRXd068490 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 15 Oct 2011 21:45:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 15 Oct 2011 21:45:23 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <4EEA1F8B-9854-4C5C-A397-95AD454D3680@bsdimp.com> References: To: Adrian Chadd X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 15 Oct 2011 21:45:29 -0600 (MDT) Cc: freebsd-arch@FreeBSD.ORG Subject: Re: newbus bus access routines and bus_space_barrier() X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2011 03:45:41 -0000 Usually they are needed, but we get away without them often because they = are needed in a limited set of circumstances and we have memory barriers = in our locking primitives. Warner On Oct 15, 2011, at 7:48 PM, Adrian Chadd wrote: > Hi all, >=20 > I'm not clued up on the way of the bus API, so please excuse the > newbie questions. >=20 > Nathan and I found that ath(4) wasn't working for a user because of a > missing bus barrier. Ath trips it up because it does lots of loops of > register reads/writes through the bus stream API rather than the > normal bus API. > It does this because it handles the register value swapping in > hardware rather than in software. >=20 > The correct fix is to teach ath(4) to use bus_space_barrier() calls > when doing stream calls, which I can do, but the newbus documentation > points out that both normal and stream bus access doesn't enforce > ordering, and barrier calls are needed. But I don't see lots of > bus_space_barrier() calls everywhere. Why's that? >=20 > Thanks, >=20 >=20 > Adrian > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org" >=20 >=20 From owner-freebsd-arch@FreeBSD.ORG Sun Oct 16 04:39:22 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E37031065673 for ; Sun, 16 Oct 2011 04:39:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id A57998FC15 for ; Sun, 16 Oct 2011 04:39:22 +0000 (UTC) Received: by ggeq3 with SMTP id q3so2797976gge.13 for ; Sat, 15 Oct 2011 21:39:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4ZL8JTi74pr3WC6DvMadhCV1rvuMoetmtX6UpbGVqK4=; b=YdB4fs142ZU4A5ssa+VFOIJK+eOPpWliHDPxkPuodk+IKtZToVFG90wmVlDlP9e6RN 2BXQp7mDAxtm9Rcclen0Esp7sSpXJnqmBj59kwZ6cdihFvvPvF2Sk0LW6n/0tS0iNa1z 9I2ftydHwgmHzglfISG8hhTx58Io7B451aHb8= MIME-Version: 1.0 Received: by 10.236.170.168 with SMTP id p28mr10923088yhl.100.1318739961903; Sat, 15 Oct 2011 21:39:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.95.147 with HTTP; Sat, 15 Oct 2011 21:39:21 -0700 (PDT) In-Reply-To: <4EEA1F8B-9854-4C5C-A397-95AD454D3680@bsdimp.com> References: <4EEA1F8B-9854-4C5C-A397-95AD454D3680@bsdimp.com> Date: Sun, 16 Oct 2011 12:39:21 +0800 X-Google-Sender-Auth: DruQAVKIyTCx1is_KYPeJWSHTZM Message-ID: From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-arch@freebsd.org Subject: Re: newbus bus access routines and bus_space_barrier() X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2011 04:39:23 -0000 On 16 October 2011 11:45, Warner Losh wrote: > Usually they are needed, but we get away without them often because they are needed in a limited set of circumstances and we have memory barriers in our locking primitives. Right. I'll just change the ath driver register ops to enforce a read/write barrier on each read or write. It'd be nice to teach the driver and the HAL about "correct" barriers but I just don't have the time. :( (FYI: apparently linux's ioread32/iowrite32 operations enforce barriers on each op.) Adrian From owner-freebsd-arch@FreeBSD.ORG Sun Oct 16 16:20:48 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DA201065677 for ; Sun, 16 Oct 2011 16:20:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4F09D8FC0C for ; Sun, 16 Oct 2011 16:20:48 +0000 (UTC) Received: by ggeq3 with SMTP id q3so3029384gge.13 for ; Sun, 16 Oct 2011 09:20:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fhAEvaB2VZIc/PGGv4eaUnEI4rzrcCMvAgGAHGC5lH4=; b=rP42WwmB53DOY7h+m6bpdBnE3KgJ+FtPXn5y+FzGC6wNAmqlmJoTzWS2CoHZQ9g3PD 3wORFEdq6bCMChsLCnqg1ilwaL07hZT6WlTwGh08Oh+JgWpD/GrdMowzUW87kVFQJs1Y KZztLh5Nw26aRXfVVaaMNbZXO7eOKcXypyx2k= MIME-Version: 1.0 Received: by 10.236.174.105 with SMTP id w69mr18423578yhl.32.1318782047559; Sun, 16 Oct 2011 09:20:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.95.147 with HTTP; Sun, 16 Oct 2011 09:20:47 -0700 (PDT) In-Reply-To: <4EEA1F8B-9854-4C5C-A397-95AD454D3680@bsdimp.com> References: <4EEA1F8B-9854-4C5C-A397-95AD454D3680@bsdimp.com> Date: Mon, 17 Oct 2011 00:20:47 +0800 X-Google-Sender-Auth: wgQbSLNPY8q3PX-GfKV21bkVQeM Message-ID: From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-arch@freebsd.org Subject: Re: newbus bus access routines and bus_space_barrier() X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2011 16:20:48 -0000 On 16 October 2011 11:45, Warner Losh wrote: > Usually they are needed, but we get away without them often because they are needed in a limited set of circumstances and we have memory barriers in our locking primitives. Hm, so should this actively be fixed for drivers? I note iwn(4) does its own (correct looking?) barrier stuff. A few other drivers do. ath doesn't (yet). wi(4) doesn't yet do barriers, but someone supplied a patch that may work better on ppc if said barriers are included. Thanks, Adrian From owner-freebsd-arch@FreeBSD.ORG Tue Oct 18 23:59:55 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39024106564A for ; Tue, 18 Oct 2011 23:59:55 +0000 (UTC) (envelope-from root@ns6.wowcardeals.com) Received: from ns6.wowcardeals.com (ns6.wowcardeals.com [217.23.9.146]) by mx1.freebsd.org (Postfix) with ESMTP id BF4268FC18 for ; Tue, 18 Oct 2011 23:59:54 +0000 (UTC) Received: by ns6.wowcardeals.com (Postfix, from userid 0) id ADAC0909948; Wed, 19 Oct 2011 03:26:19 +0400 (MSD) To: freebsd-arch@freebsd.org From: 'Drive a New BMW for R4999 P/M' Content-Disposition: inline Message-Id: <20111018232619.ADAC0909948@ns6.wowcardeals.com> Date: Wed, 19 Oct 2011 03:26:19 +0400 (MSD) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Drive A New BMW for R4999 P/M X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2011 23:59:55 -0000 wowbmw.com Drive a new BMW from R4999 per month! Can't see the pictures? [1]Click here to view this email online. Save up to R1 411.54 per month [2]BMW E90 320i BMW E90 320i Petrol (Manual) * From R4 999.00 per month. * Manual * 2.0L Petrol * Radio/CD * Aircon Climate Control * Central Locking * ABS/ASC + T&CBC * Fog Lamps * Cruise Control * Alloy Wheels * Isofix * Multifunction Steering Wheel * Cruise Control * Run Flat Tyres * 5 Year / 100 000km Motorplan Are you Interested? [3]YES / [4]NO Save up to R1 463.76 per month [5]BMW E90 Auto BMW E90 320i Petrol (Automatic) * From R5 299.00 per month. * Automatic * 2.0L Petrol * Radio/CD * Aircon Climate Control * Central Locking * ABS/ASC + T&CBC * Fog Lamps * Cruise Control * Alloy Wheels * Isofix * Multifunction Steering Wheel * Cruise Control * Run Flat Tyres * 5 Year / 100 000km Motorplan Are you Interested? [6]YES / [7]NO Subject to availability of stock. Extra's not factory fitted will be charged Terms and conditions and cost of credit General terms and conditions and cost of credit Duration of contract 72 months. Once off initiation fee of R1140.00 VAT inclusive, already included in contract. Monthly service fee of R57.00 VAT inclusive. Rate at prime +2% variable. All delivery, lic, registration and number plates included in cost of credit. No residual value or deposit. Cost of credit and repayments may vary due to your credit risk profile. Application subject (at all times) to approval from our credit providers partners. Pre quote and pre contract available at all times. Terms and conditions and cost of credit available or request of contract in all official languages To qualify, the applicant must comply with the following basic conditions: * Earn a minimum salary of R5 500.00 nett (take home); * Not listed on the ITC; * Have a SA Driver's license and ID; * The rest of our terms and conditions are set out in the example [8]Advertising Contract. Advertising initiative cost of credit: * BMW E90 320i Petrol (Manual) = R359 928.00 * BMW E90 320i Petrol (Automatic) = R381 528.00 Please note that your repayment and cost of credit may vary as per terms and conditions of the advertising agreement. Advertised payment reduction is governed by a advertising program. Re-payments exclude monthly services charged and include initiation fee as allowed by the NCR. To view an example of an advertising contract please [9]click here. Example adverts on the back of the vehicles: Branding Branding Cost of credit and repayment if you opt not to enter into the advertising initiative: * BMW E90 320i Petrol (Manual) = R465 662.88 Repayment = R6 467.54 per month * BMW E90 320i Petrol (Automatic) = R491 022.72 Repayment = R6 819.76 per month Repayments and cost of credit includes initiation and monthly service fees as prescribed by the [10]NCR. To stop receiving emails, please [11]UNSUBSCRIBE here References 1. http://www.wowbmw.com/mailer/002/agent.php?page=online&agent=002&campaign=bmw&vehicle=1 2. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=25 3. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=25 4. http://www.wowbmw.com/mailer/002/agent.php?page=decline&agent=002&campaign=bmw&vehicle=25 5. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=26 6. http://www.wowbmw.com/mailer/002/agent.php?page=apply&agent=002&campaign=bmw&vehicle=26 7. http://www.wowbmw.com/mailer/002/agent.php?page=decline&agent=002&campaign=bmw&vehicle=26 8. http://www.wowbmw.com/contract.pdf 9. http://www.wowbmw.com/contract.pdf 10. http://www.ncr.org.za/ 11. http://www.wowbmw.com/site/decline.php From owner-freebsd-arch@FreeBSD.ORG Thu Oct 20 20:59:02 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 032621065746 for ; Thu, 20 Oct 2011 20:59:02 +0000 (UTC) (envelope-from www@s113.loopia.se) Received: from s87.loopia.se (s87.loopia.se [194.9.95.112]) by mx1.freebsd.org (Postfix) with ESMTP id 9923D8FC14 for ; Thu, 20 Oct 2011 20:59:01 +0000 (UTC) Received: from s101.loopia.se (s101.loopia.se [194.9.95.47]) by s87.loopia.se (Postfix) with SMTP id 15D42465340 for ; Thu, 20 Oct 2011 22:40:33 +0200 (CEST) Received: (qmail 37646 invoked from network); 20 Oct 2011 20:40:22 -0000 Received: from s113.loopia.se (HELO s113.loopia.se) (194.9.94.207) by s101.loopia.se (qpsmtpd/0.31.1) with ESMTP; Thu, 20 Oct 2011 22:40:22 +0200 Received: from s113.loopia.se (localhost [127.0.0.1]) by s113.loopia.se (8.14.4/8.14.4) with ESMTP id p9KKeOE4007911 for ; Thu, 20 Oct 2011 22:40:24 +0200 (CEST) (envelope-from www@s113.loopia.se) Received: (from www@localhost) by s113.loopia.se (8.14.4/8.14.4/Submit) id p9KKeO1R007910; Thu, 20 Oct 2011 22:40:24 +0200 (CEST) (envelope-from www) Date: Thu, 20 Oct 2011 22:40:24 +0200 (CEST) Message-Id: <201110202040.p9KKeO1R007910@s113.loopia.se> To: freebsd-arch@freebsd.org From: Security Center Paypal MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Security Center Paypal X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2011 20:59:02 -0000 [1]PayPal [pixel.gif] Information Regarding Your account: Dear PayPal Member: Attention! Your PayPal account has been limited! As part of our security measures, we regularly screen activity in the PayPal system.We recently contacted you after noticing an issue on your account.We requested information from you for the following reason: Our system detected unusual charges to a credit card linked to your PayPal account. Reference Number: PP-259-187-991 This is the Last reminder to log in to PayPal as soon as possible. Once you log in, you will be provided with steps to restore your account access. Once you log in, you will be provided with steps to restore your account access. We appreciate your understanding as we work to ensure account safety. [2]Click here to activate your account We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account. We apologise for any inconvenience.. Sincerely, PayPal Account Review Department _________________________________________________________________ Copyright © 1999-2011 PayPal. All rights reserved. PayPal Ltd. PayPal FSA Register Number: 226056. [pixel.gif] PayPal Email ID PP059 Protect Your Account Info Make sure you never provide your password to fraudulent websites. To safely and securely access the PayPal website or your account, open a new web browser (e.g. Internet Explorer or Netscape) and type in the PayPal login page (http://paypal.com/) to be sure you are on the real PayPal site. For more information on protecting yourself from fraud, please review our Security Tips at https://www.paypal.com/us/securitytips Protect Your Password You should never give your PayPal password to anyone. References 1. https://www.paypal.com/us 2. http://paypalupdate.com.security.online.unlimited.conceptec.net/paypal.com/