aic7xxx Rev 6.3.5 problems/questions.

[Justin T. Gibbs]

> 1) DV failed to configure device. see log [1].
>   I know gibbs at scsiguy.com's response in the past has been, "File the bug
> report with Promise", as I do not know the scsi protocol can you give me
> something better to say to them than:
> 'The Linux aic7xxx Rev 6.3.5 driver reports that your device does not send
> back the correct response to a DV configuration request.'?  As communication
> seems slow with Promise, even using email, I would like to send them something
> their engineers *SHOULD* understand with out asking me any more questions.

The latest driver should, assuming you boot it in verbose mode, say
something like:

"Echo Buffer unavailable.  Performing basic DV."

This is because the Promise controllers do not provide an echo buffer.
In the past, the driver would just fail DV and complain about the
broken device.  Since the promise controllers were all developed long
after having an echo buffer was a requirement, they should support it.
I believe that their latest firmware does.

> 2) module does not accept more than one Command Line Option.
> README.aic7xxx section '3. Command Line Options' indicates that I should be
> able to put multiple options on the line that modprobe passes to insmod,
> i.e., line containing 'options aic7xxx aic7xxx=[command[,command...]]',
> however if I put options aic7xxx aic7xxx=verbose,global_tag_depth:1
> in modules.conf or do the insmod as below I get the same response of 'too many
> values for aic7xxx'.  is there something specific I am doing wrong here
> that you know of?

Try quoting the options so that your shell doesn't do funny things
with the commas.  The same may apply to /etc/modules.conf depending
on which distribution you are using and how they have implemented
their mkintrd script.  For this reason, I often use a period
instead of a comma to delineate options.

> 3) how do you build the rpm's for the rpm releases you make, or do you
> plan to start making releases for fedora core 1 (linux-2.4.22-1.*.nptl)?

The build environment is quite complex and does not use a source rpm spec
file.  It is not something that we intend to distribute.

As for Fedora core, since it is not officially supported by RedHat,
and changes even more rapidly than the RedHat distributions, it is
not something that we can support.

--
Justin