Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1337129
| From | Johannes Thumshirn <jthumshirn@suse.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] [SCSI] dpt_i2o: use proper pci driver |
| Date | 2016-02-18 09:20 +0100 |
| Message-ID | <r3rYC-2K0-21@gated-at.bofh.it> (permalink) |
| References | <r39oZ-6nX-9@gated-at.bofh.it> <r3bh8-7Ch-17@gated-at.bofh.it> <r3cGe-8sZ-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Feb 17, 2016 at 09:20:03PM +0530, Sudip Mukherjee wrote: > On Wednesday 17 February 2016 07:57 PM, One Thousand Gnomes wrote: > >On Wed, 17 Feb 2016 17:50:14 +0530 > >Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote: > > > >>This is a pci device but was not done in the usual way a pci driver is > >>done. Convert the driver into a proper pci driver. > > > >This looks completely wrong. Please read the I2O 1.5 specification > >document before playing with that code. You can't simply convert it to a > >standard PCI driver as all the IOPs are supposed to be detected and then > >the correct initialization sequence executed across the set of IOPs. IOPs > >are allowed to talk to one another and the system table binds it all > >together. > > Yes, thanks for letting me know about the spec. It is saying > "The host locates each IOP, adds it > to the system configuration table, and initializes the IOP’s outbound > message queue. The host then > provides each IOP with a list of all IOPs and the physical location of their > inbound message queue." > > > > >If you do hot plug then you need to follow the specification and do > >all the extra notifications. Unless you've got multiple FC909/FC920 > >fibechannel cards or similar to test with I would just leave this well > >alone. > > point noted. > > >Your original simple patch is *MUCH* safer in this specific case. > > The original patch is already having NACK from Johannes. So i better leave > this code here. Nah, wasn't a hard NACK. I'm OK with the original code, just was reluctant to the #ifdefs. I agree I didn't know the I2O specifics and thought a "normal" PCI driver fitting nicely in the driver model would be the way to go. Please resend your v1 with my Reviewed-by > > regards > sudip -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v2] [SCSI] dpt_i2o: use proper pci driver Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-02-17 13:30 +0100
Re: [PATCH v2] [SCSI] dpt_i2o: use proper pci driver One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> - 2016-02-17 15:30 +0100
Re: [PATCH v2] [SCSI] dpt_i2o: use proper pci driver Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-02-17 17:00 +0100
Re: [PATCH v2] [SCSI] dpt_i2o: use proper pci driver Johannes Thumshirn <jthumshirn@suse.de> - 2016-02-18 09:20 +0100
csiph-web