Can you belive it that we will make you amazeed.
You just will bring back some romantic moments that u lost in past!
Refresh ur body, just got our m3dicine and u will fill the difference
between the life
ur living now and between the life with.
http://iurl.biz/nito
- Juan Luis López [EMAIL PROTECTED] wrote:
Finally this works...
Thank you for your help.
I made it work with the David Brownell patch plus changin product and
vendor ID.
Do not mark the RNDIS option in the kernel.
I act as if i were a zaurus :
//#defineSIMPLE_VENDOR_NUM
Hi,
this is the second take of the patch to switch off autosuspend
through sysfs to allow battery powered devices to recharge of the
bus. It includes the cleanups Alan suggested.
In addition, likewise at Alan's request, it cleans up coding style in
the rest of sysfs.c
Regards
Yes the order is correct and the file you have to patch is ether.c.
On the other hand i am using the file pxa27x_udc.c from handhelds
sligtly modified for my platform.
I don't know anything about zaurus licenses, if you find anythig plaese
tell me.
Good Luck.
Juan Luis Lopez Blazquez
GAJATES
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this
are the messages I get (w/o touching the device/usb cable except pluggin it
in for the first time):
Hi,
I need lsusb -v for your device.
Hi,
I did the dirty deed. Could you please tell me which quirky devices
you know of? I am afraid this list needs to be populated and there
are outstanding regressions in Adrian's list.
Regards
Oliver
--
--- a/include/linux/usb.h 2007-01-18 13:15:25.0 +0100
On 1/19/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Hi,
I did the dirty deed. Could you please tell me which quirky devices
you know of? I am afraid this list needs to be populated and there
are outstanding regressions in Adrian's list.
ID 0471:0155 Philips Electronics PSC805
From the long
Am Freitag 19 Januar 2007 12:29 schrieb Oliver Neukum:
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the messages I get (w/o touching the device/usb cable except
pluggin it in for the
Hi,
I'm writing an USB Video Class Driver (UVC) to use the DaVinci EVM as a
video class device.
I want to stream with 30fps, so the maximum number of uframes per video
frame is 266. But I do only fill 240 uframes [1] with payload data to
transmit one video frame over the isochronous
Hello,
Can someone tell me what the preferred method for new client USB
drivers is? Is it preferable to create a new loadable module gadget
or use the gadgetfs module and write the driver in user space?
This is for a proprietary USB protocol that exists in a proprietary
OS, but releasing the
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
Hi,
I can't scan anymore. :-( I don't know which rc kernel introduced it, but
this are the messages I get (w/o touching the device/usb cable except
pluggin it in for the first time):
Hi,
I found quickly booted into a
Ross wrote:
Can someone tell me what the preferred method for new client USB
drivers is? Is it preferable to create a new loadable module gadget
or use the gadgetfs module and write the driver in user space?
This is for a proprietary USB protocol that exists in a proprietary
OS, but
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Hi,
I did the dirty deed. Could you please tell me which quirky devices
you know of? I am afraid this list needs to be populated and there
are outstanding regressions in Adrian's list.
ID
On Fri, 19 Jan 2007, Oliver Neukum wrote:
Hi,
I did the dirty deed. Could you please tell me which quirky devices
you know of? I am afraid this list needs to be populated and there
are outstanding regressions in Adrian's list.
I'll get back to you on the devices.
I think this patch could
On Fri, 19 Jan 2007, Oliver Neukum wrote:
Hi,
this is the second take of the patch to switch off autosuspend
through sysfs to allow battery powered devices to recharge of the
bus. It includes the cleanups Alan suggested.
In addition, likewise at Alan's request, it cleans up coding style in
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, Alan Stern [EMAIL PROTECTED] wrote:
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Hi,
I did the dirty deed. Could you please tell me which quirky devices
you know of? I am afraid
[Removed LKML from the CC: list]
On Fri, 19 Jan 2007, Prakash Punnoor wrote:
Hi,
I found quickly booted into a 2.6.19-rc5 kjernel which was lying around here
and here CONFIG_USB_SUSPEND doesn't make any problems with my scanner...
Do you want me to try out kernels until I find one rc
On 1/19/07, Alan Stern [EMAIL PROTECTED] wrote:
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Hi,
I did the dirty deed. Could you please tell me which quirky devices
you know of? I am afraid this list needs to be populated and there
are
On Fri, 19 Jan 2007, Ross wrote:
Hello,
Can someone tell me what the preferred method for new client USB
drivers is? Is it preferable to create a new loadable module gadget
or use the gadgetfs module and write the driver in user space?
Apart from the issues that Phil mentioned, there are
On Fri, 19 Jan 2007, Patrik Nagel wrote:
Hi,
I'm writing an USB Video Class Driver (UVC) to use the DaVinci EVM as a
video class device.
This sounds like you're writing a driver for the host, not the camera.
But what you write below contradicts that.
I want to stream with 30fps, so the
Anssi Hannula wrote:
With a multi-interface USB HID devices (i.e. my keyboards and
radio-remote receivers), on 2.6.17:
# udevinfo -q all -n /dev/input/event4
P: /class/input/input6/event4
N: input/event4
S: input/by-path/pci-:00:10.0-usb-0:1:1.1-event-
E: ID_VENDOR=Logitech
E:
Hi Alan,
Alan Stern wrote:
On Fri, 19 Jan 2007, Patrik Nagel wrote:
I'm writing an USB Video Class Driver (UVC) to use the DaVinci EVM as a
video class device.
This sounds like you're writing a driver for the host, not the camera.
But what you write below contradicts that.
On 1/19/07, Alan Stern [EMAIL PROTECTED] wrote:
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, Alan Stern [EMAIL PROTECTED] wrote:
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Hi,
I did the dirty deed. Could you please
On Friday 19 January 2007 5:50 am, Patrik Nagel wrote:
So, do I only need to set the payload length of the remaining (but
unused) packets to zero to keep the frame rate? Must I also omit the
two-byte UVC header?
If you don't provide the ISO packet data, that hardware automagically
sends a
The commit 4916b3a57fc94664677d439b911b8aaf86c7ec23 introduced a
hid regression between 2.6.19 and 2.6.20-rc1. The device put in
input_dev-cdev is now of type usb_device instead of usb_interface.
Before:
# readlink -f /sys/class/input/input6/event4/device
On Fri, 19 Jan 2007, Anssi Hannula wrote:
The commit 4916b3a57fc94664677d439b911b8aaf86c7ec23 introduced a
hid regression between 2.6.19 and 2.6.20-rc1. The device put in
input_dev-cdev is now of type usb_device instead of usb_interface.
Yes, this is apparently a bug. Thanks a lot for the
This email lists some known regressions in 2.6.20-rc5 compared to 2.6.19.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way possibly
This email lists some known regressions in 2.6.20-rc5 compared to 2.6.19
with patches available
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any
On Thu, 2007-01-18 at 20:59 +0100, Adrian Bunk wrote:
Subject: CONFIG_JFFS2_FS_DEBUG=2 compile error
References : http://lkml.org/lkml/2007/1/12/161
Submitter : Russell King [EMAIL PROTECTED]
Caused-By : Al Viro [EMAIL PROTECTED]
commit
On Friday 19 January 2007 9:17 am, Jon Smirl wrote:
There is still the unexplained case of it working ok when plugged into
a hub, it only fails on a root controller. But it failed on both ICH4
and ICH5. It works on both my USB 1.0 and USB 2.0 hubs.
Sorry if this came out in earlier discussion
On Friday 12 January 2007 2:12 pm, you wrote:
Phil:
I haven't tried testing your patch. But I have tried using the existing
gadgetfs with net2280 and uhci-hcd. There was no trouble running test #10
with the usb program or with g_zero instead of gadgetfs. I can't imagine
what's going
I act as if i were a zaurus :
//#defineSIMPLE_VENDOR_NUM0x049f
//#defineSIMPLE_PRODUCT_NUM0x505a
#defineSIMPLE_VENDOR_NUM0x04DD
#defineSIMPLE_PRODUCT_NUM0x8007
Just so you know, I won't OK merging that patch upstream. Sharp
would have a very reasonable
On Friday 19 January 2007 1:04 am, Justin Clacherty wrote:
Fantastic! I've just been going through the nightmare of trying to get RNDIS
to work with the pxa270. I'd much prefer using a cdc driver.
You wouldn't be getting a real CDC driver though ... keep that in mind.
I'm constantly amazed
On Fri, 19 Jan 2007, David Brownell wrote:
On Friday 12 January 2007 2:12 pm, you wrote:
Phil:
I haven't tried testing your patch. But I have tried using the existing
gadgetfs with net2280 and uhci-hcd. There was no trouble running test #10
with the usb program or with g_zero
Previously on:
http://lkml.org/lkml/2007/1/19/91
From /var/log/messages:
Jan 19 20:47:07 localhost kernel: usb 2-1: new full speed USB device
using uhci_hcd and address 2
Jan 19 20:47:07 localhost kernel: usb 2-1: Product: PDP95FM Series
Jan 19 20:47:07 localhost kernel: usb 2-1: Manufacturer:
On Fri, 19 Jan 2007, David Brownell wrote:
On Friday 19 January 2007 9:17 am, Jon Smirl wrote:
There is still the unexplained case of it working ok when plugged into
a hub, it only fails on a root controller. But it failed on both ICH4
and ICH5. It works on both my USB 1.0 and USB 2.0
On Friday 19 January 2007 1:30 pm, Alan Stern wrote:
On Fri, 19 Jan 2007, David Brownell wrote:
On Friday 19 January 2007 9:17 am, Jon Smirl wrote:
There is still the unexplained case of it working ok when plugged into
a hub, it only fails on a root controller. But it failed on both
From: Jeremy Roberson [EMAIL PROTECTED]
Adds GTCO CalComp Interwrite IPanels to the hid-core.c blacklist.
Signed-off-by: Jeremy A. Roberson [EMAIL PROTECTED]
---
--- a/drivers/usb/input/hid-core.c 2007-01-06 22:45:51.0 -0700
+++ b/drivers/usb/input/hid-core.c 2007-01-19
On 1/19/07, David Brownell [EMAIL PROTECTED] wrote:
On Friday 19 January 2007 1:30 pm, Alan Stern wrote:
On Fri, 19 Jan 2007, David Brownell wrote:
On Friday 19 January 2007 9:17 am, Jon Smirl wrote:
There is still the unexplained case of it working ok when plugged into
a hub,
David Brownell wrote:
If you want to use the Windows driver binaries shipped by Sharp,
you can modify their INF files to understand the SIMPLE vendor
and product identifiers.
Ok. So my procedure should read:
- apply the pxa270 udc patch
- apply David's patch
- modify Zaurus inf file to
On Fri, 19 Jan 2007, Jeremy Roberson wrote:
From: Jeremy Roberson [EMAIL PROTECTED]
Adds GTCO CalComp Interwrite IPanels to the hid-core.c blacklist.
Hi Jeremy,
applied to HID tree, thanks. I have queued it for the next -mm and for
2.6.21-rc1.
--
Jiri Kosina
On Sat, Jan 20, 2007 at 01:40:19AM +0100, Jiri Kosina wrote:
On Fri, 19 Jan 2007, Jeremy Roberson wrote:
From: Jeremy Roberson [EMAIL PROTECTED]
Adds GTCO CalComp Interwrite IPanels to the hid-core.c blacklist.
Hi Jeremy,
applied to HID tree, thanks. I have queued it for the next -mm
On Fri, 19 Jan 2007, Greg KH wrote:
Hm, so, should drivers/usb/input/hid* patches go through you or me? I
grabbed this for my tree too, so we'll just have to do the merge later
:)
Or, I'd be glad to let you take over these files too, if you want to.
:)
Actually, Vojtech asked me a few
On Sat, Jan 20, 2007 at 01:50:15AM +0100, Jiri Kosina wrote:
On Fri, 19 Jan 2007, Greg KH wrote:
Hm, so, should drivers/usb/input/hid* patches go through you or me? I
grabbed this for my tree too, so we'll just have to do the merge later
:)
Or, I'd be glad to let you take over these
On Thu, Jan 18, 2007 at 08:20:33PM +0100, Gildas Bayard wrote:
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
On Fri, 19 Jan 2007, Greg KH wrote:
Practical for me is to push it off to you :)
:)
If you want it, I have no objection to you taking these types of
patches. As long as you realize that some usb-type of patches for these
files will probably go through my tree due to historical and API
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, David Brownell [EMAIL PROTECTED] wrote:
On Friday 19 January 2007 1:30 pm, Alan Stern wrote:
On Fri, 19 Jan 2007, David Brownell wrote:
On Friday 19 January 2007 9:17 am, Jon Smirl wrote:
There is still the unexplained case
From [EMAIL PROTECTED] Fri Jan 19 16:16:23 2007
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAC7ssEXLzp8i/2dsb2JhbAAN
X-IronPort-AV: i=4.13,213,1167580800;
d=scan'208; a=28478943:sNHT7764624
Date: Sat, 20 Jan 2007 10:08:11 +1000
From: Justin Clacherty [EMAIL
David Brownell wrote:
Ok. So my procedure should read:
- apply the pxa270 udc patch
- apply David's patch
- modify Zaurus inf file to recognise the simple vendor ids
- use Zaurus Windows driver with modified inf
Seems so.
Yes, it worked.
Though: in 2.6.21 my patch should be
On 1/19/07, Alan Stern [EMAIL PROTECTED] wrote:
On Fri, 19 Jan 2007, Jon Smirl wrote:
On 1/19/07, David Brownell [EMAIL PROTECTED] wrote:
On Friday 19 January 2007 1:30 pm, Alan Stern wrote:
On Fri, 19 Jan 2007, David Brownell wrote:
On Friday 19 January 2007 9:17 am, Jon Smirl
On Friday 19 January 2007 7:40 pm, Justin Clacherty wrote:
And at some point
someone should be submitting a pxa270_udc patch for upstream ...
Yes. I'm using the patch submitted to the list by Rodolfo Giometti back
on 22/11/2006, it's based on the handhelds patch. What needs to be
51 matches
Mail list logo
