On Wed, Feb 13, 2008 at 03:54:38PM +, Sergio Callegari wrote:
> Hi,
>
> I have an ONDA N501HS (namely a rebranded ZTE MF330) UMTS pc card.
>
> I am currently using this card with the sierra driver (as in current kernels).
Which kernel version specifically?
> However I am noticing the follow
On Thu, Feb 14, 2008 at 01:15:37AM +1030, David Newall wrote:
> Consider a USB-attached serial port that is set to do RTS/CTS (or
> DSR/DTR) handshaking: What stops the kernel sending more data to it when
> the remote end lowers CTS (or DTR)?
The tty layer should look at the proper flags and not s
Original Message
Subject: Re: [Linux-uvc-devel] 064e:a101 Suyin Corp. and
Skype-2.0.0.43-suse partial success
Date: Wed, 13 Feb 2008 16:02:45 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
This list is now closed.
Please post to the linux-usb list as described at
http:
On Wed, 13 Feb 2008 17:44:01 -0500 (EST) Alan Stern wrote:
> > + * @rawdescriptors: waw descriptors for each config
>
> Typo.
>
> > + * @children: child devices - these can be either new devices (if this is a
> > + * hub device), or different instances of this same device.
> > + * Each instance
> You might want to add the "flash" functionality within the kernel
> driver
> itself, so you can get a bit tighter timing than relying on a
> userspace/kernelspace turn around to provide an accurate timing loop.
I was already considering this. At this point we fork a process to
handle the
GPIO f
On Wed, Feb 13, 2008 at 05:27:57PM -0600, Andrew McKay wrote:
> Greg KH wrote:
>> On Wed, Feb 13, 2008 at 01:31:54PM -0600, Andrew McKay wrote:
>>> Hi
>>>
>>> For a project I'm working on we had to add GPIO support to the cp2103
>>> driver in the 2.6.20.4 kernel.
>> Can't you just do this from a u
Greg KH wrote:
On Wed, Feb 13, 2008 at 01:31:54PM -0600, Andrew McKay wrote:
Hi
For a project I'm working on we had to add GPIO support to the cp2103
driver in the 2.6.20.4 kernel.
Can't you just do this from a usbfs/libusb application from userspace
instead? Why add a custom ioctl to the d
Of course there is a typo in the subject :)
2.5.25-rc1 -> 2.6.25-rc1
> Hello,
>
> I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a
> problem.
> Linux boots but with huge delay due to some issue with loading usb modules.
> Udev complains:
>
> 'Could not lock modprobe
On Wed, Feb 13, 2008 at 01:31:54PM -0600, Andrew McKay wrote:
> Hi
>
> For a project I'm working on we had to add GPIO support to the cp2103
> driver in the 2.6.20.4 kernel.
Can't you just do this from a usbfs/libusb application from userspace
instead? Why add a custom ioctl to the driver? Or a
Andrew McKay wrote:
Pete Zaitcev wrote:
On Wed, 13 Feb 2008 13:31:54 -0600, Andrew McKay <[EMAIL PROTECTED]> wrote:
spin_lock_bh(&port->lock);
if (port->write_urb_busy) {
If you lock against callbacks and do not trigger tasklets yourself,
you must use spin_lock_irqsave (or spin_lock_ir
On Wed, 13 Feb 2008, Randy Dunlap wrote:
> From: Randy Dunlap <[EMAIL PROTECTED]>
>
> Convert struct usb_device to use kernel-doc notation.
> Please especially check the @filelist and @usb_classdev descriptions.
>
> Fix a few other kernel-doc lines that should be all on one line but were on
> mu
On Wed, 13 Feb 2008, Pete Zaitcev wrote:
> On Wed, 13 Feb 2008 15:53:48 -0600, Andrew McKay <[EMAIL PROTECTED]> wrote:
>
> > Once the callback function has been called does this guarantee that the
> > URB
> > has already been sent to hardware?
>
> Yes (if the returned status was zero).
>
>
This patch refactors some shutdown code so it can be shared between
ehci_stop() and ehci_shutdown().
This also fixes a couple potential bugs:
- ehci_shutdown() was not locking ehci->lock before halting the HC.
- ehci_shutdown() didn't disable the watchdog and IAA timers.
- ehci_stop() was reset
On Wed, 13 Feb 2008 15:53:48 -0600, Andrew McKay <[EMAIL PROTECTED]> wrote:
> Once the callback function has been called does this guarantee that the URB
> has already been sent to hardware?
Yes (if the returned status was zero).
> I'll definitely look into this usbmon app. I have timed thi
On Wed, Feb 13, 2008 at 01:36:00PM -0800, David Brownell wrote:
> On Wednesday 13 February 2008, Felipe Balbi wrote:
> > On Tue, Feb 12, 2008 at 12:32:34PM -0800, David Brownell wrote:
> > >
> > > Your proposal is to strike the "is_b_host" check. In terms of the
> > > OTG (1.3) state machine, tha
Pete Zaitcev wrote:
On Wed, 13 Feb 2008 13:31:54 -0600, Andrew McKay <[EMAIL PROTECTED]> wrote:
spin_lock_bh(&port->lock);
if (port->write_urb_busy) {
If you lock against callbacks and do not trigger tasklets yourself,
you must use spin_lock_irqsave (or spin_lock_irq if you are belong
t
From: Randy Dunlap <[EMAIL PROTECTED]>
Convert struct usb_device to use kernel-doc notation.
Please especially check the @filelist and @usb_classdev descriptions.
Fix a few other kernel-doc lines that should be all on one line but were on
multiple lines.
Signed-off-by: Randy Dunlap <[EMAIL PROTE
On Wed, 13 Feb 2008 13:31:54 -0600, Andrew McKay <[EMAIL PROTECTED]> wrote:
>spin_lock_bh(&port->lock);
>if (port->write_urb_busy) {
If you lock against callbacks and do not trigger tasklets yourself,
you must use spin_lock_irqsave (or spin_lock_irq if you are belong
to Oliver's denominat
ITDs can be detached from urbs, before the active frame elapses. Now those
ITDs are immediately recycled.
If the ITD is reused then, transactions based on its new usage can already
happen while the frame is still active, too early.
Patch takes care of those ITDs by moving them into a new ehci memb
On Wednesday 13 February 2008, Felipe Balbi wrote:
> On Tue, Feb 12, 2008 at 12:32:34PM -0800, David Brownell wrote:
> >
> > Your proposal is to strike the "is_b_host" check. In terms of the
> > OTG (1.3) state machine, that removes a b_host --> b_peripheral
> > state transition.
>
> Not at all,
I'm glad this problem has been solved for good.
Listening to music is such a nice thing :-)
thanks everybody !
robert
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-in
Hi
For a project I'm working on we had to add GPIO support to the cp2103 driver in
the 2.6.20.4 kernel. We are controlling a GPIO via ictl to flash an LED. We'd
like to hit something along the lines or 1-3HZ. So nothing too fast. I use a
control URB to tell the cp2103 device to toggle its
testing
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 13 Feb 2008 [EMAIL PROTECTED] wrote:
> Dear list,
>
> I have problems with a usb device (mp3 player) which is handled by the
> kernel modules in a wrong way. It is a usb 2.0 device (which behaves
> as such on e.g. Mac OS X), but with the linux kernel (2.6.22-3 debian
> kernel) I encounter
Dear list,
I have problems with a usb device (mp3 player) which is handled by the
kernel modules in a wrong way. It is a usb 2.0 device (which behaves
as such on e.g. Mac OS X), but with the linux kernel (2.6.22-3 debian
kernel) I encounter only about 1MB/min of data transfer.
A look into /proc/b
Hi,
I have an ONDA N501HS (namely a rebranded ZTE MF330) UMTS pc card.
I am currently using this card with the sierra driver (as in current kernels).
However I am noticing the following problem:
- when I use the card for downloading from the internet, everything is fine;
- when I use the card fo
This patch (as1032) removes the Clear-Halt calls in
usb_stor_Bulk_max_lun(). Evidently some devices (such as the Oracom
MP3 player) really don't like to receive these requests when their
bulk endpoints aren't halted.
The only reason for adding them originally was to get an ancient
ZIP-100 drive t
Consider a USB-attached serial port that is set to do RTS/CTS (or
DSR/DTR) handshaking: What stops the kernel sending more data to it when
the remote end lowers CTS (or DTR)?
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More ma
On Tue, Feb 12, 2008 at 12:32:34PM -0800, David Brownell wrote:
> > > > > > Some devices claim
> > > > > > to be b_host even though they have an a_connector attached to it.
> > > > >
> > > > > Why not just fix that bug? Remember that's Linux code.
> > > >
> > > > The device claiming to be b_host
29 matches
Mail list logo
