Hello Michael,
 In a message dated 15 Aug 95 you wrote to Alain Chofardet :

 MLH> On Aug 15,  1:03pm, Alain Chofardet wrote:
 >> 	/* preserve our ID for now */
 >> 	GET_SBIC_myid (regs, my_id);

 MLH>  I would like to see what my_id contains at this point, to see how the
 MLH> GURU ROM set it up.

Well, let's try to guess... Hmmm... value is 6 !!

 >> 	else if (dev->sc_clkfreq < 160)
 >> 		my_id |= SBIC_ID_FS_12_15;
 MLH> ...
 >> 	my_id |= SBIC_ID_EAF /*| SBIC_ID_EHP*/ ;
 >> my_id = 7;
 >> my_id |= SBIC_ID_FS_12_15;
 >> 	SET_SBIC_myid(regs, my_id);
 MLH> .
 >> gtsc0 : target 6 now synchronous, period=388ns, offset=12
 >> 
 >> The only displayed device is target 6 as being a Quantum.
 MLH>  That's right !!! Notice that the period has changed.
 MLH>  It used to be 256 in my previous tries.

 MLH>  The period is incorrect because you did not change dev->sc_clkfreq.
 MLH> The period is computed based on the clock frequency specified in
 MLH> sc_clkfreq and what the SBIC_ID_FS value is.  By setting
 MLH> sbic_clock_override to 10 x the clock frequency, the driver will
 MLH> compute the period correctly, and set the SBIC_ID_FS value correctly.

Do I have to open the machine to see the clock frequency ? I've tried to have a look at docs, but without success...


Alain Chofardet
                Another brick in the wall

Fidonet  : 2:320/104.34
Amiganet : 39:180/1.34
Internet : Alain.Chofardet@ramses.fdn.org (<10ko)
           Alain.Chofardet@ramses.telesys-innov.fr (>10ko)