On Thursday 13 January 2005 7:01 am, Alan Stern wrote:
> On Thu, 13 Jan 2005, Vladimir Trukhin wrote:
>
> > Well, it seems I've found the source of this problem.
> > Today I checked usb traffic on Windows side using SnoopyPro tool
> > ...
> > But g_file_storage driver always sends only one packet
Petko Manolov wrote:
Definitly a good idea to set that - although nothing in the driver
accesses it :-)
Well, not directly. However, pegasus_get/set_settings() is doing so
through mii_ethtool_gset() for example. Look at drivers/net/mii.c;
ahh, it all makes sense now :)
and yes, the original s
On Thu, Jan 13, 2005 at 11:44:44PM +0100, Florian Echtler wrote:
> > I've applied your driver as is to the tree, and then fixed up some
> > sparse warnings that were found with it (__user and le16_to_cpu() needed
> > to be added in places.)
> Thanks! Could you perhaps send me the updated version? I
On Thu, Jan 13, 2005 at 11:46:14AM -0500, Alan Stern wrote:
> Greg:
>
> This patch corrects some misconceptions that have persisted in the USB
> error-code documentation for quite some time.
Bleah, you do this after LDD3 hits the printers, oh well..
Applied, thanks.
greg k-h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'll do it. How many minor numbers do you want? Is 1 ok?
Great - I guess one should be enough.
> Will you ever be backporting this driver to 2.4 (it matters in the
> number I give you.)
Most likely not.
> I've applied your driver as is to the
On Thu, Jan 13, 2005 at 01:12:50PM +0200, Petko Manolov wrote:
> Hi Greg,
>
> The discussion with David yielded the attached cset. The credit goes for
> David, who did most of the patch and Mike who put a good deal of testing.
>
> Please apply,
Applied, thanks.
greg k-h
--
On Thu, Jan 13, 2005 at 11:46:14AM -0500, Alan Stern wrote:
> Greg:
>
> This patch corrects some misconceptions that have persisted in the USB
> error-code documentation for quite some time.
Bleah, you do this after LDD3 hits the printers, oh well..
Applied, thanks.
greg k-h
On Thu, Jan 13, 2005 at 04:49:17AM +0100, Luca Risolia wrote:
> 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
On Thu, Jan 13, 2005 at 11:44:44PM +0100, Florian Echtler wrote:
> > I'll do it. How many minor numbers do you want? Is 1 ok?
> Great - I guess one should be enough.
>
> > Will you ever be backporting this driver to 2.4 (it matters in the
> > number I give you.)
> Most likely not.
Great, her
On Thu, Jan 13, 2005 at 04:49:17AM +0100, Luca Risolia wrote:
> 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
On Thu, Jan 13, 2005 at 01:12:50PM +0200, Petko Manolov wrote:
> Hi Greg,
>
> The discussion with David yielded the attached cset. The credit goes for
> David, who did most of the patch and Mike who put a good deal of testing.
>
> Please apply,
Applied, thanks.
greg k-h
--
On Thursday 13 January 2005 10:04 am, Alan Stern wrote:
>
> Okay, here's a patch that looks pretty good to me. The only thing I'm not
> sure about is that it may retry _too_ aggressively. If you like it I'll
> submit it to Greg.
Looks OK to me too, except that if all the first three tries fai
On Thursday 13 January 2005 3:07 am, Declan Moriarty wrote:
> It has been suggested I report this here. I am not on the list, so
> please cc to me, but can supply any information necessary. The
> particular implementation has 3 pairs of ports, of which only one has
> actual usb ports attached.
>
On Thursday 13 January 2005 12:51 pm, David Hollis wrote:
> On Wed, 2005-01-12 at 19:41 -0800, David Brownell wrote:
> > 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 dme
On Wed, 2005-01-12 at 19:41 -0800, David Brownell wrote:
> 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
On Thu, Jan 13, 2005 at 10:03:59AM +0100, Florian Echtler wrote:
> > Can you use dev_info() here? It's more descriptive. Also, if
> > CONFIG_USB_DYNAMIC_MINORS is set, this number will print out negative,
> > which I don't think you want.
> Okay.. BTW, can you give it a minor number? And should I
On Fri, 7 Jan 2005, David Brownell wrote:
> That patch looked OK, but I might prefer one that also validated
> the ep0 maxpacket size too. (The patch I sent _only_ validated
> that field.) How about something more like
>
>if (r < 8 || buf->bDescriptorType != USB_DT_DEVICE) {
> r = -EP
On Wed, 12 Jan 2005, Mick Cornut wrote:
> 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 pr
On Wed, 12 Jan 2005, Jan De Luyck wrote:
> > > The Genesys increased delay in this patch causes strange issues, the USB
> > > disconnects after a while...
> > >
> > > I rewrote the identifier like it was previous this patch
> > >
> > > --
> > > if (us->pusb_dev->descriptor.idVendor == USB_VENDOR_I
Greg:
This patch corrects some misconceptions that have persisted in the USB
error-code documentation for quite some time.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= Documentation/usb/error-codes.txt 1.13 vs edited =
--- 1.13/Documentation/usb/error-codes.txt 200
On Wed, 12 Jan 2005, CG wrote:
> 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_fil
On Wed, 12 Jan 2005, Sara Fonseca wrote:
> 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?
It depends on what error yo
On Wed, 12 Jan 2005, Matthias Urlichs wrote:
> Hi,
>
> Alan Stern:
> > None of these changes should be needed. That's not to say there aren't
> > any remaining problems -- there may well be, but they should be fixed
> > another way.
> >
> Probably. You know more about that code than I do...
>
On Thu, 13 Jan 2005, Mohan V wrote:
> 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
On Thu, 13 Jan 2005, Vladimir Trukhin wrote:
> Well, it seems I've found the source of this problem.
> Today I checked usb traffic on Windows side using SnoopyPro tool
> http://sourceforge.net/projects/usbsnoop/
Good idea. It always helps to see both sides of a transfer.
> It shows that after
Petko Manolov wrote:
On Thu, 13 Jan 2005, Mike Nix wrote:
I tested this by calling it from enable_net_traffic so that carrier was
checked whenever the interface was configured "up" - I then ran
"ifconfig eth2 down;ifconfig eth2 up" inserting / removing the cable
between runs - carrier was reporte
On Thu, 13 Jan 2005, Mike Nix wrote:
pegasus->phy = 1;
}
+ pegasus->mii.phy_id = pegasus->phy;
usb_set_intfdata(intf, pegasus);
SET_NETDEV_DEV(net, &intf->dev);
pegasus_reset_wol(net);
---
Definitly a good idea to set that - although nothing in
On Thu, 13 Jan 2005, Mike Nix wrote:
I tested this by calling it from enable_net_traffic so that carrier was
checked whenever the interface was configured "up" - I then ran
"ifconfig eth2 down;ifconfig eth2 up" inserting / removing the cable
between runs - carrier was reported correctly every tim
It has been suggested I report this here. I am not on the list, so
please cc to me, but can supply any information necessary. The
particular implementation has 3 pairs of ports, of which only one has
actual usb ports attached.
I have a box here with a Via kt400 chipset. Loading this module produc
Hi Alan!
Alan Stern wrote:
Either Windows didn't send a packet or else the PXA didn't interrupt when
the packet was received. The second is more likely. Could this be
related to the endpoint halt that occurs earlier? True, that halt is for
the bulk-in endpoint, not the bulk-out. And you said
Hi Greg,
The discussion with David yielded the attached cset. The credit goes for
David, who did most of the patch and Mike who put a good deal of testing.
Please apply,
PetkoYou can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or app
On Thu, 13 Jan 2005, Petko Manolov wrote:
On Wed, 12 Jan 2005, David Brownell wrote:
No -- CONFIG_BRIDGE. The "brctl" tool just administers the
kernel infrastructure for 802.1d bridging. There's not even
a kernel task associated with it, much less a userspace one.
Well, any reading of the PHY sho
Międzynarodowe Centrum Informacyjno - Konsultingowe "ICIC", Kijów,
Ukraina.
www.seminar-ua.com
Serdecznie zaprasza na
> XI Międzynarodową polsko - ukraińsko - rosyjską konferencję
On Wed, 12 Jan 2005, David Brownell wrote:
No -- CONFIG_BRIDGE. The "brctl" tool just administers the
kernel infrastructure for 802.1d bridging. There's not even
a kernel task associated with it, much less a userspace one.
Well, any reading of the PHY should go through the pegasus driver. Since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Can't this driver be done successfully in userspace using usbfs/libusb?
> Or is there some requirement for it to be in the kernel that I missed?
As I already stated several times on this list, the libusb solution that
we had first didn't work reliabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohan V schrieb:
|
| 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
|
36 matches
Mail list logo
