HI,
I use the following code to enable portsc of uhci
under DOS,but the port enable failed (set the bit but
it doesn`t take effect) , I don't know why . Is there
anyone know what's the problem ? Thanks :)
static void uhci_reset_port(unsigned int port)
{
unsigned short status;
On Fri, Mar 11, 2005 at 11:03:17AM -0500, Alan Stern wrote:
> Greg:
>
> When the PCI subsystem discovers a device, it calls pci_setup_device to
> initialize various things. It doesn't call pci_disable_device to stop the
> device from doing DMA, or do the equivalent (whatever that might be) to
On Fri, Mar 11, 2005 at 11:12:57AM -0700, Grant Grundler wrote:
> o platform devices (e.g. bridges) that don't have PCI drivers to re-enable
> them later. "transperent" Bridges are the only example I can come up with
> now but expect more to come out of the woodwork as this gets widely
> test
Hi Jayaprakash,
In linux system, USB devices are identified by major number 180, so you
need to create device node with major no 180 and minor no (mknod usbdrv
180 0)
While registering device driver you don't have to give major as such,
you need to mention only minor number. All these informatio
(Restoring email headers. Please always use reply-to-all)
Robert Hancock <[EMAIL PROTECTED]> wrote:
>
> Felix von Leitner wrote:
> > My new nForce 4 mainboard has 10 or so USB 2.0 outlets. In Windows,
> > they all work. In Linux, two of them work. Putting my USB stick or
> > anything else in
On Fri, 11 Mar 2005, Andrew Morton wrote:
> Felix von Leitner <[EMAIL PROTECTED]> wrote:
> >
> > My new nForce 4 mainboard has 10 or so USB 2.0 outlets. In Windows,
> > they all work. In Linux, two of them work. Putting my USB stick or
> > anything else in one of the others produces nothing in
Hi,
> Calls to dbg() or warn() or info() would get replaced with
> calls to dev_dbg() or dev_warn() or dev_info() etc ... adding
> a newline at the end of the string), passing the struct device
> from the usb interface as the first parameter.
I've been looking at the code in hid-core.c to see how
Felix von Leitner <[EMAIL PROTECTED]> wrote:
>
> My new nForce 4 mainboard has 10 or so USB 2.0 outlets. In Windows,
> they all work. In Linux, two of them work. Putting my USB stick or
> anything else in one of the others produces nothing in Linux.
> Apparently no IRQ getting through or somethi
All of the changes requested are included in the attached diff.
Signed-off-by: Nick Sillik <[EMAIL PROTECTED]>
Original message
>Date: Fri, 11 Mar 2005 16:11:06 -0500
>From: Dmitry Torokhov <[EMAIL PROTECTED]>
>Subject: Re: [linux-usb-devel] [PATCH] To add usabillity for
the Maxtor On
On Fri, Mar 04, 2005 at 10:58:33AM +0100, Luca Risolia wrote:
> Scrive Adrian Bunk <[EMAIL PROTECTED]>:
>
> > On Tue, Mar 01, 2005 at 06:46:03PM +0100, Luca Risolia wrote:
> > > Scrive Adrian Bunk <[EMAIL PROTECTED]>:
>...
> > > > - there's no w9968cf-vpp module in the kernel sources
> > >
> >
On Friday 11 March 2005 2:05 pm, Alan Stern wrote:
> On Fri, 11 Mar 2005, David Brownell wrote:
>
> > > Which function should I schedule in the irq handler instead
> > > of (or in addition to) isp116x_hub_resume() to trigger the
> > > same sequence of resuming events like via /sys interface? Or
On Fri, 11 Mar 2005, David Brownell wrote:
> > Which function should I schedule in the irq handler instead
> > of (or in addition to) isp116x_hub_resume() to trigger the
> > same sequence of resuming events like via /sys interface? Or
> > should remote wakeup handled some other way?
>
> See wh
Am Freitag, 11. März 2005 21:50 schrieb Jayaprakash Shanmugam:
> I am new to USB world. I have a basic doubt. I wrote the USB
> driver by going through some tutorials. I compiled it and inmod it
> without any problems. Now, If I want to use my driver, I need a major
> number. There I got st
On Fri, 11 Mar 2005 15:20:30 -0500 (EST), Alan Stern
<[EMAIL PROTECTED]> wrote:
> On Fri, 11 Mar 2005, Nick Sillik wrote:
>
> > I'm resubmitting the patch with the wrap removed and the list in the
> > onetouch
> > struct. I also changed usb_unlink_urb usb_kill_urb.
>
> > +int onetouch_release_in
Hi All,
I am new to USB world. I have a basic doubt. I wrote the USB
driver by going through some tutorials. I compiled it and inmod it
without any problems. Now, If I want to use my driver, I need a major
number. There I got stuck up. I didnt have any major number used in
my driver. So,
On Fri, 11 Mar 2005, Nick Sillik wrote:
> I'm resubmitting the patch with the wrap removed and the list in the onetouch
> struct. I also changed usb_unlink_urb usb_kill_urb.
> +int onetouch_release_input(struct us_data *ss)
<...>
> + usb_unlink_urb(onetouch->irq);
Should be usb_kill_
On Friday 11 March 2005 11:17 am, Olav Kongas wrote:
> Hi,
>
> Recent days I have been working on suspend/resume
> functionality of the isp116x-hcd (on 2.6.11-mm2). There are
> things I still don't understand.
>
> Basic suspend/resume of root hub (RH) from the system seems
> to be working. As
On Friday 11 March 2005 1:49 am, Andrew Morton wrote:
>
>
> http://bugme.osdl.org/show_bug.cgi?id=4325
> ...
>
> HID: (in non conflicting port)
> usb 3-1.1: new low speed USB device using ohci_hcd and address 3
> usb 3-1.2: new low speed USB device using ohci_hcd and address 4
> input: USB HID v
I'm resubmitting the patch with the wrap removed and the list in the onetouch
struct. I also changed usb_unlink_urb usb_kill_urb.
Since I don't have my drive I'm not 100% sure on the code. Especially the
changed list stuff. If one of you could give it a very quick looking over and
tell me if I hav
Hi,
Recent days I have been working on suspend/resume
functionality of the isp116x-hcd (on 2.6.11-mm2). There are
things I still don't understand.
Basic suspend/resume of root hub (RH) from the system seems
to be working. As a response to echo -n 3 >
/sys/bus/usb/devices/usb1/power/state the p
On Fri, Mar 11, 2005 at 04:19:08PM +, Matthew Wilcox wrote:
> > During a normal boot most devices are left in reasonably quiescent and
> > safe condition when the BIOS passes control to the OS. But sometimes a
> > few of them aren't; that's why we need to have the USB early-handoff quirk
> > c
On Fri, Mar 11, 2005 at 11:03:17AM -0500, Alan Stern wrote:
> When the PCI subsystem discovers a device, it calls pci_setup_device to
> initialize various things. It doesn't call pci_disable_device to stop the
> device from doing DMA, or do the equivalent (whatever that might be) to
> stop the
On Thu, 10 Mar 2005, Nick Sillik wrote:
> +struct usb_onetouch {
> + char name[128];
> + char phys[64];
> + struct input_dev dev; /* input device interface */
> + struct usb_device *udev;/* usb device */
> +
> + struct urb *irq;/* urb for inter
Greg:
When the PCI subsystem discovers a device, it calls pci_setup_device to
initialize various things. It doesn't call pci_disable_device to stop the
device from doing DMA, or do the equivalent (whatever that might be) to
stop the device from generating IRQs. Unless I'm mistaken, which is
Begin forwarded message:
Date: Fri, 11 Mar 2005 01:12:48 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 4325] New: freeze under load - system partialy
continues working but no response on keyboard/mouse
http://bugme.osdl.org/show_bug.cgi?id=4325
Summ
25 matches
Mail list logo
