- From: Calin A. Culianu <calin_at_ajvar.org>
- Date: Thu, 3 Jul 2003 10:12:06 -0400 (EDT)
On Wed, 2 Jul 2003, Frank Mori Hess wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tuesday 01 July 2003 01:11 pm, Calin A. Culianu wrote: > > I have always wanted to be able to treat more than one comedi card as a > > single card from the application's point of view. It would be nice, at > > least at first with comedi instructions only, to write a driver that can > > act as a unifying glue layer that can treat more than one comedi card as > > a single card on the machine. I would imagine if this driver only > > supported read and write instructions it wouldn't even be that > > complex... is that so? > > > > Does anyone else want this? I will perhaps do it anyway for my own Evil > > Purposes[TM], but if anyone has any ideas/input on this it may help me > > so that I don't make obvious mistakes, etc... > > > > -Calin > > > > Well, in the long run (comedi 2.0, ETA: the year 2010) I would guess that > much of the distinction made by the current API between two subdevices on > the same board, and two subdevices on different boards will disappear. Hehe, ok.. but in the meantime I started coding a bonding driver. I hope I will finish it as it isn't too tricky for the bare bones approach. It will only support instructions and will be pretty minimalistic. The only issue I have is ranges. If the two boards have different range sets one has to code his/her user app such that acquisition using instructions is very careful about range settings on a per-channel basis... -Calin
Received on 2003-07-03Z13:12:06