Am Montag, 18. April 2005 23:40 schrieb Pete Zaitcev:
> + i = 0;
> + for (;;) {
> + wb = &acm->wb[wbn];
> + if (!wb->use) {
> + wb->use = 1;
> + return wbn;
> + }
> + wbn = (wbn + 1) % AC
Is there any reason to connect ISP1362 with 4 byte offset of registers,
while all registers are 16-bit, and my data-bus width is 16-bit too?
Now i'm using 2-byte offset.
I can reset my ISP1362, I can also read chip ID, but testing memory
(with Lothar's driver) fails.
Probably resetting interrupt st
Hello All,
I have a PXA255 processor. When the processor is put in sleep mode, all
peripheral clocks are disabled. (3.4.9.4 in PXA255 Manual). So the USB
communication is disabled. My question is when the processor wakes up
from sleep mode, will the UDC resume normal operations? Should the
soft
Hm, I think I got this set up properly, but don't have an automated
script to generate the changelog and diffstat messages yet, so bear with
me...
Could you merge with:
kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/
It should be against your latest git tree. It contains a number
Duncan,
I have a problem on how to let the Fedora 2.6.10 change the Driver field
from "usbhid" to "none" in the /proc/bus/usb/devices of ePadII device?
Thanks
tclan
Here is the part of devices file:
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub
> Aaargh. It was some last minute cleanup that lead to this crash.
> I only compiled with CONFIG_USB_DEBUG disabled after this change
> which disables the BUG_ON() checking.
Aaah, I see. Thanks, I put that in.
However, I'm still having trouble. Perhaps you have an idea?
I can't seem to get th
On 18.04.2005 17:16, Stephen Morgan wrote:
> I'm converting a USB driver for Linux 2.4.20-8 to 2.6.9-1.667 and have found
> that the __FILE__ macro is now giving me the full path of the driver source.
> In 2.4, I was just getting the file name. Like:
>
> /home/me/path/yada/yada/minimum.c: minim
This patch lacked a small bit.
Updated patch below.
cu
Adrian
<-- snip -->
This patch makes needlessly global code static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/usb/media/pwc/pwc-ctrl.c | 78 +++
drivers/usb/media/pwc/pwc-if.c |2
Oliver & others:
I obtained the modem and was able to reproduce the bug. It's very easy.
Also, I turned this around with our customer. I found that the original
patch had a bug where I tried to be too clever. The patch copies the
logics from my 2.4 usbserial code, but not exactly. This is what
wri
On Mon, 18 Apr 2005, Oliver Neukum wrote:
> > > Their own fault. Drivers can do any number of stupid things with
> > > interrupts
> > > disabled.
> >
> > Well sure, but that doesn't help. It's part of the API, it's necessary if
>
> Is it necessary or is it part of the API? If the latter, then
And here are the changes to support the extra keys...
--- linux/drivers/usb/input/hid-input.c.orig2005-04-18 11:58:56.0
+0100
+++ linux/drivers/usb/input/hid-input.c 2005-04-18 13:36:16.0 +0100
@@ -270,6 +270,12 @@
case 0x227: map_key_clear(KEY_R
(type << 8), ifnum, buf, size, HZ *
USB_CTRL_GET_TIMEOUT);
+ retries--;
+ } while (result < size && retries);
+
+// wn_hack: patch wrong descriptor for this device
+// hardware sends wrong descriptor
+// AA, 20050418: sh
On Mon, 18 Apr 2005 14:51:38 -0500 Stephen Morgan wrote:
| > -Original Message-
| > From: Randy.Dunlap [mailto:[EMAIL PROTECTED]
| > Sent: Monday, April 18, 2005 11:21 AM
| > To: Stephen Morgan
| > Cc: linux-usb-devel@lists.sourceforge.net
| > Subject: Re: [linux-usb-devel] __FILE__ return
> -Original Message-
> From: Randy.Dunlap [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 18, 2005 11:21 AM
> To: Stephen Morgan
> Cc: linux-usb-devel@lists.sourceforge.net
> Subject: Re: [linux-usb-devel] __FILE__ returns full path now?
>
>
> On Mon, 18 Apr 2005 11:15:50 -0500 Stephen Morg
On Mon, 18 Apr 2005 11:15:50 -0500 Stephen Morgan wrote:
| Hello all,
|
| I'm converting a USB driver for Linux 2.4.20-8 to 2.6.9-1.667 and have found
| that the __FILE__ macro is now giving me the full path of the driver source.
| In 2.4, I was just getting the file name. Like:
|
| /home/me/
Am Montag, 18. April 2005 17:34 schrieb Alan Stern:
> > > Furthermore, there's nothing to prevent USB device drivers from calling
> > > usb_submit_urb() or usb_unlink_urb() while they have disabled interrupts
> > > for their own reasons. That's a perfectly legal thing to do, but again it
> > > mea
On Mon, Apr 18, 2005 at 08:55:21PM +0400, Roman Kagan wrote:
> On Mon, Apr 18, 2005 at 08:55:24AM -0700, Greg KH wrote:
> > On Mon, Apr 18, 2005 at 07:40:25PM +0400, Roman Kagan wrote:
> > > On Mon, Apr 18, 2005 at 08:02:25AM -0700, Greg KH wrote:
> > > > And your patch modified the map file which
On Mon, Apr 18, 2005 at 08:55:24AM -0700, Greg KH wrote:
> On Mon, Apr 18, 2005 at 07:40:25PM +0400, Roman Kagan wrote:
> > On Mon, Apr 18, 2005 at 08:02:25AM -0700, Greg KH wrote:
> > > And your patch modified the map file which is created, right?
> >
> > By no means. It only modifies the aliase
Greg:
This patch changes the g_file_storage driver to make the "stall" module
parameter generally available; currently it is available only if the
testing version of the module has been configured. It also fixes a typo
in a comment -- thanks, Pat!
Alan Stern
Signed-off-by: Alan Stern <[EMAIL
On Mon, 2005-04-18 at 12:03 -0400, Alan Stern wrote:
> All I can is, this seems to be a pretty finicky device. Of course, it's
> always possible that the problem lies not in the device but in the host
> controller. Have you tried plugging it into any of the other controllers
> on your compute
Hello all,
I'm converting a USB driver for Linux 2.4.20-8 to 2.6.9-1.667 and have found
that the __FILE__ macro is now giving me the full path of the driver source.
In 2.4, I was just getting the file name. Like:
/home/me/path/yada/yada/minimum.c: minimum_init: Loading module
instead of:
m
On Mon, 18 Apr 2005, Johannes Berg wrote:
> I have attached a three startup logs (dmesg) with CONFIG_USB_DEBUG. The
> relevant device is on 0001:10:1a.0/usb1/1-1/1-1:1.0 (or :1.1 or both,
> not sure). On the same bus there's the keyboard/trackpad/eject button
> device, so I can't really give you s
On Mon, Apr 18, 2005 at 07:40:25PM +0400, Roman Kagan wrote:
> On Mon, Apr 18, 2005 at 08:02:25AM -0700, Greg KH wrote:
> > On Mon, Apr 18, 2005 at 08:41:58AM +0400, Roman Kagan wrote:
> > > On Sun, Apr 17, 2005 at 04:19:15PM -0700, Greg KH wrote:
> > > > On Sat, Apr 09, 2005 at 09:55:21AM +0400, R
On Mon, Apr 18, 2005 at 08:02:25AM -0700, Greg KH wrote:
> On Mon, Apr 18, 2005 at 08:41:58AM +0400, Roman Kagan wrote:
> > On Sun, Apr 17, 2005 at 04:19:15PM -0700, Greg KH wrote:
> > > On Sat, Apr 09, 2005 at 09:55:21AM +0400, Roman Kagan wrote:
> > > > On Fri, Apr 08, 2005 at 02:49:13PM -0700, G
On Mon, 18 Apr 2005, Oliver Neukum wrote:
> As calling the completion handler is the latest major operation in handling
> an interrupt, it seems to me that you've already broken the guarantee
> that there will be no intervening interrupts, if you have used any tasklet
> in between.
There is no su
SOHO Bandwidth
control router
Ref.: BOSSERB
This device is created as a protection to against invaders who
peek into or destroy your internal information. The intelligent Firewall
system provides the most secure solution for critical
Enterprise data.
The Bandwidth management router is
On Mon, 18 Apr 2005, Oliver Neukum wrote:
> > Yes, this was a usb-storage measurement. That's the only sort of
> > devices I have that make serious demands on the HCD. And this _was_
> > supposed to be a worst-case measurement, after all.
>
> The worst case for latency? Then you should measur
On Sun, 17 Apr 2005, David Brownell wrote:
> Or other IRQs, etc. I punted the detailed analysis, but briefly:
>
> * OHCI typically gets a completion (WDH) IRQ at the start of a frame,
> then if there's anything on the control or bulk queues it'll do
> that for 10% of a frame and then s
On Mon, Apr 18, 2005 at 08:41:58AM +0400, Roman Kagan wrote:
> On Sun, Apr 17, 2005 at 04:19:15PM -0700, Greg KH wrote:
> > On Sat, Apr 09, 2005 at 09:55:21AM +0400, Roman Kagan wrote:
> > > On Fri, Apr 08, 2005 at 02:49:13PM -0700, Greg KH wrote:
> > > > On Thu, Mar 31, 2005 at 07:40:46PM +0400, R
On Fri, 2005-04-15 at 23:15 -0400, Alan Stern wrote:
> It would help if you set CONFIG_USB_DEBUG and provided a system log
> showing what happens when the bluetooth device is enumerated.
I have attached a three startup logs (dmesg) with CONFIG_USB_DEBUG. The
relevant device is on 0001:10:1a.0/us
Am Montag, 18. April 2005 04:24 schrieb Alan Stern:
> On Sun, 17 Apr 2005, Oliver Neukum wrote:
>
> > > Using spin_lock_bh() in enqueue or dequeue isn't a solution because
> > > existing code already calls these routines with interrupts disabled.
> >
> > How so? If you convert the irq code to a
Hi Michael,
> However, it makes my kernel crash (dereferencing a NULL pointer) in
> the isp1362_probe function, specifically in 'isp1362_write_addr'.
> After much fruitless hunting, I finally found that it's the
> _BUG_ON(!irqs_disabled()); that's doing it.
>
> ( I would have hoped that it would
Am Montag, 18. April 2005 04:37 schrieb Alan Stern:
> On Sun, 17 Apr 2005, David Brownell wrote:
>
> > So basically this was a usb-storage measurement. That's probably a
> > worst-case from the HCD perspective, since virtually everything else
> > only uses very short queues. (Other than "usbnet"
33 matches
Mail list logo
