> > And for Linux: Due to the lack of information about how FlexNet in the low > > level stage really works How the "low level stage" works comes pretty clear if you take a look at the device driver development kit. It fact it is not much different from what we are doing now. It is *very* important to implement it in that way to achieve a reasonable channel access behaviour. Another advantage flexnet has over us, is that it vitally has the CPU for its own. We are pretty close to that in kernel mode. However, we have at least two *really* big advantages over flexnet: a reasonable memory buffer concept and very powerful subsystems for card configuration (PCI) and low-level port access. We also have very nice debugging tools (kdb et al.). Writing a flexnet/16 device driver is a pain in the *ss. -- Jens
- Re: API and driver interface Tomi Manninen
- Re: API and driver interface Joerg Reuter DL1BKE
- Re: API and driver interface Tomi Manninen
- Re: API and driver interface Gerd
- Re: API and driver interface Joerg Reuter DL1BKE
- Re: API and driver interface Gerd
- Re: API and driver interface Ing. Jose A. Amador
- Re: API and driver interface Gerd
- Re: API and driver interface Ing. Jose A. Amador
- Re: API and driver interface Rob Compton
- Re: API and driver interface Jens David
- Re: API and driver interface Gerd
- Re: API and driver interface Joerg Reuter
- Re: API and driver interface Ing. Jose A. Amador
- Re: API and driver interface Joerg Reuter DL1BKE
- Re: API and driver interface Jens David
- Re: DG2FEF-AX.25 Patch for 2.2.14 available Terry Dawson
- Re: DG2FEF-AX.25 Patch for 2.2.14 available Thorsten Kranzkowski
- Re: DG2FEF-AX.25 Patch for 2.2.14 available Terry Dawson
- Re: DG2FEF-AX.25 Patch for 2.2.14 available Gerd
- Re: DG2FEF-AX.25 Patch for 2.2.14 available Terry Dawson
