The best news was Andrew's: World Domination is proceeding
according to plan!
On Saturday 24 July 2004 20:58, Greg KH wrote:
>
> David, can you think of anything that might have come up, besides the
> rewrite of the power management handling code that you said you were
> going to do? :)
You
On Saturday 24 July 2004 11:36, Alan Stern wrote:
> And I don't see why you had to modify your code... You should send the
> first 8 bytes, then wait for another IN so you can send the second eight
> bytes. When you get an OUT instead of an IN you can pretty much do
> whatever you want (excep
On Thursday 22 July 2004 16:15, Wes Janzen wrote:
> I've been having trouble with USB since 2.6.8-rc1; khubd ends up
> blocking on something which makes USB hotplugging stop working (and only
> half my devices even get initialized). I did get 2.6.8-rc1 to work once
> though it seemed to help in
On Tuesday 27 July 2004 07:45, Alan Stern wrote:
>
> I've got a Netchip 2280 board (http://www.netchip.com). It's a PCI card
> with a high-speed USB device interface, and there's a driver for it in the
> USB gadgets directory (net2280).
>
> And yes, it is very useful. About the only aspect I
On Tuesday 20 July 2004 03:40, Kurt Meier wrote:
> usb 1-1: control timeout on ep0out
> usb 1-1: can't set config #2, error -110
> usb 1-1: hotplug
>
> Can anybody say me what this "control timeout on ep0out" means?
> Am I too slow with an answer? What kind of answer is expected?
Probably you di
On Thursday 22 July 2004 08:15, Kyle Harris wrote:
> I have a check scanner device (serial function):
>
> P: Vendor=1136 ProdID=3231 Rev= 1.00
> S: Manufacturer=CTS Electronics
> S: Product=USB CTS LS100
>
> If setup requests 8 bytes during the initial get_descriptor the device will
> return
On Thursday 22 July 2004 07:04, Alan Stern wrote:
> On Thu, 22 Jul 2004, [ks_c_5601-1987] ¹ÚÈ£»ó wrote:
>
> > In file_storage.c from /driver/usb/gadget, there are two parts handling
> > Standard Request and Class-Specific Request. However, in my opinion, there
> > is one part handling Requests in
On Monday 26 July 2004 03:27, you wrote:
> David --
>
> Here is a patch to add endpoint autoconfiguration to
> the gadget serial driver. This is against 2.6.7.
>
> I pretty much copied gadget zero autoconfig for this.
> I tested it with a NetChip 2280 development board.
Looks pretty good, thank
On Wednesday 21 July 2004 09:17, Matthew Dharm wrote:
>
> So, why not make some allocations earlier? If I allocate enough URBs for a
> sg-list of such-and-such size, then tell the SCSI layer that my maximum
> sg-list length is such-and-such size, then I should be able to avoid that
> allocation.
> Fedora Core 2 - Genesys Genelink USB 2 USB network adapter
I know that GeneSys has a high speed usb-to-usb cable,
but it's not supported by the kernel.org kernels ... so
if there's a driver for it in Fedora, you should bug RedHat
to submit it to the mainstream kernel.
> ...
>
> what's happe
On Iau, 2004-07-29 at 00:10, Florian Echtler wrote:
> once at the same time. I was planning to have open() update the buffer
> with the current picture (and block when already opened) and read() just
> return the current buffer contents, at whatever position desired (and
> I know that the offset p
Wolfgang Mües wrote:
What is the recommended way of using a device with 2 configurations
in configuration #2?
I have run into the same trouble - that set_configuration is not usable
inside probe(). I have looked at the hotplug scripts, but I have found
no example for doing this. The usb hotplug s
Todd Fischer wrote:
It was straight forward to expose the UDC's capabilities to the gadget
driver once I understood the gadget framework. I started with the test zero
driver and a single bidi bulk endpoint entry. I had to scratch my head a
bit trying to figure out why the zero driver couldn't use
Wolfgang Mües wrote:
echo 2 > $DEVPATH/bConfigurationValue
The hotplug script is executed _before_ probe() is called? Even if the
driver is already in memory? And the sysfs is doing the
set_configuration() before probe() is called?
There's a "device" hotplug call, where $DEVPATH/bConfigurationVa
On Tue, 27 Jul 2004, Jonas Fährmann wrote:
> Hi Alan,
> I commented out the lines you told me to, rebuilt the kernel and gave it another try
> after rebooting.
>
> Dmesg now says:
>
> usb 3-1: new full speed USB device using address 2
> usb 3-1: device not accepting address 2, error -84
> usb 3
Marcel Holtmann wrote:
is there a problem with re-exporting it?
Other than through sysfs (or usbfs) you mean? Mostly
just locking implications.
What happens if you usb_reset_device() after loading the firmware?
Ideally that'd turn up new descriptors and the device could be made
to select the "ri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > // reset the buffer position
> > dev->buffer_pos = 0;
> > If you are allowing multiple openers you cannot reset the buffer.
> > And run it through indent.
> I don't see how you can do this with a single opener since it can
> then be threaded a
Alan Stern wrote:
I've got a Netchip 2280 board (http://www.netchip.com). It's a PCI card
with a high-speed USB device interface, and there's a driver for it in the
USB gadgets directory (net2280).
is it expensive?
I don't know what price they're currently charging, but it's not going to
be ver
On Mon, Jul 19, 2004 at 03:21:44PM -0300, Rog?rio Brito wrote:
>
> Dear Alan and Greg,
>
> I saw via lwn.net that 2.6.8-rc2 was just released and, unfortunately, it
> didn't include the patch below, which is necessary for my USB Drive to work
> correctly with the VIA southbridge on my desktop com
Hello,
On Wednesday 28 July 2004 21:10, Alan Stern wrote:
> This is still relatively new and hasn't percolated down to the level
> of the hotplug scripts yet. Nevertheless, in a hotplug script is the
> right place to do it.
H... if I had a choice, I prefer choosing the configuration from
i
On Mer, 2004-07-28 at 19:39, Oliver Neukum wrote:
> // reset the buffer position
> dev->buffer_pos = 0;
>
> If you are allowing multiple openers you cannot reset the buffer.
> And run it through indent.
I don't see how you can do this with a single opener since it can
then be threaded and is
Pradip Shah wrote:
Is there any implementation of video device class driver for the gadget
side?
Not yet, nobody's donated one. Same is true on the host side.
- Dave
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterpris
Hi,
okay, before fiddling around with that Windoze driver stuff, I tried your last
patch (uhci-hcd.c one liner) and removed all other patches, result:
I worked - at least partially. I have a log attached where both cases can
be seen. Sometimes (quite often) it seems to work and the cam is detected
On Wed, 28 Jul 2004, Wolfgang Mües wrote:
> Hello,
>
> On Wednesday 28 July 2004 07:14, David Brownell wrote:
>
> > Indirecting through schedule_work() should always be safe,
> > and that's what I'd recommend for now.
>
> What is the recommended way of using a device with 2 configurations
> in
On Tue, 27 Jul 2004, David Brownell wrote:
> Alan Stern wrote:
>
> > What do you think about the problem of stalling the bulk-out endpoint when
> > the host sends too much data? Maybe this hasn't caused you any
> > difficulty yet. The problem is that there's a race.
>
> What'd be the conseq
Hi,
Is there any implementation of video device class driver for the gadget
side?
Regards,
Pradip
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Work
Am Mittwoch, 28. Juli 2004 15:23 schrieb Florian Echtler:
> Andreas Deresch and I have written a driver for the fingerprint
> sensor in the Siemens ID USB Mouse (a FingerTIP sensor, also from
> Siemens). The mouse is cheaply available (ours did cost 15 Euro),
> and provides a decent grayscale image
Hello,
On Wednesday 28 July 2004 07:14, David Brownell wrote:
> Indirecting through schedule_work() should always be safe,
> and that's what I'd recommend for now.
What is the recommended way of using a device with 2 configurations
in configuration #2?
I have run into the same trouble - that se
On Wed, 28 Jul 2004, Duncan Sands wrote:
> > That's right. But you might not have to go to all the trouble of using
> > schedule_work(). If loading the firmware does change the device or
> > configuration descriptors at all, then calling usb_reset_device() will be
> > enough to start re-enumerat
> That's right. But you might not have to go to all the trouble of using
> schedule_work(). If loading the firmware does change the device or
> configuration descriptors at all, then calling usb_reset_device() will be
> enough to start re-enumeration and reprobing. It would only be necessary
>
On Wed, 28 Jul 2004, Todd Fischer wrote:
> I have some notes about other aspects of the gadget framework I do not
> understand (like the zero field in a request), but am holding off asking
> questions or proposing changes to the DocBook documentation until the OTG
> changes settle out.
>
> Overal
On Wed, 28 Jul 2004, Marcel Holtmann wrote:
> I can't tell you that right now, because the 2.4 version was different
> and I haven't used the usb_set_configuration() call outside the probe()
> routine. My plan is to do it this way:
>
> probe()
> switch (configuration)
>
On Wed, 28 Jul 2004, Tuukka Toivonen wrote:
> Thanks for your suggestions. I must apologize that I was incorrect: it
> wasn't a problem in 2.6.7 but rather in my LILO configuration. The root for
> the problems was "serial console" (which was enabled for 2.6.7 but not for
> other kernels).
>
> By
On Tue, 27 Jul 2004, Duncan Sands wrote:
> Hi Alan,
>
> > I've got a Netchip 2280 board (http://www.netchip.com). It's a PCI card
> > with a high-speed USB device interface, and there's a driver for it in the
> > USB gadgets directory (net2280).
>
> is it expensive?
I don't know what price t
On Wed, 28 Jul 2004, Gerhard Jaeger wrote:
> Hi,
>
> as far as I understood now, it is not of great help to "snoop" the traffic
> between the cam and Windoze - isn't it? Because when usbsnoopy
> is working, the initial setup is already done - am I right?
That's exactly right.
> As Windoze98 do
On Tue, 27 Jul 2004, Todd Fischer wrote:
> Since there is a race condition, I would recommend changing the code where
> the race condition occurs to get rid of it forever. Using the no-stall
> option my cause reasonable use of stall to be disabled as well.
>
> Also, on the Linux 2.4 driver, it s
Hi David,
> >>>I found out that usb_set_configuration() was removed from the USB API by
> >>>you. ...
> >
> > it is not exported anymore and that is my problem.
>
> Oh, sorry. That was so long ago! Nobody was using it
> outside of usbcore.
is there a problem with re-exporting it?
> >>You
Marcel Holtmann wrote:
I found out that usb_set_configuration() was removed from the USB API by
you. ...
it is not exported anymore and that is my problem.
Oh, sorry. That was so long ago! Nobody was using it
outside of usbcore.
Your firmware load
isn't the "load then re-enumerate" typ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
Andreas Deresch and I have written a driver for the fingerprint
sensor in the Siemens ID USB Mouse (a FingerTIP sensor, also from
Siemens). The mouse is cheaply available (ours did cost 15 Euro),
and provides a decent grayscale image.
> -Original Message-
> From: David Brownell [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 28, 2004 12:04 AM
> To: Todd Fischer
> Cc: Usb
> Subject: Re: [linux-usb-devel] file_storage.c stalling the out bulk
> endpoint, but not clearing the stall
>
>
> Todd Fischer wrote:
>
> > I am deve
Thanks for your suggestions. I must apologize that I was incorrect: it
wasn't a problem in 2.6.7 but rather in my LILO configuration. The root for
the problems was "serial console" (which was enabled for 2.6.7 but not for
other kernels).
By enabling serial console, 2.6.0 had the same behaviour. By
Hi Alan,
> I've got a Netchip 2280 board (http://www.netchip.com). It's a PCI card
> with a high-speed USB device interface, and there's a driver for it in the
> USB gadgets directory (net2280).
is it expensive?
> And yes, it is very useful. About the only aspect I can criticize is that
> S
42 matches
Mail list logo
