[linux-usb-devel] \x82\xDD\x82\xE3\x82\xA4\x83T\x83}\x82\xA9\x82\xE7\x82\xCCButterfly!AdultGreetingsCard\x82\xCC\x8C\xE4\x88\xC4\x93\xE0\x82\xC5\x82\xB7\x81B
\x82\xB1\x82\xF1\x82\xC9\x82\xBF\x82\xCD\x81AButterfly!\x83O\x83\x8A\x81[\x83e\x83B\x83\x93\x83O\x82\xC5\x82\xB7\x81B(In English Below) \x82\xDD\x82\xE3\x82\xA4(ID:52167)\x97l\x82\xA9\x82\xE7 \x82\xA0\x82\xC8\x82\xBD\x82\xD6\x81A\x83O\x83\x8A\x81[\x83e\x83B\x83\x93\x83O\x83J\x81[\x83h\x82\xAA\x93\xCD\x82\xA2\x82\xC4\x82\xA2\x82\xDC\x82\xB7\x81B \x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\ \x8E\x9F\x82\xCCURL\x82\xF0\x83N\x83\x8A\x83b\x83N\x82\xB5\x82\xC4\x81A\x82\xB3\x82\xC1\x82\xBB\x82\xAD\x83J\x81[\x83h\x82\xF0\x82\xB2\x97\x97\x82\xAD\x82\xBE\x82\xB3\x82\xA2\x81I \x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB\x81\xAB http://www.allfrees.com.nmnb.net/butterfly/Greetings52167.php \x83J\x81[\x83h\x82\xCD30\x93\xFA\x8A\xD4\x82\xB2\x97\x97\x82\xA2\x82\xBD\x82\xBE\x82\xAF\x82\xDC\x82\xB7\x81B \x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\ \x81\xA1\x95\xD4\x90M\x82\xB7\x82\xE9\x82\xC9\x82\xCD \x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\ \x82\xB1\x82\xCC\x83\x81\x81[\x83\x8B\x82\xC9\x95\xD4\x90M\x82\xF0\x82\xB5\x82\xC4\x82\xE0\x81A\x82\xA0\x82\xC8\x82\xBD\x82\xC9\x83J\x81[\x83h\x82\xF0\x91\x97\x82\xC1\x82\xC4\x82\xAD\x82\xEA\x82\xBD \x82\xDD\x82\xE3\x82\xA4(ID:52167)\x97l\x82\xC9\x82\xCD\x93\xCD\x82\xAB\x82\xDC\x82\xB9\x82\xF1\x81B \x93\xCD\x82\xA2\x82\xBD\x83J\x81[\x83h\x89\xE6\x96\xCA\x82\xCC\x89\xBA\x92i\x82\xC9\x95\ｦ\x82\xB3\x82\xEA\x82\xE9 \x81u\x82\xB1\x82\xCC***\x82\xB3\x82\xF1\x82\xC9\x95\xD4\x90M\x82\xB7\x82\xE9\x81v\x82\xA9\x81u***\x82\xB3\x82\xF1\x82\xCC\x83y\x81[\x83W\x81v\x82\xF0\x83N\x83\x8A\x83b\x83N\x82\xB5\x82\xC4\x82\xAD\x82\xBE\x82\xB3\x82\xA2\x81B \x82\xBB\x82\xB1\x82\xA9\x82\xE7\x82\xB2\x95\xD4\x90M\x82\xAD\x82\xBE\x82\xB3\x82\xA2\x81B\x82\xA0\x82\xC6\x82\xCD\x89\xE6\x96\xCA\x95\ｦ\x82\xC9\x82\xB5\x82\xBD\x82\xAA\x82\xC1\x82\xC4\x91\x80\x8D\xEC\x82\xB7\x82\xE9\x82\xBE\x82\xAF\x82\xC5\x82\xB7\x81B \x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\ \x81\xA0 Butterfly!\x83O\x83\x8A\x81[\x83e\x83B\x83\x93\x83O \x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\\x81\ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH pd55] Add all Logitech Harmonies to HID blacklist
Phil Dibowitz wrote: This patch adds the entire range of Logitech's ProductIDs that are reserved for their Harmony remotes. The in-kernel HID driver can't do anything with these, and now there is a GPL user-space application that can handle them: http://www.sf.net/projects/harmonycontrol As Andrew Morton pointed out to another HID patch, there were significant differences between .22 and .23. This is an updated patch against .23-rc1-git4, the latest and greatest patch. Should diff more cleanly. Signed-off-by: Phil Dibowitz [EMAIL PROTECTED] -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming This patch adds the entire range of Logitech's ProductIDs that are reserved for their Harmony remotes. The in-kernel HID driver can't do anything with these, and now there is a GPL user-space application that can handle them: http://www.sf.net/projects/harmonycontrol Signed-off-by: Phil Dibowitz [EMAIL PROTECTED] --- linux-2.6.23-rc1-git4-dev-phil/drivers/hid/usbhid/hid-quirks.c | 132 ++ 1 file changed, 132 insertions(+) diff -puN drivers/hid/usbhid/hid-quirks.c~usb_hid_ignore_harmony drivers/hid/usbhid/hid-quirks.c --- linux-2.6.23-rc1-git4-dev/drivers/hid/usbhid/hid-quirks.c~usb_hid_ignore_harmony 2007-07-27 00:53:11.0 -0700 +++ linux-2.6.23-rc1-git4-dev-phil/drivers/hid/usbhid/hid-quirks.c 2007-07-27 00:53:11.0 -0700 @@ -198,6 +198,70 @@ #define USB_VENDOR_ID_LOGITECH 0x046d #define USB_DEVICE_ID_LOGITECH_RECEIVER 0xc101 +#define USB_DEVICE_ID_LOGITECH_HARMONY 0xc110 +#define USB_DEVICE_ID_LOGITECH_HARMONY_2 0xc111 +#define USB_DEVICE_ID_LOGITECH_HARMONY_3 0xc112 +#define USB_DEVICE_ID_LOGITECH_HARMONY_4 0xc113 +#define USB_DEVICE_ID_LOGITECH_HARMONY_5 0xc114 +#define USB_DEVICE_ID_LOGITECH_HARMONY_6 0xc115 +#define USB_DEVICE_ID_LOGITECH_HARMONY_7 0xc116 +#define USB_DEVICE_ID_LOGITECH_HARMONY_8 0xc117 +#define USB_DEVICE_ID_LOGITECH_HARMONY_9 0xc118 +#define USB_DEVICE_ID_LOGITECH_HARMONY_10 0xc119 +#define USB_DEVICE_ID_LOGITECH_HARMONY_11 0xc11a +#define USB_DEVICE_ID_LOGITECH_HARMONY_12 0xc11b +#define USB_DEVICE_ID_LOGITECH_HARMONY_13 0xc11c +#define USB_DEVICE_ID_LOGITECH_HARMONY_14 0xc11d +#define USB_DEVICE_ID_LOGITECH_HARMONY_15 0xc11e +#define USB_DEVICE_ID_LOGITECH_HARMONY_16 0xc11f +#define USB_DEVICE_ID_LOGITECH_HARMONY_17 0xc120 +#define USB_DEVICE_ID_LOGITECH_HARMONY_18 0xc121 +#define USB_DEVICE_ID_LOGITECH_HARMONY_19 0xc122 +#define USB_DEVICE_ID_LOGITECH_HARMONY_20 0xc123 +#define USB_DEVICE_ID_LOGITECH_HARMONY_21 0xc124 +#define USB_DEVICE_ID_LOGITECH_HARMONY_22 0xc125 +#define USB_DEVICE_ID_LOGITECH_HARMONY_23 0xc126 +#define USB_DEVICE_ID_LOGITECH_HARMONY_24 0xc127 +#define USB_DEVICE_ID_LOGITECH_HARMONY_25 0xc128 +#define USB_DEVICE_ID_LOGITECH_HARMONY_26 0xc129 +#define USB_DEVICE_ID_LOGITECH_HARMONY_27 0xc12a +#define USB_DEVICE_ID_LOGITECH_HARMONY_28 0xc12b +#define USB_DEVICE_ID_LOGITECH_HARMONY_29 0xc12c +#define USB_DEVICE_ID_LOGITECH_HARMONY_30 0xc12d +#define USB_DEVICE_ID_LOGITECH_HARMONY_31 0xc12e +#define USB_DEVICE_ID_LOGITECH_HARMONY_32 0xc12f +#define USB_DEVICE_ID_LOGITECH_HARMONY_33 0xc130 +#define USB_DEVICE_ID_LOGITECH_HARMONY_34 0xc131 +#define USB_DEVICE_ID_LOGITECH_HARMONY_35 0xc132 +#define USB_DEVICE_ID_LOGITECH_HARMONY_36 0xc133 +#define USB_DEVICE_ID_LOGITECH_HARMONY_37 0xc134 +#define USB_DEVICE_ID_LOGITECH_HARMONY_38 0xc135 +#define USB_DEVICE_ID_LOGITECH_HARMONY_39 0xc136 +#define USB_DEVICE_ID_LOGITECH_HARMONY_40 0xc137 +#define USB_DEVICE_ID_LOGITECH_HARMONY_41 0xc138 +#define USB_DEVICE_ID_LOGITECH_HARMONY_42 0xc139 +#define USB_DEVICE_ID_LOGITECH_HARMONY_43 0xc13a +#define USB_DEVICE_ID_LOGITECH_HARMONY_44 0xc13b +#define USB_DEVICE_ID_LOGITECH_HARMONY_45 0xc13c +#define USB_DEVICE_ID_LOGITECH_HARMONY_46 0xc13d +#define USB_DEVICE_ID_LOGITECH_HARMONY_47 0xc13e +#define USB_DEVICE_ID_LOGITECH_HARMONY_48 0xc13f +#define USB_DEVICE_ID_LOGITECH_HARMONY_49 0xc140 +#define USB_DEVICE_ID_LOGITECH_HARMONY_50 0xc141 +#define USB_DEVICE_ID_LOGITECH_HARMONY_51 0xc142 +#define USB_DEVICE_ID_LOGITECH_HARMONY_52 0xc143 +#define USB_DEVICE_ID_LOGITECH_HARMONY_53 0xc144 +#define USB_DEVICE_ID_LOGITECH_HARMONY_54 0xc145 +#define USB_DEVICE_ID_LOGITECH_HARMONY_55 0xc146 +#define USB_DEVICE_ID_LOGITECH_HARMONY_56 0xc147 +#define USB_DEVICE_ID_LOGITECH_HARMONY_57 0xc148 +#define USB_DEVICE_ID_LOGITECH_HARMONY_58 0xc149 +#define USB_DEVICE_ID_LOGITECH_HARMONY_59 0xc14a +#define USB_DEVICE_ID_LOGITECH_HARMONY_60 0xc14b +#define USB_DEVICE_ID_LOGITECH_HARMONY_61 0xc14c +#define USB_DEVICE_ID_LOGITECH_HARMONY_62 0xc14d +#define
Re: [linux-usb-devel] usb-storage autosuspend bug?
Am Donnerstag 26 Juli 2007 schrieb Greg KH: Alan and Oliver, was this caused by the autosuspend changes for usb-storage? The oops itself looks like refcounting. What caused the initial io error does not become clear from the log. It is possible that the device cannot stand suspension. But there's no evidence from that. On the contrary, these devices usually do an unplug/plug cycle, which is not in the log. Regards Oliver - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Good summer
attachment: themall.gif- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] About current state of supporting USB selective suspend feature
Dear All: I am trying to develop a USB device driver in Linux platform. I want to know the current state of supporting USB selective suspend feature of Linux USB core. This feature is described by USB specification 2.0. Thank you! With Best Regard! Abei _ 免费下载 MSN Explorer: http://explorer.msn.com/lccn - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] 提供各行业投资服务,包括项目评估,项目策划,投资项目委托,项目可行性分析报告,商业计划书,各行业市场研究报告,深度决策分析，各类投标书
专业策划撰写商业计划书（含可研报告等） 广州纳福咨询有限公司按国际惯例策划、撰写的项目商业计划书已经成为众多境内外实力雄厚的投资银行、国际风险投资公司、境内优秀企业投资立项的重要依椐。为能使贵公司的项目与国际投资银行、风险投资公司、境内实力雄厚的企业投资合作更加顺利开展和运行，按国际惯例撰写项目商业计划书是获得有关境内外投资合作的必要途径。只有这样，才能将您的项目更加系统、完善地展现给境内外投融资商的高层决策者；也才有可能更好地获得境内外投融资商的青睐与投资合作。 提供各行业投资服务,包括项目评估,项目策划,投资项目委托,项目可行性分析报告,商业计划书,各行业市场研究报告,深度决策分析，各类投标书。（各类文书可中英文书写） 一、什么是商业计划书？ 二、为什么要撰写商业计划书？ 三、商业计划书的格式与内容? 四、我们的经验及实力 一、什么是商业计划书？ 商业计划书是公司或项目单位为了达到招商融资和其它发展目标之目的，在经过前期对项目科学地调研、分析、搜集与整理有关资料的基础上，根据一定的格式和内容的具体要求而编辑整理的一个向读者全面展示公司和项目目前状况、未来发展潜力的书面材料。它有别于传统的《项目建议书及项目可行性研究报告》。商业计划书考虑问题更全面，更注重操作性、更强调经济效益，也有不同的格式和内容的具体要求。另外二者所针对的对象也有所不同，前者是针对我国各级政府和其它有关部门的要求而整理的书面材料，而商业计划书是针对各类潜在的投资者而一开始就需要准备的一项最重要的书面材料。如果国际融资是你融资计划的一个范畴，那么你一定要准备一份英文版的商业计划书。 二、为什么要撰写商业计划书？ 从广义上来讲，因为所有公司、企业的项目在运作中都或多或少地含有这样那样的风险，单是从经济层面来考虑，也没有100%的保证。所以，从投资者的角度来看都会把所有的项目看作风险项目，把准备投资的公司、企业看作风险企业。国内外融资方式虽说有很多种，但从严格意义上来讲，它们都应该归属于风险投资这个大范畴。对于正在寻求资金的风险企业来说，商业计划书的好坏，往往决定了投资交易的成败。 企业整理、撰写商业计划书的过程，也是首先把该项目推销给企业和企业家自己的过程。作为连你自己都不相信的商业计划，你是不可能推销给别人的，更不用说精明过人的国内、国际投资者。反过来，即使一个实际上很好的项目，如果没有通过商业计划书这一众多投资者认可的文字方式充分展示出来，其结果很可能仍是把项目留给了企业家自己。其次，商业计划书还能帮助把计划中的风险企业推销给风险投资家，它的主要目的之一就是为了招商融资，谋求更大发展。最后，对已建的风险企业来说，它还可以为企业的发展定下较具体的重点和方向，从而使员工了解企业的经营目标，并激励他们为共同的目标而努力。 商业计划书的重要性不言而喻。现代招商融资没有商业计划书几乎是不可能成功的，同样没有一个正规、完整的商业计划书那也是希望渺茫。 三、商业计划书的格式与内容： 尽管每一份商业计划书都有各自的特色，但是投资者们还是希望看到其共同点，即商业计划书的基本构成和内容： 第一部分： 计划摘要。（计划摘要浓缩了的商业计划书的精华，主要是用来激起投资者的兴趣，以求一目了然，以便投资者能在几分钟时间内评审计划并做出初步判断。） 第二部分： 综述。主要包括：1、公司概述；2、技术、产品（服务）；3、市场分析；4、竞争分析；5、营销策略；6、投资说明；7、投资报酬与退出机制；8、风险分析；9、人员及组织管理；10、经营预测；11、财务规划分析。 第三部分： 附录（包括附件和附表） 四、我们的经验及实力 广州纳福咨询有限公司，它拥有一个专业的中、英文商业计划书写团队，具有工商管理、信息技术、经济、金融等专业知识，通晓国内外商业计划书撰写的方式及方法，客观、公正、实效、科学是我们的工作原则。并且成功为国内多家企业、组织、个人完成商业计划书的撰写、审核以及招商融资咨询服务，得到客户的满意和肯定。 广州纳福咨询有限公司随时恭候您的来电来函，并愿意为贵公司招商融资工作的成功助一臂之力！ 广州纳福咨询有限公司 地址:广州市环市东路花园酒店大厦637室邮政编码:510064 电话:020-85801047 39700976 传真:020-83338999-637 E-mail:[EMAIL PROTECTED] ―― 【注意】上面的邮件内容与以下文字无关。本软件仅限于合法用途! 该邮件由《Volleymail邮件群发专家》软件发送；被网友评为最厉害 的邮件群发软件而多次要求破解！现免费下载，无限时间使用。 详情请访问我们的主页：http://www.cnysoft.com/- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage autosuspend bug?
On Fri, 27 Jul 2007, Oliver Neukum wrote: Am Donnerstag 26 Juli 2007 schrieb Greg KH: Alan and Oliver, was this caused by the autosuspend changes for usb-storage? The oops itself looks like refcounting. What caused the initial io error does not become clear from the log. It is possible that the device cannot stand suspension. But there's no evidence from that. On the contrary, these devices usually do an unplug/plug cycle, which is not in the log. I don't think it's a refcounting problem. My guess is that the underlying cause is the bug in your urb-status removal patch for usb_start_wait_urb() -- the one I fixed here: http://marc.info/?l=linux-usb-develm=118531582013355w=2 Of course, my guess could be wrong. I haven't tried to recreate Linus's bug with that patch reverted. But with the patch present I was not able to duplicate the bug. Alan Stern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] About current state of supporting USB selective suspend feature
On Fri, 27 Jul 2007, gutian abei wrote: Dear All: I am trying to develop a USB device driver in Linux platform. I want to know the current state of supporting USB selective suspend feature of Linux USB core. This feature is described by USB specification 2.0. The USB core supports selective suspend (also known as runtime suspend or autosuspend). However individual USB device drivers must also include support, which means the driver must implement at least a suspend() and a resume() method, and it must set the .supports_autosuspend flag in its usb_driver structure. It also must call usb_autopm_get_interface() and usb_autopm_put_interface() at the appropriate times. There's a lot of documention in the comments in drivers/usb/core/driver.c. Alan Stern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] ehci problem triggerable by storage
On Fri, 27 Jul 2007, Oliver Neukum wrote: Hi, stressing a flash disk I rapidly get this error: Jul 27 12:35:00 oenone kernel: ehci_hcd :00:02.2: devpath 3.4 ep1in 3strikes Jul 27 12:35:00 oenone kernel: usb-storage: Status code -71; transferred 8192/122880 Is there a way I can enable more debugging about this cause of -EPROTO? In my experience this sort of thing tends to be caused by low-level hardware communications errors. Noise in the USB data lines or a missing handshake packet, stuff like that. Not much extra debugging can be done; the 3strikes indication comes directly from the controller hardware. It's possible that a CPU speed transition could interfere with DMA during a transfer. You could see if disabling CPU_FREQ makes any difference. Alan Stern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] force USB_SPEED_FULL for device
Hello, How could one force a device to be configured with USB_SPEED_FULL if it's a USB_SPEED_LOW device i.e. a Dell keyboard? I tried to simply set usb_device-speed = USB_SPEED_FULL but I get a protocol error. I then tried to trace where the EPROTO is being generated but couldn't do so. Thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On 7/27/07, Gabriel Maganis [EMAIL PROTECTED] wrote: Hello, How could one force a device to be configured with USB_SPEED_FULL if it's a USB_SPEED_LOW device i.e. a Dell keyboard? If it's a low_speed-only device it won't work as full speed. This doesn't depend only on the controller/hub, but the usb device controller chip on the keyboard. Thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel -- Best Regards, Felipe Balbi [EMAIL PROTECTED] - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] ehci problem triggerable by storage
Hi, stressing a flash disk I rapidly get this error: Jul 27 12:35:00 oenone kernel: usb-storage: *** thread awakened. Jul 27 12:35:00 oenone kernel: usb-storage: Command READ_10 (10 bytes) Jul 27 12:35:00 oenone kernel: usb-storage: 28 00 00 00 25 f8 00 00 3c 00 Jul 27 12:35:00 oenone kernel: usb-storage: Bulk Command S 0x43425355 T 0x28b L 122880 F 128 Trg 0 LUN 0 CL 10 Jul 27 12:35:00 oenone kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes Jul 27 12:35:00 oenone kernel: usb-storage: Status code 0; transferred 31/31 Jul 27 12:35:00 oenone kernel: usb-storage: -- transfer complete Jul 27 12:35:00 oenone kernel: usb-storage: Bulk command transfer result=0 Jul 27 12:35:00 oenone kernel: usb-storage: usb_stor_bulk_transfer_sglist: xfer 122880 bytes, 2 entries Jul 27 12:35:00 oenone kernel: ehci_hcd :00:02.2: devpath 3.4 ep1in 3strikes Jul 27 12:35:00 oenone kernel: usb-storage: Status code -71; transferred 8192/122880 Jul 27 12:35:00 oenone kernel: usb-storage: -- unknown error Jul 27 12:35:00 oenone kernel: usb-storage: Bulk data transfer result 0x4 Jul 27 12:35:00 oenone kernel: usb-storage: -- transport indicates error, resetting Jul 27 12:35:00 oenone kernel: usb-storage: storage_pre_reset Jul 27 12:35:00 oenone kernel: usb 3-3.4: reset high speed USB device using ehci_hcd and address 10 Jul 27 12:35:00 oenone kernel: usb_endpoint usbdev3.10_ep01: ep_device_release called for usbdev3.10_ep01 Jul 27 12:35:00 oenone kernel: usb_endpoint usbdev3.10_ep81: ep_device_release called for usbdev3.10_ep81 Jul 27 12:35:00 oenone kernel: usb-storage: storage_post_reset Jul 27 12:35:00 oenone kernel: usb-storage: usb_reset_composite_device returns 0 Jul 27 12:35:00 oenone kernel: usb-storage: scsi cmd done, result=0x7 Jul 27 12:35:00 oenone kernel: usb-storage: queuecommand called Jul 27 12:35:00 oenone kernel: usb-storage: *** thread sleeping. Jul 27 12:35:00 oenone kernel: usb-storage: *** thread awakened. Jul 27 12:35:00 oenone kernel: usb-storage: Command READ_10 (10 bytes) Jul 27 12:35:00 oenone kernel: usb-storage: 28 00 00 00 25 f8 00 00 3c 00 Jul 27 12:35:00 oenone kernel: usb-storage: Bulk Command S 0x43425355 T 0x28c L 122880 F 128 Trg 0 LUN 0 CL 10 Jul 27 12:35:00 oenone kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes Jul 27 12:35:00 oenone kernel: usb-storage: Status code 0; transferred 31/31 Jul 27 12:35:00 oenone kernel: usb-storage: -- transfer complete Jul 27 12:35:00 oenone kernel: usb-storage: Bulk command transfer result=0 Jul 27 12:35:00 oenone kernel: usb-storage: usb_stor_bulk_transfer_sglist: xfer 122880 bytes, 2 entries Is there a way I can enable more debugging about this cause of -EPROTO? Regards Oliver - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Do it for pleasure
attachment: tamtam.gif- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Experimental driver for USB dongle 07d0:4100 (Kingsun/Dazzle) - looking for testers
Yesterday, Ashik Ahamed from the irda-users mailing list send me a SnoopyPro log showing communication for the USB IrDA dongle whose descriptors are 07d0:4100 (which I call the Kingsun/Dazzle dongle). I do not have the dongle, so this driver is completely untested. I only guarantee that it will compile. At least once. On 2.6.23-rc1. On my home machine :-) I am looking for people who do have the dongle, and are willing to see if this driver works for them. Please point out any stupid mistakes I may have done in the code. Also test if the range of speeds this dongle supports, which might be higher (or lower!) than the 2400-115200 bps indicated by the probe routine. Even if you are not running exactly 2.6.23-rc1, you can test it if you run any 2.6.x kernel. Alex Villacís Lasso -- perl -e '$x=2.4;print sprintf(%.0f + %.0f = %.0f\n,$x,$x,$x+$x);' ksdazzle.tar.bz2 Description: BZip2 compressed data - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
Hi, from the device side a low speed and a full speed device differ fundamentally. They even differ in the way a resistor is connected to the USB data lines. You can't just overwrite this by software. It's a hardware thing. Till Am Freitag 27 Juli 2007 schrieb Gabriel Maganis: Hello, How could one force a device to be configured with USB_SPEED_FULL if it's a USB_SPEED_LOW device i.e. a Dell keyboard? I tried to simply set usb_device-speed = USB_SPEED_FULL but I get a protocol error. I then tried to trace where the EPROTO is being generated but couldn't do so. Thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Volunteer to be the new usb.ids maintainer!!
I think we need a new usb.ids maintainer ... I get way too much email from folk saying Vojtech hasn't responded so would I please merge the IDs. (Vojtech, if you disagree, please speak up!) What's required? Be a member of the sourceforge linux-usb project, so you can update the CVS for http://www.linux-usb.org/usb.ids ... and respond to the emails periodically. Maybe read new USB.org class specs to collect new IDs they assign. Other members of that project will update that file periodically, but there needs to be a designated lead contact. So -- someone, please volunteer! - Dave - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On 7/27/07, Pete Zaitcev [EMAIL PROTECTED] wrote: On Fri, 27 Jul 2007 11:29:07 -0700, Gabriel Maganis [EMAIL PROTECTED] wrote: Thanks for the help below. I am trying to answer what will the keyboard send me if I send it a packet configured over USB_SPEED_FULL?. Simply setting usb_device-speed to USB_SPEED_FULL doesn't work as the packet does not even get sent by the subsystem/hcd. How do you know that the packet is not sent? The EPROTO you are getting is what happens when packet IS sent and gets no reply. -- Pete P.S. Gmail is not a valid excuse for top-posting. I have one of those protocol analyzers in between and it doesn't see anything. I tried to look for where the EPROTO is being returned from but grep -r doesn give me relevant results. I also looked at the sanity checks in submit_urb but I don't think any are doing anything about the speed. Would you know which file would contain the lowest level routine that sends the packets? Thanks. Gabriel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On Fri, 27 Jul 2007 11:29:07 -0700, Gabriel Maganis [EMAIL PROTECTED] wrote: Thanks for the help below. I am trying to answer what will the keyboard send me if I send it a packet configured over USB_SPEED_FULL?. Simply setting usb_device-speed to USB_SPEED_FULL doesn't work as the packet does not even get sent by the subsystem/hcd. How do you know that the packet is not sent? The EPROTO you are getting is what happens when packet IS sent and gets no reply. -- Pete P.S. Gmail is not a valid excuse for top-posting. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
Hello, Thanks for the help below. I am trying to answer what will the keyboard send me if I send it a packet configured over USB_SPEED_FULL?. Simply setting usb_device-speed to USB_SPEED_FULL doesn't work as the packet does not even get sent by the subsystem/hcd. Would you have an idea how I can at least send the packet over the wire? Thanks, Gabriel On 7/27/07, Till Harbaum / Lists [EMAIL PROTECTED] wrote: Hi, from the device side a low speed and a full speed device differ fundamentally. They even differ in the way a resistor is connected to the USB data lines. You can't just overwrite this by software. It's a hardware thing. Till Am Freitag 27 Juli 2007 schrieb Gabriel Maganis: Hello, How could one force a device to be configured with USB_SPEED_FULL if it's a USB_SPEED_LOW device i.e. a Dell keyboard? I tried to simply set usb_device-speed = USB_SPEED_FULL but I get a protocol error. I then tried to trace where the EPROTO is being generated but couldn't do so. Thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On Fri, 27 Jul 2007, Gabriel Maganis wrote: On 7/27/07, Pete Zaitcev [EMAIL PROTECTED] wrote: On Fri, 27 Jul 2007 11:29:07 -0700, Gabriel Maganis [EMAIL PROTECTED] wrote: Thanks for the help below. I am trying to answer what will the keyboard send me if I send it a packet configured over USB_SPEED_FULL?. Simply setting usb_device-speed to USB_SPEED_FULL doesn't work as the packet does not even get sent by the subsystem/hcd. How do you know that the packet is not sent? The EPROTO you are getting is what happens when packet IS sent and gets no reply. -- Pete P.S. Gmail is not a valid excuse for top-posting. I have one of those protocol analyzers in between and it doesn't see anything. I tried to look for where the EPROTO is being returned from but grep -r doesn give me relevant results. I also looked at the sanity checks in submit_urb but I don't think any are doing anything about the speed. Would you know which file would contain the lowest level routine that sends the packets? A more important question is: Why do you want to change usb_device-speed from USB_SPEED_LOW to USB_SPEED_FULL? Was there something wrong with the USB_SPEED_LOW setting? Alan Stern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
Hi, Am Freitag 27 Juli 2007 schrieb Gabriel Maganis: I have one of those protocol analyzers in between and it doesn't see anything. I tried to look for where the EPROTO is being returned from Where is this in between? Is it directly in front of the keyboard? I am quite sure that full speed messages are dropped by the hub the low speed device is connected to as it just can't forward the packet on the low speed link. If there was some seperate hub before the keyboard you might see something on this hubs upstream link as that is a full speed link. If your keyboard is directly connected to the pc you won't see anything with your analyzer since the root hub inside your pc does not forward the full speed packet to the usb output of your pc the low speed device is connected to. Till - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On 7/27/07, Alan Stern [EMAIL PROTECTED] wrote: On Fri, 27 Jul 2007, Gabriel Maganis wrote: On 7/27/07, Pete Zaitcev [EMAIL PROTECTED] wrote: On Fri, 27 Jul 2007 11:29:07 -0700, Gabriel Maganis [EMAIL PROTECTED] wrote: Thanks for the help below. I am trying to answer what will the keyboard send me if I send it a packet configured over USB_SPEED_FULL?. Simply setting usb_device-speed to USB_SPEED_FULL doesn't work as the packet does not even get sent by the subsystem/hcd. How do you know that the packet is not sent? The EPROTO you are getting is what happens when packet IS sent and gets no reply. -- Pete P.S. Gmail is not a valid excuse for top-posting. I have one of those protocol analyzers in between and it doesn't see anything. I tried to look for where the EPROTO is being returned from but grep -r doesn give me relevant results. I also looked at the sanity checks in submit_urb but I don't think any are doing anything about the speed. Would you know which file would contain the lowest level routine that sends the packets? A more important question is: Why do you want to change usb_device-speed from USB_SPEED_LOW to USB_SPEED_FULL? Was there something wrong with the USB_SPEED_LOW setting? Alan Stern Hello Alan, I would just like to know what response (if at all, garbage, or meaningful) it would give me if I send it a packet at USB_SPEED_FULL. Do I also need to change some fields in the usb_device structure? I tried changing the ep0.desc.wMaxPacketSize to match a device configured at full speed but it didn't work also. Thanks, Gabriel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On Fri, 27 Jul 2007, Gabriel Maganis wrote: A more important question is: Why do you want to change usb_device-speed from USB_SPEED_LOW to USB_SPEED_FULL? Was there something wrong with the USB_SPEED_LOW setting? Alan Stern Hello Alan, I would just like to know what response (if at all, garbage, or meaningful) it would give me if I send it a packet at USB_SPEED_FULL. Do I also need to change some fields in the usb_device structure? I tried changing the ep0.desc.wMaxPacketSize to match a device configured at full speed but it didn't work also. But why? If you have a low-speed device like a keyboard and you send it a packet at full-speed, the device won't be able to receive the packet. Hence it won't send a reply, at any speed. There's no need to actually do a test; it can't possibly work. Alan Stern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On 7/27/07, Till Harbaum / Lists [EMAIL PROTECTED] wrote: Hi, Am Freitag 27 Juli 2007 schrieb Gabriel Maganis: I have one of those protocol analyzers in between and it doesn't see anything. I tried to look for where the EPROTO is being returned from Where is this in between? Is it directly in front of the keyboard? I am quite sure that full speed messages are dropped by the hub the low speed device is connected to as it just can't forward the packet on the low speed link. If there was some seperate hub before the keyboard you might see something on this hubs upstream link as that is a full speed link. If your keyboard is directly connected to the pc you won't see anything with your analyzer since the root hub inside your pc does not forward the full speed packet to the usb output of your pc the low speed device is connected to. Till Ah. I'm pretty sure the connection is such that the analyzer is a passive listener i.e. the keyboard is connected to my computer, so that means I have to modify some routine in hub.c to forward the packet anyway? I guess my question has been where might I look for the code that can let me bypass the logic that prevents the root hub from forwarding this packet? Thanks! Gabriel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] force USB_SPEED_FULL for device
On Fri, 27 Jul 2007, Gabriel Maganis wrote: Hello Alan, I guess I'm trying to bypass the code that makes it so it can't possibly work. I'm trying not to say what it is I'm trying to do in general I guess :). But I really would just like to be able to send that packet. Would you know if the code I might look at is in usbcore or should I look at the HCD code? I've tried grepping around quite a bit but I'm not sure what it is really I should look for. It isn't code at all -- it won't work because of the hardware! The low-speed keyboard's USB interface hardware is looking for signals at 1.5 MHz. If the computer starts sending full-speed data, it will be modulated at 12 MHz. Furthermore, at low-speed a 0 is indicated by a high voltage on the D- line whereas at full-speed a 0 is indicated by a high voltage on the D+ line. (Or maybe I have them reversed, but one is definitely the opposite of the other.) The keyboard's hardware can't possible cope with that. Alan Stern - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Edgeport UPS Monitoring Problems
On Fri, 27 Jul 2007 13:37:08 -0700 Nick Pasich [EMAIL PROTECTED] wrote: Greg/Peter/Al, added linux-usb-devel. I've been using the edgeport 4 port USB to Serial Converter to monitor APC Smart UPS's via apcupsd for quite awhile on various Linux boxes. I just upgraded to Kernel Version 2.6.22.1 from 2.6.20.6 on a couple of systems and both the edgeports stopped communicating. I tried applying various patches, PATCH 026/149 and PATCH 082/149 and one by Alan Cox.. but they didn't fix the problem. I copied the 2.6.20.6 edgeport module sources to the new 2.6.22.1 tree and everything works again. linux/drivers/usb/serial/io_edgeport.c linux/drivers/usb/serial/io_edgeport.h linux/drivers/usb/serial/io_edgeport.mod.c linux/drivers/usb/serial/io_tables.h I thought you guys ought to be aware of this Straightforward regression, most serious. Thanks for reporting it. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
