Hello,
I'm trying to understand how USB works on Linux and I'm getting
confused about special devices:
- Documentation/devices.txt says that major 189 is for "USB serial
converters - alternate devices" but any usb device seems to have this
major (as I figure out from /dev/usb/00x/00x kind of speci
On Thursday 18 January 2007 10:08 am, Phil Endecott wrote:
> David Brownell wrote:
> > On Thursday 18 January 2007 9:50 am, Phil Endecott wrote:
> >> David Brownell wrote:
> >> > I've checked the updated "usb.c" code into CVS; not sure when it'l be
> >> > visible on the website, presumably tomorrow
David Brownell wrote:
> On Thursday 18 January 2007 9:50 am, Phil Endecott wrote:
>> David Brownell wrote:
>> > With that and the other patches I've sent (notably the race fix, none
>> > of the others ought to matter here), I don't see problem any more.
>>
>> I still see the problem after applying
Sorry I'm talking rubbish; I'm looking at testusb.c not usb.c.
Phil.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & bu
David Brownell wrote:
> On Thursday 18 January 2007 9:50 am, Phil Endecott wrote:
>> David Brownell wrote:
>> > I've checked the updated "usb.c" code into CVS; not sure when it'l be
>> > visible on the website, presumably tomorrow morning, but I'd expect
>> > it's available from CVS already.
>>
>>
(resend, first reply went off the list)
Olaf Hering wrote:
> https://bugzilla.novell.com/show_bug.cgi?id=234147
>
> The joydev driver is not loaded automatically for this joystick:
>
> ...
> Hardware Class: unknown
> Model: "Mega World International USB Game Controllers"
> Vendor: usb 0x07b5 "Me
On Thursday 18 January 2007 9:50 am, Phil Endecott wrote:
> David Brownell wrote:
> > With that and the other patches I've sent (notably the race fix, none
> > of the others ought to matter here), I don't see problem any more.
>
> I still see the problem after applying all of the kernel patches, b
David Brownell wrote:
> With that and the other patches I've sent (notably the race fix, none
> of the others ought to matter here), I don't see problem any more.
I still see the problem after applying all of the kernel patches, but
I'm still using the original usb.c.
> I've checked the updated
On Thu, 18 Jan 2007, Oliver Neukum wrote:
> > > +static ssize_t
> > > +show_autosuspend (struct device *dev, struct device_attribute *attr,
> > > char *buf)
> >
> > The current convention is that we will not put a blank between the
> > function name and the following open paren in new code. Old
Am Donnerstag, 18. Januar 2007 16:17 schrieb Alan Stern:
> On Thu, 18 Jan 2007, Oliver Neukum wrote:
>
> > Hi,
> >
> > this patch introduces a new attribute for USB devices named "autosuspend".
> > It can be used to block autosuspend for each device individually. 0 means
> > disallow suspending;
Am Donnerstag, 18. Januar 2007 16:51 schrieb Oliver Neukum:
> > What happened to the code that actually checks the flag?
>
> It got deleted as unnecessary. Indeed they existed :-;
> usb_autoresume_device() and usb_autosuspend_device() go to:
> status = usb_autopm_do_device(udev, -1);
Of course th
On Thu, 18 Jan 2007, Oliver Neukum wrote:
> Hi,
>
> this patch introduces a new attribute for USB devices named "autosuspend".
> It can be used to block autosuspend for each device individually. 0 means
> disallow suspending; 1 means allow suspending.
>
> This is needed for devices which recharg
From: Jeremy Roberson <[EMAIL PROTECTED]>
Added a kernel module (gtco) to the USB Input subsystem. This kernel
module adds support for all GTCO CalComp USB InterWrite School products.
Signed-off-by: Jeremy A. Roberson <[EMAIL PROTECTED]>
---
diff -uprN a/drivers/usb/input/gtco.c b/drivers/usb/
Hi,
this implements autosuspend for usb printers. It compiles and is tested.
Regards
Oliver
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
--
--- a/drivers/usb/class/usblp.c 2007-01-18 14:12:27.0 +0100
+++ b/drivers/usb/class/usblp.c 2007-01-18 14:42:03.000
Hi,
this patch introduces a new attribute for USB devices named "autosuspend".
It can be used to block autosuspend for each device individually. 0 means
disallow suspending; 1 means allow suspending.
This is needed for devices which recharge their batteries of the bus.
It compiles and is tested.
I use zaurus windows driver. I think this is the C860 ones but other
zaurus drivers (or other embedded product drivers) may work.
When you connect to windows systems it works, but the connection with
linux host depends on the kernel you are using.
With a 2.6.10 it works well.
With 2.6.14 you get
Am Mittwoch, 17. Januar 2007 20:33 schrieb Roberson, Jeremy:
> Thank you for your comments and your help, but should these latest changes
> really need to be made in order to submit to the kernel? It's done the same
> way the usb/input/aiptek.c driver does it.
I've rechecked. Your open() method
17 matches
Mail list logo