This is a cut at 7.2 time projects... 1. Insert set/sense mode code into any drivers not done in 7.1 and allow control of: 6/10 byte mode sense sdtr wdtr tcq timeout values used for devices ring buffer control (see below) special tape processing choices if tape at least, per device. This would provide the beginnings of a mechanism to let us address CLDs & QARs that have to do with commodity devices that don't respond right to something. We should attempt to put in some device capabilities structures too, though not necessarily start using them as part of this subproject. 2. Address the lots-o-IDs 'n' LUNs problems of 16 IDs and even of FC/AL scsi3 fiber loops. These are getting attention from outside and we need to get data structures in shape for this at least. Possibly leave the option open while mucking into data structures here to pull CMD buffers into SCDRPs. (Depends on scope of work which Mary's study will make more clear.) We're getting lots of push from storage and clusters for this and addressing it may not be optional. 3. Rationalize error log entries & messages, as Rick suggested. 4. Generate some ring buffer code for problem diagnosis that can be enabled at customer sites to get us better info what goes wrong. 5. (If there's time to schedule it): reorganize either mkdriver or scsicommon so that in the first case special case code is better isolated, or in the second so we start moving the queue manager into specific port drivers. 6. I think Rick's "white paper" about how current drivers work could be a good thing and will help people understand what might have to be altered when writing glue code somewhere else in the system. Glenn