On Sat, 17 Dec 2005, Pete Zaitcev wrote:
> On Sat, 17 Dec 2005 17:57:28 -0500 (EST), Alan Stern <[EMAIL PROTECTED]>
> wrote:
>
> > I did my best to test and check that no errors are introduced by these
> > patches, but their sum is so large and far-reaching that problems are
> > practically in
Marwan Cyril Sabra wrote:
> Le mercredi 07 décembre 2005 à 10:16 -0500, Alan Stern a écrit :
>
>>On Wed, 7 Dec 2005, Marwan Cyril Sabra wrote:
>>
>>
>>>[4296233.326000] usb-storage: This device (0482,0105,0100 S 06 P 50) has
>>>unneede d SubClass and Protocol entries in unusual_devs.h
>>>[4296233.
On Sat, 17 Dec 2005 17:57:28 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> I did my best to test and check that no errors are introduced by these
> patches, but their sum is so large and far-reaching that problems are
> practically inevitable. You might want to hold off sending them to
>
I was hoping to add the change to sys_write or furthur
down in the chain i.e adding a lookup table with the
file path and a unique usb device id. In addition add
a few new apis to the kernel. If during a sys_write a
match is found then perforn a callback/event to the
application layer and dump the
【网络营销大全】光盘专业版V2005
-把您的广告信息直接投入到客户的信箱
...会员制网站！一次付费，永久享受免费会员升级服务!
...每月提供100万以上免费升级更新服务!
...免费为会员定制搜索。
...QQ在线答疑，解答使用中的各类问题。
---包括8300万综合邮件地址，2819万分地区、分行业邮箱地址。
---自由选择，可以定向群发。
---赠送各类群发软件、邮箱搜索软件、信息发布软件、邮箱切割软件、
邮箱过滤重复
On Sat, 17 Dec 2005, gary clark wrote:
> Hi Randy,
>
> I wanted to know the sequence of drivers and calls
> that are involved when a "cp" is performed to a usb
> device. Alan Stern gave of course an excellent
> response on this. Seems like there are a few more
> actors in this than I thought.
>
It sounds like you should be looking at Dazuko (www.dazuko.org) which
allows you to trap exactly such events.
Matt
On Sat, Dec 17, 2005 at 02:51:12PM -0800, gary clark wrote:
>
> Hi Randy,
>
> I wanted to know the sequence of drivers and calls
> that are involved when a "cp" is performed to a u
On Sat, 17 Dec 2005 14:51:12 -0800 (PST) gary clark wrote:
>
> Hi Randy,
>
> I wanted to know the sequence of drivers and calls
> that are involved when a "cp" is performed to a usb
> device. Alan Stern gave of course an excellent
> response on this. Seems like there are a few more
> actors in t
Greg:
This patch (as626) makes some improvements to the debugging code in
uhci-hcd. The main change is that now the code won't get compiled if
CONFIG_USB_DEBUG isn't set. But there are other changes too, like adding
a missing .owner field and printing a debugging dump if the controller
dies.
Al
Greg:
As part of reorienting uhci-hcd away from URBs and toward endpoint queues,
this patch (as625) eliminates the driver's main list of URBs. The list
wsa used mainly in checking for URB completions; now the driver goes
through the list of active endpoints and checks the members of the queues
Greg:
This patch (as624) fixes a hardware race in uhci-hcd by adding a dummy TD
to the end of each endpoint's queue. Without the dummy the host
controller will effectively turn off the queue when it reaches the end,
which happens asynchronously. This leads to a potential problem when new
transfe
Greg:
The following set of patches makes some drastic changes to the internal
organization of uhci-hcd. The current version is based on a design that
goes back to the days of Linux 2.3, I believe. It is centered around the
idea of URBs, and all its processing is based on that concept. In
partic
Hi Randy,
I wanted to know the sequence of drivers and calls
that are involved when a "cp" is performed to a usb
device. Alan Stern gave of course an excellent
response on this. Seems like there are a few more
actors in this than I thought.
I have been asked to log all files that are copied to
I didnt know I was including the archive. If so I wont
do it. Anyway thanks for the info. Thats certainly
quite a list of drivers involved in writing a message.
Thanks,
garyc
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> PLEASE, in the future don't include long irrelevant
> copies of a
> mail-ar
PLEASE, in the future don't include long irrelevant copies of a
mail-archive digest message in your postings!!
On Sat, 17 Dec 2005, gary clark wrote:
> Hello,
>
> I want to trace what happens when a file is copied to
> a usb storage device. The linux "cp" command will
> perform an open on
> th
On Sat, 17 Dec 2005, Gerardo Contreras wrote:
> Hi.
>
> I got an IPAQ rx3115. No matter what I do, I can't get it working on my
> machine.
>
> When I connect it to the USB port, I get this on the console:
> [4377232.98] usb 3-2: new full speed USB device using uhci_hcd and
> address
> 2
>
On Sat, 17 Dec 2005 12:49:35 -0800 (PST) gary clark wrote:
>
> Hello,
>
> I want to trace what happens when a file is copied to
> a usb storage device. The linux "cp" command will
> perform an open on
> the path given and obtain the inode which is used to
> access the usb device. Can somebody te
Hello,
I want to trace what happens when a file is copied to
a usb storage device. The linux "cp" command will
perform an open on
the path given and obtain the inode which is used to
access the usb device. Can somebody tell me what
driver is used that has the write function or an ioctl
call to th
Hi.
I got an IPAQ rx3115. No matter what I do, I can't get it working on my
machine.
When I connect it to the USB port, I get this on the console:
[4377232.98] usb 3-2: new full speed USB device using uhci_hcd and address
2
[4377233.135000] ipaq 3-2:2.0: PocketPC PDA converter detected
[437
On Sat, 17 Dec 2005, Pete Zaitcev wrote:
> Resets are done at the context of the system event daemon, using the
> yucky API copied from usb-storage. This was the most expeditious way,
> but my gosh, that code is more horrible than I imagined...
I understand and sympathize with your reaction. Can
Implement command retries and resets in ub. It is advantageous for users
to know if their devices are getting bad. However, failing every I/O
is not practical if you have a external USB enclosure with a hard drive.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
---
Resets are done at the contex
Am Donnerstag, 15. Dezember 2005 22:13 schrieb Sam Bishop:
> Oliver Neukum wrote:
> > On second thought, the skeleton driver doesn't even limit the buffersize
> > to something sane. Triggering 128K allocations in unlimited numbers is
> > not nice at all.
> >
> > Regards
> > Oliver
22 matches
Mail list logo
