From owner-freebsd-usb@FreeBSD.ORG Sun Jun 28 09:55:16 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E3311065673; Sun, 28 Jun 2009 09:55:16 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id A275B8FC0C; Sun, 28 Jun 2009 09:55:15 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=hlIU1J3LQChSjWV/CGRL5g==:17 a=m4X4Y5dQOB2DOwTTiTYA:9 a=8ipVIBLg3e7VFiSgQXBdK4HAca8A:4 Received: from [193.217.167.6] (account mc467741@c2i.net HELO laptop.selasky.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1167912719; Sun, 28 Jun 2009 11:55:13 +0200 From: Hans Petter Selasky To: Alexandr Rybalko , freebsd-arm@freebsd.org Date: Sun, 28 Jun 2009 11:54:40 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> <20090623121129.d18492a3.ray@dlink.ua> <200906231912.20741.hselasky@c2i.net> In-Reply-To: <200906231912.20741.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906281154.43392.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org, Rafal Jaworowski , thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2009 09:55:16 -0000 Hi Piotr and Rafal, Your patch is not fully correct. It will break support for x86 and more when bounce pages are uses. Let's get the definitions right: man busdma BUS_DMASYNC_PREREAD Perform any synchronization required prior to an update of host memory by the device. BUS_DMASYNC_PREWRITE Perform any synchronization required after an update of host memory by the CPU and prior to device access to host memory. BUS_DMASYNC_POSTREAD Perform any synchronization required after an update of host memory by the device and prior to CPU access to host memory. BUS_DMASYNC_POSTWRITE Perform any synchronization required after device access to host memory. My view: XXX_PREXXX functions should be used prior to read/write device access. In other words, PRE has to be a flush operation. XXX_POSTXXX functions should be used after read/write device access. In other words, POST has to be an invalidate operation. Reading: src/sys/arm/arm/busdma_machdep.c I find bus_dmamap_sync_buf() to be coherent with this view. Can you check if the COHERENT bit is set for your allocation? if (map->flags & DMAMAP_COHERENT) return; Summed up: The existing code is doing correct. What is known is a problem with the memory mapping, so that the same memory page can get mapped with different attributes, which makes the problem appear. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 09:11:22 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D77781065673; Mon, 29 Jun 2009 09:11:22 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 363278FC12; Mon, 29 Jun 2009 09:11:22 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from [10.0.0.5] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id 7E74CC3BBC; Mon, 29 Jun 2009 11:10:02 +0200 (CEST) From: Piotr =?utf-8?q?Zi=C4=99cik?= Organization: Semihalf To: Hans Petter Selasky Date: Mon, 29 Jun 2009 11:11:20 +0200 User-Agent: PLD Linux KMail/1.9.10 References: <200906231035.43096.kosmo@semihalf.com> <200906231912.20741.hselasky@c2i.net> <200906281154.43392.hselasky@c2i.net> In-Reply-To: <200906281154.43392.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291111.20725.kosmo@semihalf.com> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 09:11:23 -0000 Sunday 28 June 2009 11:54:40 Hans Petter Selasky napisa=C5=82(a): > Hi Piotr and Rafal, > > Your patch is not fully correct. It will break support for x86 and more > when bounce pages are uses. > > Let's get the definitions right: > > man busdma > (...) > > My view: > > XXX_PREXXX functions should be used prior to read/write device access. > > In other words, PRE has to be a flush operation. > > XXX_POSTXXX functions should be used after read/write device access. > > In other words, POST has to be an invalidate operation. > > Reading: > > src/sys/arm/arm/busdma_machdep.c > > I find bus_dmamap_sync_buf() to be coherent with this view. If everything is OK, then why USB does not work on ARM and MIPS ? Let's look into busdma for these platforms: usb_pc_cpu_invalidate(): [BUS_DMASYNC_POSTREAD | BUS_DMASYNC_POSTWRITE] i386: NOP arm: Invalidate + hacks for VIPT cache. mips: NOP usb_pc_cpu_flush(): [BUS_DMASYNC_PREREAD | BUS_DMASYNC_PREWRITE] i386: NOP arm: Writeback invalidate mips: Writeback invalidate. I do not see direct coherency between flags passed to bus_dma and cache=20 operations, which could be source of problem. Let's also look at usb_pc_cpu_invalidate() usage in=20 sys/dev/usb/controller/ehci.c: while (1) { usb_pc_cpu_invalidate(td->page_cache); status =3D hc32toh(sc, td->qtd_status); (...) if (status & EHCI_QTD_HALTED) { break; } (...) td =3D td->obj_next; In my oppinion usb_pc_cpu_invalidate() used here suggests that it is doing= =20 cache invalidation not "Perform any synchronization required after = =20 an update of host memory by the device and prior to CPU access to host=20 memory". As this function is implemented as bus_dmamap_sync() all busdma rules shoul= d=20 be applied: If read and write operations are not preceded and followed by the appropriate synchronization operations, behavior is undefined. In code shown above (and many more places in USB stack) there is no followi= ng synchronization operation, which also could be source of problem. My major question here is why bus_dma is used for flushing and invalidation CPU caches instead of cpu_*() functions wich was written for this purpuose. > Can you check if the COHERENT bit is set for your allocation? > > if (map->flags & DMAMAP_COHERENT) > return; > No. This bit is not set. > Summed up: > > The existing code is doing correct. What is known is a problem with the > memory mapping, so that the same memory page can get mapped with different > attributes, which makes the problem appear. I don't think so: $ man busdma BUS_DMA_COHERENT Attempt to map this memory such that cache sync operations are as cheap as possible. This flag is typically set on memory that will be accessed by b= oth a CPU and a DMA engine, frequently. Use of this flag does not remove the= =20 requirement of using bus_dmamap_sync, but it may reduce the cost of =09 performing these operations.=20 This means that BUS_DMA_COHERENT does not guarantee no-cache mapping - this= is only a hint for busdma subsystem that region will be synced frequently. Ple= ase=20 look at discussion at=20 http://kerneltrap.org/mailarchive/freebsd-current/2009/5/27/5817243 =2D-=20 Best regards. Piotr Ziecik From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 09:55:45 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CD3E1065674; Mon, 29 Jun 2009 09:55:45 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 7C8DB8FC16; Mon, 29 Jun 2009 09:55:43 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=dT19lrtdAAAA:8 a=JB0F7hjHzw5RfXIn3lQA:9 a=awSKR1t7wlnHVe-XWeKBqYDR5Q4A:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.selasky.org) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1267858797; Mon, 29 Jun 2009 11:55:42 +0200 From: Hans Petter Selasky To: Piotr =?utf-8?q?Zi=C4=99cik?= Date: Mon, 29 Jun 2009 11:55:11 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> <200906281154.43392.hselasky@c2i.net> <200906291111.20725.kosmo@semihalf.com> In-Reply-To: <200906291111.20725.kosmo@semihalf.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291155.13941.hselasky@c2i.net> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 09:55:46 -0000 Hi Piotr and Rafal, On Monday 29 June 2009 11:11:20 Piotr Zi=C4=99cik wrote: > Sunday 28 June 2009 11:54:40 Hans Petter Selasky napisa=C5=82(a): > > Hi Piotr and Rafal, > > > > Your patch is not fully correct. It will break support for x86 and more > > when bounce pages are uses. > > > > Let's get the definitions right: > > > > man busdma > > (...) > > > > My view: > > > > XXX_PREXXX functions should be used prior to read/write device access. > > > > In other words, PRE has to be a flush operation. > > > > XXX_POSTXXX functions should be used after read/write device access. > > > > In other words, POST has to be an invalidate operation. > > > > Reading: > > > > src/sys/arm/arm/busdma_machdep.c > > > > I find bus_dmamap_sync_buf() to be coherent with this view. > > If everything is OK, then why USB does not work on ARM and MIPS ? I'm not saying everything is OK, I just don't agree that the problem is in= =20 USB. If you look at: http://fxr.watson.org/fxr/source/i386/i386/busdma_machdep.c#L931 Then you see the XXX_PREXXX means copy from client buffer (bpage->datavaddr= )=20 to real DMA buffer (bpage->vaddr). That means flush memory from cache to RA= M.=20 You want to change it into a XXX_POSTXXX (???) in the USB code, and that wo= n't=20 work for x86 and amd64 ... Then you also see that XXX_POSTXXX is doing the opposite, cleaning the cach= e=20 and copying from RAM into the "cache" buffer. > Let's look into busdma for these platforms: > > usb_pc_cpu_invalidate(): [BUS_DMASYNC_POSTREAD | BUS_DMASYNC_POSTWRITE] > i386: NOP > arm: Invalidate + hacks for VIPT cache. > mips: NOP Isn't this correct cleaning the cache on ARM? > > usb_pc_cpu_flush(): [BUS_DMASYNC_PREREAD | BUS_DMASYNC_PREWRITE] > i386: NOP > arm: Writeback invalidate > mips: Writeback invalidate. Isn't this correct flushing the cache to RAM on ARM? > > I do not see direct coherency between flags passed to bus_dma and cache > operations, which could be source of problem. Can you explain a little bit more what you see is not coherent? > > Let's also look at usb_pc_cpu_invalidate() usage in > sys/dev/usb/controller/ehci.c: > > while (1) { > usb_pc_cpu_invalidate(td->page_cache); > status =3D hc32toh(sc, td->qtd_status); > > (...) > > if (status & EHCI_QTD_HALTED) { > break; > } > > (...) > > td =3D td->obj_next; > > > In my oppinion usb_pc_cpu_invalidate() used here suggests that it is doing > cache invalidation not "Perform any synchronization required after > an update of host memory by the device and prior to CPU access to host > memory". The invalidate means: Clean the cache, so that the succeeding read fetches = its=20 value from RAM. > > As this function is implemented as bus_dmamap_sync() all busdma rules > should be applied: > > If read and write operations are not preceded and followed by the > appropriate synchronization operations, behavior is undefined. > > > In code shown above (and many more places in USB stack) there is no > following synchronization operation, which also could be source of proble= m. All cases where transfer descriptors are updated are wrapped with bus-sync= =20 operations, through the "usb_pc_cpu_xxx()" functions. Else mutexes are used= =2E=20 Please give an example of such a place where improper synchronisation happe= ns. > > My major question here is why bus_dma is used for flushing and invalidati= on > CPU caches instead of cpu_*() functions wich was written for this purpuos= e. Because that is what other drivers are doing. I think using cpu_*() is more= =20 alike Linux, and also, if the memory is on a bounce page, cpu_*() will yiel= d=20 the wrong result. > > Can you check if the COHERENT bit is set for your allocation? > > > > if (map->flags & DMAMAP_COHERENT) > > return; > > No. This bit is not set. > > > Summed up: > > > > The existing code is doing correct. What is known is a problem with the > > memory mapping, so that the same memory page can get mapped with > > different attributes, which makes the problem appear. > =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 10:49:45 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB050106564A; Mon, 29 Jun 2009 10:49:45 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 184568FC0A; Mon, 29 Jun 2009 10:49:44 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from [10.0.0.5] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id 9A893C3BB0; Mon, 29 Jun 2009 12:48:25 +0200 (CEST) From: Piotr =?utf-8?q?Zi=C4=99cik?= Organization: Semihalf To: Hans Petter Selasky Date: Mon, 29 Jun 2009 12:49:43 +0200 User-Agent: PLD Linux KMail/1.9.10 References: <200906231035.43096.kosmo@semihalf.com> <200906291111.20725.kosmo@semihalf.com> <200906291155.13941.hselasky@c2i.net> In-Reply-To: <200906291155.13941.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291249.43983.kosmo@semihalf.com> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 10:49:46 -0000 Monday 29 June 2009 11:55:11 Hans Petter Selasky napisa=C5=82(a): > Hi Piotr and Rafal, > > I'm not saying everything is OK, I just don't agree that the problem is in > USB. > > If you look at: > > http://fxr.watson.org/fxr/source/i386/i386/busdma_machdep.c#L931 > > Then you see the XXX_PREXXX means copy from client buffer > (bpage->datavaddr) to real DMA buffer (bpage->vaddr). That means flush > memory from cache to RAM. You want to change it into a XXX_POSTXXX (???) = in > the USB code, and that won't work for x86 and amd64 ... > > Then you also see that XXX_POSTXXX is doing the opposite, cleaning the > cache and copying from RAM into the "cache" buffer. > > Isn't this correct flushing the cache to RAM on ARM? > It is correct if you use busdma in correct way: [... prepare data to transfer ...] bus_dmamap_sync(..., PREREAD | PREWRITE); [... do transfer ...] bus_dmamap_sync(..., POSTREAD | POSTWRITE); [... check results ...] > > I do not see direct coherency between flags passed to bus_dma and cache > > operations, which could be source of problem. > > Can you explain a little bit more what you see is not coherent? I thought about direct relation between calling bus_dmamap_sync() with given flag and cache operation. usb_pc_cpu_invalidate() not always is doing invalidate and usb_pc_cpu_flush() not always is doing flush. > > In my oppinion usb_pc_cpu_invalidate() used here suggests that it is > > doing cache invalidation not "Perform any synchronization required after > > an update of host memory by the device and prior to CPU access to host > > memory". > > The invalidate means: Clean the cache, so that the succeeding read fetches > its value from RAM. But usb_pc_cpu_invalidate(), which should do cache invalidate, doing NOP or other operations depending on architecture bus_dma implementation.=20 Therefore these functions should not be used for enforcing cache operations. > > As this function is implemented as bus_dmamap_sync() all busdma rules > > should be applied: > > > > If read and write operations are not preceded and followed by the > > appropriate synchronization operations, behavior is undefined. > > > > > > In code shown above (and many more places in USB stack) there is no > > following synchronization operation, which also could be source of > > problem. > > All cases where transfer descriptors are updated are wrapped with bus-sync > operations, through the "usb_pc_cpu_xxx()" functions. Else mutexes are > used. Please give an example of such a place where improper synchronisati= on > happens. Look into ehci_check_transfer() function=20 (http://fxr.watson.org/fxr/source/dev/usb/controller/ehci.c#L1294)=20 usb_pc_cpu_invalidate() [bus_dmamap_sync()] is not used in this function=20 correcly. It is not paired with usb_pc_cpu_flush() [opposite=20 bus_dmamap_sync()] as busdma requires (see part of manpage cited above). The same problem is in part of code shown in previous mail. If usb_pc_cpu_invalidate()/usb_pc_cpu_flush() functions had been implemente= d=20 without using busdma, for example as cpu_*() functions, ehci_check_transfer= ()=20 would have been 100% correct. In current code busdma requirements are simpl= y=20 not met. > > My major question here is why bus_dma is used for flushing and > > invalidation CPU caches instead of cpu_*() functions wich was written f= or > > this purpuose. > > Because that is what other drivers are doing. I think using cpu_*() is mo= re > alike Linux, and also, if the memory is on a bounce page, cpu_*() will > yield the wrong result. Ok. So if you use bus_dma(), please use it in correct way. =2D-=20 Best Regards. Piotr Ziecik From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 11:07:09 2009 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9932F106566C for ; Mon, 29 Jun 2009 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 853448FC22 for ; Mon, 29 Jun 2009 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5TB790N046533 for ; Mon, 29 Jun 2009 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5TB78Iw046529 for freebsd-usb@FreeBSD.org; Mon, 29 Jun 2009 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Jun 2009 11:07:09 GMT Message-Id: <200906291107.n5TB78Iw046529@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 11:07:10 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/135938 usb [aue] aue driver only passes traffic in promisc mode o usb/135857 usb RTL8187 Wireless Adapter o usb/135575 usb [usbdevs] [patch] Add HTC Wizard phone vid/pid informa o usb/135542 usb [keyboard] boot loader does not work with a usb keyboa o usb/135372 usb Quirk report for Teclast TL-C300 usb media player o usb/135348 usb [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata) o usb/135206 usb machine reboots when inserted USB device o usb/135200 usb SAMSUNG i740 usb mass: Synchronize cache failed, statu o usb/135182 usb UMASS quirk - Olympus FE20 camera o usb/134950 usb Lowering DTR for USB-modem via ubsa is not possible o usb/134633 usb Add support for WILLCOM03(SHARP smart phone) o usb/134631 usb [usbdevs] [patch] WiSPY DBx support requires usb tweak o usb/134476 usb [usb2] [umass] [quirk] Add quirk for Cypress xx6830xx o usb/134299 usb Kernel Panic plugging in MF626 USB UMTS Stick u3g o usb/134193 usb System freeze on usb MP3 player insertion o usb/134117 usb [Patch] Add support for 'Option GlobeTrotter HSDPA Mod o usb/134085 usb [umass] Adding usb quirk for Sony USB flash drive o usb/133989 usb [newusb] [ukbd] USB keyboard dead at mountroot> prompt f usb/133545 usb [usb] [panic] Kernel crash in usb2_intr_schedule_adjus o usb/133390 usb umass crashes system in 7.1 when Olympus D-540 attache o usb/133296 usb rum driver not working properly in hostap mode p usb/132799 usb [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA o usb/132785 usb [usb] [patch] Gemtech remote powersocket is classed as o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] Kernel panic after NOMEM caused by rum c o usb/132066 usb [ukbd] Keyboard failure USB keyboard DELL 760 o usb/132036 usb [panic] page fault when connecting Olympus C740 camera o usb/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [newusb] DVD drive detects as 'da' device o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup s usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] [panic] enabling usb keyboard and mouse support o usb/127248 usb [ucom] panic while uplcom devices attaach and detach o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125264 usb [patch] sysctl for set usb mouse rate (very useful for o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [new driver] [patch] New driver for Sierra Wireless 3G o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] [panic] FreeBSD fails to boot with usb legacy s o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [new driver] [patch] add utoppy device from NetBSD o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o kern/99200 usb [bluetooth] SMP-Kernel crashes reliably when Bluetooth o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 323 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 11:38:24 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A17AB1065670; Mon, 29 Jun 2009 11:38:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swipnet.se [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id 965498FC1D; Mon, 29 Jun 2009 11:38:23 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=dT19lrtdAAAA:8 a=tPo35w6jI4Rau6MQO3MA:9 a=mkklXvtNmbOxkHJfpxbL30FRJesA:4 a=S1CdNgxGSc7KuUU9:21 a=mYAzaKh1ZkpupjlU:21 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe09.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 923352543; Mon, 29 Jun 2009 13:38:11 +0200 From: Hans Petter Selasky To: Piotr =?utf-8?q?Zi=C4=99cik?= Date: Mon, 29 Jun 2009 13:37:41 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> <200906291155.13941.hselasky@c2i.net> <200906291249.43983.kosmo@semihalf.com> In-Reply-To: <200906291249.43983.kosmo@semihalf.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291337.43635.hselasky@c2i.net> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 11:38:25 -0000 Hi, On Monday 29 June 2009 12:49:43 Piotr Zi=C4=99cik wrote: > Monday 29 June 2009 11:55:11 Hans Petter Selasky napisa=C5=82(a): > > Hi Piotr and Rafal, > > Look into ehci_check_transfer() function > (http://fxr.watson.org/fxr/source/dev/usb/controller/ehci.c#L1294) > > usb_pc_cpu_invalidate() [bus_dmamap_sync()] is not used in this function > correcly. It is not paired with usb_pc_cpu_flush() [opposite > bus_dmamap_sync()] as busdma requires (see part of manpage cited above). > The same problem is in part of code shown in previous mail. > > If usb_pc_cpu_invalidate()/usb_pc_cpu_flush() functions had been > implemented without using busdma, for example as cpu_*() functions, > ehci_check_transfer() would have been 100% correct. In current code busdma > requirements are simply not met. Good point. Unfortunately I cannot pair like you suggest, because then I ca= n=20 overwrite values updated by the hardware, if I first read the status for=20 example, and the same 32-bits are updated by hardware, before the old value= is=20 flushed over the new one.. Also I cannot find the word "pair" in the busdma= =20 manpage? Where is this requirement stated? I see some things: You wrote earlier that the COHERENT flag was not set. That means your setup= is=20 using bounce pages for DMA? Right? Then I see a problem, if I do several POST operations in a row then I can s= ee=20 that the real DMA memory can get cached: In: "src/sys/arm/arm/busdma_machdep.c" Is "vaddr_nocache" set or cleared? if (op & BUS_DMASYNC_POSTREAD) { if (bpage->vaddr_nocache =3D=3D 0) { cpu_dcache_inv_range(bpage->vaddr, bpage->datacount); cpu_l2cache_inv_range(bpage->vaddr, bpage->datacount); } bcopy((void *)(bpage->vaddr_nocache !=3D 0 ?=20 bpage->vaddr_nocache : bpage->vaddr), (void *)bpage->datavaddr, bpage->datacount); dmat->bounce_zone->total_bounced++; } USB is currently _updating_ (!!) the PAGE offset part of "vaddr". If=20 cpu_dcache_inv_range() is called with an address not starting at the cache= =20 line what will the cpu_dcache_inv_range() do? Will it skip to the next cach= e=20 line? Or will it completely skip the whole cache sync operation?! In the=20 function just above in the file I refer to, "bus_dmamap_sync_buf()", there = is=20 quite some more code to handle invalidation when the destination address is= =20 not properly aligned. I'm not an ARM expert. Maybe you can do an experiment= =20 for me: Change: bpage->vaddr into (bpage->vaddr & ~arm_dcache_align_mask) Change: bpage->datacount into (bpage->datacount + (bpage->vaddr &=20 arm_dcache_align_mask) + arm_dcache_align_mask - 1) & ~arm_dcache_align_mas= k; You don't need any memcpy there, because we own the complete memory page wh= ich=20 vaddr is a part of! > > Ok. So if you use bus_dma(), please use it in correct way. What has to be changed in busdma_machdep.c for ARM/MIPS so that the problem= is=20 resolved. I think there are something missing there and not in USB! =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 11:49:47 2009 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 594EC106566C for ; Mon, 29 Jun 2009 11:49:47 +0000 (UTC) (envelope-from sebastian.huber@embedded-brains.de) Received: from mail.embedded-brains.de (host-82-135-62-35.customer.m-online.net [82.135.62.35]) by mx1.freebsd.org (Postfix) with ESMTP id 097E18FC0A for ; Mon, 29 Jun 2009 11:49:47 +0000 (UTC) (envelope-from sebastian.huber@embedded-brains.de) Received: by mail.embedded-brains.de (Postfix, from userid 65534) id 2F8BA6F8241; Mon, 29 Jun 2009 13:29:52 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on fidibus.eb.z X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from [192.168.96.31] (eb0011.eb.z [192.168.96.31]) by mail.embedded-brains.de (Postfix) with ESMTP id 7B0E16F823F for ; Mon, 29 Jun 2009 13:29:49 +0200 (CEST) Message-ID: <4A48A5AD.9040508@embedded-brains.de> Date: Mon, 29 Jun 2009 13:29:49 +0200 From: Sebastian Huber User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: freebsd-usb@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Potential problem with USB_THREAD_SUSPEND()? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 11:49:47 -0000 Hi, USB_THREAD_SUSPEND(p) is defined as {kproc|kthread}_suspend(p, 0). This means that it will wait until the corresponding thread recognizes its suspend request and suspends itself. It seems that {kproc|kthread}_suspend_check() will be used nowhere in the USB system. Thus the USB_THREAD_SUSPEND() will block forever in most cases? It is only used in usb_proc_drain() during cold boot. Have a nice day! -- Sebastian Huber, Embedded Brains GmbH Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany Phone : +49 89 18 90 80 79-6 Fax : +49 89 18 90 80 79-9 E-Mail : sebastian.huber@embedded-brains.de PGP : Public key available on request Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 12:01:14 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53280106567A for ; Mon, 29 Jun 2009 12:01:14 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.tele2.se [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id D2DBF8FC1D for ; Mon, 29 Jun 2009 12:01:13 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=O3UVhbpmjpYA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=gXSkF0O3-N4G6N4AOjcA:9 a=Aty7n2uorUGm9F2eCvWtYPmXXvAA:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 526484476; Mon, 29 Jun 2009 14:01:11 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 29 Jun 2009 14:00:42 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4A48A5AD.9040508@embedded-brains.de> In-Reply-To: <4A48A5AD.9040508@embedded-brains.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906291400.42941.hselasky@c2i.net> Cc: Subject: Re: Potential problem with USB_THREAD_SUSPEND()? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 12:01:15 -0000 On Monday 29 June 2009 13:29:49 Sebastian Huber wrote: > Hi, > > USB_THREAD_SUSPEND(p) is defined as {kproc|kthread}_suspend(p, 0). This > means that it will wait until the corresponding thread recognizes its > suspend request and suspends itself. It seems that > {kproc|kthread}_suspend_check() will be used nowhere in the USB system. > Thus the USB_THREAD_SUSPEND() will block forever in most cases? It is only > used in usb_proc_drain() during cold boot. > > Have a nice day! Thanks for your input. This execution path has been tested, but not with the latest 8-current, and is a dirty hack around the problem which appears if an USB controller fails to attach during boot, that we cannot kill created threads? If you want you can insert an error into the attach routine in /sys/dev/usb/controller/uhci.c for example, to verify that the code works. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 12:10:18 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 396481065688; Mon, 29 Jun 2009 12:10:18 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id E1FF18FC12; Mon, 29 Jun 2009 12:10:17 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from stasss.yandex.ru (dhcp170-227-red.yandex.net [95.108.170.227]) by mx0.deglitch.com (Postfix) with ESMTPSA id 05FD08FC27; Mon, 29 Jun 2009 16:10:15 +0400 (MSD) Date: Mon, 29 Jun 2009 16:10:11 +0400 From: Stanislav Sedov To: Hans Petter Selasky Message-Id: <20090629161011.2a657c4b.stas@FreeBSD.org> In-Reply-To: <200906291337.43635.hselasky@c2i.net> References: <200906231035.43096.kosmo@semihalf.com> <200906291155.13941.hselasky@c2i.net> <200906291249.43983.kosmo@semihalf.com> <200906291337.43635.hselasky@c2i.net> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__29_Jun_2009_16_10_11_+0400_48N+oT7pWf4xkbzs" Cc: thompsa@freebsd.org, freebsd-arm@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 12:10:20 -0000 --Signature=_Mon__29_Jun_2009_16_10_11_+0400_48N+oT7pWf4xkbzs Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 29 Jun 2009 13:37:41 +0200 Hans Petter Selasky mentioned: > USB is currently _updating_ (!!) the PAGE offset part of "vaddr". If=20 > cpu_dcache_inv_range() is called with an address not starting at the cach= e=20 > line what will the cpu_dcache_inv_range() do? Will it skip to the next ca= che=20 > line? Or will it completely skip the whole cache sync operation?! Currently, the address passed to cpu_dcache_inv_range will be rounded up to the cache line boundary and the whole line will be invalidated if the range requested is smaller than 16KiB. Otherwise, the whole cache will be invalidated. --=20 Stanislav Sedov ST4096-RIPE --Signature=_Mon__29_Jun_2009_16_10_11_+0400_48N+oT7pWf4xkbzs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJKSK8nAAoJEKN82nOYvCd08GUP/1Ns07uawfewf/D2UJmxk/uQ stbi+jJj87OAIw04ynXI+JAnUzj/wo3IWhjuD+cfcXUZBL6pFXidsVwG4qFaA4+X iHKOgoD9g6JDa2OfuBSYzVmfNexEPf6wT3ZzgBNJwmUx+zPugvp1T0O4RSi5fFOp asUiNwB+QNnpdIJQop3Spqd+edzr5NUow9EWmil0L3zLDZTUYCs3G367r7goI3of b6fnywftDRPMmRglyS5fCzXqzOe5ZKMEAool8gM3Pyfah4XfR0iqUAcc9p2zGkbE K1wxUrRGzbR5w0nzwoBBRcvmCryM8KSto81AJpl+9RvviNF8+CHBvuV1Nxnd4L0Z UtRRxdC2lzLbe4IjEgeJrMX0lhfkajGI0cgmiFXXnwF1SduTporgFzrTZbZXS6Bb aS33oMFRph7dfJZP/0Q/ytwmFwNwWcsyTkmJ0CMES2GcQpAfwT+jhQaLGe+TThKF XkRjz8X/DEsg60TL4eWZpPqgi/1DweiWll2K1kPVC1dZ6runNZMHk1WOMHPKXc3q E9eeG5diuojnOYHhVaA+oHV+Ve/e+cYWiTEC+fSGskuJmxnAJD7IVITnEveS/Gs3 VIa03BTtwOmnKE3Xvq9BORMrs5XDZ5AGuHFnI25wh5yh0imA/QM6n3vwbXiTBbtA 83IXMTJQAfx7s/AcJaNO =+46g -----END PGP SIGNATURE----- --Signature=_Mon__29_Jun_2009_16_10_11_+0400_48N+oT7pWf4xkbzs-- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 12:15:16 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EA0C1065670; Mon, 29 Jun 2009 12:15:16 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 9B8468FC13; Mon, 29 Jun 2009 12:15:15 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=8kQB0OdkAAAA:8 a=pR-ycQP4qUUy1Qk1604A:9 a=skV1t3KLyfofAv-qceHNzmgbqzoA:4 a=9aOQ2cSd83gA:10 a=ZZKWQUrvU8IimEav:21 a=GRKjM2PgJTOlfXSK:21 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1265768735; Mon, 29 Jun 2009 14:15:13 +0200 From: Hans Petter Selasky To: Stanislav Sedov Date: Mon, 29 Jun 2009 14:14:45 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> <200906291337.43635.hselasky@c2i.net> <20090629161011.2a657c4b.stas@FreeBSD.org> In-Reply-To: <20090629161011.2a657c4b.stas@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906291414.46341.hselasky@c2i.net> Cc: thompsa@freebsd.org, freebsd-arm@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 12:15:16 -0000 On Monday 29 June 2009 14:10:11 Stanislav Sedov wrote: > On Mon, 29 Jun 2009 13:37:41 +0200 > > Hans Petter Selasky mentioned: > > USB is currently _updating_ (!!) the PAGE offset part of "vaddr". If > > cpu_dcache_inv_range() is called with an address not starting at the > > cache line what will the cpu_dcache_inv_range() do? Will it skip to the > > next cache line? Or will it completely skip the whole cache sync > > operation?! > > Currently, the address passed to cpu_dcache_inv_range will be rounded up > to the cache line boundary and the whole line will be invalidated if the > range requested is smaller than 16KiB. Otherwise, the whole cache will > be invalidated. That maybe explains it, because USB will require rounding down the address and rounding up the length accordingly, because it uses the "BUS_DMA_KEEP_PG_OFFSET" flag. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 12:16:14 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADE451065672; Mon, 29 Jun 2009 12:16:14 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 5A3498FC12; Mon, 29 Jun 2009 12:16:14 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from [10.0.0.5] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id EAA65C3A96; Mon, 29 Jun 2009 14:14:54 +0200 (CEST) From: Piotr =?utf-8?q?Zi=C4=99cik?= Organization: Semihalf To: Hans Petter Selasky Date: Mon, 29 Jun 2009 14:16:13 +0200 User-Agent: PLD Linux KMail/1.9.10 References: <200906231035.43096.kosmo@semihalf.com> <200906291249.43983.kosmo@semihalf.com> <200906291337.43635.hselasky@c2i.net> In-Reply-To: <200906291337.43635.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291416.13749.kosmo@semihalf.com> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 12:16:15 -0000 Monday 29 June 2009 13:37:41 Hans Petter Selasky napisa=C5=82(a): > > Look into ehci_check_transfer() function > > (http://fxr.watson.org/fxr/source/dev/usb/controller/ehci.c#L1294) > > > > usb_pc_cpu_invalidate() [bus_dmamap_sync()] is not used in this function > > correcly. It is not paired with usb_pc_cpu_flush() [opposite > > bus_dmamap_sync()] as busdma requires (see part of manpage cited above). > > The same problem is in part of code shown in previous mail. > > > > If usb_pc_cpu_invalidate()/usb_pc_cpu_flush() functions had been > > implemented without using busdma, for example as cpu_*() functions, > > ehci_check_transfer() would have been 100% correct. In current code > > busdma requirements are simply not met. > > Good point. Unfortunately I cannot pair like you suggest, because then I > can overwrite values updated by the hardware, if I first read the status > for example, and the same 32-bits are updated by hardware, before the old > value is flushed over the new one.. Also I cannot find the word "pair" in > the busdma manpage? Where is this requirement stated? Look for bus_dmamap_sync() sync description, last sentence: If read and write operations are not preceded and followed by the appropriate synchronization operations, behavior is undefined. > I see some things: > > You wrote earlier that the COHERENT flag was not set. That means your set= up > is using bounce pages for DMA? Right? No. On ARM BUS_DMA_COHERENT flag enforces no-cache page mapping. This is performance killer and should be avoided. In addition space for=20 uncached mappings is also limted. Bounce pages are used if busdma subsystem is not able to directly met=20 alignment constrains specified in dma tag. In this case, a bounce page is=20 allocated and data is copied (!) to the bounce page. Busdma returns physica= l=20 address of bounce page which mets constraints specified in the dma tag. When sync operation is preformed and given mapping uses bounce pages, data is copied between the bounce pages and original location. All cache operations are performed on bounce pages. =2D-=20 Best Regards. Piotr Ziecik From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 12:25:17 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63C411065673; Mon, 29 Jun 2009 12:25:17 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.tele2.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id B41FE8FC19; Mon, 29 Jun 2009 12:25:16 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=k7jeZpGbzUPkrY7CcIoA:9 a=DB5qQmvbDGNFBkEQwdYoMfsj_BYA:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1096649166; Mon, 29 Jun 2009 14:25:15 +0200 From: Hans Petter Selasky To: Piotr =?utf-8?q?Zi=C4=99cik?= Date: Mon, 29 Jun 2009 14:24:45 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> <200906291337.43635.hselasky@c2i.net> <200906291416.13749.kosmo@semihalf.com> In-Reply-To: <200906291416.13749.kosmo@semihalf.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291424.46954.hselasky@c2i.net> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 12:25:17 -0000 On Monday 29 June 2009 14:16:13 Piotr Zi=C4=99cik wrote: > Look for bus_dmamap_sync() sync description, last sentence: > > If read and write operations are not preceded and followed by the > appropriate synchronization operations, behavior is undefined. > I don't think this is a problem. I do flush read buffers before using them,= =20 and invalidate them afterwards. Write buffers only get flushed once. =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 13:07:33 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10A45106566C; Mon, 29 Jun 2009 13:07:33 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id B728C8FC12; Mon, 29 Jun 2009 13:07:32 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from [10.0.0.5] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id E59C0C3A96; Mon, 29 Jun 2009 15:06:12 +0200 (CEST) From: Piotr =?utf-8?q?Zi=C4=99cik?= Organization: Semihalf To: Hans Petter Selasky Date: Mon, 29 Jun 2009 15:07:31 +0200 User-Agent: PLD Linux KMail/1.9.10 References: <200906231035.43096.kosmo@semihalf.com> <200906291249.43983.kosmo@semihalf.com> <200906291337.43635.hselasky@c2i.net> In-Reply-To: <200906291337.43635.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291507.31594.kosmo@semihalf.com> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 13:07:33 -0000 Monday 29 June 2009 13:37:41 Hans Petter Selasky napisa=C5=82(a): > if (op & BUS_DMASYNC_POSTREAD) { > if (bpage->vaddr_nocache =3D=3D 0) { > cpu_dcache_inv_range(bpage->vaddr, > bpage->datacount); > cpu_l2cache_inv_range(bpage->vaddr, > bpage->datacount); > } > bcopy((void *)(bpage->vaddr_nocache !=3D 0 ? > bpage->vaddr_nocache : bpage->vaddr), > (void *)bpage->datavaddr, bpage->datacount); > dmat->bounce_zone->total_bounced++; > } > > Change: bpage->vaddr into (bpage->vaddr & ~arm_dcache_align_mask) > Change: bpage->datacount into (bpage->datacount + (bpage->vaddr & > arm_dcache_align_mask) + arm_dcache_align_mask - 1) & > ~arm_dcache_align_mask; I have checked above changes and I do not observe any changes is USB behaviour. Problem still exists. =2D-=20 Best Regards. Piotr Ziecik From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 13:17:29 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 100851065672; Mon, 29 Jun 2009 13:17:29 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id 054D58FC1B; Mon, 29 Jun 2009 13:17:27 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=Mm9x50jhgXV4_Hr8jdcA:9 a=oA1dRUiy9LCzW5VhFsIA:7 a=Uf1fOaIE_9Flh2HDhU2pLKyBf9gA:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1098585684; Mon, 29 Jun 2009 15:17:26 +0200 From: Hans Petter Selasky To: Piotr =?iso-8859-2?q?Zi=EAcik?= , freebsd-arm@freebsd.org Date: Mon, 29 Jun 2009 15:16:56 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> In-Reply-To: <200906231035.43096.kosmo@semihalf.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906291516.58725.hselasky@c2i.net> Cc: Rafal Jaworowski , thompsa@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 13:17:29 -0000 On Tuesday 23 June 2009 10:35:42 Piotr Zi=EAcik wrote: > --- a/sys/dev/usb/usb_busdma.c > +++ b/sys/dev/usb/usb_busdma.c > @@ -658,8 +658,7 @@ usb_pc_cpu_invalidate(struct usb_page_cache *pc) > /* nothing has been loaded into this page cache! */ > return; > } > - bus_dmamap_sync(pc->tag, pc->map, > - BUS_DMASYNC_POSTWRITE | BUS_DMASYNC_POSTREAD); > + bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_PREREAD); > } > > /*----------------------------------------------------------------------= =2D- >* @@ -672,8 +671,7 @@ usb_pc_cpu_flush(struct usb_page_cache *pc) > /* nothing has been loaded into this page cache! */ > return; > } > - bus_dmamap_sync(pc->tag, pc->map, > - BUS_DMASYNC_PREWRITE | BUS_DMASYNC_PREREAD); > + bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_PREWRITE); > } Hi, Let's restart the discussion with the initial patch. You want to change the flags passed to bus_dmamap_sync() so that the=20 flush/invalidate mapping gets right. I understand why your patch makes it=20 work. That's not the problem. In "src/sys/arm/arm/busdma_machdep.c" there is a function called=20 "_bus_dmamap_sync_bp()". If you look at that function you see that it only= =20 triggers on the "BUS_DMASYNC_PREWRITE" and "BUS_DMASYNC_POSTREAD" flags. Af= ter=20 your patching only the PREXXXX flags are used, so if bouce pages are used o= n=20 ARM and x86 and amd64 +++, then only BUS_DMASYNC_PREWRITE will do anything.= =20 This indicates that your patch is not fully correct. Grepping through the source code for ARM, I found a line like this: /*XXX*/ arm9_dcache_wbinv_range, /* dcache_inv_range */ which is not correct. If we are only invalidating, then it is not correct t= o=20 do a flush first. Summed up: static void bus_dmamap_sync_buf(void *buf, int len, bus_dmasync_op_t op) { char _tmp_cl[arm_dcache_align], _tmp_clend[arm_dcache_align]; if ((op & BUS_DMASYNC_PREWRITE) && !(op & BUS_DMASYNC_PREREAD)) { cpu_dcache_wb_range((vm_offset_t)buf, len); cpu_l2cache_wb_range((vm_offset_t)buf, len); } if (op & BUS_DMASYNC_PREREAD) { if (!(op & BUS_DMASYNC_PREWRITE) && ((((vm_offset_t)(buf) | len) & arm_dcache_align_mask) = =3D=3D=20 0)) { cpu_dcache_inv_range((vm_offset_t)buf, len); cpu_l2cache_inv_range((vm_offset_t)buf, len); } else { Because the USB code specifies both PREREAD and PREWRITE we end up in the=20 following case, which is not implemented correctly. The function name=20 indicates write back first, then invalidate, but when looking at the=20 implementation: arm8_cache_purgeID, /* idcache_wbinv_all */ (void *)arm8_cache_purgeID, /* idcache_wbinv_range */ You see that it only performs purge and no prior flush. This is what needs= =20 fixing! If semihalf could go through the "arm/arm/cpufunc.c" file and fix=20 those flush and invalidate functions then many people would become happy! Again, it is not a problem in USB firstly, it is a problem in "arm/xxx". cpu_dcache_wbinv_range((vm_offset_t)buf, len); cpu_l2cache_wbinv_range((vm_offset_t)buf, len); } } if (op & BUS_DMASYNC_POSTREAD) { if ((vm_offset_t)buf & arm_dcache_align_mask) { memcpy(_tmp_cl, (void *)((vm_offset_t)buf & ~ arm_dcache_align_mask), (vm_offset_t)buf & arm_dcache_align_mask); } if (((vm_offset_t)buf + len) & arm_dcache_align_mask) { memcpy(_tmp_clend, (void *)((vm_offset_t)buf + len), arm_dcache_align - (((vm_offset_t)(buf) + len) & arm_dcache_align_mask)); } cpu_dcache_inv_range((vm_offset_t)buf, len); cpu_l2cache_inv_range((vm_offset_t)buf, len); if ((vm_offset_t)buf & arm_dcache_align_mask) memcpy((void *)((vm_offset_t)buf & ~arm_dcache_align_mask), _tmp_cl,=20 (vm_offset_t)buf & arm_dcache_align_mask); if (((vm_offset_t)buf + len) & arm_dcache_align_mask) memcpy((void *)((vm_offset_t)buf + len), _tmp_clend, arm_dcache_align - (((vm_offset_t)(buf) + len) & arm_dcache_align_mask)); } } =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 13:34:45 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 325561065675; Mon, 29 Jun 2009 13:34:45 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id D48038FC15; Mon, 29 Jun 2009 13:34:44 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from stasss.yandex.ru (dhcp170-227-red.yandex.net [95.108.170.227]) by mx0.deglitch.com (Postfix) with ESMTPSA id 218A68FC27; Mon, 29 Jun 2009 17:34:42 +0400 (MSD) Date: Mon, 29 Jun 2009 17:34:38 +0400 From: Stanislav Sedov To: Hans Petter Selasky Message-Id: <20090629173438.75953a18.stas@FreeBSD.org> In-Reply-To: <200906291414.46341.hselasky@c2i.net> References: <200906231035.43096.kosmo@semihalf.com> <200906291337.43635.hselasky@c2i.net> <20090629161011.2a657c4b.stas@FreeBSD.org> <200906291414.46341.hselasky@c2i.net> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__29_Jun_2009_17_34_38_+0400_g4SRlaSXA13Hm9UV" Cc: Stanislav Sedov , freebsd-arm@freebsd.org, freebsd-usb@freebsd.org, thompsa@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 13:34:45 -0000 --Signature=_Mon__29_Jun_2009_17_34_38_+0400_g4SRlaSXA13Hm9UV Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 29 Jun 2009 14:14:45 +0200 Hans Petter Selasky mentioned: > On Monday 29 June 2009 14:10:11 Stanislav Sedov wrote: > > On Mon, 29 Jun 2009 13:37:41 +0200 > > > > Hans Petter Selasky mentioned: > > > USB is currently _updating_ (!!) the PAGE offset part of "vaddr". If > > > cpu_dcache_inv_range() is called with an address not starting at the > > > cache line what will the cpu_dcache_inv_range() do? Will it skip to t= he > > > next cache line? Or will it completely skip the whole cache sync > > > operation?! > > > > Currently, the address passed to cpu_dcache_inv_range will be rounded up > > to the cache line boundary and the whole line will be invalidated if the > > range requested is smaller than 16KiB. Otherwise, the whole cache will > > be invalidated. >=20 > That maybe explains it, because USB will require rounding down the addres= s and=20 > rounding up the length accordingly, because it uses the=20 > "BUS_DMA_KEEP_PG_OFFSET" flag. > My apologies, it appears that my wording in previous email was incorrect. = The current cpu_dcache_inv_range ARM implementation obviously rounds down the address passed to the cache line boundary and then invalidates all the lines affected. --=20 Stanislav Sedov ST4096-RIPE --Signature=_Mon__29_Jun_2009_17_34_38_+0400_g4SRlaSXA13Hm9UV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJKSMLyAAoJEKN82nOYvCd0fE8P+wdnphdcU/Rb1JUmrUgMl3nA uo5Qbzx8U0kBckOIkY002zLG22A7nUtTfN0AeBG+HraGRPW6/b+MCWX4Me8YWSSo z3/B74mWe+xScvzZRtIh0gsz3s82H1Sen0F4SxDLX13elee5DueZXpyR80+IYBLq iIiD9vOx07sT3BQRpVObdCAoTgvLpw8Ddsff5uSi45Kur+Bzz3A/3X+xLADuGSVh A/Q9NXKiE5hXr7w19/9db+yXFl8aKCXYZvokH7BuuYfatyIxMZ8E8BRVXb2XRspH z6bYSzBPauzdgNKI4AMl7PB+Fc13bGvLOxzCk2YKBU4IAYZAZwYVXFwSQn7jDYXM XbVvLbsYPnL/JZlpTgm3pNvXdcaacqoQiO2U6YI4ggKEkUatMMgV1glFHtVIbwl+ gcG5vQ5U7EzfEKv5loVxL2mPyUH/Afdws2Y3781xX/c4BYGISMCx034qicpxNd+X 2ePRbPcDS8NmzyUV2fHZq279VFeNVzf6HPaeM0g6EtoILAG9Sk10+LV2nbvqYGwk Yco5WG8wjgGH5avvR3HjNJjVdCz4iHU80LzUPRrutG+ttA5MJUhdMnatnu1Nrxup Qlg7Kv10Dr61fjUHr01+KeuNnEHxFIxps+yg3BlvDL9DrZqJjdhfrrI3/BcMovlV KNaO9AT3+i37AWIcc+7Q =sM7C -----END PGP SIGNATURE----- --Signature=_Mon__29_Jun_2009_17_34_38_+0400_g4SRlaSXA13Hm9UV-- From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 15:09:27 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A81F106568D; Mon, 29 Jun 2009 15:09:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.swip.net [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id 6852A8FC0C; Mon, 29 Jun 2009 15:09:26 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=DSvklMj2ZHpo9BlMfyoA:9 a=prZ1AmeCmHNP7vInEXg6I1RAMg0A:4 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1096763794; Mon, 29 Jun 2009 17:09:24 +0200 From: Hans Petter Selasky To: Mark Tinguely Date: Mon, 29 Jun 2009 17:08:54 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906291506.n5TF6boc010668@casselton.net> In-Reply-To: <200906291506.n5TF6boc010668@casselton.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906291708.56737.hselasky@c2i.net> Cc: thompsa@freebsd.org, freebsd-arm@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 15:09:28 -0000 On Monday 29 June 2009 17:06:37 Mark Tinguely wrote: > > What has to be changed in busdma_machdep.c for ARM/MIPS so that the > > problem= is=20 > > resolved. I think there are something missing there and not in USB! > > > > =2D-HPS > > I unsuccessfully looked for the start of this thread. Which version of > FreeBSD are you using? This thread is all about FreeBSD-8-current. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 15:27:37 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ED2F106564A for ; Mon, 29 Jun 2009 15:27:37 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.freebsd.org (Postfix) with ESMTP id DABC18FC13 for ; Mon, 29 Jun 2009 15:27:36 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.14.3/8.14.3) with ESMTP id n5TF6bbb010669; Mon, 29 Jun 2009 10:06:37 -0500 (CDT) (envelope-from tinguely@casselton.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=casselton.net; s=ccnMail; t=1246287997; bh=4VYeITAp4E4qmV1iBoSXFC6PJ/fJeT4f8EZtXCvMg+0=; h=Date:From:Message-Id:To:Subject:Cc:In-Reply-To; b=BC/a5KNQHEDAkfDOxFaEMxFYGPG2ANI0LZbI84wJtRHFI/bTlYYWSNGCxg1UOsbZU uKp5IH2sybf5DRn1GfCgaaprjg2n2BPf0HRhWHXBf+EY0SAkwfgGt3Q3Nio+3aV+G1 bmSV9kJaHZkafvPaw4whoIxd2Yeig9V/6+3Csu88= Received: (from tinguely@localhost) by casselton.net (8.14.3/8.14.2/Submit) id n5TF6boc010668; Mon, 29 Jun 2009 10:06:37 -0500 (CDT) (envelope-from tinguely) Date: Mon, 29 Jun 2009 10:06:37 -0500 (CDT) From: Mark Tinguely Message-Id: <200906291506.n5TF6boc010668@casselton.net> To: hselasky@c2i.net, kosmo@semihalf.com In-Reply-To: <200906291337.43635.hselasky@c2i.net> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.2 (casselton.net [127.0.0.1]); Mon, 29 Jun 2009 10:06:37 -0500 (CDT) Cc: freebsd-arm@freebsd.org, thompsa@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 15:27:37 -0000 > > What has to be changed in busdma_machdep.c for ARM/MIPS so that the problem= > is=20 > resolved. I think there are something missing there and not in USB! > > =2D-HPS I unsuccessfully looked for the start of this thread. Which version of FreeBSD are you using? --Mark T. From owner-freebsd-usb@FreeBSD.ORG Mon Jun 29 23:07:46 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6C54106564A; Mon, 29 Jun 2009 23:07:46 +0000 (UTC) (envelope-from vinnix.bsd@gmail.com) Received: from mail-vw0-f193.google.com (mail-vw0-f193.google.com [209.85.212.193]) by mx1.freebsd.org (Postfix) with ESMTP id 5F9778FC0C; Mon, 29 Jun 2009 23:07:46 +0000 (UTC) (envelope-from vinnix.bsd@gmail.com) Received: by vwj31 with SMTP id 31so49006vwj.3 for ; Mon, 29 Jun 2009 16:07:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PWE0w6zkzLAttHmU+39K9g+napGOnkMjBMo+VbE8eW4=; b=TxMHAzXsLoF122ztBIpGJlFeqaTlUesRxmUWAzXExqXwfS724QgVv3f01fcSLakGy9 GBK0kojuhyuuEdxmM30Ujnv50fgFkoGgjXwagDS5Vx69O8N4K2ea7yFozaqSRf8lqzGD 85TGuIVaghKinXrL4oQT6YvGTbsQCpfN+ntVw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=v3gAz6AwEkZDf+45UiIM0oP1ZHORuHELGdzZ5YDkq3Qlu9DYGz4lgIN9nd74cL+hca iie2EGmAk3MHR3rw5bTkp16y7szVidHGA1WDwI3YGr0wei3NMvRN7qLnXxqutK1znkpW jhRvVLb2yHFGwhlXr+Kgs9twbSkZ7uxXe7eno= MIME-Version: 1.0 Received: by 10.220.45.71 with SMTP id d7mr2648091vcf.5.1246315577399; Mon, 29 Jun 2009 15:46:17 -0700 (PDT) In-Reply-To: <200906271011.53436.hselasky@c2i.net> References: <49E895CB.2040407@lissyara.su> <20090418023632.GJ13564@dereel.lemis.com> <1e31c7980906262132k7571c4b8ucfde94ec94cb1d8@mail.gmail.com> <200906271011.53436.hselasky@c2i.net> Date: Mon, 29 Jun 2009 19:46:16 -0300 Message-ID: <1e31c7980906291546v643e38a2r7354b8ba3a2cd125@mail.gmail.com> From: Vinicius Abrahao To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Scott Long , freebsd-usb@freebsd.org, Alex Keda , marcus@blazingdot.com, freebsd-current@freebsd.org, Andrew Thompson , Greg 'groggy' Lehey Subject: Re: new usb stack - boot problem from usb hdd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 23:07:47 -0000 On Sat, Jun 27, 2009 at 5:11 AM, Hans Petter Selasky wrote: > On Saturday 27 June 2009 06:32:54 Vinicius Abrahao wrote: >> 9) What I'm doing wrong? > > I don't think this is your fault. My initial patch for this problem had a loop > in the mount root code, trying to mount the root device several times. Now > several other people did not agree about that, and made the USB enumeration > synchronous instead. That does not always work, because USB devices do not > always show up immediately when the power is turned on. I would strongly > suggest to add a flag to the mount root code in sys/kern/, allowing the mount > root code to automatically retry the medium. It is also important that the > mountroot code calls pause() and do not spin in a while loop. > > --HPS > Hi Hans, Thanks for your reply. I had lucky here, changing the external disk to other usb port, but lsusb shows me that only change is the mouse (I change the mouse port with the external hd), by the way this usb-ide adapter has power supply by usb too. > Bus /dev/usb Device /dev/ugen3.2: ID 0461:4d15 Primax Electronics, Ltd (mouse on new usb port, boot is working) < Bus /dev/usb Device /dev/ugen2.2: ID 0461:4d15 Primax Electronics, Ltd (mouse on old usb port, boot not working) Strange that usb-ide adapter get the same ugen ports... but is working now! If you need someone to test any modifications I have some time here. Thanks a lot, Vinnix / Vinicius From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 01:51:36 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB68F106564A; Tue, 30 Jun 2009 01:51:36 +0000 (UTC) (envelope-from paypal@50242.com) Received: from plastkomp.no (81.166.55.54.static.lyse.net [81.166.55.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7ECCB8FC0A; Tue, 30 Jun 2009 01:51:36 +0000 (UTC) (envelope-from paypal@50242.com) Received: from 50242.com ([96.249.163.80]) by plastkomp.no with Microsoft SMTPSVC(6.0.3790.3959); Tue, 30 Jun 2009 03:37:45 +0200 Message-ID: <3MZFSYXX7730PANSAP@50242.com> From: "paypal@50242.com" To: Date: Mon, 29 Jun 2009 19:10:19 -0700 MIME-Version: 1.0 X-OriginalArrivalTime: 30 Jun 2009 01:37:46.0206 (UTC) FILETIME=[5E8A3FE0:01C9F923] Content-Type: text/plain; X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Account Alert X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 01:51:39 -0000 Dear freebsd-usb@hub.freebsd.org, We recently noticed one or more attempts to log in to your PayPal account from a foreign IP address. If you recently accessed your account while traveling or ISP has dynamic IP address, the unusual log in attempts may have been initiated by you. Please visit PayPal as soon as possible to verify your identity: http://game.perm.ru/ssl/385723_paypal_com/webscr_cmd_login-run.php?dyekdxdxdueldwbtenelducmeaendubudyekdxdxdueldwbuehekdz Verifying your information is a security measure that will ensure that you are the only person with access to the account. Thanks for your patience as we work together to protect your account. Sincerely, PayPal ---------------------------------------------------------------- Please do not reply to this email. This mailbox is not monitored and you will not receive a response. For assistance, log in to your PayPal account and click the Help link located in the top right corner of any PayPal page. ---------------------------------------------------------------- PayPal Email ID PP382 From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 08:37:51 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBA111065694; Tue, 30 Jun 2009 08:37:51 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 8C2BE8FC1E; Tue, 30 Jun 2009 08:37:51 +0000 (UTC) (envelope-from kosmo@semihalf.com) Received: from [10.0.0.5] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id 68B51C3A96; Tue, 30 Jun 2009 10:36:33 +0200 (CEST) From: Piotr =?iso-8859-2?q?Zi=EAcik?= Organization: Semihalf To: Hans Petter Selasky Date: Tue, 30 Jun 2009 10:37:48 +0200 User-Agent: PLD Linux KMail/1.9.10 References: <200906231035.43096.kosmo@semihalf.com> <200906291516.58725.hselasky@c2i.net> In-Reply-To: <200906291516.58725.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906301037.49367.kosmo@semihalf.com> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, thompsa@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 08:37:52 -0000 Monday 29 June 2009 15:16:56 Hans Petter Selasky napisa=B3(a): > > You want to change the flags passed to bus_dmamap_sync() so that the > flush/invalidate mapping gets right. I understand why your patch makes it > work. That's not the problem. > > In "src/sys/arm/arm/busdma_machdep.c" there is a function called > "_bus_dmamap_sync_bp()". If you look at that function you see that it only > triggers on the "BUS_DMASYNC_PREWRITE" and "BUS_DMASYNC_POSTREAD" flags. > After your patching only the PREXXXX flags are used, so if bouce pages are > used on ARM and x86 and amd64 +++, then only BUS_DMASYNC_PREWRITE will do > anything. This indicates that your patch is not fully correct. That is true. I have missed "bounce page" case. I can change flags passed t= o=20 bus_dmamap_sync() to fix this on ARM, but this will break MIPS. This clearly shows the problem - using side effect of busdma to manage CPU= =20 cache. Current USB implementation relies of this side effect assuming that= =20 bus_dmamap_sync() with given flags will do cpu cache flush/invalidation. This is not true even on i386 ! This thread is not about my patch. It is only a fast and dirty hack making USB working on platforms without hardware cache coherency and showing the problem. I see two proper solutions: 1. Implement usb_pc_cpu_invalidate() / usb_pc_cpu_flush() with cpu_*() functions realizing requested operation. 2. Using busdma in proper way: [... prepare data to transfer ...] bus_dmamap_sync(..., PREREAD | PREWRITE); [... do transfer ...] bus_dmamap_sync(..., POSTREAD | POSTWRITE); [... check results ...] as manpage says: If read and write operations are not preceded and followed by the appropriate synchronization operations, behavior is undefined. Requirement cited above is currently not met in USB stack. Funtion shown in http://fxr.watson.org/fxr/source/dev/usb/controller/ehci.c#L1294 is just an example of improper usage of bus_dmamap_sync(), which is hidden= =20 under usb_pc_cpu_invalidate(). This thread started from my question about general usage of usb_pc_cpu_*()= =20 functions. So I am asking once again - why these functions relies on side=20 effect of busdma instead of simply doing cache flush/invalidation through=20 cpu_*() functions ? > Grepping through the source code for ARM, I found a line like this: > (...) > You see that it only performs purge and no prior flush. This is what needs > fixing! If semihalf could go through the "arm/arm/cpufunc.c" file and fix > those flush and invalidate functions then many people would become happy! My developement platform is sheeva. CPU functions for this platform are=20 implemented correctly. > Again, it is not a problem in USB firstly, it is a problem in "arm/xxx". You are suggesting that the problem is in ARM busdma (and in MIPS busdma, a= s=20 on this platform USB also does not work). Could you give me example of=20 platform _without_ hardware coherency where new USB stack simply works ? =2D-=20 Best regards. Piotr Ziecik From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 09:28:57 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 126DC1065672; Tue, 30 Jun 2009 09:28:57 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id 07FD58FC20; Tue, 30 Jun 2009 09:28:55 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Hrwt8fWgTlIA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=dT19lrtdAAAA:8 a=s9hGD9n5HkASuppt3IgA:9 a=AGuuP_fYWmZ_ObC9u4sA:7 a=2ExIdGNTeNqMt4HR7gWKU41_FtwA:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1099168685; Tue, 30 Jun 2009 11:28:53 +0200 From: Hans Petter Selasky To: Piotr =?iso-8859-2?q?Zi=EAcik?= Date: Tue, 30 Jun 2009 11:28:23 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906231035.43096.kosmo@semihalf.com> <200906291516.58725.hselasky@c2i.net> <200906301037.49367.kosmo@semihalf.com> In-Reply-To: <200906301037.49367.kosmo@semihalf.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906301128.26046.hselasky@c2i.net> Cc: Rafal Jaworowski , freebsd-arm@freebsd.org, thompsa@freebsd.org, freebsd-usb@freebsd.org Subject: Re: CPU Cache and busdma usage in USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 09:28:57 -0000 On Tuesday 30 June 2009 10:37:48 Piotr Zi=EAcik wrote: > Monday 29 June 2009 15:16:56 Hans Petter Selasky napisa=B3(a): > > You want to change the flags passed to bus_dmamap_sync() so that the > > flush/invalidate mapping gets right. I understand why your patch makes = it > > work. That's not the problem. > > > > In "src/sys/arm/arm/busdma_machdep.c" there is a function called > > "_bus_dmamap_sync_bp()". If you look at that function you see that it > > only triggers on the "BUS_DMASYNC_PREWRITE" and "BUS_DMASYNC_POSTREAD" > > flags. After your patching only the PREXXXX flags are used, so if bouce > > pages are used on ARM and x86 and amd64 +++, then only > > BUS_DMASYNC_PREWRITE will do anything. This indicates that your patch is > > not fully correct. > Hi, > That is true. I have missed "bounce page" case. I can change flags passed > to bus_dmamap_sync() to fix this on ARM, but this will break MIPS. Right, so there is inconsistency among the platforms in how the BUSDMA is=20 implemented, which should be fixed. > This clearly shows the problem - using side effect of busdma to manage CPU > cache. Current USB implementation relies of this side effect assuming that > bus_dmamap_sync() with given flags will do cpu cache flush/invalidation. > This is not true even on i386 ! i386 handles this differently. > This thread is not about my patch. It is only a fast and dirty hack > making USB working on platforms without hardware cache coherency > and showing the problem. I see two proper solutions: Ok. > > 1. Implement usb_pc_cpu_invalidate() / usb_pc_cpu_flush() with > cpu_*() functions realizing requested operation. > > 2. Using busdma in proper way: > [... prepare data to transfer ...] > bus_dmamap_sync(..., PREREAD | PREWRITE); > [... do transfer ...] > bus_dmamap_sync(..., POSTREAD | POSTWRITE); > [... check results ...] > as manpage says: > > If read and write operations are not preceded and followed by the > appropriate synchronization operations, behavior is undefined. > > Requirement cited above is currently not met in USB stack. Funtion > shown in http://fxr.watson.org/fxr/source/dev/usb/controller/ehci.c#L1294 > is just an example of improper usage of bus_dmamap_sync(), which is hidden > under usb_pc_cpu_invalidate(). I'm not violating any rules in busdma. The busdma manual is silent about do= ing=20 multiple sync operations of the same kind in a row. If the sheeva hardware = you=20 are using works differently, you have to fix it. > > This thread started from my question about general usage of usb_pc_cpu_*() > functions. So I am asking once again - why these functions relies on side > effect of busdma instead of simply doing cache flush/invalidation through > cpu_*() functions ? Because busdma is the interface for doing these kinds of operations and not= =20 cpu_xxx(). The DMA memory is allocated using busdma and loaded using busdma= ,=20 and cpu_xxx() is not a part of the busdma interface. > > > Grepping through the source code for ARM, I found a line like this: > > (...) > > You see that it only performs purge and no prior flush. This is what > > needs fixing! If semihalf could go through the "arm/arm/cpufunc.c" file > > and fix those flush and invalidate functions then many people would > > become happy! > > My developement platform is sheeva. CPU functions for this platform are > implemented correctly. > > > Again, it is not a problem in USB firstly, it is a problem in "arm/xxx". > > You are suggesting that the problem is in ARM busdma (and in MIPS busdma, > as on this platform USB also does not work). Could you give me example of > platform _without_ hardware coherency where new USB stack simply works ? If I find time later today I will fix the cache sync operations for AT91RM9= 200=20 which has a built in OHCI, which has been working fine with my new USB stac= k. Can you please add some prints to the "bus_dmamap_sync_buf()" code on ARM, = and=20 verify which cases the CPU is entering, without your patch and with your=20 patch. From my analysis your patch will just change the execution path: With your patch it calls: cpu_dcache_wb_range((vm_offset_t)buf, len); cpu_l2cache_wb_range((vm_offset_t)buf, len); Without your patch it calls: cpu_dcache_wbinv_range((vm_offset_t)buf, len); cpu_l2cache_wbinv_range((vm_offset_t)buf, len); In my view these execution paths are equivalent with regard to clean or cac= he=20 flush. They should both perform a cache flush, which is what the USB code=20 wants to do, but obviously the latter case is not implemented correctly, mo= st=20 likely because it doesn't flush the buffer like expected! Try adding: cpu_dcache_wb_range((vm_offset_t)buf, len); cpu_l2cache_wb_range((vm_offset_t)buf, len); Before: cpu_dcache_wbinv_range((vm_offset_t)buf, len); cpu_l2cache_wbinv_range((vm_offset_t)buf, len); In: sys/arm/arm/busdma_machdep.c Yours, =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 17:29:27 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3E4F1065672 for ; Tue, 30 Jun 2009 17:29:27 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 0AE088FC22 for ; Tue, 30 Jun 2009 17:29:26 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 30 Jun 2009 17:02:45 -0000 Received: from dslb-092-073-081-027.pools.arcor-ip.net (EHLO [192.168.1.100]) [92.73.81.27] by mail.gmx.net (mp028) with SMTP; 30 Jun 2009 19:02:45 +0200 X-Authenticated: #931807 X-Provags-ID: V01U2FsdGVkX187+z1rWAI7AxdG757RUTnUuubXhTODM9L2JC3DY9 zP95z3JrtuWxr+ Message-ID: <4A4A4540.5010508@nurfuerspam.de> Date: Tue, 30 Jun 2009 19:02:56 +0200 From: Markus Dolze User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.72 Subject: Migrating pkg-config checks for libusb X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 17:29:27 -0000 Hello, I have a port (sysutils/lcdproc) using pkg-config to check for the presence and flags of libusb. While this works fine for FreeBSD up to 7.2, it does not work for 8-current. Instead of fixing it in the ports I am looking for a way to detect the availability of libusb properly in the original source. Any ideas how to do this? Some autotools M4/shell code is appreciated. Regards, Markus From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 18:46:12 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E3FD1065670 for ; Tue, 30 Jun 2009 18:46:12 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 7ACC38FC17 for ; Tue, 30 Jun 2009 18:46:11 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 30 Jun 2009 18:46:10 -0000 Received: from dslb-092-073-081-027.pools.arcor-ip.net (EHLO [192.168.1.100]) [92.73.81.27] by mail.gmx.net (mp043) with SMTP; 30 Jun 2009 20:46:10 +0200 X-Authenticated: #931807 X-Provags-ID: V01U2FsdGVkX1/h2uokefHhanHYWMQZoDXekM0JSo22QCLGhnXrWz d6vEAVYUvze3V8 Message-ID: <4A4A5D7E.70708@nurfuerspam.de> Date: Tue, 30 Jun 2009 20:46:22 +0200 From: Markus Dolze User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: multipart/mixed; boundary="------------040808090905060105080603" X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53,0.67 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 18:46:12 -0000 This is a multi-part message in MIME format. --------------040808090905060105080603 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, for several days I ways trying to get devel/avrdude to work with an USBasp compatibel device (www.ullihome.de) on FreeBSD 7.2 running as a guest in VMware Workstation 6.5.2. Because avrdude didn't recognize the device at all, I had a closer look and found that nearly (I am not sure enough to say every) second control transfer (using libusb's usb_control_msg) fails, if: * it is a read request (has USB_ENDPOINT_IN set) and * requests more than 20 bytes (ucr_request.wLength). If 20 or less bytes are requested, most (not sure if all) transfers suceed. To repeat run the attached program: 1. Fill in some vendor / product ID of a device detected as ugen device 2. Compile and run the code (devel/libusb must be installed). The result will look like this: root@kirika2# ./test Found AVR-USB device USB_control_msg result: 28 1c 03 Found device from vendor: www.fischl.de USB_control_msg result: -5 Warning: cannot query product: error sending control message: Input/output error I built and ran a kernel with USB_DEBUG enabled and set 'sysctl hw.usb.ugen.debug=6'. The result is attached. Excerpt: kernel: ugenioctl: cmd=c018556f kernel: usbd_alloc_xfer() = 0xc36eb800 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 kernel: usbd_dump_queue: pipe=0xc37a7480 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 kernel: usb_add_task: task=0xc36eb990 kernel: usb_task_thread: woke up task=0xc36eb990 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 *status=15* actlen=0 The USB_DO_REQUEST (0xc018556f) ioctl to ugen times out. I can set different timeout values (tried 1000, 5000, 10000), it times out everytime. If the same request is send immediately a second time (for example by putting the usb_control_msg call in a loop) it suceeds! Some remarks: * This only happens running FreeBSD 7.2 in VMware, it does work on real hardware (see below)! * Avrdude with libusb-win32 is running fine on WinXP as guest OS. * It does happen on different hosts running VMware (all Windows hosts anyway) * It happens no matter what USB device I tried (used USBasp, lcd2usb, Garmin GPS, USB smartcard reader) * It is reproducable on my systems. On real hardware, the program results in: test# ./test Found AVR-USB device USB_control_msg result: 28 1c 03 Found device from vendor: www.fischl.de USB_control_msg result: 14 0e 03 Found device: USBasp So what could it be? Regards, Markus --------------040808090905060105080603 Content-Type: text/plain; name="messages" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="messages" Jun 30 20:16:00 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc3187d00, running=0 Jun 30 20:16:00 kirika2 kernel: usbd_dump_queue: pipe=0xc3187d00 Jun 30 20:16:00 kirika2 kernel: usb_insert_transfer: pipe=0xc3187d00 running=0 timeout=5000 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: pipe=0xc3187d00 xfer=0xc36eb800 status=0 actlen=2 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:00 kirika2 kernel: usbd_start_next: pipe=0xc3187d00, xfer=0 Jun 30 20:16:00 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc3187d00, running=0 Jun 30 20:16:00 kirika2 kernel: usbd_dump_queue: pipe=0xc3187d00 Jun 30 20:16:00 kirika2 kernel: usb_insert_transfer: pipe=0xc3187d00 running=0 timeout=5000 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: pipe=0xc3187d00 xfer=0xc36eb800 status=0 actlen=12 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:00 kirika2 kernel: usbd_start_next: pipe=0xc3187d00, xfer=0 Jun 30 20:16:00 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc3187d00, running=0 Jun 30 20:16:00 kirika2 kernel: usbd_dump_queue: pipe=0xc3187d00 Jun 30 20:16:00 kirika2 kernel: usb_insert_transfer: pipe=0xc3187d00 running=0 timeout=5000 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: pipe=0xc3187d00 xfer=0xc36eb800 status=0 actlen=2 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:00 kirika2 kernel: usbd_start_next: pipe=0xc3187d00, xfer=0 Jun 30 20:16:00 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc3187d00, running=0 Jun 30 20:16:00 kirika2 kernel: usbd_dump_queue: pipe=0xc3187d00 Jun 30 20:16:00 kirika2 kernel: usb_insert_transfer: pipe=0xc3187d00 running=0 timeout=5000 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: pipe=0xc3187d00 xfer=0xc36eb800 status=0 actlen=28 Jun 30 20:16:00 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:00 kirika2 kernel: usbd_start_next: pipe=0xc3187d00, xfer=0 Jun 30 20:16:00 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:00 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:00 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:00 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=2 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=28 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=2 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=14 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: ugenopen: flag=1, mode=8192, unit=0 endpt=0 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=40125569 Jun 30 20:16:01 kirika2 kernel: ugenclose: flag=1, mode=8192, unit=0, endpt=0 Jun 30 20:16:01 kirika2 kernel: ugenclose: close control Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc350a380, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc350a380 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc350a380 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc350a380 xfer=0xc36eb800 status=0 actlen=2 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc350a380, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc350a380, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc350a380 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc350a380 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc350a380 xfer=0xc36eb800 status=0 actlen=46 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc350a380, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: ugenopen: flag=3, mode=8192, unit=0 endpt=0 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=80045572 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=c018556f Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=1000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=8 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=80045572 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=c018556f Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=1000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=18 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: ugenclose: flag=3, mode=8192, unit=0, endpt=0 Jun 30 20:16:01 kirika2 kernel: ugenclose: close control Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc3082800, flags=6, pipe=0xc31c4880, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc31c4880 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc31c4880 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc31c4880 xfer=0xc3082800 status=0 actlen=2 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc31c4880, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc3082800, flags=6, pipe=0xc31c4880, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc31c4880 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc31c4880 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc31c4880 xfer=0xc3082800 status=0 actlen=18 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc31c4880, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc3082800, flags=6, pipe=0xc31c4880, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc31c4880 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc31c4880 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc31c4880 xfer=0xc3082800 status=0 actlen=2 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc31c4880, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc3082800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc3082800, flags=6, pipe=0xc31c4880, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc31c4880 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc31c4880 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc31c4880 xfer=0xc3082800 status=0 actlen=28 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc31c4880, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc3082800 Jun 30 20:16:01 kirika2 kernel: ugenopen: flag=3, mode=8192, unit=0 endpt=0 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=80045572 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=c018556f Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=0 actlen=28 Jun 30 20:16:01 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:01 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:01 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=80045572 Jun 30 20:16:01 kirika2 kernel: ugenioctl: cmd=c018556f Jun 30 20:16:01 kirika2 kernel: usbd_alloc_xfer() = 0xc36eb800 Jun 30 20:16:01 kirika2 kernel: usbd_transfer: xfer=0xc36eb800, flags=6, pipe=0xc37a7480, running=0 Jun 30 20:16:01 kirika2 kernel: usbd_dump_queue: pipe=0xc37a7480 Jun 30 20:16:01 kirika2 kernel: usb_insert_transfer: pipe=0xc37a7480 running=0 timeout=5000 Jun 30 20:16:06 kirika2 kernel: usb_add_task: task=0xc36eb990 Jun 30 20:16:06 kirika2 kernel: usb_task_thread: woke up task=0xc36eb990 Jun 30 20:16:06 kirika2 kernel: usb_transfer_complete: pipe=0xc37a7480 xfer=0xc36eb800 status=15 actlen=0 Jun 30 20:16:06 kirika2 kernel: usb_transfer_complete: repeat=0 new head=0 Jun 30 20:16:06 kirika2 kernel: usbd_start_next: pipe=0xc37a7480, xfer=0 Jun 30 20:16:06 kirika2 kernel: usbd_free_xfer: 0xc36eb800 Jun 30 20:16:06 kirika2 kernel: ugenclose: flag=3, mode=8192, unit=0, endpt=0 Jun 30 20:16:06 kirika2 kernel: ugenclose: close control Jun 30 20:16:33 kirika2 kernel: usb_event_thread: woke up Jun 30 20:16:33 kirika2 kernel: usb_discover Jun 30 20:16:36 kirika2 kernel: usb_event_thread: woke up Jun 30 20:16:36 kirika2 kernel: usb_discover Jun 30 20:17:33 kirika2 kernel: usb_event_thread: woke up Jun 30 20:17:33 kirika2 kernel: usb_discover Jun 30 20:17:36 kirika2 kernel: usb_event_thread: woke up Jun 30 20:17:36 kirika2 kernel: usb_discover Jun 30 20:18:27 kirika2 kernel: netsmb_dev: loaded Jun 30 20:18:33 kirika2 kernel: usb_event_thread: woke up Jun 30 20:18:33 kirika2 kernel: usb_discover Jun 30 20:18:36 kirika2 kernel: usb_event_thread: woke up Jun 30 20:18:36 kirika2 kernel: usb_discover --------------040808090905060105080603-- From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 20:04:23 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E70671065678 for ; Tue, 30 Jun 2009 20:04:23 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id B98548FC08 for ; Tue, 30 Jun 2009 20:04:22 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 30 Jun 2009 20:04:21 -0000 Received: from dslb-092-073-081-027.pools.arcor-ip.net (EHLO [192.168.1.100]) [92.73.81.27] by mail.gmx.net (mp035) with SMTP; 30 Jun 2009 22:04:21 +0200 X-Authenticated: #931807 X-Provags-ID: V01U2FsdGVkX1/qKtFxKNrq6u9BNM8u9slXYqQV0/YFCsNFtKDmUq YO8o7Jh2z6ZD49 Message-ID: <4A4A6FD2.8000109@nurfuerspam.de> Date: Tue, 30 Jun 2009 22:04:34 +0200 From: Markus Dolze User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Hans Petter Selasky References: <4A4A5D7E.70708@nurfuerspam.de> <200906302120.40790.hselasky@c2i.net> In-Reply-To: <200906302120.40790.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53 Cc: freebsd-usb@freebsd.org Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 20:04:24 -0000 Hans Petter Selasky wrote: > On Tuesday 30 June 2009 20:46:22 Markus Dolze wrote: >> Hello, >> >> for several days I ways trying to get devel/avrdude to work with an >> USBasp compatibel device (www.ullihome.de) on FreeBSD 7.2 running as a >> guest in VMware Workstation 6.5.2. >> >>... > > FYI: Not a solution maybe, but 8-current has a new USB stack. > > Works with AVRDUDE. > > --HPS > Hi, yes, I know. Therefore I already tried and the result is even worse. Output from the test program: freebsd8# ./main ./main: Command not found. freebsd8# ./test Found AVR-USB device USB_control_msg result: 20 2e 00 Found device from vendor: (null) USB_control_msg result: 6 61 00 Found device: (null) freebsd8# uname -v FreeBSD 8.0-CURRENT-200906 #0: Mon Jun 29 23:38:52 CEST 2009 root@freebsd8.intra.mdolze.de:/usr/obj/usr/src/sys/CUSTOM It does not even get string descriptors back (second byte of buffer is 0x00). Avrdude doesn't work either: freebsd8# avrdude -c usbasp -p atmega8 -U eeprom:r:-:h avrdude: error: usbasp_transmit: Unknown error Regards, Markus From owner-freebsd-usb@FreeBSD.ORG Tue Jun 30 20:11:36 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E365106564A for ; Tue, 30 Jun 2009 20:11:36 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 7CDE88FC0C for ; Tue, 30 Jun 2009 20:11:35 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 30 Jun 2009 20:11:34 -0000 Received: from dslb-092-073-081-027.pools.arcor-ip.net (EHLO [192.168.1.100]) [92.73.81.27] by mail.gmx.net (mp066) with SMTP; 30 Jun 2009 22:11:34 +0200 X-Authenticated: #931807 X-Provags-ID: V01U2FsdGVkX1+XR4V4TQiXP09nUOA0AKXipiZMHai44rIoyow2Wx qbJVxJ49uhNnvz Message-ID: <4A4A7183.2060700@nurfuerspam.de> Date: Tue, 30 Jun 2009 22:11:47 +0200 From: Markus Dolze User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <4A4A5D7E.70708@nurfuerspam.de> In-Reply-To: <4A4A5D7E.70708@nurfuerspam.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.47 Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 20:11:36 -0000 Markus Dolze wrote: > To repeat run the attached program: > > 1. Fill in some vendor / product ID of a device detected as ugen device > 2. Compile and run the code (devel/libusb must be installed). > > The result will look like this: > > The mailing list didn't send the attachment. Here is the code, put together from different example programs: /* * A program to test USB control messages */ #include #include #include #define USBASP_SHARED_VID 0x16C0 #define USBASP_SHARED_PID 0x05DC #define TIMEOUT 5000 #define LANGID 0x0409 /* english */ char* usbStringToAscii(char *buffer, int len) { char buf[256]; int i; printf("%02x %02x\n", buffer[0], buffer[1]); if(buffer[1] != USB_DT_STRING){ *buf = 0; return 0; } if((unsigned char)buffer[0] < len) len = (unsigned char)buffer[0]; len /= 2; /* lossy conversion to ISO Latin1: */ for(i=1;i sizeof(buf)) /* destination buffer overflow */ break; buf[i-1] = buffer[2 * i]; if(buffer[2 * i + 1] != 0) /* outside of ISO Latin1 range */ buf[i-1] = '?'; } buf[i-1] = 0; return strdup(buf); } int main(int argc, char *argv[]) { struct usb_bus *bus; struct usb_device *dev; usb_dev_handle *handle = NULL; char string[255]; int len; usb_init(); usb_find_busses(); usb_find_devices(); for(bus = usb_get_busses(); bus; bus = bus->next) { for(dev = bus->devices; dev; dev = dev->next) { if((dev->descriptor.idVendor == USBASP_SHARED_VID && dev->descriptor.idProduct == USBASP_SHARED_PID) { printf("Found AVR-USB device\n"); handle = usb_open(dev); if(!handle) { printf("Warning: cannot open USB device: %s\n", usb_strerror()); continue; } memset(string, 0, sizeof(string)); len = usb_control_msg(handle, USB_ENDPOINT_IN, USB_REQ_GET_DESCRIPTOR, (USB_DT_STRING << 8) + dev->descriptor.iManufacturer, LANGID, string, sizeof(string), TIMEOUT); printf("USB_control_msg result: %d\n", len); if(len < 0) printf("Warning: cannot query manufacturer for device: %s\n", usb_strerror()); else printf("Found device from vendor: %s\n", usbStringToAscii(string, len)); memset(string, 0, sizeof(string)); len = usb_control_msg(handle, USB_ENDPOINT_IN, USB_REQ_GET_DESCRIPTOR, (USB_DT_STRING << 8) + dev->descriptor.iProduct, LANGID, string, sizeof(string), TIMEOUT); printf("USB_control_msg result: %d\n", len); if(len < 0) printf("Warning: cannot query product: %s\n", usb_strerror()); else printf("Found device: %s\n", usbStringToAscii(string, len)); usb_close(handle); handle = NULL; } } } return 0; } From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 07:08:08 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1F75106564A for ; Wed, 1 Jul 2009 07:08:08 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 5E1838FC18 for ; Wed, 1 Jul 2009 07:08:07 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=kHiLD6Pb4HYA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=JjkNSL0xAAAA:8 a=qzFoFaD7qbPoc53dh-AA:9 a=wFqe2Ruvhb9JhV0UgVItlb384ZgA:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1275417612; Wed, 01 Jul 2009 09:08:06 +0200 From: Hans Petter Selasky To: Markus Dolze Date: Wed, 1 Jul 2009 09:07:38 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4A4A5D7E.70708@nurfuerspam.de> <200906302120.40790.hselasky@c2i.net> <4A4A6FD2.8000109@nurfuerspam.de> In-Reply-To: <4A4A6FD2.8000109@nurfuerspam.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907010907.39860.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 07:08:09 -0000 On Tuesday 30 June 2009 22:04:34 Markus Dolze wrote: > Hans Petter Selasky wrote: > > On Tuesday 30 June 2009 20:46:22 Markus Dolze wrote: > >> Hello, > >> > >> for several days I ways trying to get devel/avrdude to work with an > >> USBasp compatibel device (www.ullihome.de) on FreeBSD 7.2 running as a > >> guest in VMware Workstation 6.5.2. > >> > >>... > > > > FYI: Not a solution maybe, but 8-current has a new USB stack. > > > > Works with AVRDUDE. > > > > --HPS > > Hi, > > yes, I know. Therefore I already tried and the result is even worse. > Output from the test program: > > freebsd8# ./main > ./main: Command not found. > freebsd8# ./test > Found AVR-USB device > USB_control_msg result: 20 > 2e 00 > Found device from vendor: (null) > USB_control_msg result: 6 > 61 00 > Found device: (null) > > freebsd8# uname -v > FreeBSD 8.0-CURRENT-200906 #0: Mon Jun 29 23:38:52 CEST 2009 > root@freebsd8.intra.mdolze.de:/usr/obj/usr/src/sys/CUSTOM > > It does not even get string descriptors back (second byte of buffer is > 0x00). > > > Avrdude doesn't work either: > > freebsd8# avrdude -c usbasp -p atmega8 -U eeprom:r:-:h > avrdude: error: usbasp_transmit: Unknown error > That's maybe a bug in the firmware in your USB device! Can you try reading the strings using usbconfig -u XXX -a YYY dump_string ZZZ What does usbconfig output? --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 07:13:36 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E8E81065701 for ; Wed, 1 Jul 2009 07:13:36 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id A34698FC24 for ; Wed, 1 Jul 2009 07:13:35 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=kHiLD6Pb4HYA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=eV8P6yYn3RY_HASUdv0A:9 a=I3UTY94dQe9DR8gRP4l9V0SsZKUA:4 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1269348762; Wed, 01 Jul 2009 09:13:34 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Wed, 1 Jul 2009 09:13:08 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4A4A5D7E.70708@nurfuerspam.de> <4A4A7183.2060700@nurfuerspam.de> In-Reply-To: <4A4A7183.2060700@nurfuerspam.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907010913.08747.hselasky@c2i.net> Cc: Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 07:13:36 -0000 On Tuesday 30 June 2009 22:11:47 Markus Dolze wrote: > Markus Dolze wrote: > > To repeat run the attached program: > > > > 1. Fill in some vendor / product ID of a device detected as ugen > > device 2. Compile and run the code (devel/libusb must be installed). > > You should use this function when reading strings: int usb_get_string_simple(usb_dev_handle * dev, int index, char *buf, size_t buflen); --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 18:26:39 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75F62106566C for ; Wed, 1 Jul 2009 18:26:39 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id D75428FC0A for ; Wed, 1 Jul 2009 18:26:38 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 01 Jul 2009 18:26:36 -0000 Received: from dslb-092-073-081-027.pools.arcor-ip.net (EHLO [192.168.1.100]) [92.73.81.27] by mail.gmx.net (mp069) with SMTP; 01 Jul 2009 20:26:36 +0200 X-Authenticated: #931807 X-Provags-ID: V01U2FsdGVkX1+LYn506yqL7uEI/89rJQM9YUCFLjTz2Z84bOWAGY e+uHBE9QGh0xgW Message-ID: <4A4BAA5B.9050002@nurfuerspam.de> Date: Wed, 01 Jul 2009 20:26:35 +0200 From: Markus Dolze User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Hans Petter Selasky References: <4A4A5D7E.70708@nurfuerspam.de> <200906302120.40790.hselasky@c2i.net> <4A4A6FD2.8000109@nurfuerspam.de> <200907010907.39860.hselasky@c2i.net> In-Reply-To: <200907010907.39860.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.51 Cc: freebsd-usb@freebsd.org Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 18:26:39 -0000 Hans Petter Selasky wrote: > On Tuesday 30 June 2009 22:04:34 Markus Dolze wrote: >> Hans Petter Selasky wrote: >>> On Tuesday 30 June 2009 20:46:22 Markus Dolze wrote: >>>> Hello, >>>> >>>> for several days I ways trying to get devel/avrdude to work with an >>>> USBasp compatibel device (www.ullihome.de) on FreeBSD 7.2 running as a >>>> guest in VMware Workstation 6.5.2. >>>> >>>> ... >>> FYI: Not a solution maybe, but 8-current has a new USB stack. >>> >>> Works with AVRDUDE. >>> >>> --HPS >> Hi, >> >> yes, I know. Therefore I already tried and the result is even worse. >> Output from the test program: >> >> freebsd8# ./main >> ./main: Command not found. >> freebsd8# ./test >> Found AVR-USB device >> USB_control_msg result: 20 >> 2e 00 >> Found device from vendor: (null) >> USB_control_msg result: 6 >> 61 00 >> Found device: (null) >> >> freebsd8# uname -v >> FreeBSD 8.0-CURRENT-200906 #0: Mon Jun 29 23:38:52 CEST 2009 >> root@freebsd8.intra.mdolze.de:/usr/obj/usr/src/sys/CUSTOM >> >> It does not even get string descriptors back (second byte of buffer is >> 0x00). >> >> >> Avrdude doesn't work either: >> >> freebsd8# avrdude -c usbasp -p atmega8 -U eeprom:r:-:h >> avrdude: error: usbasp_transmit: Unknown error >> > > That's maybe a bug in the firmware in your USB device! Can you try reading the > strings using usbconfig -u XXX -a YYY dump_string ZZZ > > What does usbconfig output? > > --HPS > Here's the output: freebsd8# usbconfig -u 0 -a 3 dump_string 1 STRING_0x01 = freebsd8# usbconfig -u 0 -a 3 dump_string 2 STRING_0x02 = I already took a problem with the usb stack into account. The stack used is V-USB formerly known as AVR-USB (http://www.obdev.at/products/vusb/index.html). As written previously I tried several different devices including GPS and smartcard terminals with the same bad result. It may also be a problem with VMware's virtual devices or host drivers. Thanks, Markus From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 18:31:44 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CB1E1065672 for ; Wed, 1 Jul 2009 18:31:44 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 91DFB8FC17 for ; Wed, 1 Jul 2009 18:31:43 +0000 (UTC) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 01 Jul 2009 18:31:42 -0000 Received: from dslb-092-073-081-027.pools.arcor-ip.net (EHLO [192.168.1.100]) [92.73.81.27] by mail.gmx.net (mp011) with SMTP; 01 Jul 2009 20:31:42 +0200 X-Authenticated: #931807 X-Provags-ID: V01U2FsdGVkX1/W0BdlRbvWhFqUJPBAgR9B3AuF+3B7QessDw4fpr 2xuAjdgwu5QSid Message-ID: <4A4BAB8D.9000502@nurfuerspam.de> Date: Wed, 01 Jul 2009 20:31:41 +0200 From: Markus Dolze User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Hans Petter Selasky References: <4A4A5D7E.70708@nurfuerspam.de> <4A4A7183.2060700@nurfuerspam.de> <200907010913.08747.hselasky@c2i.net> In-Reply-To: <200907010913.08747.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.57 Cc: freebsd-usb@freebsd.org Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 18:31:44 -0000 Hans Petter Selasky wrote: > On Tuesday 30 June 2009 22:11:47 Markus Dolze wrote: >> Markus Dolze wrote: >>> To repeat run the attached program: >>> >>> 1. Fill in some vendor / product ID of a device detected as ugen >>> device 2. Compile and run the code (devel/libusb must be installed). >>> > > You should use this function when reading strings: > > int usb_get_string_simple(usb_dev_handle * dev, int index, char *buf, > size_t buflen); > Yes, this is more easy, but I crafted the control transfers myself to show that actually the control transfer is failing. Libusb's usb_get_string_simple internally uses to control transfers to read a string. The first one to get a list of supported languages and the second one to actually retrieve the string. I found that the second control transfer always errors out. If I replace the usb_control_msg() in my test program with usb_get_string_simple() I get: root@freebsd7:./test Found AVR-USB device USB_control_msg result: -5 Warning: cannot query manufacturer for device: error sending control message: Input/output error USB_control_msg result: -5 Warning: cannot query product: error sending control message: Input/output error Thanks, Markus From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 19:08:17 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1BB91065673 for ; Wed, 1 Jul 2009 19:08:17 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id 42B468FC23 for ; Wed, 1 Jul 2009 19:08:17 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=kHiLD6Pb4HYA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=ZpyUl-9OMg4V-Xq-HS8A:9 a=kwPVBIDVjR4EFKwxmY4A:7 a=5ENWLNFQZprS79Be7GT7GryFgbkA:4 a=bvicLqxvdINj6Xfm:21 a=-eUaa8lvHVCfQbgE:21 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe09.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 924938892; Wed, 01 Jul 2009 21:08:16 +0200 From: Hans Petter Selasky To: Markus Dolze Date: Wed, 1 Jul 2009 21:07:47 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4A4A5D7E.70708@nurfuerspam.de> <200907010913.08747.hselasky@c2i.net> <4A4BAB8D.9000502@nurfuerspam.de> In-Reply-To: <4A4BAB8D.9000502@nurfuerspam.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907012107.48635.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 19:08:18 -0000 On Wednesday 01 July 2009 20:31:41 Markus Dolze wrote: > Hans Petter Selasky wrote: > > On Tuesday 30 June 2009 22:11:47 Markus Dolze wrote: > >> Markus Dolze wrote: > >>> To repeat run the attached program: > >>> > >>> 1. Fill in some vendor / product ID of a device detected as ugen > >>> device 2. Compile and run the code (devel/libusb must be installed). > > > > You should use this function when reading strings: > > > > int usb_get_string_simple(usb_dev_handle * dev, int index, char *buf, > > size_t buflen); > > Yes, this is more easy, but I crafted the control transfers myself to > show that actually the control transfer is failing. Sometimes you have to pass the exact length of the string, and not the maximum length when doing the control request. > > Libusb's usb_get_string_simple internally uses to control transfers to > read a string. The first one to get a list of supported languages and > the second one to actually retrieve the string. I found that the second > control transfer always errors out. > > If I replace the usb_control_msg() in my test program with > usb_get_string_simple() I get: > > root@freebsd7:./test > Found AVR-USB device > USB_control_msg result: -5 > Warning: cannot query manufacturer for device: error sending control > message: Input/output error > USB_control_msg result: -5 > Warning: cannot query product: error sending control message: > Input/output error usbconfig is using the same function to dump the device string. Strange you get different results. --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 19:09:24 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7378B1065675 for ; Wed, 1 Jul 2009 19:09:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.tele2.se [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 006768FC14 for ; Wed, 1 Jul 2009 19:09:23 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=kHiLD6Pb4HYA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=fpW7bVhsAAAA:8 a=pFeSvpgjAAAA:8 a=GkJFkYWz3ygcTjpyLw0A:9 a=3WEcSb7XsGcZUU38sbajqphAbVIA:4 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 524819826; Wed, 01 Jul 2009 21:09:22 +0200 From: Hans Petter Selasky To: Markus Dolze Date: Wed, 1 Jul 2009 21:08:55 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4A4A5D7E.70708@nurfuerspam.de> <200907010907.39860.hselasky@c2i.net> <4A4BAA5B.9050002@nurfuerspam.de> In-Reply-To: <4A4BAA5B.9050002@nurfuerspam.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907012108.56663.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: Failing controls transfers in VMware X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 19:09:25 -0000 On Wednesday 01 July 2009 20:26:35 Markus Dolze wrote: > Hans Petter Selasky wrote: > > On Tuesday 30 June 2009 22:04:34 Markus Dolze > > freebsd8# usbconfig -u 0 -a 3 dump_string 1 > STRING_0x01 = > freebsd8# usbconfig -u 0 -a 3 dump_string 2 > STRING_0x02 = > > I already took a problem with the usb stack into account. The stack used > is V-USB formerly known as AVR-USB > (http://www.obdev.at/products/vusb/index.html). As written previously I > tried several different devices including GPS and smartcard terminals > with the same bad result. > > It may also be a problem with VMware's virtual devices or host drivers. > Try without VM-ware, and see if the result is the same. --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Jul 1 20:52:22 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEDCB106566C for ; Wed, 1 Jul 2009 20:52:20 +0000 (UTC) (envelope-from sent2400@respread.com) Received: from smtp20.respread.com (smtp20.respread.com [66.252.230.170]) by mx1.freebsd.org (Postfix) with ESMTP id 7DD998FC0C for ; Wed, 1 Jul 2009 20:52:20 +0000 (UTC) (envelope-from sent2400@respread.com) Received: from DS1030 ([204.10.77.184]) by smtp20.respread.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Jul 2009 15:52:21 -0500 From: "WORLD CROWN ELECTRONICS LTD" To: "freebsd-usb@freebsd.org" Date: Wed, 01 Jul 2009 15:52:13 -0500 MIME-Version: 1.0 X-Mailer: aspNetEmail ver 3.6.0.67 X-Spread-CampaignId: 25556 X-Spread-SubscriberId: 7647985 X-Spread-SpreaderId: 2400 Message-ID: X-OriginalArrivalTime: 01 Jul 2009 20:52:21.0954 (UTC) FILETIME=[D4844220:01C9FA8D] Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Card Reader at USD 0.59/pc 1K pcs up (CR35) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sales@worldcrown.net List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 20:52:22 -0000 = Promotional gift with YOU= R OWN LOGO =0D=0D Card Reader at USD 0=2E59/pc 1K pcs up CR35 =0D=0D ( = http://rs-tr=2Ecom//t=2Easpx/subid/7647985/camid/25556/rs-tr=2Ecom//t=2Ea= spx/subid/6782126/camid/25489/www=2Eworldcrown=2Enet/product_info=2Easp?i= d=3D529 ) ( http://rs-tr=2Ecom//t=2Easpx/subid/7647985/camid/25556/rs-tr=2E= com//t=2Easpx/subid/6782126/camid/25489/worldcrown=2Enet/product_info=2Ea= sp?id=3D539 ) ( http://rs-tr=2Ecom//t=2Easpx/subid/7647985/camid/25556/rs= -tr=2Ecom//t=2Easpx/subid/6782126/camid/25489/https/rspd_col///www=2Ereas= onablespread=2Ecom/Management/Campaign/AddCampaignContent=2Easpx?campaign= _id=3D15518 ) =09 ( http://rs-tr=2Ecom//t=2Easpx/subid/7647985/camid/2555= 6/rs-tr=2Ecom//t=2Easpx/subid/6782126/camid/25489/worldcrown=2Enet/produc= t_info=2Easp?id=3D592 ) =09 ( http://rs-tr=2Ecom//t=2Easpx/subid/7647985/= camid/25556/rs-tr=2Ecom//t=2Easpx/subid/6782126/camid/25489/www=2Eam730=2E= com=2Ehk/ ) =0D=0DCR25 =09=0D=0DCR60 =09=0D=0DCR66 =0D=0D=09 =09= =0D=0D=09 CR53 =09 CR29 =09= =0D=0D CR35 =0D=0D=09 =09=0D=0D=09 = CR55 =09 CR23 =09=0D=0D = CR21 =0D=0DFor more product details, please visit http://wo= rldcrown=2Enet ( http://rs-tr=2Ecom//t=2Easpx/subid/7647985/camid/25556/r= s-tr=2Ecom//t=2Easpx/subid/6782126/camid/25489/worldcrown=2Enet/ ) =0D=0D= Please tell me your MSN or Skype so we can discuss directly=2E My MSN is = world=2Ecrown=40hotmail=2Ecom ( ) and Skype is sales3_worldcrown=2Enet =0D= =0DMs Li _________________________ Direct Line: (852) 31870298 , Email: = li=40worldcrown=2Enet ( ), Skype: sales3_worldcrown=2Enet, MSN: world=2E= crown=40hotmail=2Ecom ( ) =0D=0DWORLD CROWN ELECTRONICS LTD =0D=0DHong = Kong =0D=0DOffice =26 Showroom: Unit 371-374, 3/F=2E, Sino Industrial Pl= aza, 9 Kai Cheung Road, Kowloon Bay, Kowloon, Hong Kong =0D=0DTel: (852)= 3187 0228 (18 Lines) Fax:(852) 2155 0985 (3 Lines) =0D=0DChina =0D=0D= Office Address: Unit A516, Automobile Building, 45 Zhenhua Road, Futian D= istrict, Shenzhen, China Factory Adddress: 6/F=2E, B7 Building, Xujingch= ang Industry Park, Fuyuanyi Road, Xinhe Community, Fuyong Street, Bao An = District, Shenzhen, China=2E =0D=0D=09 =09=09 =09=0D=0D=09 =09=09 =09=0D= =0D=09 =09=09 =09=0D=0D=09 =09=09 =09=0D=0DThey trust and rely on us with= their important promotional projects=2E How about you? Please make your = first step to contact our sales department=2E You are ensured that your r= equirements will be our first priority=2E =0D=0DForward this email ( h= ttp://rs-ar=2Ecom/2400-25556/=2Enewsletter/Card_Reader_at_USD_0=2E59pc_1K= _pcs_up_(CR35)/forward=2Easpx )=0D=0D=09 Update Email =26 Profile ( http:= //rs-sub=2Ecom/SubscribeFormDetail=2Easpx?ens=3DsdUASjfpOA7IYYkm5rnZ6Q=3D= =3D=26type=3Dprofile ) =7C Unsubscribe ( http://rs-sub=2Ecom/Unsubscribe=2E= aspx?sub=3D7647985=26user=3D2400=26campid=3D25556=26type=3Dp ) =09 ( htt= p://rs-w=2Ecom/about=2Easpx?subid=3D7647985=26campid=3D25556 ) From owner-freebsd-usb@FreeBSD.ORG Thu Jul 2 15:01:13 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1A56106564A; Thu, 2 Jul 2009 15:01:13 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 9DA5E8FC16; Thu, 2 Jul 2009 15:01:12 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=-C_3ZPTwNAkA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=GaNxpZAkVcGcGMhTNGoA:9 a=L7s4sSZD9cNdtay08dYA:7 a=dVKp4SPAa-r4XVwOhKDApwT3xLkA:4 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1271753061; Thu, 02 Jul 2009 17:01:10 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Thu, 2 Jul 2009 17:00:37 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906080902.43391.hselasky@c2i.net> <4A4CC9C1.4080200@freebsd.org> In-Reply-To: <4A4CC9C1.4080200@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907021700.39350.hselasky@c2i.net> Cc: Lawrence Stewart , freebsd-usb@freebsd.org, freebsd-ports@freebsd.org, markus@brueffer.de Subject: Re: Temporary patch to fix USB in kdebase4 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2009 15:01:14 -0000 On Thursday 02 July 2009 16:52:49 Lawrence Stewart wrote: > Hans Petter Selasky wrote: > > See attachment. > > --HPS > > Any chance you (or someone with the right clue) could update this patch > to work with more recent 8-CURRENT? I get the following output when > trying to compile kdebase4 (which applies your original patch as > extra-patch-libusb20) on r195046 world/kernel: > > > Scanning dependencies of target kcm_usb > > [ 67%] Building CXX object > apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcm_usb_automoc.o > [ 67%] Building CXX object > apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcmusb.o > In file included from > /usr/ports/x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/usbdevi >ces.h:20, > > Hi, It looks like you have two set of header files. Second, change the USB "dev/" header files to: # include # include Else there are no further changes. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Jul 2 15:14:41 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85CC21065670; Thu, 2 Jul 2009 15:14:41 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 140638FC12; Thu, 2 Jul 2009 15:14:40 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lstewart-laptop.caia.swin.edu.au (c149.al.cl.cam.ac.uk [128.232.110.149]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n62FEMnR012481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jul 2009 01:14:25 +1000 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4A4CCECA.40607@freebsd.org> Date: Thu, 02 Jul 2009 16:14:18 +0100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.22 (X11/20090626) MIME-Version: 1.0 To: Hans Petter Selasky References: <200906080902.43391.hselasky@c2i.net> <4A4CC9C1.4080200@freebsd.org> <200907021700.39350.hselasky@c2i.net> In-Reply-To: <200907021700.39350.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org, freebsd-usb@freebsd.org, markus@brueffer.de Subject: Re: Temporary patch to fix USB in kdebase4 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2009 15:14:42 -0000 Hans Petter Selasky wrote: > On Thursday 02 July 2009 16:52:49 Lawrence Stewart wrote: >> Hans Petter Selasky wrote: >>> See attachment. >>> --HPS >> Any chance you (or someone with the right clue) could update this patch >> to work with more recent 8-CURRENT? I get the following output when >> trying to compile kdebase4 (which applies your original patch as >> extra-patch-libusb20) on r195046 world/kernel: >> >> >> Scanning dependencies of target kcm_usb >> >> [ 67%] Building CXX object >> apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcm_usb_automoc.o >> [ 67%] Building CXX object >> apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcmusb.o >> In file included from >> /usr/ports/x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/usbdevi >> ces.h:20, >> >> > > Hi, > > It looks like you have two set of header files. Second, change the USB "dev/" > header files to: > > # include > # include > > Else there are no further changes. ah ha, had forgotten to run "make delete-old" after last update. Thanks for the hint and thanks for the include fix. Trying it out now. Cheers, Lawrence From owner-freebsd-usb@FreeBSD.ORG Thu Jul 2 15:20:20 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2134B106567E; Thu, 2 Jul 2009 15:20:20 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 9E1B18FC17; Thu, 2 Jul 2009 15:20:19 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lstewart-laptop.caia.swin.edu.au (c149.al.cl.cam.ac.uk [128.232.110.149]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n62Eqrhs057661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jul 2009 00:52:56 +1000 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4A4CC9C1.4080200@freebsd.org> Date: Thu, 02 Jul 2009 15:52:49 +0100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.22 (X11/20090626) MIME-Version: 1.0 To: Hans Petter Selasky References: <200906080902.43391.hselasky@c2i.net> In-Reply-To: <200906080902.43391.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_05,SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org, freebsd-usb@freebsd.org, markus@brueffer.de Subject: Re: Temporary patch to fix USB in kdebase4 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2009 15:20:20 -0000 Hans Petter Selasky wrote: > See attachment. > --HPS Any chance you (or someone with the right clue) could update this patch to work with more recent 8-CURRENT? I get the following output when trying to compile kdebase4 (which applies your original patch as extra-patch-libusb20) on r195046 world/kernel: Scanning dependencies of target kcm_usb [ 67%] Building CXX object apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcm_usb_automoc.o [ 67%] Building CXX object apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcmusb.o In file included from /usr/ports/x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/usbdevices.h:20, from /usr/ports/x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/kcmusb.cpp:27: /usr/include/dev/usb/usb_revision.h:33: error: multiple definition of 'enum usb_dev_speed' /usr/include/dev/usb/usb.h:686: error: previous definition here /usr/include/dev/usb/usb_revision.h:34: error: conflicting declaration 'USB_SPEED_VARIABLE' /usr/include/dev/usb/usb.h:687: error: 'USB_SPEED_VARIABLE' has a previous declaration as 'usb_dev_speed USB_SPEED_VARIABLE' /usr/include/dev/usb/usb_revision.h:35: error: conflicting declaration 'USB_SPEED_LOW' /usr/include/dev/usb/usb.h:688: error: 'USB_SPEED_LOW' has a previous declaration as 'usb_dev_speed USB_SPEED_LOW' /usr/include/dev/usb/usb_revision.h:36: error: conflicting declaration 'USB_SPEED_FULL' /usr/include/dev/usb/usb.h:689: error: 'USB_SPEED_FULL' has a previous declaration as 'usb_dev_speed USB_SPEED_FULL' /usr/include/dev/usb/usb_revision.h:37: error: conflicting declaration 'USB_SPEED_HIGH' /usr/include/dev/usb/usb.h:690: error: 'USB_SPEED_HIGH' has a previous declaration as 'usb_dev_speed USB_SPEED_HIGH' /usr/include/dev/usb/usb_revision.h:38: error: conflicting declaration 'USB_SPEED_SUPER' /usr/include/dev/usb/usb.h:691: error: 'USB_SPEED_SUPER' has a previous declaration as 'usb_dev_speed USB_SPEED_SUPER' /usr/include/dev/usb/usb_revision.h:45: error: multiple definition of 'enum usb_revision' /usr/include/dev/usb/usb.h:698: error: previous definition here /usr/include/dev/usb/usb_revision.h:46: error: conflicting declaration 'USB_REV_UNKNOWN' /usr/include/dev/usb/usb.h:699: error: 'USB_REV_UNKNOWN' has a previous declaration as 'usb_revision USB_REV_UNKNOWN' /usr/include/dev/usb/usb_revision.h:47: error: conflicting declaration 'USB_REV_PRE_1_0' /usr/include/dev/usb/usb.h:700: error: 'USB_REV_PRE_1_0' has a previous declaration as 'usb_revision USB_REV_PRE_1_0' /usr/include/dev/usb/usb_revision.h:48: error: conflicting declaration 'USB_REV_1_0' /usr/include/dev/usb/usb.h:701: error: 'USB_REV_1_0' has a previous declaration as 'usb_revision USB_REV_1_0' /usr/include/dev/usb/usb_revision.h:49: error: conflicting declaration 'USB_REV_1_1' /usr/include/dev/usb/usb.h:702: error: 'USB_REV_1_1' has a previous declaration as 'usb_revision USB_REV_1_1' /usr/include/dev/usb/usb_revision.h:50: error: conflicting declaration 'USB_REV_2_0' /usr/include/dev/usb/usb.h:703: error: 'USB_REV_2_0' has a previous declaration as 'usb_revision USB_REV_2_0' /usr/include/dev/usb/usb_revision.h:51: error: conflicting declaration 'USB_REV_2_5' /usr/include/dev/usb/usb.h:704: error: 'USB_REV_2_5' has a previous declaration as 'usb_revision USB_REV_2_5' /usr/include/dev/usb/usb_revision.h:52: error: conflicting declaration 'USB_REV_3_0' /usr/include/dev/usb/usb.h:705: error: 'USB_REV_3_0' has a previous declaration as 'usb_revision USB_REV_3_0' /usr/include/dev/usb/usb_revision.h:59: error: multiple definition of 'enum usb_hc_mode' /usr/include/dev/usb/usb.h:712: error: previous definition here /usr/include/dev/usb/usb_revision.h:60: error: conflicting declaration 'USB_MODE_HOST' /usr/include/dev/usb/usb.h:713: error: 'USB_MODE_HOST' has a previous declaration as 'usb_hc_mode USB_MODE_HOST' /usr/include/dev/usb/usb_revision.h:61: error: conflicting declaration 'USB_MODE_DEVICE' /usr/include/dev/usb/usb.h:714: error: 'USB_MODE_DEVICE' has a previous declaration as 'usb_hc_mode USB_MODE_DEVICE' /usr/include/dev/usb/usb_revision.h:62: error: conflicting declaration 'USB_MODE_DUAL' /usr/include/dev/usb/usb.h:715: error: 'USB_MODE_DUAL' has a previous declaration as 'usb_hc_mode USB_MODE_DUAL' /usr/include/dev/usb/usb_revision.h:69: error: multiple definition of 'enum usb_dev_state' /usr/include/dev/usb/usb.h:722: error: previous definition here /usr/include/dev/usb/usb_revision.h:70: error: conflicting declaration 'USB_STATE_DETACHED' /usr/include/dev/usb/usb.h:723: error: 'USB_STATE_DETACHED' has a previous declaration as 'usb_dev_state USB_STATE_DETACHED' /usr/include/dev/usb/usb_revision.h:71: error: conflicting declaration 'USB_STATE_ATTACHED' /usr/include/dev/usb/usb.h:724: error: 'USB_STATE_ATTACHED' has a previous declaration as 'usb_dev_state USB_STATE_ATTACHED' /usr/include/dev/usb/usb_revision.h:72: error: conflicting declaration 'USB_STATE_POWERED' /usr/include/dev/usb/usb.h:725: error: 'USB_STATE_POWERED' has a previous declaration as 'usb_dev_state USB_STATE_POWERED' /usr/include/dev/usb/usb_revision.h:73: error: conflicting declaration 'USB_STATE_ADDRESSED' /usr/include/dev/usb/usb.h:726: error: 'USB_STATE_ADDRESSED' has a previous declaration as 'usb_dev_state USB_STATE_ADDRESSED' /usr/include/dev/usb/usb_revision.h:74: error: conflicting declaration 'USB_STATE_CONFIGURED' /usr/include/dev/usb/usb.h:727: error: 'USB_STATE_CONFIGURED' has a previous declaration as 'usb_dev_state USB_STATE_CONFIGURED' *** Error code 1 Stop in /usr/ports/x11/kdebase4/work/kdebase-4.2.4/build. *** Error code 1 Stop in /usr/ports/x11/kdebase4/work/kdebase-4.2.4/build. *** Error code 1 Stop in /usr/ports/x11/kdebase4/work/kdebase-4.2.4/build. *** Error code 1 Stop in /usr/ports/x11/kdebase4. Cheers, Lawrence From owner-freebsd-usb@FreeBSD.ORG Thu Jul 2 15:31:24 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 301621065676; Thu, 2 Jul 2009 15:31:24 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmmtai105.cox.net (eastrmmtai105.cox.net [68.230.240.12]) by mx1.freebsd.org (Postfix) with ESMTP id BA8938FC1D; Thu, 2 Jul 2009 15:31:23 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao107.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090702150515.GWPL4885.eastrmmtao107.cox.net@eastrmimpo03.cox.net>; Thu, 2 Jul 2009 11:05:15 -0400 Received: from localhost ([68.103.37.153]) by eastrmimpo03.cox.net with bizsmtp id B35E1c00B3JFCbG0235E9Y; Thu, 02 Jul 2009 11:05:15 -0400 X-VR-Score: -220.00 X-Authority-Analysis: v=1.0 c=1 a=-C_3ZPTwNAkA:10 a=6I5d2MoRAAAA:8 a=kviXuzpPAAAA:8 a=Z8JsemIFVpmymWuZVRwA:9 a=TnFUQNAWKIVIPj-EqJ4A:7 a=VU7_dud1WVF3KmXX-G0doK5fnJMA:4 a=SV7veod9ZcQA:10 a=4vB-4DCPJfMA:10 X-CM-Score: 0.00 Date: Thu, 02 Jul 2009 10:05:53 -0500 To: "Lawrence Stewart" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <200906080902.43391.hselasky@c2i.net> <4A4CC9C1.4080200@freebsd.org> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <4A4CC9C1.4080200@freebsd.org> User-Agent: Opera Mail/9.64 (Linux) Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org, freebsd-ports@freebsd.org, markus@brueffer.de Subject: Re: Temporary patch to fix USB in kdebase4 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2009 15:31:24 -0000 On Thu, 02 Jul 2009 09:52:49 -0500, Lawrence Stewart wrote: > Hans Petter Selasky wrote: >> See attachment. >> --HPS > > Any chance you (or someone with the right clue) could update this patch > to work with more recent 8-CURRENT? I get the following output when > trying to compile kdebase4 (which applies your original patch as > extra-patch-libusb20) on r195046 world/kernel: There is no usb_revision.h in recently -CURRENT. I have nothing of it in my system, I always run make delete-old and delete-old-libs. However, I am able to installed both kdebase3 and kdebase4 by tweak in extra-patch-libusb20. All I have to do like this: Change from: +#include To: +/*#include */ As for the kdebase3, I just took a patch from ports/135860 then tweak a bit. I am planning to follow up in its PR. But, I haven't run those in runtime yet thought. Cheers, Mezz > Scanning dependencies of target kcm_usb [ 67%] Building CXX object > apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcm_usb_automoc.o > [ 67%] Building CXX object > apps/kinfocenter/usbview/CMakeFiles/kcm_usb.dir/kcmusb.o > In file included from > /usr/ports/x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/usbdevices.h:20, > from > /usr/ports/x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/kcmusb.cpp:27: > /usr/include/dev/usb/usb_revision.h:33: error: multiple definition of > 'enum usb_dev_speed' > /usr/include/dev/usb/usb.h:686: error: previous definition here > /usr/include/dev/usb/usb_revision.h:34: error: conflicting declaration > 'USB_SPEED_VARIABLE' > /usr/include/dev/usb/usb.h:687: error: 'USB_SPEED_VARIABLE' has a > previous declaration as 'usb_dev_speed USB_SPEED_VARIABLE' > /usr/include/dev/usb/usb_revision.h:35: error: conflicting declaration > 'USB_SPEED_LOW' > /usr/include/dev/usb/usb.h:688: error: 'USB_SPEED_LOW' has a previous > declaration as 'usb_dev_speed USB_SPEED_LOW' > /usr/include/dev/usb/usb_revision.h:36: error: conflicting declaration > 'USB_SPEED_FULL' > /usr/include/dev/usb/usb.h:689: error: 'USB_SPEED_FULL' has a previous > declaration as 'usb_dev_speed USB_SPEED_FULL' > /usr/include/dev/usb/usb_revision.h:37: error: conflicting declaration > 'USB_SPEED_HIGH' > /usr/include/dev/usb/usb.h:690: error: 'USB_SPEED_HIGH' has a previous > declaration as 'usb_dev_speed USB_SPEED_HIGH' > /usr/include/dev/usb/usb_revision.h:38: error: conflicting declaration > 'USB_SPEED_SUPER' > /usr/include/dev/usb/usb.h:691: error: 'USB_SPEED_SUPER' has a previous > declaration as 'usb_dev_speed USB_SPEED_SUPER' > /usr/include/dev/usb/usb_revision.h:45: error: multiple definition of > 'enum usb_revision' > /usr/include/dev/usb/usb.h:698: error: previous definition here > /usr/include/dev/usb/usb_revision.h:46: error: conflicting declaration > 'USB_REV_UNKNOWN' > /usr/include/dev/usb/usb.h:699: error: 'USB_REV_UNKNOWN' has a previous > declaration as 'usb_revision USB_REV_UNKNOWN' > /usr/include/dev/usb/usb_revision.h:47: error: conflicting declaration > 'USB_REV_PRE_1_0' > /usr/include/dev/usb/usb.h:700: error: 'USB_REV_PRE_1_0' has a previous > declaration as 'usb_revision USB_REV_PRE_1_0' > /usr/include/dev/usb/usb_revision.h:48: error: conflicting declaration > 'USB_REV_1_0' > /usr/include/dev/usb/usb.h:701: error: 'USB_REV_1_0' has a previous > declaration as 'usb_revision USB_REV_1_0' > /usr/include/dev/usb/usb_revision.h:49: error: conflicting declaration > 'USB_REV_1_1' > /usr/include/dev/usb/usb.h:702: error: 'USB_REV_1_1' has a previous > declaration as 'usb_revision USB_REV_1_1' > /usr/include/dev/usb/usb_revision.h:50: error: conflicting declaration > 'USB_REV_2_0' > /usr/include/dev/usb/usb.h:703: error: 'USB_REV_2_0' has a previous > declaration as 'usb_revision USB_REV_2_0' > /usr/include/dev/usb/usb_revision.h:51: error: conflicting declaration > 'USB_REV_2_5' > /usr/include/dev/usb/usb.h:704: error: 'USB_REV_2_5' has a previous > declaration as 'usb_revision USB_REV_2_5' > /usr/include/dev/usb/usb_revision.h:52: error: conflicting declaration > 'USB_REV_3_0' > /usr/include/dev/usb/usb.h:705: error: 'USB_REV_3_0' has a previous > declaration as 'usb_revision USB_REV_3_0' > /usr/include/dev/usb/usb_revision.h:59: error: multiple definition of > 'enum usb_hc_mode' > /usr/include/dev/usb/usb.h:712: error: previous definition here > /usr/include/dev/usb/usb_revision.h:60: error: conflicting declaration > 'USB_MODE_HOST' > /usr/include/dev/usb/usb.h:713: error: 'USB_MODE_HOST' has a previous > declaration as 'usb_hc_mode USB_MODE_HOST' > /usr/include/dev/usb/usb_revision.h:61: error: conflicting declaration > 'USB_MODE_DEVICE' > /usr/include/dev/usb/usb.h:714: error: 'USB_MODE_DEVICE' has a previous > declaration as 'usb_hc_mode USB_MODE_DEVICE' > /usr/include/dev/usb/usb_revision.h:62: error: conflicting declaration > 'USB_MODE_DUAL' > /usr/include/dev/usb/usb.h:715: error: 'USB_MODE_DUAL' has a previous > declaration as 'usb_hc_mode USB_MODE_DUAL' > /usr/include/dev/usb/usb_revision.h:69: error: multiple definition of > 'enum usb_dev_state' > /usr/include/dev/usb/usb.h:722: error: previous definition here > /usr/include/dev/usb/usb_revision.h:70: error: conflicting declaration > 'USB_STATE_DETACHED' > /usr/include/dev/usb/usb.h:723: error: 'USB_STATE_DETACHED' has a > previous declaration as 'usb_dev_state USB_STATE_DETACHED' > /usr/include/dev/usb/usb_revision.h:71: error: conflicting declaration > 'USB_STATE_ATTACHED' > /usr/include/dev/usb/usb.h:724: error: 'USB_STATE_ATTACHED' has a > previous declaration as 'usb_dev_state USB_STATE_ATTACHED' > /usr/include/dev/usb/usb_revision.h:72: error: conflicting declaration > 'USB_STATE_POWERED' > /usr/include/dev/usb/usb.h:725: error: 'USB_STATE_POWERED' has a > previous declaration as 'usb_dev_state USB_STATE_POWERED' > /usr/include/dev/usb/usb_revision.h:73: error: conflicting declaration > 'USB_STATE_ADDRESSED' > /usr/include/dev/usb/usb.h:726: error: 'USB_STATE_ADDRESSED' has a > previous declaration as 'usb_dev_state USB_STATE_ADDRESSED' > /usr/include/dev/usb/usb_revision.h:74: error: conflicting declaration > 'USB_STATE_CONFIGURED' > /usr/include/dev/usb/usb.h:727: error: 'USB_STATE_CONFIGURED' has a > previous declaration as 'usb_dev_state USB_STATE_CONFIGURED' *** Error > code 1 > Stop in /usr/ports/x11/kdebase4/work/kdebase-4.2.4/build. > *** Error code 1 > > Stop in /usr/ports/x11/kdebase4/work/kdebase-4.2.4/build. > *** Error code 1 > > Stop in /usr/ports/x11/kdebase4/work/kdebase-4.2.4/build. > *** Error code 1 > > Stop in /usr/ports/x11/kdebase4. > > > > > Cheers, > Lawrence > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-usb@FreeBSD.ORG Fri Jul 3 07:50:06 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84F62106566C for ; Fri, 3 Jul 2009 07:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 591F58FC12 for ; Fri, 3 Jul 2009 07:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n637o6RS090428 for ; Fri, 3 Jul 2009 07:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n637o6WX090427; Fri, 3 Jul 2009 07:50:06 GMT (envelope-from gnats) Date: Fri, 3 Jul 2009 07:50:06 GMT Message-Id: <200907030750.n637o6WX090427@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Dominic Fandrey Cc: Subject: Re: usb/122936: [ucom] [ubsa] Device does not receive interrupt X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominic Fandrey List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 07:50:06 -0000 The following reply was made to PR usb/122936; it has been noted by GNATS. From: Dominic Fandrey To: bug-followup@FreeBSD.org, kamikaze@bsdforen.de Cc: Subject: Re: usb/122936: [ucom] [ubsa] Device does not receive interrupt Date: Fri, 03 Jul 2009 09:23:59 +0200 Since U3G made it into the last release, this really should be closed. From owner-freebsd-usb@FreeBSD.ORG Fri Jul 3 16:01:10 2009 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83BFB1065670 for ; Fri, 3 Jul 2009 16:01:10 +0000 (UTC) (envelope-from sanpei@sanpei.org) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 53E7E8FC14 for ; Fri, 3 Jul 2009 16:01:10 +0000 (UTC) (envelope-from sanpei@sanpei.org) Received: from cherry.sanpei.org (j069113.ppp.asahi-net.or.jp [61.213.69.113]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 518B47C89C for ; Sat, 4 Jul 2009 01:01:09 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by cherry.sanpei.org (8.14.3/8.13.8) with ESMTP id n63G17Mi021361; Sat, 4 Jul 2009 01:01:08 +0900 (JST) (envelope-from sanpei@sanpei.org) Date: Sat, 04 Jul 2009 01:01:07 +0900 (JST) Message-Id: <20090704.010107.116362740.sanpei@sanpei.org> To: freebsd-usb@FreeBSD.org From: MIHIRA Sanpei Yoshiro X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-3.0 (cherry.sanpei.org [127.0.0.1]); Sat, 04 Jul 2009 01:01:08 +0900 (JST) Cc: Subject: [8-current] kernel panic at usbd_get_page+0x59 with uaudio X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 16:01:10 -0000 Hi. I use 8-current(csup-ed today) and uaudio device. I record FM radio with below line. /usr/local/bin/wavrec -d /dev/dsp0.0 -x -t 10 -S -s 48000 test.wav kernel panic at usbd_get_page+0x59. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id=00 fault virtual address =0xc0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07997c9 stack pointer = 0x20:0xe64b1bcc frame pointer = 0x20:0xe64b1bd4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL =0 current process = 15(usbus0) thread pid 15 tid 100035 ] stopped at usbd_get_page+0x59; addl 0(%ebx), $eax Is this known problem? source tree which was csup at June/13/2009 was no problem. Cheers. --- MIHIRA, Sanpei Yoshiro Tokyo, Japan. From owner-freebsd-usb@FreeBSD.ORG Fri Jul 3 16:23:54 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CFB01065670 for ; Fri, 3 Jul 2009 16:23:54 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id D04048FC1F for ; Fri, 3 Jul 2009 16:23:53 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=EXzeDOZG6rMA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=mopnxqesqmxVJCEVzbIA:9 a=ST6ihnHjenEIhhMEaafk_5l5YE8A:4 a=pMv_4yDYm7DZLDD462kA:9 a=ASN1p6bhOA-dUleAPDmmlqNt1uAA:4 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 216962683; Fri, 03 Jul 2009 18:23:52 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 3 Jul 2009 18:23:28 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <20090704.010107.116362740.sanpei@sanpei.org> In-Reply-To: <20090704.010107.116362740.sanpei@sanpei.org> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_BCjTKf63Wn82i1n" Message-Id: <200907031823.29040.hselasky@c2i.net> Cc: MIHIRA Sanpei Yoshiro Subject: Re: [8-current] kernel panic at usbd_get_page+0x59 with uaudio X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 16:23:54 -0000 --Boundary-00=_BCjTKf63Wn82i1n Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Friday 03 July 2009 18:01:07 MIHIRA Sanpei Yoshiro wrote: > Hi. > > I use 8-current(csup-ed today) and uaudio device. > > I record FM radio with below line. > /usr/local/bin/wavrec -d /dev/dsp0.0 -x -t 10 -S -s 48000 test.wav > > kernel panic at usbd_get_page+0x59. > There has been a regression. Try the attached patch. --HPS --Boundary-00=_BCjTKf63Wn82i1n Content-Type: text/x-patch; charset="iso-8859-1"; name="uaudio.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="uaudio.diff" --- /usr/8-current/src/sys/dev/sound/usb/uaudio.c 2009-06-28 08:48:04.000000000 +0200 +++ uaudio.c 2009-07-03 18:20:32.000000000 +0200 @@ -1256,7 +1256,7 @@ for (n = 0; n != nframes; n++) { offset1 = offset0; - pc = usbd_xfer_get_frame(xfer, n); + pc = usbd_xfer_get_frame(xfer, 0); len = usbd_xfer_frame_len(xfer, n); while (len > 0) { --Boundary-00=_BCjTKf63Wn82i1n-- From owner-freebsd-usb@FreeBSD.ORG Fri Jul 3 20:16:07 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C285106568A for ; Fri, 3 Jul 2009 20:16:07 +0000 (UTC) (envelope-from plaxo@mx.plaxo.com) Received: from mx.plaxo.com (mx.plaxo.com [66.151.128.13]) by mx1.freebsd.org (Postfix) with ESMTP id 60BF28FC21 for ; Fri, 3 Jul 2009 20:16:07 +0000 (UTC) (envelope-from plaxo@mx.plaxo.com) Received: from localhost by mx.plaxo.com (StrongMail Enterprise 3.2.2.2(3.00.287)); Fri, 03 Jul 2009 13:16:05 -0700 X-VirtualServer: Pulse, mx.plaxo.com, 10.1.6.56 X-PlaxoMailType: Pulse X-Destination-ID: freebsd-usb@freebsd.org X-MailingID: 00000::00000::00000::00000::::4199975 X-SMHeaderMap: mid="X-MailingID" X-SMFBL: ZnJlZWJzZC11c2JAZnJlZWJzZC5vcmc= From: "Jean Dupre" To: freebsd-usb@freebsd.org Message-Id: <0d02456bc6228d4176f8c82c2d3a8037@xpertmailer.com> X-VirtualServerGroup: Pulse Errors-To: plaxo@mx.plaxo.com Date: Fri, 03 Jul 2009 12:42:29 -0700 X-Mailer: XPM4 v.0.3 < www.xpertmailer.com > MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?utf-8?q?Jean_Dupre_a_partag=C3=A9_un_message_avec_vous_sur_Pul?= =?utf-8?q?se?= X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ja.dupre@live.fr List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 20:16:09 -0000 Jean Dupre a partag=C3=A9 un message avec vous sur Pulse et souhaitait vous le faire savoir. http://www.plaxo.com/public/event/189178955319?src=3Demail&et=3D6&el=3Dfr_o= 1&key=3D70634ecb3f154d61ab941ea5fed30e573283e72f&email=3Dfreebsd-usb%40free= bsd.org&share_id=3D4662483&share_key=3D1326838780&name=3D&webmailfix=3D1&la= ng=3Dfr Besoin de pr=C3=AAt ? Bonjour, Je suis DUPRE JEAN ALBERT. Ancien th=C3=A9rapeute, financier suisse et Directeur d=E2=80=99=C3=A9tude de projets dans une banque. J'octroie des pr=C3=AAts =C3=A0 toute personne d=C3=A9sireuse selon le= s crit=C3=A8res suivants: Choix du montant : =C3=A0 partir de 15.000 =E2=82=AC Choix de la dur=C3=A9e de remboursement : 8 ans maximum TEG annuel fixe : 2,15%* (*offre soumise =C3=A0 condition) En option : l=E2=80=99assurance e... http://www.plaxo.com/public/event/189178955319?src=3Demail&et=3D6&el=3Dfr_o= 1&key=3D70634ecb3f154d61ab941ea5fed30e573283e72f&email=3Dfreebsd-usb%40free= bsd.org&share_id=3D4662483&share_key=3D1326838780&name=3D&webmailfix=3D1&la= ng=3Dfr Merci ! L'=C3=A9quipe Plaxo Plus de 20=C2=A0millions de personnes utilisent Plaxo pour rester en contact avec leur entourage dans le cadre priv=C3=A9 comme professionnel.=20 Vous ne voulez plus recevoir d'e-mails de Plaxo=C2=A0? Rendez-vous sur=C2=A0: http://www.plaxo.com/stop?src=3Demail&et=3D6&el=3Dfr_o1&email=3Dfreebsd-usb= %40freebsd.org From owner-freebsd-usb@FreeBSD.ORG Sat Jul 4 01:00:16 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2FA1106564A for ; Sat, 4 Jul 2009 01:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 85FD58FC08 for ; Sat, 4 Jul 2009 01:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n6410GbA078999 for ; Sat, 4 Jul 2009 01:00:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n6410G3a078998; Sat, 4 Jul 2009 01:00:16 GMT (envelope-from gnats) Date: Sat, 4 Jul 2009 01:00:16 GMT Message-Id: <200907040100.n6410G3a078998@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Aragon Gouveia Cc: Subject: Re: usb/123714: Panic when hald-storage-probe runs with umass device inserted X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Aragon Gouveia List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2009 01:00:17 -0000 The following reply was made to PR usb/123714; it has been noted by GNATS. From: Aragon Gouveia To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-usb@FreeBSD.org Cc: Subject: Re: usb/123714: Panic when hald-storage-probe runs with umass device inserted Date: Sat, 04 Jul 2009 02:54:10 +0200 This problem is fixed in 8.0-CURRENT with the new USB stack. I'd say this PR can be closed soon (if not already). From owner-freebsd-usb@FreeBSD.ORG Sat Jul 4 01:05:45 2009 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12919106566C for ; Sat, 4 Jul 2009 01:05:45 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id A35B98FC08 for ; Sat, 4 Jul 2009 01:05:44 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from igor.geek.sh (unknown [196.209.244.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.geek.sh (Postfix) with ESMTPSA id 4330F39827; Sat, 4 Jul 2009 02:54:16 +0200 (SAST) Message-ID: <4A4EA832.5070403@phat.za.net> Date: Sat, 04 Jul 2009 02:54:10 +0200 From: Aragon Gouveia User-Agent: Thunderbird 2.0.0.21 (X11/20090331) MIME-Version: 1.0 To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-usb@FreeBSD.org References: <200805152030.m4FKU1YI010344@freefall.freebsd.org> In-Reply-To: <200805152030.m4FKU1YI010344@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: usb/123714: Panic when hald-storage-probe runs with umass device inserted X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2009 01:05:45 -0000 This problem is fixed in 8.0-CURRENT with the new USB stack. I'd say this PR can be closed soon (if not already). From owner-freebsd-usb@FreeBSD.ORG Sat Jul 4 07:50:40 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4629E106564A for ; Sat, 4 Jul 2009 07:50:40 +0000 (UTC) (envelope-from sanpei@sanpei.org) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 11D918FC15 for ; Sat, 4 Jul 2009 07:50:40 +0000 (UTC) (envelope-from sanpei@sanpei.org) Received: from cherry.sanpei.org (j069113.ppp.asahi-net.or.jp [61.213.69.113]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 3DD347CA27; Sat, 4 Jul 2009 16:50:38 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by cherry.sanpei.org (8.14.3/8.13.8) with ESMTP id n647obJ4031903; Sat, 4 Jul 2009 16:50:38 +0900 (JST) (envelope-from sanpei@sanpei.org) Date: Sat, 04 Jul 2009 16:50:37 +0900 (JST) Message-Id: <20090704.165037.212701737.sanpei@sanpei.org> To: hselasky@c2i.net From: MIHIRA Sanpei Yoshiro In-Reply-To: <200907031823.29040.hselasky@c2i.net> References: <20090704.010107.116362740.sanpei@sanpei.org> <200907031823.29040.hselasky@c2i.net> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-3.0 (cherry.sanpei.org [127.0.0.1]); Sat, 04 Jul 2009 16:50:38 +0900 (JST) Cc: freebsd-usb@freebsd.org Subject: Re: [8-current] kernel panic at usbd_get_page+0x59 with uaudio X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2009 07:50:40 -0000 Hi. >> I use 8-current(csup-ed today) and uaudio device. >> >> I record FM radio with below line. >> /usr/local/bin/wavrec -d /dev/dsp0.0 -x -t 10 -S -s 48000 test.wav >> >> kernel panic at usbd_get_page+0x59. >> > >There has been a regression. Try the attached patch. That patch fix my problem. Thanks. --- MIHIRA, Sanpei Yoshiro Tokyo, Japan. From owner-freebsd-usb@FreeBSD.ORG Sat Jul 4 19:08:59 2009 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9166C106567A; Sat, 4 Jul 2009 19:08:59 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (unknown [IPv6:2001:2f0:104:80a0:21b:78ff:fe37:f1cf]) by mx1.freebsd.org (Postfix) with ESMTP id 32C768FC2E; Sat, 4 Jul 2009 19:08:59 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (ns1.ninth-nine.com [219.127.74.121] (may be forged)) (authenticated bits=0) by sakura.ninth-nine.com (8.14.3/8.14.3/NinthNine) with ESMTP id n64J8qZL022146; Sun, 5 Jul 2009 04:08:57 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 5 Jul 2009 04:08:52 +0900 From: Norikatsu Shigemura To: freebsd-usb@FreeBSD.org Message-Id: <20090705040852.d8d1966a.nork@FreeBSD.org> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.16.2; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Norikatsu Shigemura Subject: usb touch screen support? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2009 19:09:00 -0000 Hi. I got a usb touch screen device A.K.A. eGalax. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ugen4.4: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - In this time, however, FreeBSD doesn't support usb touch screen. So I researched Linux's (drivers/input/touchscreen/usbtouchscreen.c) and NetBSD's (uep(4)) implementations. It's too simple. I considered making modified ums(4) to adapt usb touch screen. But I noticed that ums(4) should be become a mouse subsystem like ucom(4), and I gave up:-). Anyone, do you have any idea?