I have been using my USB2 devices with Linux for some time now, but
recently have started having troubles with them.
Beginning with Linux 2.6.10, my 1GB USB drive sometimes required more
than one attempt before it would connect. In other words, I often had
to remove it and reinsert it in its p
On Wed, 2 Nov 2005, gary clark wrote:
> Hi Alan,
>
> Thanks for the response. Basically I want to avoid the
> kernel driver modifications until next time.
> But your right it probably was easier to make the
> modification in usb_storage.
> By calling the usb_detach_kernel_driver_np on a
> specifi
On Wed, 2 Nov 2005, Greg KH wrote:
> > > Your only requirement is that it is outside of your local
> > > device structure so that you can syncronize things.
> >
> > Obviously :-) I suppose the reason why I need a semaphore and can't use a
> > spinlock is that the call to kref_put in disconnect(
> > > Yes, if you don't like using the BKL (and I admit that it was a fun
> > > hack for me to use it), just have a static semaphore in your driver for
> > > all devices.
> >
> > Using the BKL for new code is not recommanded,
>
> Says who?
(from lib/kernel_lock.c)
/*
* The 'big kernel semaphore'
On Wed, Nov 02, 2005 at 02:07:58PM +0100, Laurent Pinchart wrote:
> > Yes, if you don't like using the BKL (and I admit that it was a fun hack
> > for me to use it), just have a static semaphore in your driver for all
> > devices.
>
> Using the BKL for new code is not recommanded,
Says who?
> so
On Wed, Nov 02, 2005 at 09:45:28AM +0100, Oliver Neukum wrote:
> Am Mittwoch, 2. November 2005 09:03 schrieb Greg KH:
> > On Wed, Nov 02, 2005 at 08:54:22AM +0100, Duncan Sands wrote:
> > > > > + * sometime hotplug don't have time to give the firmware the
> > > > > + * first time, retry it.
> > > >
On Wed, Nov 02, 2005 at 09:52:56AM +0100, Duncan Sands wrote:
> On Wednesday 2 November 2005 09:45, Oliver Neukum wrote:
> > Am Mittwoch, 2. November 2005 09:03 schrieb Greg KH:
> > > On Wed, Nov 02, 2005 at 08:54:22AM +0100, Duncan Sands wrote:
> > > > > > + * sometime hotplug don't have time to g
On Wed, Nov 02, 2005 at 04:29:58PM +1100, Andrew Morton wrote:
> matthieu castet <[EMAIL PROTECTED]> wrote:
> >
> > Hi Duncan,
> >
> > Duncan Sands wrote:
> > > Hi Andrew,
> > >
> > >
> > > this code looks like a 'orrible hack to work around a common problem
> > > with USB modem's of this type:
On Sun, Oct 30, 2005 at 02:51:07AM +0200, Lengyel Gabor wrote:
> Hi!
>
> I've written a kernel module that on certain conditions can disable and
> reenable AT and PS/2 keyboards and mice. But how should I do this properly
> with usb input peripherals? I've read what I could, looked at usbkbd.c,
On Wed, 2 Nov 2005, gary clark wrote:
> Hi Alan,
>
> My thinking is that usb_storage has snagged the
> interface before I even get there. What options do I
> have to grabbing the interface? I'm already super user
> when I run my application.
I'm not sure exactly what you're trying to accomplish.
Hi,
When I load the net2280.ko on 2.6.12 I get the following oops message. I
am connected with netchip2280 on PCI slot.
The dump follows.
Nov 2 14:47:12 localhost kernel: Unable to handle kernel NULL pointer
dereference at virtual address 02a8
Nov 2 14:47:12 localhost kernel: printing e
Jas Sandhu
Network
Administrator
Prime Signal Ltd.
Tel:604-940-3688
Fax:604-940-8714
[EMAIL PROTECTED]
matthieu castet wrote:
Hi Greg,
+/*
+ * sometime hotplug don't have time to give the firmware the
+ * first time, retry it.
+ */
+static int sleepy_request_firmware(const struct firmware **fw,
+const char *name, struct device *dev)
+{
+if (request_firmware(fw, name, dev) == 0)
+
Hi Greg,
thanks for your review.
Greg KH wrote:
On Sun, Oct 30, 2005 at 12:37:41AM +0200, matthieu castet wrote:
Please comment and consider for inclusion.
I need a "Signed-off-by:" line in order to be able to add it. Care to
redo things based on the comments you have had and resend it wi
On Wed, 2 Nov 2005, David Brownell wrote:
UNRECOGNIZED: 05 24 ab 05 15
... except for that particular subtype 0xAB, that's not yet
recognized by "lsusb". It's communications class, with subclass
of 0xfe; does anyone know what that's supposed to mean? I see
it's got a CDC union descri
On Wednesday 02 November 2005 1:02 am, Richard Purdie wrote:
> To allow multiple platforms to use the PXA27x OHCI driver, the platform
> code needs to be moved into the board specific files in
> arch/arm/mach-pxa. This patch does this for mainstone and adds
> preliminary hooks to allow other boards
On Wednesday 02 November 2005 10:04 am, Alex Kanavin wrote:
> For reference, here's Nokia 6680 USB configuration.
It might be good to update to a more current version of "lsusb".
The CVS version should decode most of the descriptors this dump
lists as "unrecognized" (in fact, so should lsusb
Hi Greg,
the newly added dku2 driver is not suitable for at least Nokia 6680 and
6670, you should exclude these phones from being taken by the driver. I'm
not sure if you're familiar with Nokia phones, but they're all divided
into two large groups: Series 40 (running Nokia's proprietary OS) an
On Wednesday 02 November 2005 1:02 am, Richard Purdie wrote:
> Add power management functions for the pxa27x USB OHCI host controller.
> This is a totally rewritten version of the patch by Nicolas Pitre and
> Todd Poynor which accounts for recent USB changes.
>
> Signed-off-by: Richard Purdie
Sig
On Wed, 2 Nov 2005, Oliver Neukum wrote:
> Am Mittwoch, 2. November 2005 02:21 schrieb gary clark:
> > I want to know that if I call usb_claim_interface will
> > in an application will this prevent a user from
> > attempting to mount that device? i.e state that the
> > device is busy.
> > Is there
On Tue, 1 Nov 2005, Greg KH wrote:
> > +/* we need to use semaphore until sysfs and removable devices is fixed
> > + * the problem is explained on
> > http://marc.theaimsgroup.com/?t=11200648413
> > + */
>
> This is the proper fix, why do you think it should be fixed in the
> driver core?
I
On Tue, 1 Nov 2005, Mike King wrote:
> Alan,
>
> Nothing was resolved on this failure. I haven't been able to try it
> on 2.6.14 because I can't get mkinitrd to build an image. It keeps
> complaining about 'No module ata_piix found'.
>
> I don't think it is the device because it works find on
> Yes, if you don't like using the BKL (and I admit that it was a fun hack
> for me to use it), just have a static semaphore in your driver for all
> devices.
Using the BKL for new code is not recommanded, so I'll use a static
driver-wide semaphore.
> Your only requirement is that it is outside
Hi Roman, glad to see you're still alive!
On Wednesday 2 November 2005 11:46, Roman Kagan wrote:
> On Tue, Nov 01, 2005 at 01:04:02PM +, David Woodhouse wrote:
> > On Tue, 2005-11-01 at 13:40 +0100, Duncan Sands wrote:
> > > this code looks like a 'orrible hack to work around a common problem
On Tue, Nov 01, 2005 at 01:04:02PM +, David Woodhouse wrote:
> On Tue, 2005-11-01 at 13:40 +0100, Duncan Sands wrote:
> > this code looks like a 'orrible hack to work around a common problem
> > with USB modem's of this type: if the modem is plugged in while the
> > system boots, the driver may
On Wednesday 2 November 2005 09:45, Oliver Neukum wrote:
> Am Mittwoch, 2. November 2005 09:03 schrieb Greg KH:
> > On Wed, Nov 02, 2005 at 08:54:22AM +0100, Duncan Sands wrote:
> > > > > + * sometime hotplug don't have time to give the firmware the
> > > > > + * first time, retry it.
> > > > > + *
Am Mittwoch, 2. November 2005 09:03 schrieb Greg KH:
> On Wed, Nov 02, 2005 at 08:54:22AM +0100, Duncan Sands wrote:
> > > > + * sometime hotplug don't have time to give the firmware the
> > > > + * first time, retry it.
> > > > + */
> > > > +static int sleepy_request_firmware(const struct firmware
On Wed, Nov 02, 2005 at 08:54:22AM +0100, Duncan Sands wrote:
> > > + * sometime hotplug don't have time to give the firmware the
> > > + * first time, retry it.
> > > + */
> > > +static int sleepy_request_firmware(const struct firmware **fw,
> > > + const char *name, struct device *dev)
>
On Wednesday 2 November 2005 08:45, David Woodhouse wrote:
> On Wed, 2005-11-02 at 08:42 +0100, Duncan Sands wrote:
> > we could do this for the speedtouch - in fact we used to do this: when
> > someone tried to open a connection, we loaded the firmware if it
> > hadn't been loaded yet. The proble
29 matches
Mail list logo
