Date: Wed, 14 Jan 2015 11:21:52 -0500 (EST) From: Salvage Drive <info@salvagedrive.com> To: arch@freebsd.org Subject: Special Package Deal 4 Cars Message-ID: <1119764708435.1115603422701.1254712288.0.241121JL.1002@scheduler.constantcontact.com>
next in thread | raw e-mail | index | archive | help
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ HOT PACKAGE DEAL!!! 4 Cars for ONLY $9,999 Selling our in-house inventory No Auction Fees No Salvage Drive Fees ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ 2009 Hyundai Elantra Salvage Title Odometer: 47,136 miles ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ 2010 Kia Sportage Salvage Title Odometer: 85,328 miles ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ 2011 Hyundai Santa Fe Salvage Title Odometer: 75,470 miles ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ 2009 Toyota Corolla Salvage Title Odometer: n/a ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ Disclaimer: These vehicles are sold as is and where is, without warranty. T= he price offered only applies to the actual purchase of all 4 (Four) vehicles as a "= Package Deal" Buyer will be responsible for shipping cost of each unit, plus $50 Document= ation fee for each Vehicle. No Cars may be removed by the purchaser prior to mak= ing full payment. This offer is based on First-come, first-served (FCFS) Policy. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ SalvageDrive.com [http://r20.rs6.net/tn.jsp?f=3D001ELVijS5E-2wKONURIV28orxZ= 8ckw8zIY4ntcXx2OmI5LxZwX6_CFmU5B7em_L5p9MF29Vml4jXREAuP0agTrY_kFKH-mUthzWSG= 1pINgK2sYoTIG-nnL8LBajyGC-xBivXX0Ru8XJSjNHQL3FHW0sh75vxRcG1R6kd7RyTlHz6cZx5= TxSjBeiA=3D=3D&c=3Di1fcX5LizTp_0bf2nRYcqBj1AYbvQZwYT1Vk2KRqbJTlO_U_wnUOtg= =3D=3D&ch=3Da-ElDxCcHM-DN4nLL1_lUeD7pRyPgXCDtDUBXUGd52_m7JxRQs1nEQ=3D=3D] SalvageDrive.com [http://r20.rs6.net/tn.jsp?f=3D001ELVijS5E-2wKONURIV28orxZ= 8ckw8zIY4ntcXx2OmI5LxZwX6_CFmWL-5hFR-7y8mEjC7QGz69Kvl5HFjApBVd1rIc4D-gDuKPA= P_FvuJ0JmltCxtHzQog5pVXX3d2QiozYgpkmB8YKQReBdSiyzexZ0LlOlH_39QkeAkQdGYLQcHl= 87NbxtlOuZTWTnQ8IakyH0VwGrevnKoTWP-CAq8eV7yXwmybnf&c=3Di1fcX5LizTp_0bf2nRYc= qBj1AYbvQZwYT1Vk2KRqbJTlO_U_wnUOtg=3D=3D&ch=3Da-ElDxCcHM-DN4nLL1_lUeD7pRyPg= XCDtDUBXUGd52_m7JxRQs1nEQ=3D=3D] 1-844-227-7411 Toll Free 1-347-492-1727 Tel. Skype: salvagedrive info@SalvageDrive.com [mailto:info@SalvageDrive.com] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ Sincerely, Salvage Drive Team ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ ___________________________________________________________________________= __________ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ You can choose to unsubscribe from our Email Newsletters service by replyin= g to=20 this email with the word "STOP" and we will remove you from any future mail= ings. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ Don't forget to add info@salvagedrive.com to your Address Book to keep it f= rom skipping your inbox or getting caught in spam filters. We want your experience with the Salvage Drive to be as smooth and reassuri= ng as possible. Accordingly, we diligently safeguard your privacy. If you wish t= o review our Privacy Policy at any time, please click on the link below, or copy and= paste it into your web browser's location window Salvage Drive Privacy Policy [http://r20.rs6.net/tn.jsp?f=3D001ELVijS5E-2wK= ONURIV28orxZ8ckw8zIY4ntcXx2OmI5LxZwX6_CFmWL-5hFR-7y8YCQgjliJDM3ZQMaGzS0vcL7= lRdlOJQaOXvZxewGMpJaO8kUqEDHadw08VhB3NRrNUkUU0_rcVPHAwQ3y24KgjcEoYPT4lOz_yG= 8MuUNuAodgdy9Ng_xojkteHnP0Oa90UsUrT4mVw5E1gnzPFY6HH_2zRWNHGshV&c=3Di1fcX5Li= zTp_0bf2nRYcqBj1AYbvQZwYT1Vk2KRqbJTlO_U_wnUOtg=3D=3D&ch=3Da-ElDxCcHM-DN4nLL= 1_lUeD7pRyPgXCDtDUBXUGd52_m7JxRQs1nEQ=3D=3D] =C2=A9 2014 SalvageDrive, Inc. | All rights reserved ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~ This email was sent to arch@freebsd.org by info@salvagedrive.com. Update Profile/Email Address http://visitor.constantcontact.com/do?p=3Doo&m=3D001byRd3MOrEzrBc_e8AIN5jg%= 3D%3D&ch=3D8b131940-9839-11e4-9cca-d4ae528eade9&ca=3Dbc46b500-0079-4568-a2d= f-8c3cbcd0be98 Instant removal with SafeUnsubscribe(TM) http://visitor.constantcontact.com/do?p=3Dun&m=3D001byRd3MOrEzrBc_e8AIN5jg%= 3D%3D&ch=3D8b131940-9839-11e4-9cca-d4ae528eade9&ca=3Dbc46b500-0079-4568-a2d= f-8c3cbcd0be98 Privacy Policy: http://ui.constantcontact.com/roving/CCPrivacyPolicy.jsp Online Marketing by Constant Contact(R) www.constantcontact.com Salvage Drive, Inc | 217 Broadway | Suite 515 | New York | NY | 10007 From owner-freebsd-arch@FreeBSD.ORG Wed Jan 14 23:56:23 2015 Return-Path: <owner-freebsd-arch@FreeBSD.ORG> Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9ED5EE11 for <arch@freebsd.org>; Wed, 14 Jan 2015 23:56:23 +0000 (UTC) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A2AA3EE for <arch@freebsd.org>; Wed, 14 Jan 2015 23:56:23 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id y10so1377802pdj.13 for <arch@freebsd.org>; Wed, 14 Jan 2015 15:56:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=VHELp2LLMnbh7EUNsX+NOw0vjTq9bdpviLVZV8J1cRY=; b=CLVn4OMteX33i4TkvYMVDgyOPmQXoaUa4er6C5iOITeamb4CUMqMch98hq8LOW2ds2 hz8F03qmDrMxBrgaqu5TKSZaYMAXfR/tzr1Vt/Tv22Zu6kK4MCpDbO34/aqnAci1waOe 75/dklU1zL/Sg6y3hJwJoRI5ZQckG+Vk1aHPTjI+nLSkFDNhHdYiujzKRFazIxpcajlT /x2AJ9JWrh8bv12f+zAtnWBe8t2H8NShTPwNso4ERwqO8vDHR/qfc7zJKbQEPoLp6oBo Su0U3+OTwtQztqn+LYTfAQhJ5AZtLGWbeVtO/vwddaTKJrFdIZCLX5rFoh8de4O7HkNm SxiA== X-Gm-Message-State: ALoCoQnUMVg1UVVkQGv6KCpY2XuYIHFQS29CmcsuzrZL0HRxPs0GmUelFL9H29DZP68sGtv0XwyD X-Received: by 10.70.103.197 with SMTP id fy5mr9599565pdb.131.1421279782576; Wed, 14 Jan 2015 15:56:22 -0800 (PST) Received: from [10.64.25.14] ([69.53.236.236]) by mx.google.com with ESMTPSA id pf10sm20655309pbc.82.2015.01.14.15.56.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 14 Jan 2015 15:56:21 -0800 (PST) Sender: Warner Losh <wlosh@bsdimp.com> Subject: Re: devctl(8): A device control utility Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_724ABB64-B20B-4A5C-8428-9E19B43BA4A9"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b3 From: Warner Losh <imp@bsdimp.com> In-Reply-To: <54B44448.1090901@FreeBSD.org> Date: Wed, 14 Jan 2015 16:56:18 -0700 Message-Id: <E3CAE124-1D8E-4A89-8113-D8301436BFE9@bsdimp.com> References: <3200196.9ZgXApgRdA@ralph.baldwin.cx> <54AAF60A.9070609@FreeBSD.org> <54AAFAEB.2090505@selasky.org> <6155572.yV5dxPJznD@ralph.baldwin.cx> <54B3F349.9050703@FreeBSD.org> <11219A27-4C5B-4429-8847-3E54F9C4CD1E@bsdimp.com> <54B44448.1090901@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> X-Mailer: Apple Mail (2.1993) Cc: Hans Petter Selasky <hps@selasky.org>, arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>, <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>; List-Post: <mailto:freebsd-arch@freebsd.org> List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>, <mailto:freebsd-arch-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 14 Jan 2015 23:56:23 -0000 --Apple-Mail=_724ABB64-B20B-4A5C-8428-9E19B43BA4A9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 12, 2015, at 3:01 PM, John Baldwin <jhb@FreeBSD.org> wrote: >=20 > On 1/12/15 12:01 PM, Warner Losh wrote: >>=20 >>> On Jan 12, 2015, at 9:16 AM, John Baldwin <jhb@FreeBSD.org> wrote: >>>=20 >>> On 1/5/15 4:18 PM, John Baldwin wrote: >>>> On Monday, January 05, 2015 09:58:19 PM Hans Petter Selasky wrote: >>>>> On 01/05/15 21:37, John Baldwin wrote: >>>>>> On 1/5/15 3:13 PM, Hans Petter Selasky wrote: >>>>>>> On 01/05/15 21:01, John Baldwin wrote: >>>>>>>> The devctl(8) utility is then a thin wrapper around libdevctl = (and >>>>>>>> does not >>>>>>>> yet have a manpage). >>>>>>>>=20 >>>>>>>> Do folks have any feedback? >>>>>>>=20 >>>>>>> Hi, >>>>>>>=20 >>>>>>> In the USB area attach and detach must be synchronized to the = USB stack >>>>>>> and "usbconfig -d X.Y set_config Z" or "usbconfig -d X.Y reset" = should >>>>>>> be used to avoid races attaching and detaching drivers! >>>>>>=20 >>>>>> I think this points to one or more missing bus methods so that = the bus >>>>>> can hook into device_probe_and_attach() to reset a device as = needed. >>>>>> (e.g. if you had bus_probe_started / bus_probe_finished and = possibly >>>>>> similar methods for attach. PCI could use a = bus_attach_finished() >>>>>> callback so that it could clean up any dangling resources and = possibly >>>>>> power down on a failed attach the way it does in = bus_child_detached as >>>>>> well). >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> USB has its own threads to allocate/free devices. Another problem = is how >>>>> to atomically get a reference count across multiple layers like = PCI and >>>>> USB. It doesn't allow probe/attach when called from outside these = threads. >>>>=20 >>>> That just means you need to use some locks. :) Cardbus also uses = an event >>>> thread to handle auto-attach of devices when it detected a card = change event, >>>> but that doesn't prevent it from servicing an ioctl request. >>>=20 >>> Another option btw would be to add bus methods that wrap probe and >>> attach (rather than pre and post event hooks). I wish = bus_add_child() >>> were done this way such that device_add_child_ordered() were renamed = to >>> bus_generic_add_child() (and was the default add_child method) and = that >>> device_add_child_ordered() called 'BUS_ADD_CHILD()' so that >>> 'device_add_child()' was the proper public API (instead of exposing >>> BUS_ADD_CHILD()). Similarly, I think that 'device_attach()' and >>> 'device_probe_and_attach()' should be the public API and that one = way or >>> another we should add hooks to allow bus drivers to modify their >>> behavior if needed. However, they should be fine for devctl ioctls = to >>> invoke as well as other kernel bits. >>=20 >> When I was doing CardBus and PC Card I wished for similar things. = Then >> I realized I didn=E2=80=99t need them because as the bus author, I = know when these >> events happened and could take appropriate actions for the bus. I = didn=E2=80=99t have >> that atomic access issues though, since as the bus author I also = controlled how >> and when mutexes were taken out and when I allowed access to the bus. = I >> only used mutexes in CardBus and PC Card because most of the sleeps = were >> short, but other ways to do locking are quite possible... >=20 > I think the problem here is that devctl introduces events that happen > without the bus's knowledge. When we did the kludge sysctl power stuff for cardbus (which was never = committed), we sent a message to the bus to tell it to do the power off and cope with = whatever else was needed. There were times that it couldn=E2=80=99t comply, iirc, so this =E2=80=98command= =E2=80=99 allowed errors to be returned for things that were forbidden / not allowed for some reason at the time rather = than getting a message that this thing happened and we had to mop up now. Warner --Apple-Mail=_724ABB64-B20B-4A5C-8428-9E19B43BA4A9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUtwIjAAoJEGwc0Sh9sBEAC68QANxHxKO4hnx82BojE9fMVi6/ /oPh7toXq1YqLLq4QwMBH2izkL+5XjwHQbe0EGItQXKVasIwiIu8Bf5fIv04FIfy 5++do7LVUE1yA3LBHdiOVnFP5eXQ59kYR+cIwAEjpA1mevt8Psqd8frYlzwdgj2z pFw1OAil4LXWG/ujAzNP60iP6Pxu5f4offHk12Sqn22x3tHpN6cIASW+h4rmPLEM tBhhc0AbpnunP8MCEBy/BrZi/jgKvQOh1PTpG0Xo4F4Uo4ZbG0absy8cut/+s4dq 9O+0UAXabNN68hLUqLtl92SnLNv89gl3GcE6NeUAF0+L7JjYexZBVuNQmZZpGyaI ms9t8K/PxzLKxTmFiwgnzzQaox8/PzrXb9ffkx4stFG8K1mzoRkl6A/qFNjK0x1J RTdzYbjyBVVGxlNkXYBmyCbN0MBoa53pSIkx40YF1z1+MI579XdJfLxqG7vWlS/R 2BMxYakT2ORHunX0U9JEG9psHGOa0t6GCskEhNv6yJkwgCLAHBjTrJKMusQIgf9z HdYJTc4XDNSJi/N5AKAvTwYaxoO5b3tta9//elSSqQePA3VtVfo1YkiOR6Mhxe46 VevVt6RP405SiUzoJ574iHuLI3X1BoGrVAwZQRyQ185BelUWhso12Tuzvp0Vc6Bw aCQI7s7kIzNIhu6mCWiW =MGb6 -----END PGP SIGNATURE----- --Apple-Mail=_724ABB64-B20B-4A5C-8428-9E19B43BA4A9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1119764708435.1115603422701.1254712288.0.241121JL.1002>