Hello All,
I am using usbser.sys(Windows Host) and generating Virtual COM port.
My device side application writes 2000 bytes to that port. The host side
application reads some data, comes out of read and parses the first 2
bytes to get the actual length of data to read, and then issues a read
ca
>> Can anybody with experience in pxa255 explain whether it's possible for
>> pxa255 or for pxa2xx_udc driver to lose an bulk-out interrupt?
>
>You mean, is this a bug in that driver?
Of course not! At least not at this time.
>Maybe. It's not changed
>a lot recently ... but for what it's wort
Hi David!
I got what you meant. Sorry, it seems I misled you with my modified
logs. But anyway the behaviour of g_file_storage gadget and pxa2xx_udc
driver is the same as if I use only standard output or even without any
debugging output at all.
Ok, here are the log messages with debug level tu
Kent Forschmiedt wrote:
Excuse me, that's "cat /proc/kmsg". /proc/kmsg acts like a fifo.
Kent Forschmiedt
Wildseed, Ltd.
http://www.wildseed.com
-Original Message-
From: Kent Forschmiedt
Sent: Wednesday, January 12, 2005 2:30 PM
To: 'David Brownell'; linux-usb-devel@lists.sourceforge.net
I didn't realize FC3 was mounting this drive, else I might have done
things differently ... but I think everyone will agree that oopsing
is not OK. See the following dmesg trace.
I've seen a lot of messages about similar failures lately, as if
maybe more distros are automounting removable drives.
SN9C10x driver updates.
Changes:
@ Fix the sysfs interface
@ Fix allocated minor number after device detection
+ Add "force_munmap" module parameter
+ Documentation updates
+ Add support for old VIDIOC_S_PARM_OLD and VIDIOC_S_CTRL_OLD ioctl's
Signed-off-by: Luca Risolia <[EMAIL PROTECTED]>
Greg
On Wed, Jan 12, 2005 at 09:08:19PM +0100, Florian Echtler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This patch adds a new usb-misc driver for the fingerprint sensor that
> can be found in the Siemens ID Mouse USB. "cat /dev/usb/idmouseX"
> yields a 225x288 greyscale PNM with the
All true, and still, it helps a lot. I did say "It helps", not "It fixes
everything". Printk to memory is way faster than printk to serial and
creates fewer problems. I do a lot of USB debugging on PXA255 and PXA26x,
and this trick saves me a lot of grief.
Kent Forschmiedt
Wildseed, Ltd.
http:/
Excuse me, that's "cat /proc/kmsg". /proc/kmsg acts like a fifo.
Kent Forschmiedt
Wildseed, Ltd.
http://www.wildseed.com
-Original Message-
From: Kent Forschmiedt
Sent: Wednesday, January 12, 2005 2:30 PM
To: 'David Brownell'; linux-usb-devel@lists.sourceforge.net
Cc: Alan Stern; Vladi
It helps if you do this:
echo 0 >/proc/sys/kernel/printk
tail -f /proc/kmsg
Kent Forschmiedt
Wildseed, Ltd.
http://www.wildseed.com
-Original Message-
From: David Brownell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 12, 2005 2:24 PM
To: linux-usb-devel@lists.sourceforge.net
Cc: A
On Wednesday 12 January 2005 2:30 pm, Kent Forschmiedt wrote:
> It helps if you do this:
>
> echo 0 >/proc/sys/kernel/printk
> tail -f /proc/kmsg
>
Not for all problems. Like if you're chasing a system lockup,
you really _need_ to know the last few events, and "tail" is
never going to show them
On Tuesday 11 January 2005 8:13 am, Alan Stern wrote:
> On Tue, 11 Jan 2005, Vladimir Trukhin wrote:
>
> This extra wakeup must be from the completion of the previous bulk-in
> message.
>
> > g_file_storage gadget: get_next_command: wait for next packet (time:
> > 7806.73421 s):
> >
> > udc: p
On Wednesday 12 January 2005 22:19, Alan Stern wrote:
> On Wed, 12 Jan 2005, Jan De Luyck wrote:
> > On Wednesday 12 January 2005 06:09, Linus Torvalds wrote:
> > > Matthew Dharm:
> > > o USB Storage: support 'bulk32' devices
> > > o USB Storage: Increase Genesys delay
> >
> > The Genesys incre
On Wed, 12 Jan 2005, Jan De Luyck wrote:
> On Wednesday 12 January 2005 06:09, Linus Torvalds wrote:
>
> > Matthew Dharm:
> > o USB Storage: support 'bulk32' devices
> > o USB Storage: Increase Genesys delay
>
> The Genesys increased delay in this patch causes strange issues, the USB
> disc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This patch adds a new usb-misc driver for the fingerprint sensor that
can be found in the Siemens ID Mouse USB. "cat /dev/usb/idmouseX"
yields a 225x288 greyscale PNM with the fingerprint information.
It's now in version 0.5, which uses memcpy() inste
On Wed, 12 Jan 2005, David Brownell wrote:
> No timer. This should be detected by checking the packets
> sent by the device. There are basically two cases when
> reading any IN (*) packet (not just control transfers):
>
> - Peripheral sends N = maxpacket bytes ... this particular
>packet w
> No timer. This should be detected by checking the packets
> sent by the device. There are basically two cases when
> reading any IN (*) packet (not just control transfers):
>
> - Peripheral sends N = maxpacket bytes ... this particular
>packet wasn't "short", so the transfer proceeds (unl
Hi I have that message in my dmesg. If somebody is interested in that
can contact me by e-mail to provide more informations.
I use Slackware current with custom build kernel 2.6.10
On a Sony Vaio PCG-GRT816S laptop.
Best Regards
Sasa Ostrouska
quickcam: QuickCam USB camera found (driver version
On Wednesday 12 January 2005 06:09, Linus Torvalds wrote:
> Matthew Dharm:
> o USB Storage: support 'bulk32' devices
> o USB Storage: Increase Genesys delay
The Genesys increased delay in this patch causes strange issues, the USB
disconnects after a while...
I rewrote the identifier like it
On Tue, Jan 11, 2005 at 07:53:05PM -0800, David Brownell wrote:
> Please merge; this patch adds another device, and finally makes sure
> that Zaurus (and similar) models can never by mis-claimed by the CDC
> Ethernet support, even if the Zaurus support is disabled.
Applied, thanks.
greg k-h
---
Hi everybody,
We are currently working with uClinux, kernel 2.4.26-uc1
I've imported the USB serial adapter console feature from the kernel 2.5.75,
and after some changes in function's names and prototypes, it compiles
successfully... the problem is, even after specifying the new console to th
Begin forwarded message:
Date: Wed, 12 Jan 2005 04:15:22 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 4024] New: fault to mount usb storage
http://bugme.osdl.org/show_bug.cgi?id=4024
Summary: fault to mount usb storage
Kernel Version: 2.6.10-mm3
On Wed, Jan 12, 2005 at 06:07:02PM +0200, Alexey Dobriyan wrote:
> Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Thanks for rediffing this. Applied to my trees.
greg k-h
---
The SF.Net email is sponsored by: Beat the post-holiday blues
G
On Wed, 12 Jan 2005, Brian Ristuccia wrote:
> On Wed, Jan 12, 2005 at 07:42:57AM -0800, David Brownell wrote:
> >
> > The current stack doesn't have such a way, but it sounds almost like
> > you're describing the ability to selectively power down (and back up)
> > a given hub port ... which USB c
Hi David,
here is a patch that fixes an obvious copy/paste error in your
sl811-hcd driver:
--- linux-2.6.10/drivers/usb/host/sl811-hcd.c
+++ linux-2.6.10-karo/drivers/usb/host/sl811-hcd.c
@@ -1768,7 +1768,7 @@
status = -ENOMEM;
goto fail;
}
- sl811->d
On Wed, 12 Jan 2005, David Brownell wrote:
Sounds like the theory I was ending up with ... :)
What a coincidence.. ;-)
The bridge code was able to detect the link coming back up, as if
maybe it were talking directly to the MII and not needing to rely
You mean the user level code running on the same
On Wednesday 12 January 2005 8:47 am, Petko Manolov wrote:
> On Wed, 12 Jan 2005, David Brownell wrote:
>
> > The bridge code was able to detect the link coming back up, as if
> > maybe it were talking directly to the MII and not needing to rely
>
> You mean the user level code running on the sam
On Wed, Jan 12, 2005 at 07:42:57AM -0800, David Brownell wrote:
>
> The current stack doesn't have such a way, but it sounds almost like
> you're describing the ability to selectively power down (and back up)
> a given hub port ... which USB certainly allows.
>
Yes! You've hit the nail right on
On Wed, 12 Jan 2005, David Brownell wrote:
You're the maintainer, so it'd be good if you added Signed-off-by and
forwarded it to him.
OK.
Mike Nix confirmed it resolved the bridging issue for him too, but
reported some problems detecting carrier loss. Does that ring any
bells for you? I found the
On Wednesday 12 January 2005 8:13 am, David Brownell wrote:
> The _really_ tricky bit is that if your HCD skips the
> DATA stage it'll usually work. Except ... that some
> peripherals will misbehave (badly) when you do that,
> leading to some mysterious failures later on, but only
> with c
On Wednesday 12 January 2005 8:02 am, Petko Manolov wrote:
> On Wed, 12 Jan 2005, David Brownell wrote:
>
> > Mike Nix confirmed it resolved the bridging issue for him too, but
> > reported some problems detecting carrier loss. Does that ring any
> > bells for you? I found the link status bit yo
On Wednesday 12 January 2005 6:56 am, Petko Manolov wrote:
> Thanks Dave, very exhaustive patch description. :-)
It's penance for updating more than one thing in a patch ... ;)
> Played wiht it in the morning and seems that the is working fine. Will
> you send the patch to Greg or i do this?
On Wednesday 12 January 2005 7:18 am, Olav Kongas wrote:
> Hi David,
>
> I've got usbtest running on top of isp116x-hcd, the
> periferal end is net2280 chip.
Good! I see it's already helped you find an issue... ;)
> When running test #10 subtest #10, the driver is in
> trouble. This is the cas
On Wednesday 12 January 2005 3:37 am, Trukhin Vladimir Igorevich wrote:
>
> Can anybody with experience in pxa255 explain whether it's possible for
> pxa255 or for pxa2xx_udc driver to lose an bulk-out interrupt?
You mean, is this a bug in that driver? Maybe. It's not changed
a lot recently ..
Thanks Dave, very exhaustive patch description. :-)
Played wiht it in the morning and seems that the is working fine. Will
you send the patch to Greg or i do this?
Petko
On Tue, 11 Jan 2005, David Brownell wrote:
I ran into http://bugme.osdl.org/show_bug.cgi?id=3978 a while back, did
On Tuesday 11 January 2005 8:01 pm, Brian Ristuccia wrote:
>
> Is there an existing way for me to programaticly disconnect a device from
> the USB bus? Perhaps I'm looking in the wrong places, but I can't find
> anything in the linux USB API.
>
> I can get roughly the behavior I want by installin
Hi David,
I've got usbtest running on top of isp116x-hcd, the
periferal end is net2280 chip.
When running test #10 subtest #10, the driver is in
trouble. This is the case, where 1KiB data is requested,
while URB_SHORT_NOT_OK flag is set for urb. The device
returns 32 bytes, IIRC, and then keeps N
Hello,
I can now install g_file_storage. But I got some strange messages once I
plug the usb cable to the host and mount it.
First of all, I created a file like that :
>dd bs=1024 count=1024 if=/dev/zero of=/root/data/backing_file
>insmod g_file_storage.o (I changed, in file_storage.c, the
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
class/usblp.c |2 +-
core/devio.c|6 +++---
core/hcd.c |2 +-
core/hub.c |6 +++---
core/message.c |4 ++--
host/ehci-hcd.c |2 +-
host/ehci-mem.c |8
host/ehci-q.c
In the UFI specification: " If the medium is unformatted, unknown, or
not presented, the UFI device fails the READ CAPACITY and sets the
sense key to an appropriate value as listed in section 5." Which sense
key is that?
thanks!
---
The SF.Net
This topic has been originated from the following correspondence between me and
Alan Stern:
http://sourceforge.net/mailarchive/forum.php?thread_id=6291609&forum_id=5398
The problem is that g_file_storage driver and Windows XP can not make a
connection. But g_file_storage works fine with Linux ho
41 matches
Mail list logo
