Re: 1394 Device : Bus reset while installing driver

From: Bill McKenzie (bill.mckenzie_at_nospam.conexant.com)
Date: 11/08/04 

Date: Mon, 8 Nov 2004 13:54:15 -0600

> But, if I unplug the second device and replug it,
> it's Bus Reset routine is called.
> And all cameras working properly.

Are you sure you know which driver instance's bus reset handler is being
called?

I would suspect that the instance of the driver that controls a device just
getting plugged in would not get its bus reset handler called. After all,
that instance of the driver will not have registered a bus reset
notification routine when the bus reset occurs, right? Thus, the driver
should be updating the generation count on initialization as well as in the
bus reset notification routine. Is your driver doing this? 

-- 
Bill McKenzie
Software Engineer - Prism 802.11 Wireless Solutions
Conexant Systems, Inc.
"James" <conqweb@hotmail.com> wrote in message
news:b1aaa61c.0411042322.2d358b22@posting.google.com...
> Hello list!
>
> I am developing device driver for 1394 device and I faced somewhat
> unusual while installing the driver.
>
> My environment is as follows.
>   OS : Windows2000 SP4
>   OHCI 1394 : TI chipset
>   two 1394 camera
>
> First, if I use one camera, there is no problem.
>
> After I connected one camera(first) and install driver manual,
> I unplug the device
> and I connect another camera(second) and install driver manually.
> Now, I reconnect the first camera again.
> Then, the Bus Reset routine of the driver of the second device
> doesn't called.
> So, the second driver is not controlled properly, because the
> generation count is not correct.
>
> But, if I unplug the second device and replug it,
> it's Bus Reset routine is called.
> And all cameras working properly.
>
> I don't know why this situation is occurred.
>
> I think the sequence of the driver installation is same
> when I install the driver manually and when I replug.
>
> I tried to call REQUEST_BUS_RESET when the SRB_INITIALIZATION_COMPLETE
> is called, but the result is same.
>
> What am I supposed to do?
> Any suggestions will be appreciated.
>
> - James.

Relevant Pages

  • Re: 1394 Device : Bus reset while installing driver
    ... >> it's Bus Reset routine is called. ... I checked the device extension and camera model name in the driver, ... I use same driver for the two camera. ...
    (microsoft.public.development.device.drivers)
  • Re: [PATCH 0/3] New firewire stack
    ... My main point about ohci1394 (the old stacks PCI driver) is, ... The big problems in the ohci1394 drivers is the irq_handler, bus reset ... reset, so there is no need to complicate the core stack with this extra state, ... interfaces have slightly disjoint feature sets and can't really be phased out. ...
    (Linux-Kernel)
  • Re: [PATCH 0/3] New firewire stack
    ... My main point about ohci1394 (the old stacks PCI driver) is, ... The big problems in the ohci1394 drivers is the irq_handler, bus reset ... reset, so there is no need to complicate the core stack with this extra state, ... interfaces have slightly disjoint feature sets and can't really be phased out. ...
    (Linux-Kernel)
  • 1394 devices: Bus reset while processing SRB_INITIALIZE_DEVICE !
    ... a IEEE1394 device on device initialization. ... The driver gets an SRB_INITIALIZE_DEVICE request. ... not use this generation count unless the next Bus Reset Notification is ...
    (microsoft.public.development.device.drivers)
Loading