Hello I have read a couple of interesting Greg Kroah articles on Linux
Journal n.120 and n.122 about creation of a new USB driver with the reverse
engineering of USB visual signal indicator.
Now I'd like to do something like that porting a WindowsXP driver to linux.
I have not the sources and I
On Tue, Jun 21, 2005 at 07:02:22PM -0700, Andrew Morton wrote:
>
>
> Begin forwarded message:
>
> Date: Tue, 21 Jun 2005 18:44:03 -0700
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [Bugme-new] [Bug 4776] New: uhci_hcd: host controller halted, very
> bad!
>
>
> http://bugzilla.
Alfred Ganz wrote:
> Phil,
> Date: Tue, 21 Jun 2005 21:45:21 -0700
> Subject: Re: [linux-usb-devel] Please send a copy
>
> > Attached please find an extract from my syslog files as requested
> there. I
> > am running Fedora Core 3 with all released updates as of today
>
On Tue, Jun 21, 2005 at 10:19:26PM +, Userstack wrote:
> Hello,
>
> I am running gentoo64 with the following kernel
> . . .
> $uname -a
> Linux amd64 2.6.12 #1 Fri Jun 17 22:16:51 UTC 2005 x86_64 AMD Athlon(tm)
> 64 Processor 3000+ AuthenticAMD GNU/Linux
> . . .
>
> I have plugged three USB f
Thank you for your reply,
I use a boad similar to fads and try to make m8xxhci.c driver work ( i
connect the CLK3 on PA5 and timer 1 exit on PA6).
The driver detects correctly the device on the USB bus, but no data goes out
on the usb data out pins of MPC885.
Here is the trace i get :
m8x
SN9C10x driver updates.
Changes: + new, - removed, * cleanup, @ bugfix
@ Remove bad get_ctrl()'s
* Documentation updates
+ Add 0x0c45/0x602d to the list of SN9C10x based devices
+ Add support for OV7630 image sensors
Signed-off-by: Luca Risolia <[EMAIL PROTECTED]>
Greg, please apply.
Luca Riso
Hi,
With the latest git tree, the USB core no longer creates sysfs entries
for interfaces which haven't been probed by a driver. It used to work
until yesterday. I am talking about these:
defiant:/sys/devices/pci0001:10/0001:10:1a.0/usb1/1-2 125 > ls -al
total 0
drwxr-xr-x 5 root root0 2005-
Le mercredi 22 juin 2005 à 15:50 +0200, Stelian Pop a écrit :
> I use the 'atp' input driver from http://popies.net/atp/ to drive this
> touchpad. When removing the driver I also get an oops, possibly related
> to the previous failure to create the sysfs file:
> usbcore: deregistering driver atp
>
I got no answer in usb-user, so I'm trying usb-devel... Any
assistance is greatly appreciated.
Thanks
Ted
On 20 Jun 2005, [EMAIL PROTECTED] wrote:
> I didn't want to submit a bug report without checking that this really
> is a bug and not something I've missed. Any help would be greatly
> app
Le mercredi 22 juin 2005 à 16:07 +0200, Stelian Pop a écrit :
> Le mercredi 22 juin 2005 à 15:50 +0200, Stelian Pop a écrit :
>
> > I use the 'atp' input driver from http://popies.net/atp/ to drive this
> > touchpad. When removing the driver I also get an oops, possibly related
> > to the previous
On Wed, Jun 22, 2005 at 03:50:56PM +0200, Stelian Pop wrote:
> I use the 'atp' input driver from http://popies.net/atp/ to drive this
> touchpad. When removing the driver I also get an oops, possibly related
> to the previous failure to create the sysfs file:
Sounds like a bug in that driver, care
Le mercredi 22 juin 2005 à 07:59 -0700, Greg KH a écrit :
> On Wed, Jun 22, 2005 at 03:50:56PM +0200, Stelian Pop wrote:
> > I use the 'atp' input driver from http://popies.net/atp/ to drive this
> > touchpad. When removing the driver I also get an oops, possibly related
> > to the previous failure
On Wed, 22 Jun 2005, Stelian Pop wrote:
> Le mercredi 22 juin 2005 à 07:59 -0700, Greg KH a écrit :
> > On Wed, Jun 22, 2005 at 03:50:56PM +0200, Stelian Pop wrote:
> > > I use the 'atp' input driver from http://popies.net/atp/ to drive this
> > > touchpad. When removing the driver I also get an
Le mercredi 22 juin 2005 à 11:41 -0400, Alan Stern a écrit :
> This is a curious aspect of the driver model core. Should failure of a
> driver to bind be considered serious enough to cause device_add to fail?
> The current answer is Yes unless the driver's probe routine returns
> -ENODEV or -EN
On Wed, 22 Jun 2005, Stelian Pop wrote:
> Notice the '1-2:1.1' is missing. Upon booting I get:
>
> Jun 22 13:34:04 localhost kernel: HID device not claimed by input or hiddev
> Jun 22 13:34:04 localhost kernel: usbhid: probe of 1-2:1.1 failed with error
> -5
> Jun 22 13:34:04 localhost kernel: u
On Wed, Jun 22, 2005 at 04:56:30PM +0200, Stelian Pop wrote:
> Le mercredi 22 juin 2005 ?? 16:07 +0200, Stelian Pop a ??crit :
> > Le mercredi 22 juin 2005 ?? 15:50 +0200, Stelian Pop a ??crit :
> >
> > > I use the 'atp' input driver from http://popies.net/atp/ to drive this
> > > touchpad. When r
On Wed, Jun 22, 2005 at 05:53:28PM +0200, Stelian Pop wrote:
> Le mercredi 22 juin 2005 ?? 11:41 -0400, Alan Stern a ??crit :
>
> > This is a curious aspect of the driver model core. Should failure of a
> > driver to bind be considered serious enough to cause device_add to fail?
> > The current
On Wed, Jun 22, 2005 at 05:53:28PM +0200, Stelian Pop wrote:
> Le mercredi 22 juin 2005 ?? 11:41 -0400, Alan Stern a ??crit :
>
> > This is a curious aspect of the driver model core. Should failure of a
> > driver to bind be considered serious enough to cause device_add to fail?
> > The current
Le mercredi 22 juin 2005 à 09:26 -0700, Greg KH a écrit :
> > - return -EIO;
> > + return -ENODEV;
> > }
>
> Also need to do the same a few lines above in the code. I've fixed that
> too now.
Indeed, especially since the only way to use an alternate driver for a
real hid
Le mercredi 22 juin 2005 à 09:22 -0700, Greg KH a écrit :
> On Wed, Jun 22, 2005 at 05:53:28PM +0200, Stelian Pop wrote:
> > Le mercredi 22 juin 2005 ?? 11:41 -0400, Alan Stern a ??crit :
> >
> > > This is a curious aspect of the driver model core. Should failure of a
> > > driver to bind be con
Le mercredi 22 juin 2005 à 12:03 -0400, Alan Stern a écrit :
> On Wed, 22 Jun 2005, Stelian Pop wrote:
>
> > Notice the '1-2:1.1' is missing. Upon booting I get:
> >
> > Jun 22 13:34:04 localhost kernel: HID device not claimed by input or hiddev
> > Jun 22 13:34:04 localhost kernel: usbhid: probe
Phil,
Date: Wed, 22 Jun 2005 00:47:43 -0700
Subject: Re: [linux-usb-devel] Please send a copy
Patch your kernel source and then do:
"make M=drivers/usb/storage"
and it will just build the usb-storage module (assuming you've
On Wed, Jun 22, 2005 at 02:41:48PM -0400, Alfred Ganz wrote:
> Phil,
> Date: Wed, 22 Jun 2005 00:47:43 -0700
> Subject: Re: [linux-usb-devel] Please send a copy
>
> Patch your kernel source and then do:
>
> "make M=drivers/usb/storage"
>
> and it
Hi,
I am somewhat tired now.
Which function is called upon probe() for usb serial drivers?
TIA
Oliver
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps,
On Wed, Jun 22, 2005 at 10:44:03PM +0200, Oliver Neukum wrote:
> Hi,
>
> I am somewhat tired now.
> Which function is called upon probe() for usb serial drivers?
The one that they specify should be :)
Seriously, they all point to usb_serial_probe(). Then it's up to that
function to call the ind
Greg,
Attached is a patch to remove an unneeded SubClass and Protocol entry
from unusual_devs.h. Please apply.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://ww
Am Donnerstag, 23. Juni 2005 07:06 schrieb Greg KH:
> On Wed, Jun 22, 2005 at 10:44:03PM +0200, Oliver Neukum wrote:
> > Hi,
> >
> > I am somewhat tired now.
> > Which function is called upon probe() for usb serial drivers?
>
> The one that they specify should be :)
>
> Seriously, they all point
dekkker wrote:
>
> usb-storage: This device (059f,a601,0200 S 01 P 01) has an unneeded Protocol
> entry in unusual_devs.h
>Please send a copy of this message to
>
Can you please try the attached patch?
> This appeared in my dmesg when I connect the mentioned disk.
>
> mount says: /dev/sd
On Thu, Jun 23, 2005 at 07:52:18AM +0200, Oliver Neukum wrote:
> Am Donnerstag, 23. Juni 2005 07:06 schrieb Greg KH:
> > On Wed, Jun 22, 2005 at 10:44:03PM +0200, Oliver Neukum wrote:
> > > Hi,
> > >
> > > I am somewhat tired now.
> > > Which function is called upon probe() for usb serial drivers?
Here's two patches that fixes some oopses with the USB code due to a
change in the driver core (could also cause problems with other
subsystems, just happened to notice it in the USB code.) Many thanks to
Stelian Pop for noticing this and figuring out the fix for it.
Please pull from:
rsy
[PATCH] driver core: Fix up the device_attach() error handling in
bus_add_device()
Don't error out if something "bad" happens when trying to bind a driver to a
device. We want the sysfs attributes to be present for later when we try to
tear down the device.
Signed-off-by: Greg Kroah-Hartman <[E
[PATCH] USB: fix hid core to return proper error code from probe
Drivers need to return -ENODEV when they can't bind to a device.
Anything else stops the "bind a device to a driver" search.
From: Stelian Pop <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
commit 479
hi
i m linux user.
is there any linux doc on driver for USB GADGET for OBEX.?
can you help me???
thank you
regards rakesh
--
RAKESH YADAV
B.Tech final Year
Electronics and Communication ENGG
I.I.T. ROORKEE
---
SF.Net email is sponsored by: Di
33 matches
Mail list logo
