Am Dienstag, 6. März 2007 05:13 schrieb Eric Buddington:
reiser4[khubd(163)]: commit_current_atom
(fs/reiser4/txnmgr.c:1049)[nikita-3176]:
WARNING: Flushing like mad: 16384
reiser4[khubd(163)]: commit_current_atom
(fs/reiser4/txnmgr.c:1049)[nikita-3176]:
WARNING: Flushing like mad: 32768
On Tue, 6 Mar 2007, Li Yu wrote:
If we define HID bus allowing drivers to bind on VID:PID and provide
default library module for parsing HID reports and providing access to
HID transports (USB/BT) then writing tiny drivers adjusting just a
part of hid_input_event and relying on default
Hi,
this fixes the spinlock recursion issue. The older fix was incomplete.
Regards
Oliver
Signed-off-by: Oliver Neukum [EMAIL PROTECTED]
-
--- a/drivers/usb/class/cdc-acm.c 2007-03-06 10:39:50.0 +0100
+++ b/drivers/usb/class/cdc-acm.c 2007-03-06
when trying to access /dev/ttyUSB0, which is a port on a dual port
usb-serial cable (mos7720 based) an kernel OOPS happens
the driver loads ok, first access via minicom - OOPS
(config.gz attached)
Mar 6 11:21:49 emerald Unable to handle kernel paging request at
81093d0e3668 RIP:
Mar 6
From: Cyrill Gorcunov [EMAIL PROTECTED]
Avoid NULL pointer usage if workqueue creation failed.
Signed-off-by: Cyrill Gorcunov [EMAIL PROTECTED]
Cc: Pete Zaitcev [EMAIL PROTECTED]
Cc: Greg KH [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
drivers/usb/misc/ftdi-elan.c |
Duck wrote:
The USB blocks in the 8349 and mx31 are basically the same,
with some minor exceptions. The 8349 has one host controller
with two ports plus a dual-role (OTG) controller. The mx31
has two host controllers (one port each), plus an OTG controller.
The 8349 has some additional
From: Simon Arlott [EMAIL PROTECTED]
There is currently no path from the ATM device in /sys to the USB device's
interface that the driver is using; this patch creates a device symlink. It
is then possible to get to the cxacru ADSL statistics
(http://lkml.org/lkml/2007/2/23/328):
From: Simon Arlott [EMAIL PROTECTED]
I've acquired a second device for testing and plan to make some changes in
the near future to export all the device stats to sysfs (based on my
proposed patch to add them to the proc file ~2007-01-30).
Signed-off-by: Simon Arlott [EMAIL PROTECTED]
Acked-by:
From: Simon Arlott [EMAIL PROTECTED]
When the device is polled for status there is a lot of useful status
information available that is ignored. This patch stores the device info
array when the status is polled and adds sysfs files to the usb device to
allow userspace to query it. Since the
Am Montag, 5. März 2007 20:45 schrieb Alan Stern:
On Fri, 2 Mar 2007, Oliver Neukum wrote:
Have a delay attribute per interface and give each device an attribute
SuspensionState with the permissible values on, auto suspend
Handle RemoteWakeup as an orthogonal issue.
After some more
Am Dienstag, 6. März 2007 11:33 schrieb Dirk Schoebel:
when trying to access /dev/ttyUSB0, which is a port on a dual port
usb-serial cable (mos7720 based) an kernel OOPS happens
the driver loads ok, first access via minicom - OOPS
(config.gz attached)
Please apply:
On 06/03/07, Li Yu [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
If we define HID bus allowing drivers to bind on VID:PID and provide
default library module for parsing HID reports and providing access to
HID transports (USB/BT) then writing tiny drivers adjusting just a
part of
But (You may guess I will say this word :), before the HID bus or other
better
implementation come , I hope use the extended keys of my keyboard on
Linux, and I guess other people
also think same with me, so we need something here temporarily, even it
do not merge
into upstream code tree.
Am Freitag, 2. März 2007 17:03 schrieb Alan Stern:
On Thu, 1 Mar 2007, Oliver Neukum wrote:
Actually I had in mind something simpler, like getting rid of the
GET_DESCRIPTOR_TRIES loop for i (or reducing it to one attempt using the
new scheme and one attempt using the old scheme) and
Am Samstag, 3. März 2007 10:07 schrieb Cristian Mammoli:
On ven, 2007-03-02 at 02:08 +0100, Cristian Mammoli wrote:
On gio, 2007-03-01 at 22:14 +0100, Oliver Neukum wrote:
Most recent kernel where this bug did *NOT* occur: 2.6.17
Very good. You are the first one to report a working
On Monday 05 March 2007, Gene Heskett wrote:
Repost, slight edit.
No one has any comments on this lack of usb connectivity?
I have a new F6C1500 Belkin UPS, which when I plug in a pl2303
cable, becomes /dev/ttyUSB0 and Belkins own monitor soft works about
99%.
Its found by the kernel and an
Hi,
this is an update for handling modules in usbvideo
- subdrivers can be compiled into the kernel, don't warn about NULL modules
- a device whose module's open count cannot be upped must not be opened
Regards
Oliver
Signed-off-by: Oliver Neukum [EMAIL PROTECTED]
-
Oliver Neukum wrote:
Am Dienstag, 6. März 2007 11:33 schrieb Dirk Schoebel:
when trying to access /dev/ttyUSB0, which is a port on a dual port
usb-serial cable (mos7720 based) an kernel OOPS happens
the driver loads ok, first access via minicom - OOPS
Please apply:
Am Samstag, 3. März 2007 10:07 schrieb Cristian Mammoli:
On ven, 2007-03-02 at 02:08 +0100, Cristian Mammoli wrote:
On gio, 2007-03-01 at 22:14 +0100, Oliver Neukum wrote:
Most recent kernel where this bug did *NOT* occur: 2.6.17
Very good. You are the first one to report a working
Am Dienstag, 6. März 2007 15:52 schrieb Dirk Schoebel:
hmm, applied these patches, still crashes
Please apply the attached debugging patch.
Regards
Oliver
--- a/drivers/usb/serial/mos7720.c 2007-03-06 16:16:16.0 +0100
+++ b/drivers/usb/serial/mos7720.c
Hi,
GFP_KERNEL will do.
Regards
Oliver
Signed-off-by: Oliver Neukum [EMAIL PROTECTED]
-
--- a/drivers/usb/serial/mos7720.c 2007-03-06 16:16:16.0 +0100
+++ b/drivers/usb/serial/mos7720.c 2007-03-06 16:19:10.0 +0100
@@ -353,7 +353,7 @@
new trace
(if i should activate some kernel debugging optioons just mention it)
Mar 6 16:28:02 emerald usbcore: registered new interface driver moschip7720
Mar 6 16:28:12 emerald Unable to handle kernel NULL pointer dereference at
0070 RIP:
Mar 6 16:28:12 emerald
[881895fb]
On Tue, 6 Mar 2007, Oliver Neukum wrote:
Am Dienstag, 6. März 2007 05:13 schrieb Eric Buddington:
reiser4[khubd(163)]: commit_current_atom
(fs/reiser4/txnmgr.c:1049)[nikita-3176]:
WARNING: Flushing like mad: 16384
reiser4[khubd(163)]: commit_current_atom
On Tue, 6 Mar 2007, Valentin Longchamp wrote:
Alan Stern wrote:
c-desc.bMaxPower is what the hub makes available for each port and
udev-bus_mA is what the device requests.
It's the reverse: (c-desc.bMaxPower * 2) is what the device requests and
udev-bus_mA is what the hub makes
On Tue, 6 Mar 2007, Oliver Neukum wrote:
As you say, remote wakeup is an orthogonal issue. So if remote wakeup is
enabled when the user writes suspend to the attribute, the device will
wakeup when an external event occurs. If not, it won't.
OK, so we have two attributes
On Tue, 6 Mar 2007, Gene Heskett wrote:
On Monday 05 March 2007, Gene Heskett wrote:
Repost, slight edit.
No one has any comments on this lack of usb connectivity?
I have a new F6C1500 Belkin UPS, which when I plug in a pl2303
cable, becomes /dev/ttyUSB0 and Belkins own monitor soft works
Alan Stern wrote:
Ok. So the hub code rejects a device needing 150 mA (which resluts in
300) althoug the MIC2536 is able to provide 150 mA. For me it rejects a
configuration that should be accepted, doestn't it ?
No, no. If c-desc.bMaxPower == 150 then the device really needs 300 mA.
On Tuesday 06 March 2007, Alan Stern wrote:
On Tue, 6 Mar 2007, Gene Heskett wrote:
On Monday 05 March 2007, Gene Heskett wrote:
Repost, slight edit.
No one has any comments on this lack of usb connectivity?
I have a new F6C1500 Belkin UPS, which when I plug in a pl2303
cable, becomes
On 3/6/07, Valentin Longchamp [EMAIL PROTECTED] wrote:
Alan Stern wrote:
Ok. So the hub code rejects a device needing 150 mA (which resluts in
300) althoug the MIC2536 is able to provide 150 mA. For me it rejects a
configuration that should be accepted, doestn't it ?
No, no. If
On Tue, 6 Mar 2007 10:47:04 +0100, Oliver Neukum [EMAIL PROTECTED] wrote:
this fixes the spinlock recursion issue. The older fix was incomplete.
+++ b/drivers/usb/class/cdc-acm.c 2007-03-06 10:39:55.0 +0100
@@ -332,9 +332,9 @@
if (!ACM_READY(acm))
return;
On Tuesday 06 March 2007, Alan Stern wrote:
On Tue, 6 Mar 2007, Gene Heskett wrote:
On Monday 05 March 2007, Gene Heskett wrote:
Repost, slight edit.
No one has any comments on this lack of usb connectivity?
I have a new F6C1500 Belkin UPS, which when I plug in a pl2303
cable, becomes
On Tue, 6 Mar 2007, Gene Heskett wrote:
Further update Alan;
I've managed to get a /dev/hiddev0 created, and if I cat it, there is data
coming out of it at about 1 or 2 bytes/second. But their upsd daemon
doesn't seem to be getting the data when configured for that device. So
its
...btw...
another usb serial adapter (single port ftdi) works well, no OOPSes
so.. maybe the error is less to search within usb-serial itself but more the
interaction or the driver itself...
Dirk.
-
Take Surveys. Earn
On Tue, 6 Mar 2007, Eric Buddington wrote:
On Tue, Mar 06, 2007 at 10:36:20AM -0500, Alan Stern wrote:
On Tue, 6 Mar 2007, Oliver Neukum wrote:
Am Dienstag, 6. M??rz 2007 05:13 schrieb Eric Buddington:
reiser4[khubd(163)]: commit_current_atom
On Tuesday 06 March 2007, Alan Stern wrote:
On Tue, 6 Mar 2007, Gene Heskett wrote:
Further update Alan;
I've managed to get a /dev/hiddev0 created, and if I cat it, there is
data coming out of it at about 1 or 2 bytes/second. But their upsd
daemon doesn't seem to be getting the data when
Oliver Neukum ha scritto:
Well,something weird is going on here...
2.6.17 ubuntu edgy binary: works
2.6.20 ubuntu feisty binary: broken
2.6.17 vanilla: broken O_O
2.6.17 ubuntu edgy patched sources: broken
Can you confirm that you built the kernel from the same sources as
the working
Hi Li,
==
HID device simple driver interface
==
actually, I don't think we need a simple driver interface. We need a HID
driver interface in general. For example that you can register a driver
for one or multiple report ID and
Hi Dmitry,
This also means that the current keyboard and mouse
input devices will become a HID driver.
Are you talking about usbmouse and usbkbd?
no, because if I recall correctly these are the boot mode drivers and
actually not used at all in any modern distribution.
For me the task of
On 3/5/07, Marcel Holtmann [EMAIL PROTECTED] wrote:
This also means that the current keyboard and mouse
input devices will become a HID driver.
Are you talking about usbmouse and usbkbd?
--
Dmitry
-
Take Surveys. Earn
On Mon, 5 Mar 2007, Marcel Holtmann wrote:
actually, I don't think we need a simple driver interface. We need a HID
driver interface in general. For example that you can register a driver
for one or multiple report ID and then it handles input and output for
these report IDs. This also
On Mon, 5 Mar 2007, Marcel Holtmann wrote:
no, because if I recall correctly these are the boot mode drivers and
actually not used at all in any modern distribution.
That's correct.
For me the task of converting HID reports into input events shouldn't be
actually the job of the HID core
Hi Jiri,
For me the task of converting HID reports into input events shouldn't be
actually the job of the HID core layer. My understanding is that the HID
core should support multiple transport layers. This is currently
achieved through the hid_device abstraction and used by the USB
Begin forwarded message:
Date: Tue, 6 Mar 2007 09:31:18 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 8135] New: Sitecom CN-103 USB to Printer cable
adapter doesn't work
http://bugzilla.kernel.org/show_bug.cgi?id=8135
Summary: Sitecom CN-103 USB to
Jon Smirl wrote:
I have five various 802.11 dongles and they all need 300mA.
I'm not sure why the board designers selected the MIC2536
for the mx31ads. When they did the the mx27ads board
they used MIC2026 parts instead, which can supply 500mA.
The parts look to be pin compatible.
You could
This is a note to let you know that we have just queued up the patch titled
Subject: USB: fix concurrent buffer access in the hub driver
to the 2.6.20-stable tree. Its filename is
usb-fix-concurrent-buffer-access-in-the-hub-driver.patch
A git repo of this tree can be found at
This is a note to let you know that we have just queued up the patch titled
Subject: UHCI: fix port resume problem
to the 2.6.20-stable tree. Its filename is
uhci-fix-port-resume-problem.patch
A git repo of this tree can be found at
I got a friend with the same device to USBSnoopy the device in windows and
send me the logs... the problem is... I don't know how to read them. They're
binary files.
Is there a linux viewer to read the logs and see what USB commands its
sending..? I searched around and found usb-robot which will
Hello,
We had the following questions for a peripheral controller driver. We
do have an idea about some of the answers, evidently our understanding
is not complete.
1. The gadget can ask the peripheral controller to send/receive zero
byte packets. Consider the following sub-cases:
a)
On Mon, 2007-03-05 at 15:58 -0800, Pete Zaitcev wrote:
I'm afraid that I have to take back some of the superlatives that
I attached to this patch previously.
Yeep. I was wondering about submitting a CV to RH or something :-)
#2 - The setting and testing of the monitoring flag was completely
49 matches
Mail list logo
