[Wlug] kernel driver vs module

[John Stoffel]

Mike> well, now can someone explain why putting a bin file in
Mike> /lib/firmware i now get the following after a insmod qla2xxx:

Umm... because the card can now initialize itself with the firmware
image and do the initial logins to the SAN?  I dunno, I've never used
them under Linux.  Yet.  :]

Mike> QLogic Fibre Channel HBA Driver
Mike> qla2xxx 0000:00:01.0: Found an ISP2312, irq 9, iobase 0xf8aa6000
Mike> qla2xxx 0000:00:01.0: Configuring PCI space...
Mike> qla2xxx 0000:00:01.0: Configure NVRAM parameters...
Mike> qla2xxx 0000:00:01.0: Verifying loaded RISC code...
Mike> qla2xxx 0000:00:01.0: Waiting for LIP to complete...
Mike> qla2xxx 0000:00:01.0: LOOP UP detected (2 Gbps).
Mike> qla2xxx 0000:00:01.0: Topology - (F_Port), Host Loop address 0xffff
Mike> scsi6 : qla2xxx
Mike> qla2xxx 0000:00:01.0: 
Mike>  QLogic Fibre Channel HBA Driver: 8.01.04-k
Mike>   QLogic QLA2340 - 133MHz PCI-X to 2Gb FC, Single Channel
Mike>   ISP2312: PCI (33 MHz) @ 0000:00:01.0 hdma-, host#=6, fw=3.03.20 IPX

So that's good.

Mike> My redhat servers don't even have a /lib/firmware directory...is
Mike> this a debian thing?

It's a Linux 2.6 thing

Mike> Seems by simply putting a qla2300_fw.bin file in /lib/firmware
Mike> fixed my problem.

Good.  

Mike> I have yet to get actual SAN disks, but at least the card came
Mike> up this time.

Yeah!  I assume that there are some tools under Linux to actually
probe the fabric and see what's out there.  It sounds like you're most
of the way there now, unless of course you run into SAN zoning
issues.  

Mike> Also, what is a KCONFIG entry?

It's part of the Linux kernel source code tree.  When you extract the
kernel source and do:

	make xconfig

it prompts you with entries from the KCONFIG files for each
driver/kernel feature that you need to configure.  I just cut'n'pasted
the info from my local copy of the kernel source before.

Good luck,
John