On Sunday 02 December 2007, Daniel Drake wrote:
> I wonder if something else in the chain will reject
> big control urbs.
The HCDs have limits. ISTR that OHCI and EHCI pick
something convenient; 4 KBytes is save, more is iffy.
-
To unsubscribe from this list: send the line "unsubscribe linux-u
On Monday 13 August 2007, Daniel Exner wrote:
> David Brownell wrote:
> > On Monday 13 August 2007, [EMAIL PROTECTED] wrote:
> > > With the VIA controller I have,
> >
> > Which kind is that? The VT6202 is buggy as all get-out, and
> > they sold a *LOT* of th
On Monday 13 August 2007, [EMAIL PROTECTED] wrote:
> With the VIA controller I have,
Which kind is that? The VT6202 is buggy as all get-out, and
they sold a *LOT* of those discrete chips for use in add-on PCI
cards. We generally warn people away from those. A more current
version is the VT6212,
On Monday 13 August 2007, Midhun Agnihotram wrote:
> Hi All,
>
> We are have a development kit on which we are trying to run USB
> host port. The drivers are from the vendor. The kernel recognizes the
> USB host controller. But as soon as we insert a USB flash drive, the
> kernel hangs with th
On Monday 13 August 2007, vivekanand kumar wrote:
> Hi,
>Can someone guide me to adapt changes to host contoller layer
>to suit oxford USB host controller on uclinux blackfin processor.
You shouldn't need any changes to that layer. You should be able
to just write a new HCD using the exi
On Sunday 12 August 2007, [EMAIL PROTECTED] wrote:
> Add file pattern to MAINTAINER entry
>
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
>
I seem to be missing some context for these "2many" patches; and
don't really see any in the MARC archives either. This seems like
about 600 patches out
On Friday 10 August 2007, Gabriel C wrote:
> Getting that with gcc 4.2.1 :
>
> drivers/usb/host/ohci-dbg.c: In function 'show_registers':
> drivers/usb/host/ohci-dbg.c:620: warning: the address of 'next' will always
> evaluate as 'true'
> drivers/usb/host/ohci-dbg.c:639: warning: the address of 'n
On Saturday 11 August 2007, Alan Stern wrote:
> On Fri, 10 Aug 2007, David Brownell wrote:
>
> > > The code in ohci-hcd isn't very sophisticated about
> > > checking for interference from the firmware. Maybe because there are
> > > so many different i
On Friday 10 August 2007, Felipe Balbi wrote:
>Better indentation
I don't think so. This whole patch seems to make one
type of change:
> - unsigned char St_ModeID;
> - unsigned short St_ModeFlag;
> - unsigned char St_StTableIndex;
> - unsigned char St_CRT2CRTC;
>
On Friday 10 August 2007, [EMAIL PROTECTED] wrote:
> Previous boards were likely seeing USB_ARCH_HAS_HCD selected by way of
> PCMCIA or PCI, though none of those are required for hcd support on SH.
> Enable support unconditionally.
In fact, maybe that ARCH_HAS_HCD switch should vanish.
On Friday 10 August 2007, Alan Stern wrote:
> > When the OLPC comes up from suspend, a small bit of Open Firmware code
> > gets run, this writes 1 to HcCommandStatus, resetting the OHCI chip into
> > Suspend mode, then writes into HcRhDescriptorB and HcRhPortStatus*,
> > bringing up the power to th
On Friday 10 August 2007, Folkert van Heusden wrote:
> My question now is: will each device always have the same node? Will
> device A always get for example /dev/usb/hiddev0? and C always
> /dev/usb/hiddev2?
Not as a rule, although you might notice they don't differ a lot
in some cases. I'd cert
On Thursday 09 August 2007, Zephaniah E. Hull wrote:
> OHCI isn't coming back on the OLPC after resume.
>
> After a bit of testing, the problem seems to have come down to two points.
>
> The first is that ohci_pci_resume is not forcing the root hub to be resumed
> properly, that's a fairly trivia
It appears that one reason the "iConnect"-labeled multi-card reader was
on sale for only $5 is that it doesn't handle suspend/resume correctly.
Other than that, it was a good deal for a highspeed MMC/SD bridge.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
driv
On Tuesday 07 August 2007, Felipe Balbi wrote:
> Hello all,
>
> Is there a way of reseting USB HCD from userspace without removing the
> kernel module?
No. That would reset the entire bus ... which "should" only be done
after cleanly disconnecting all devices on that bus.
> I can see there's a
On Monday 06 August 2007, Tobias wrote:
> > The rndis_host driver isn't expected to work with all RNDIS
> > devices, that's why it's still "EXPERIMENTAL". You could find
> > out what's wrong and fix it. :)
> >
>
> Ok but it is the right driver to start work with it, right ?
It's the only hos
On Monday 06 August 2007, you wrote:
> Hi,
>
> i have an USB Host to Host Bridge (PL-2502) which can act like an rndis
You don't mean PL-2501 do you? The Prolific website doesn't
talk about a new PL-2502 chip.
Of course it doesn't include any specs for the PL-2501 either,
which makes it hard t
On Friday 03 August 2007, Lorenzo T. Flores wrote:
>
> Anyways, for a while now, I've been trying to get the ethernet gadget
> driver working on a Cirrus EP9315A development board contains the
> Phillips ISP1581 usb device controller.
There is no drivers/usb/gadget/isp1581.c driver ...
> The
On Friday 03 August 2007, Dave Jones wrote:
> > > Plus if you're connected to such a device for monitoring purposes you're
> > > probably powered by it as well, so you have little to gain from suspend
> > > even if it works.
> >
> > I currently don't have any HID UPS by hand to verify, but
On Friday 03 August 2007, Matthew Garrett wrote:
> On Fri, Aug 03, 2007 at 07:37:55AM -0700, David Brownell wrote:
> > On Friday 03 August 2007, Matthew Garrett wrote:
> > > Popping up a box saying "Is your device broken?" isn't good UI.
> >
> >
On Friday 03 August 2007, Dave Jones wrote:
> > We have been playing with runtime autosuspend of HID devices, are
> > currently postponed the full support, as it turns out that many devices
> > don't support this feature properly (probably due to not being tested in
> > Windows).
>
> Intere
On Friday 03 August 2007, Matthew Garrett wrote:
> On Fri, Aug 03, 2007 at 07:01:11AM -0700, David Brownell wrote:
>
> > Which is, as I pointed out, the wrong response. Desktoppy
> > people should be making their tools do more intelligent things
> > with new USB d
On Friday 03 August 2007, Thaens Tim wrote:
> ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected
> drivers/usb/serial/ftdi_sio.c: Detected FT232BM
That seems wrong. An FT232 is a serial adapter.
While an FT245 is a parallel adapter.
-
On Friday 03 August 2007, Dave Jones wrote:
> On Thu, Aug 02, 2007 at 11:06:08PM -0700, David Brownell wrote:
>
> > Sometimes when I plug in a USB device I get a dialog asking if I want to
> > configure it ... surely it would be possible to have that mechanism also
>
On Friday 03 August 2007, gutian abei wrote:
> I am trying to develop a USB device driver in Linux platform.
> Our device has the ability of re-enumeration.
Like the Cypress chips, which use one device ID before the
firmware is loaded and then another one later after it restarts
with that new firm
On Friday 03 August 2007, Oliver Neukum wrote:
> Well, I've thought a bit about this. I know a hub is to blame. Even if I did
> learn what causes this specific error, it wouldn't help in the other cases.
> IMHO improving error handling is better than avoiding this fault.
But do you know *how* a hu
On Friday 03 August 2007, Matthew Garrett wrote:
> On Fri, Aug 03, 2007 at 02:26:43PM +0200, Rogan Dawes wrote:
>
> > Which one is more likely to conclude at some point?
Good question ... though "how will it conclude" is also relevant.
> > Compare that to:
> >
> > "My USB printer broke, guess I
On Thursday 02 August 2007, Oliver Neukum wrote:
> Am Freitag 03 August 2007 schrieb David Brownell:
> > On Wednesday 01 August 2007, Oliver Neukum wrote:
> > > Am Dienstag 31 Juli 2007 schrieb Alan Stern:
> > > > You assign dev->intf in both the usbnet framework
On Thursday 02 August 2007, Matthew Garrett wrote:
> The main
> concern I have is that kernel developers just don't tend to be the sort
> of people that use webcams, printers or scanners, so we're relying on
> normal users to go to the effort of reporting that their device has
> stopped working
On Thursday 02 August 2007, Alan Stern wrote:
> Also, building something this sweeping into a kernel driver feels like
> a mistake. It ought to be more easily configurable from userspace, say
> via a sysfs file.
Yeah, I could have sworn there was extensive discussion over the
creation of a sysfs
On Wednesday 01 August 2007, Oliver Neukum wrote:
> Am Dienstag 31 Juli 2007 schrieb Alan Stern:
> > You assign dev->intf in both the usbnet framework driver and the
> > subdriver. Could the subdriver's assignment be removed?
>
> Here we go again.
>
> Regards
> Oliver
> Signe
On Wednesday 01 August 2007, Steve Calfee wrote:
> At 10:42 PM 7/16/2007, David Brownell wrote:
> >I don't recall testing high bandwidth ISO. In general, ISO support
> >is pretty weak with EHCI ...
Actually, now that I think of it I *did* test it, but only using
the "
x27;t pass gfp_t around when it's
always going to be GFP_ATOMIC, and do static init of serial number.
Also go to straight GPL; there's no real point in dual licensing this
stuff any more.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
... same as previous version except
On Thursday 02 August 2007, Alan Stern wrote:
> On Thu, 2 Aug 2007, David Brownell wrote:
>
> > Clean up the file storage gadget, using newer APIs and conventions:
> >
> > - gadget_is_dualspeed() and gadget_is_otg() ... #ifdef removal
> >
> >
x27;t pass gfp_t around when it's
always going to be GFP_ATOMIC, and do static init of serial number.
Also go to straight GPL; there's no real point in dual licensing this
stuff any more.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb
l dislikes the __user annotations)
This gave only a minor object code shrinkage.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
Cc: Alan Stern <[EMAIL PROTECTED]>
---
drivers/usb/gadget/file_storage.c | 118 ++
1 file changed, 45 inser
.
This gave only a minor object code shrinkage, but the source looks
much cleaner in various places.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
Cc: Al Borchers <[EMAIL PROTECTED]>
---
drivers/usb/gadget/serial.c | 166 +++-
1 file changed, 7
Clean up the midi gadget, using newer APIs and conventions:
- Remove many now-needless #includes
- Use the DEBUG (from Kconfig+Makefile) and VERBOSE_DEBUG conventions.
- Whitespace fixes
There should be no effect on object code size.
Signed-off-by: David Brownell <[EMAIL PROTECTED]&
aved about 2K of code (16%) on a fullspeed-only
ARMv4 platform. I'm bit puzzled by that (it's so much!), but approve
of the result.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/gadget/ether.c | 147 +
1 file cha
me from patches which will follow.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/gadget/fsl_usb2_udc.c |9 ++-
drivers/usb/gadget/inode.c| 44 +-
drivers/usb/gadget/omap_udc.c | 10 ++--
include/linux/usb_g
Following this are several minor gadget stack updates:
- Add gadget_is_dualspeed() and gadget_is_otg() predicates,
which can help remove #ifdeffery and associated cleanups.
Includes updates to fsl_usb2_udc, omap_udc, and gadgetfs.
- Use those to cleanup the Ethernet gadget. Amazingly, th
On Wednesday 01 August 2007, Daniel Mack wrote:
> on an i.MX31 ARM based system which has an EHCI controller on-chip,
> kernel version 2.6.19.2 crashes occur randomly
What does "randomly" mean?
And why aren't you using 2.6.23-rc1-git?
> with lots of USB bulk
> traffic in action, usually aft
This just fixes some whitespace bugs in ,
mostly extraneous spaces where a single tab suffices.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
include/linux/usb_gadget.h | 62 ++---
1 file changed, 31 insertions(+), 31 deletions(-)
--- g2
aq quirk and a NEC quirk are now properly compiled out for
non-PCI builds of this driver.
Signed-off-by: Mike Nuss <[EMAIL PROTECTED]>
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/host/ohci-hcd.c | 166
drivers/usb/host/o
On Wednesday 01 August 2007, Li Yang-r58472 wrote:
> Hi Dave,
>
> We are using Ethernet gadget to communicate with Windows
> host with RNDIS mode. We tried to use NFS on the simulated
> network, but keep getting "no response" error when
> transmitting big files. As you mentioned in the ether.c
>
On Tuesday 31 July 2007, Alan Stern wrote:
> > Related: consider making urb->interval and its neighbors
> > be "u32" or maybe even "u16".
>
> Hmmm... maybe. It's not clear the space savings would matter much; I
> doubt that terribly many URBs ever get allocated at the same time.
I don't follow
On Monday 30 July 2007, Alan Stern wrote:
> +static inline int usb_urb_dir_in(struct urb *urb)
> +{
> + return (urb->transfer_flags & URB_DIR_MASK) != URB_DIR_OUT;
> +}
Clearer would be: == URB_DIR_IN ... or does that generate bad code?
On Monday 30 July 2007, Alan Stern wrote:
> /* power of two? */
> - while (temp > urb->interval)
> - temp >>= 1;
> - urb->interval = temp;
> + while (max > urb->interval)
> + max >>= 1;
> +
This removes complaints about the gadget stack which are generated by
the currrent "sparse": it doesn't like the fact that zero is the null
pointer. (Last I checked, C guarantees that's correct ...)
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/
On Thursday 26 July 2007, Srinivas rao wrote:
> Now I need a linux application for 4 or more bulk endpoints because my
> device
> controller supports 6bulk endpoints.
Why would you "need" that?
> Please any one suggest me for multiple endpoints application.
Composite devices of course.
On Monday 30 July 2007, Oliver Neukum wrote:
>
> > But -- never actually having had both a highspeed USB sniffer *AND*
> > hardware exhibiting this problem in the same place -- I've not been
> > able to test that theory.
>
> The hub in question is light and small. Give me your address and I'll
>
On Monday 30 July 2007, Boris Losev wrote:
> I've got the APC Back-UPS CS 650 and Debian Etch with the kernel
> 2.6.18-4-686. I've tried to connect my UPS to PC via USB cable and got
> the errors:
>
> usb 2-1: new low speed USB device using ohci_hcd and address 14
> usb 2-1: device not accepting
On Monday 30 July 2007, Alan Stern wrote:
> > Maybe if he echo'es correctly on sysfs, he could achieve this...
>
> Nope. You cannot turn off the USB bus power on the computer's USB
> ports no matter what you do; the hardware doesn't permit it.
It does on some systems. Rarely on PCs though.
On Saturday 19 May 2007, Ragner Magalhaes wrote:
> The following series implements USB Composite Gadget Support.
And I'm finally looking at this again. :)
These patches seem to be "step one", just starting to
make conversions. I'm assuming that you're circulating
them to get feedback (which, so
On Sunday 29 July 2007, Nikita V. Youshchenko wrote:
> Hello people.
>
> Currently (as of 2.6.23-rc1), there are two definition of USB_OTG in
> Kconfig files - one is in drivers/usb/core/Kconfig, and second is in
> drivers/usb/gadget/Kconfig (and there, inside a choice).
>
> Is this double-defi
On Sunday 29 July 2007, Jon Smirl wrote:
> On 7/29/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > On Sat, Jul 28, 2007 at 09:42:40AM -0400, Jon Smirl wrote:
> > > I have a large patch (megabytes) including a rework of the USB OTG
> > > code from 2.6.10 by Philips. It's too large to post.
> >
> > Then t
On Friday 27 July 2007, Alan Stern wrote:
> > stressing a flash disk I rapidly get this error:
>
> > Jul 27 12:35:00 oenone kernel: ehci_hcd :00:02.2: devpath 3.4 ep1in
> > 3strikes
> > Jul 27 12:35:00 oenone kernel: usb-storage: Status code -71; transferred
> > 8192/122880
>
> > Is there a
I think we need a new usb.ids maintainer ... I get way too much
email from folk saying Vojtech hasn't responded so would I please
merge the IDs. (Vojtech, if you disagree, please speak up!)
What's required? Be a member of the sourceforge linux-usb project,
so you can update the CVS for http://ww
On Thursday 26 July 2007, [EMAIL PROTECTED] wrote:
>
> 1. SET_LINE_CODING handling in gs_setup_class() copies req->buf to its
> port_line_coding struct but data stage has not been reached yet.
Known bug ... someone ought to submit a patch to fix this.
---
On Wednesday 25 July 2007, Gabriel Maganis wrote:
> Hello,
> Section 9.4 of the USB spec says that devices should respond to
> the standard requests like GET_STATUS even if they haven't been
> configured yet or given an address. How could one do that without a
> pointer to a struct usb_device?
On Wednesday 25 July 2007, Mike Nuss wrote:
> David Brownell wrote:
> >
> > This fix enhances the scope of the existing OHCI_QUIRK_ZFMICRO flag:
> >
> > 1. A watchdog routine periodically scans the OHCI structures to check
> > for orphaned TDs. In these ca
aq quirk and a NEC quirk are now properly compiled out for
non-PCI builds of this driver.
Signed-off-by: Mike Nuss <[EMAIL PROTECTED]>
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/host/ohci-hcd.c | 151
drivers/usb/host/o
On Tuesday 24 July 2007, Zach Brown wrote:
> So, the sad story is that the cancellation support in fs/aio.c is a
> mess. Before we get lost on those details can we talk about simply
> not allowing cancelation of these usbfs2 aio read requests? If they
> guarantee forward progress
Nope ...
On Tuesday 24 July 2007, Aras Vaichas wrote:
> Hello,
>
> does anyone know of a reason why I wouldn't be able to backport the 2.6.22.1
> drivers/usb/gadget/ether.c to work with a 2.6.16 kernel?
Nothing beyond potential minor backport issues; the kernel has
changed a bit since then! But I can't
On Tuesday 24 July 2007, Pavel Roskin wrote:
> > The URB_SHORT_NOT_OK flag is not default. I don't remember exactly why.
>
> I guess you mean that the temporary URB in usb_internal_control_msg()
> should use that flag? That sounds like a good idea, at least on the
> surface.
No it doesn't. It's
On Tuesday 24 July 2007, Sarah Sharp wrote:
> The problem comes when someone calls sys_io_cancel() on a read. If the
> retry function has started before this point, everything is fine.
> However, if sys_io_cancel() runs before the retry function, aio_run_iocb
> will notice the iocb is cancelled an
On Wednesday 20 June 2007, Haavard Skinnemoen wrote:
> This is a driver for the Atmel USBA UDC which can be found integrated
> on AT32AP700x AVR32 processors.
Hmm, scripts/checkpatch.pl reports a few issues (see at the end).
Mostly extraneous brackets; but please fix.
Also, it won't build agains
64bit powerpc
not using an IOMMU define ... and its IOMMU_VMERGE config can always
be overridden on the kernel command line. So this is better, but
still imperfect.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/core/message.c | 14 ++
1 file changed, 10 inser
On Saturday 21 July 2007, Rodolfo Giometti wrote:
> I reworked the driver according to latest suggestions from you.
... except for the most important one, which is to remove the
requirement to change every part of the gadget driver stack to
work around quirks in that particular hardware!!
I hope
d!) double buffering capability.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/usb/gadget/pxa2xx_udc.c | 30 --
1 file changed, 30 deletions(-)
--- pxa.orig/drivers/usb/gadget/pxa2xx_udc.c2007-07-21 10:59:20.0
-0700
+++ pxa/dr
> If we imagine a scenario where host sends a IN/OUT token and device
> consistenly responds with NAK. what does the driver do in that case ?
Whatever it wants. Usually it's correct to keep waiting for the
deice to provide the data.
> Does the driver timeout and abandaon the transaction in such
On Wednesday 18 July 2007, Alan Stern wrote:
> This has led to a rather strange difficulty. As part of dequeuing an
> URB, the HCD will have to verify that the URB is linked into the
> endpoint's urb_list. However the endpoint is accessed via a pointer in
> an array (udev->ep_in[] or udev->ep_out
On Wednesday 18 July 2007, Alan Stern wrote:
> We currently don't have any way to go from the endpoint structure to
> the usb_device structure, so dev is not implicit.
Easy enough to fix if we want. Similarly with the relevant interface
(a one-to-one mapping except for ep0).
--
On Saturday 14 July 2007, Alain Degreffe wrote:
> By the way, I don't well understand if I must try to port the driver in the
> gadget part.
I don't quite understand the question. Are you saying that this
peripheral runs Linux inside, and you want to make its firmware
use standard interfaces?
Si
On Tuesday 17 July 2007, Greg KH wrote:
> On Fri, Jul 13, 2007 at 11:07:24PM +0200, Alain Degreffe wrote:
> > As requested, I have replaced all DMA by kmalloc. The CodingStyle came from
> > Lindent script. The all defines are now in a .h file So I'm ready for
> > your comments... Thanks for you
On Friday 13 July 2007, Kenneth Watson wrote:
> Hi,
>
> I'm having a slight problem using the gadget serial device on an
> AT91SAM9260 board. When trying to connect to a virtual console on
> windows or the ACM driver on linux, it seems I'm receive a control
> message to do a SET_LINE_COD
On Friday 13 July 2007, Sagusti.Robert wrote:
> Hi,
>
> I'm running kernel 2.6.20 on an AT91RM9200 processor. I have
> the gadget serial driver loaded and I am successfully reading
> and writing data in and out the USB port to a windows terminal.
> In my user code, when I open the gadget driver po
On Wednesday 11 July 2007, Christoph wrote:
> So,
>
> since yesterday I'm running this:
>
> drivers/usb/host/ehci-hcd.c:611
> /* complete the unlinking of some qh [4.15.2.3] */
> if (status & STS_IAA) {
> if (ehci->reclaim) {
> COUNT (ehci->stats.reclaim);
>
On Tuesday 10 July 2007, Steve Calfee wrote:
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x81 EP 1 IN
> > bmAttributes1
> > Transfer TypeIsochronous
> >
On Thursday 12 July 2007, S.Selin Jeba Shanthi wrote:
> We are using the AT91SAM9261 board for our application.
> Now our device is act as mass storage but i want that
> device to be act as serial device parallely.
Presumably you mean you want what the USB spec calls
a "composite" device.
>
ts the driver to build again; the
> original version included broken versions of since-removed methods.
Remove that last paragraph; that got fixed already.
> Signed-off-by: David Brownell <[EMAIL PROTECTED]>
> Signed-off-by: Yoshihiro Shimoda <[EMAIL PROTECTED]>
Thanks
On Monday 16 July 2007, Steve Calfee wrote:
> I am working on a project using a generic (non-FPGA) cypress fx2 to
> test host controllers.
>
> The good news is that Linux runs interrupt IN/OUTs at 3x1024 byte
> packets uframe, 24MBytes per second, over as long as I have tested,
> seconds. Verif
On Monday 16 July 2007, Greg KH wrote:
> Can the both of you agree on a patch that solves the needed issues for
> this driver and send it to me? I've seen too many patches on this
> thread to be able to determine what is correct :)
Sure. I'll suggest that Y.Shimodo do that, since he has all of
On Sunday 15 July 2007, Aras Vaichas wrote:
> Hi,
>
> I can't seem to Google any information or precedents on anyone who has
> obtained
> WHQL certification for the Linux RNDIS USB gadget host drivers? I understand
> that the actual binary drivers are provided by Windows anyway. So, can anyone
On Sunday 15 July 2007, Yoshihiro Shimoda wrote:
> David Brownell wrote:
> > On Saturday 14 July 2007, Yoshihiro Shimoda wrote:
> > > > Does the following patch behave, with all the locking test
> > > > options in the kernel debug menu enabled?
> > >
On Sunday 15 July 2007, Dave Jones wrote:
> On Sun, Jul 15, 2007 at 08:07:01PM -0700, David Brownell wrote:
> > On Sunday 15 July 2007, Dave Jones wrote:
> >
> > > Before I dig deeper, are there other side-effects of changing
> > > this default ?
> >
&
On Sunday 15 July 2007, Dave Jones wrote:
> Before I dig deeper, are there other side-effects of changing
> this default ?
Other than spending more power than necessary? :)
I don't think there should be, but Alan's most on top of these
particular issues. The main thing I'd worry about is root
Fix is available:
http://marc.info/?l=linux-usb-devel&m=118443180810424&w=2
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits.
On Friday 13 July 2007, Matthias Kaehlcke wrote:
> The USB gadget serial driver uses a semaphore as mutex. Use the
> mutex API instead of the (binary) semaphore.
>
> Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
ACK (and thanks)
>
> --
>
> diff --git a/drivers/usb/gadget/serial.c b/driv
On Friday 13 July 2007, Yoshihiro Shimoda wrote:
> David Brownell wrote:
> > On Thursday 12 July 2007, Greg KH wrote:
> >> On Thu, Jul 12, 2007 at 05:23:41PM -0700, David Brownell wrote:
> >
> >>> What I'll do is provide a patch to update this to the lates
On Thursday 12 July 2007, Greg Kroah-Hartman wrote:
>
> +#define VERBOSE_DEBUG 0
> +
> +#if VERBOSE_DEBUG
> +#define dev_vdbg dev_dbg
> +#else
> +#define dev_vdbg(dev, fmt, args...)do { } while (0)
> +#endif
> +
*snicker*
Just last week some feedback from Andrew made me think that
thi
On Thursday 12 July 2007, Greg Kroah-Hartman wrote:
>
> From: Yoshihiro Shimoda <[EMAIL PROTECTED]>
>
> I would like to submit Renesas M66592 udc driver.
>
> The M66592 is Renesas USB 2.0 peripheral controller.
> This controller supports USB high-speed.
>
> The driver has been tested Gadget Zero
On Wednesday 09 May 2007, Yoshihiro Shimoda wrote:
> I would like to submit Renesas R8A66597 USB HCD driver.
>
> R8A66597 is Renesas USB 2.0 host and peripheral combined
> controller device originally designed for embedded products.
> As a limitation of this device, it does not support externel
>
list);
> + if (usb_ep_dequeue (dev->in_ep, req))
> + DEBUG (dev, "Failed to dequeue in req %p\n", req);
Shouldn't the ep_disable() calls above have aborted all pending
transfers? So if there are still active requests, that's jus
On Tuesday 10 July 2007, Alan Stern wrote:
> On Tue, 10 Jul 2007, Christoph wrote:
> > > For whatever it's worth, the crash occurred in end_async_unlink because
> > > ehci->reclaim was NULL. This may imply that ehci->reclaim_ready was
> > > set when it shouldn't be. Don't ask me how either of th
On Monday 09 July 2007, Rodolfo Giometti wrote:
> On Sat, Jun 30, 2007 at 06:46:14AM -0700, David Brownell wrote:
> >
> > Has someone actually signed up to develop and maintain such a
> > controller driver? If so, that would be a Fine Thing, but not
> > one I
On Saturday 07 July 2007, Alan Stern wrote:
> On Fri, 6 Jul 2007, David Brownell wrote:
>
> > > The total number of interrupts would depend on the HCD. Right now OHCI
> > > is probably the worst case.
> >
> > Worst??? No, I'd say it's intermediate
On Friday 06 July 2007, Alan Stern wrote:
> On Fri, 6 Jul 2007, David Brownell wrote:
>
> > On Monday 02 July 2007, Alan Cox wrote:
> >
> > > Why not just bite the bullet and change the callback convention. ...
> >
> > On the other hand, that *could* dovet
On Friday 06 July 2007, Mike Nuss wrote:
>
> I'm very interested in the source of the existing quirk though. Do we
> know who wrote that code, and where the insight came from? Did s/he
> discover it experimentally or is there mention of the issue in the ZF
> data book somewhere?
I forget; check t
On Monday 02 July 2007, Alan Stern wrote:
> On Mon, 2 Jul 2007, Oliver Neukum wrote:
>
> > > I don't think so. For one thing, we'd be allocating fewer URBs. For
> > > another, the total number of submissions would be the same; they would
> > > just be spread out in time instead of all at once.
1 - 100 of 5700 matches
Mail list logo
