drivers/scsi/imm.h
Source file repositories/reference/linux-study-clean/drivers/scsi/imm.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/imm.h- Extension
.h- Size
- 5133 bytes
- Lines
- 146
- Domain
- Driver Families
- Bucket
- drivers/scsi
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/stddef.hlinux/module.hlinux/kernel.hlinux/ioport.hlinux/delay.hlinux/proc_fs.hlinux/stat.hlinux/blkdev.hlinux/sched.hlinux/interrupt.hasm/io.hscsi/scsi_host.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _IMM_H
#define _IMM_H
#define IMM_VERSION "2.05 (for Linux 2.4.0)"
/*
* 10 Apr 1998 (Good Friday) - Received EN144302 by email from Iomega.
* Scarry thing is the level of support from one of their managers.
* The onus is now on us (the developers) to shut up and start coding.
* 11Apr98 [ 0.10 ]
*
* --- SNIP ---
*
* It manages to find the drive which is a good start. Writing data during
* data phase is known to be broken (due to requirements of two byte writes).
* Removing "Phase" debug messages.
*
* PS: Took four hours of coding after I bought a drive.
* ANZAC Day (Aus "War Veterans Holiday") 25Apr98 [ 0.14 ]
*
* Ten minutes later after a few fixes.... (LITERALLY!!!)
* Have mounted disk, copied file, dismounted disk, remount disk, diff file
* ----- It actually works!!! -----
* 25Apr98 [ 0.15 ]
*
* Twenty minutes of mucking around, rearanged the IEEE negotiate mechanism.
* Now have byte mode working (only EPP and ECP to go now... :=)
* 26Apr98 [ 0.16 ]
*
* Thirty minutes of further coding results in EPP working on my machine.
* 27Apr98 [ 0.17 ]
*
* Due to work commitments and inability to get a "true" ECP mode functioning
* I have decided to code the parport support into imm.
* 09Jun98 [ 0.18 ]
*
* Driver is now out of beta testing.
* Support for parport has been added.
* Now distributed with the ppa driver.
* 12Jun98 [ 2.00 ]
*
* Err.. It appears that imm-2.00 was broken....
* 18Jun98 [ 2.01 ]
*
* Patch applied to sync this against the Linux 2.1.x kernel code
* Included qboot_zip.sh
* 21Jun98 [ 2.02 ]
*
* Other clean ups include the follow changes:
* CONFIG_SCSI_PPA_HAVE_PEDANTIC => CONFIG_SCSI_IZIP_EPP16
* added CONFIG_SCSI_IZIP_SLOW_CTR option
* [2.03]
* Fix kernel panic on scsi timeout. 20Aug00 [2.04]
*
* Avoid io_request_lock problems.
* John Cavan <johncavan@home.com> 16Nov00 [2.05]
*/
/* ------ END OF USER CONFIGURABLE PARAMETERS ----- */
#include <linux/stddef.h>
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/ioport.h>
#include <linux/delay.h>
#include <linux/proc_fs.h>
#include <linux/stat.h>
#include <linux/blkdev.h>
#include <linux/sched.h>
#include <linux/interrupt.h>
#include <asm/io.h>
#include <scsi/scsi_host.h>
/* batteries not included :-) */
/*
* modes in which the driver can operate
*/
#define IMM_AUTODETECT 0 /* Autodetect mode */
#define IMM_NIBBLE 1 /* work in standard 4 bit mode */
#define IMM_PS2 2 /* PS/2 byte mode */
#define IMM_EPP_8 3 /* EPP mode, 8 bit */
#define IMM_EPP_16 4 /* EPP mode, 16 bit */
#define IMM_EPP_32 5 /* EPP mode, 32 bit */
#define IMM_UNKNOWN 6 /* Just in case... */
static char *IMM_MODE_STRING[] =
{
[IMM_AUTODETECT] = "Autodetect",
[IMM_NIBBLE] = "SPP",
[IMM_PS2] = "PS/2",
Annotation
- Immediate include surface: `linux/stddef.h`, `linux/module.h`, `linux/kernel.h`, `linux/ioport.h`, `linux/delay.h`, `linux/proc_fs.h`, `linux/stat.h`, `linux/blkdev.h`.
- Atlas domain: Driver Families / drivers/scsi.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.