Hello
Someone tried to make psdocs for 2.6.0-test5? I was trying to get some
documentation for usb, and it seemed successful, just until it reached
usb stuff..
Ashok raj
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
> "Alan" == Alan Stern <[EMAIL PROTECTED]> writes:
[Sorry for the delay in replying - at conference/on vacation...]
Alan> Here are some changes for UHCI power management. Martin,
Alan> maybe you can try them out and see if they help with getting
Alan> your USB mouse to work after
Alan Stern wrote:
But it will take a while to make the changes, and in any case I'm waiting
for some of David Brownell's submitted patches (that touch parts of the
same code) to be accepted before I begin.
I'm believing that's the usb_set_configuration() changes I just
sent along -- yes?
- Dave
This is the latest update of the patch resolving bugs in how device
configurations were reflected in the driver model. It addresses
the last significant problems I know about in that area.
- Moves code around so that usb_set_configuration() updates sysfs
to reflect the current configuration.
David Brownell wrote:
Alan Stern wrote:
The struct device embedded within a struct usb_interface is
initialized as soon as the structure is allocated, so that when
put_device() is called it will contain valid data.
put_device() is not called for unallocated interfaces.
Sounds related to
Alan Stern wrote:
The struct device embedded within a struct usb_interface is
initialized as soon as the structure is allocated, so that when
put_device() is called it will contain valid data.
put_device() is not called for unallocated interfaces.
Sounds related to something I recently ran int
This patch implements the change discussed last weekend. Rather than
allocating separate memory areas for the "extra" descriptors and copying
the descriptor contents, it simply makes the "extra" pointers refer to
memory within the rawdescriptor arrays.
Alan Stern
# This is a BitKeeper genera
This patch adds some extra error checking. The patch-comments list most
it. Particularly worth noting is the check on the endpoint addresses.
Since these addresses are used as indexes for the epmaxpacketin and
epmaxpacketout arrays, illegal values could result in overwriting
unrelated areas
This patch changes the usb_parse_interface() routine so that it only
handles a single interface/altsetting descriptor at a time, rather than
trying to handle all the altsettings for an interface at once. Besides
shrinking the code slightly, this has the advantage of not requiring the
interfaces to
This patch centralizes the error checking for invalid descriptor lengths
and unexpected descriptor types. Instead of doing it in three different
places -- while parsing configuration, interface, and endpoint descriptors
-- the new code does it all at once. Not surprisingly, this yields a net
savi
This patch removes the home-brewed resizeable arrays used to store
altsetting structures, along with the now-unneeded max_altsetting field.
Since we are already making a preliminary pass through all the descriptors
to check their lengths, we take the opportunity to also count the number
of altset
Although it's hard to tell from reading the patch, this just moves one
section of code to a slightly different spot. Currently the code that
skips over the extra class- and vendor-specific configuration-related
descriptors is part of the loop that parses interface descriptors. The
patch moves
This patch includes a bunch of little local improvements to the code,
listed in the patch comments. There are only two notable changes. If a
device has more configurations than our maximum, the code doesn't reject
the device but simply parses as many configurations as it can and ignores
the rest.
Everybody:
Here follows a set of changes for the descriptor parsing routines in
core/config.c, broken up into a set of 9 patches. The code isn't very
complex but it does require study, and I would appreciate people reading
through my changes to make sure there aren't any mistakes. Though perh
This patch fixes the most blatant problems that can happen when an error
is encountered during descriptor parsing.
The struct device embedded within a struct usb_interface is
initialized as soon as the structure is allocated, so that when
put_device() is called it will contain valid data.
On Sun, 14 Sep 2003, Matthew Dharm wrote:
> (NOTE: Cross-posted to several lists. Watch your replies.)
>
> For a while now in 2.5 and 2.6, I've been getting reports of an
> incompatibility between st.ko and the usb-storage driver. I've finally
> managed to figure out the problem; it only affects
On Mon, Sep 15, 2003 at 10:12:40AM -0500, [EMAIL PROTECTED] wrote:
>
> Why are the two different? I don't see how booting into another OS would change
> anything, but it does. Our other devices using the Cypress FX chip do not have
> this issue.
The windows driver downloaded the firmware for th
On Fri, Sep 12, 2003 at 06:32:51PM -0400, Johannes Erdfelt wrote:
> On Fri, Sep 12, 2003, Jean Tourrilhes <[EMAIL PROTECTED]> wrote:
> > I just spent some time tracking a problem with hci_usb (BlueZ
> > USB driver) and uhci. This happens on 2 different PCs with different
> > hardware and 2.4.X
Alan Stern wrote:
David and Greg:
This patch fixes usbnet and usbtest. When checking endpoints, they
iterate through all interfaces out to intf->max_altsetting, but they
should only go up to intf->num_altsetting. The max_altsetting value
refers to the amount of space _allocated_ for usb_host_int
David and Greg:
This patch fixes usbnet and usbtest. When checking endpoints, they
iterate through all interfaces out to intf->max_altsetting, but they
should only go up to intf->num_altsetting. The max_altsetting value
refers to the amount of space _allocated_ for usb_host_interface
structures,
Randy.Dunlap wrote:
On Mon, 15 Sep 2003 16:09:08 +0100 Paulo Marques <[EMAIL PROTECTED]> wrote:
|
| Hi all,
|
| I sent an email to the current "USB PRINTER DRIVER" maintainer in 04 Aug and 11
| Sep, to warn about a bug found in the printer.c driver in kernel version 2.4.22.
| I even corrected
M.S. Lucas wrote:
Hello,
I'm having problems with my APC UPS using an USB cable and the 2.6.0-test5
kernel
I hope somebody can help me?
...
So it looks like it enumerated OK, but then the HID code misbehaved.
[EMAIL PROTECTED]:/etc/apcupsd $ /etc/init.d/apcupsd-devel start
Starting APC UPS powe
On Mon, 15 Sep 2003 16:09:08 +0100 Paulo Marques <[EMAIL PROTECTED]> wrote:
|
| Hi all,
|
| I sent an email to the current "USB PRINTER DRIVER" maintainer in 04 Aug and 11
| Sep, to warn about a bug found in the printer.c driver in kernel version 2.4.22.
| I even corrected the bug and sent a p
Hi all,
I sent an email to the current "USB PRINTER DRIVER" maintainer in 04 Aug and 11
Sep, to warn about a bug found in the printer.c driver in kernel version 2.4.22.
I even corrected the bug and sent a patch.
As listed in MAINTAINERS, the current maintainer is Vojtech Pavlik
([EMAIL PROTECT
After getting some more time to play with my usb-storage device
that was stalling and timing out when used with the ehci usb 2.0
driver, i finally tried what David mentioned below, and although it
didn't work with 0x00ff or 0xaff, but taking out the mask altogether
and now my device works perfectly
As long as I'm being a nusance today, I might as well put my whole problem out
on the board, and see if anyone recognize anything in the problem.
I am working with a Filter Wheel (FW) developed in house(fli-cam.com) based on
the Cypress FX UB chip. It displays some strange behavior. If I plug th
Arun Prasad wrote:
Hello,
I'll have to write gadget/device mode USB driver for a custom(MIPS) board.
Any pointer/reference would be of great help.
Start with the pointer Stephen Gowdy gave you earlier: the
link off the front page of http://www.linux-usb.org/ gives
the BK repositories, and mention
Hello,
I'm having problems with my APC UPS using an USB cable and the 2.6.0-test5
kernel
I hope somebody can help me?
[EMAIL PROTECTED]:/etc/apcupsd $ uname -a
Linux orion 2.6.0-test5 #4 SMP Sun Sep 14 20:06:21 CEST 2003 i686 GNU/Linux
[EMAIL PROTECTED]:/etc/apcupsd $ lspci -v
02:08.0 USB Contr
This patch adds Wake On LAN (WOL) and eeprom dumping support via ethtool
to the ax8817x portion of usbnet. This only permits the configuration
of WOL for the device, actual operation of WOL would seem to be handled
at lower levels of the USB subsystem. It also serves as an example of
how othe
Yeah,
Ignore the reduenent sniffer message . I wrote that Friday, and sent it out
this morning before reading the list.
Quoting "Stephen J. Gowdy" <[EMAIL PROTECTED]>:
> This question was raised a few days ago, see (and the various
> followups);
>
> http://marc.theaimsgroup.com/?l=linux-usb-
This question was raised a few days ago, see (and the various followups);
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=106339758818614&w=2
On Mon, 15 Sep 2003 [EMAIL PROTECTED] wrote:
> Hey, I feel like a jerk asking the list this question, but I have looked high
> and low, and found little
Hey, I feel like a jerk asking the list this question, but I have looked high
and low, and found little or nothing.
I have a device that is getting a bad idVendor and idProduct in Linux, but not
in windows.*
I think that sniffing the USB connection would help me figure it out, but after
30 google
FROM: THE DESK OF THE VICE PRESIDENT
INTERNATIONAL PROMOTIONS/PRIZE AWARD DEPT.
REF NO: EGS/2560145701/02.
BATCH NO:14/0013/1PD
Date:11 JULY..,2003.
ATTN:
RE:AWARD NOTIFICATION FINAL NOTICE
WE are pleased to inform you of the release of the results of the
GLOBAL NET SWEEPSTAK
On Mon, 2003-09-15 at 05:25, David Brownell wrote:
> Thomas, this goes on top of the other patch. It fixes several
> other lint warnings/bugs in lsusb; it was the only file with
> those problems. How correct is that HID parsing? :)
I don't know :)
I've applied most of your patch, thanks.
Tom
Hello,
I'll have to write gadget/device mode USB driver for a custom(MIPS) board.
Any pointer/reference would be of great help.
Warm Regards
Arun
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_
35 matches
Mail list logo
