Re: [Uisp-dev] The many cables

[Joakim Arfvidsson]

Generally a decent idea.

While not into all kinds of cables, I have some comments:

- Most of the parallell cables would fit under this. The only 
parameters for these cables are pins and inverts.

- The "intelligent" cables are probably hard to describe in this way. I 
don't know if there are any more besides AVR910 and STK500, but a lot 
of information would have to be described in the config file. It would 
be very complex just do devise a file format to store all needed info.

Joakim






On 2004-10-20, at 18.50, Margarita Manterola wrote:

> Hi!
>
> I've been giving some thought to the many cables problem.
>
> Could we have the description of each cable stored in a file, and read
> the values into variables from that file, according to the type of
> cable selected?
>
> The file would have to store the usual pins, if they are inverted or
> not, and if there's any special behaviour going on.
>
> It's quite easy to know if a pin is control, status or data.  We don't
> need to have the long case that does always the same, just a case for
> the type of pin... For example:
>
> void
> TDAPA::OutReset(int b)
> {
> (...)
>   switch (rst_type)
>   {
>   case CONTROL:
>     if (b) par_ctrl |= rst_pin; else par_ctrl &= ~rst_pin;
>     ParportWriteCtrl();
>     break;
>
>   case DATA:
>     if (b) par_data |= rst_pin; else par_data &= ~rst_pin;
>     ParportWriteData();
>     break;
>   }
> (...)
> }
>
> This is just for parallel, something like that could be done for 
> serial as well.
>
> What do you think?
>
> --
> Besos,
> Marga
>
>
> _______________________________________________
> Uisp-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/uisp-dev

smime.p7s
Description: S/MIME cryptographic signature