SANA-II files for development in SAS/C?

[mousehouse]

After installing SAS/C 6.58 from my still functional original floppies I went looking for the SANA-2 files needed for writing some C code... On my installed system it is not present (thus not included in SAS/C), I found the following using Google,

http://amigadev.elowar.com/read/ADCD_2.1/AmigaMail_Vol2_guide/node01DE.html

This seems to be an online version of the Amiga Developer CD 2.1. Can somebody comment if these are the latest header files available for SANA-II development?

[Matt_H]

These are more up to date.

[mousehouse]

Thanks! On Aminet of all places ;-)

Does anybody know if the sources for sanamon or similar have ever been released? I'm looking for some understandable sample code...

[ncafferkey]

I don't know about Sanamon, but the sources for SanaUtil are available. The are sources for some drivers available too if you're interested in implementing a SANA-II device.

BTW, those includes on Aminet don't include the additions to the standard made in subsequent years.

[Matt_H]

I don't know about Sanamon, but the sources for SanaUtil are available. The are sources for some drivers available too if you're interested in implementing a SANA-II device.

BTW, those includes on Aminet don't include the additions to the standard made in subsequent years.

Oh, that's right, I think the package I linked was SANA-II R2. I remember some documentation about a semi-official SANA-II R3 and maybe R4. Did Olaf Barthel work on those? Or was it someone else?

[Golem!dk]

Multicast address range extensions to SANA-II Rev 3, Extending the SANA-II network driver specification SANA-II R4 & Hook-based callback function extensions for SANA-II (SANA-II R5).

[mousehouse]

Thanks for those excellent resources.

One thing that puzzles me (because of a lack of understanding - I have never done anything with the networking- or kernel part of AmigaOS and as far as programming goes, I am only an average C programmer with dated skills) is the functionality provided by the SANA layer.

Am I correct in understanding that SANA provides an abstraction layer between the hardware (NICs or software interfaces) and possible software that use it?

If so, I need to be able to address SANA supplied functions and procedures to make the abstracted hardware do as I wish ;-) I've actually read the complete spec but the wisdom doesn't come to me yet...

[Piru]

SANA2 drivers are used by the TCP/IP stack to send and receive packets. Very few other applications use SANA2 directly (Envoy comes to mind).

[billt]

Multicast address range extensions to SANA-II Rev 3, Extending the SANA-II network driver specification SANA-II R4 & Hook-based callback function extensions for SANA-II (SANA-II R5).

Did these go past proposal and discussion to be ratified into the spec?

[mousehouse]

SANA2 drivers are used by the TCP/IP stack to send and receive packets. Very few other applications use SANA2 directly (Envoy comes to mind).

Yes, this would be the exact thing I'm trying to achieve.

Thus, in order to be able to address the networking hardware in my Amiga (it being anything supported by a SANA compliant driver) I need to talk "SANA"...

Is SANA included with Kickstart 3.1? In the documentation I only see references to header files, structs and functions. What library provides these functions? Or am I completely missing the mark here?

[Golem!dk]

Did these go past proposal and discussion to be ratified into the spec?

Don't know how that would work these days, R3 was included on H&P's Developer CD 2.1, but I'm not sure who was involved with that besides Heinz Wrobel. Seems the few people implementing stacks and drivers have extended the spec as needed.

[Piru]

Yes, this would be the exact thing I'm trying to achieve.

What exactly are you trying to achieve?

Is SANA included with Kickstart 3.1?

No. SANA2 are device drivers located in DEVS:Networks. Kickstart is ROM only. Workbench 3.1 doesn't include any network drivers either. Typically these drivers were provided by the HW manufacturer. Later on drivers were provided for common PCMCIA network cards, for instance.

In the documentation I only see references to header files, structs and functions. What library provides these functions? Or am I completely missing the mark here?

No library provides any functions.  The device drivers do provide the S2 commands.

[Trev]

Did these go past proposal and discussion to be ratified into the spec?

That implies some sort of ratification process. I think they can be considered official as of OS4; however, any device driver writer is free to implement newer features.

[olsen]

Did these go past proposal and discussion to be ratified into the spec?

They represent the current state of the technology. It's not as if we had a board of officers charged with reviewing and casting proposals into a common specification. With SANA-II it's more like a cheap version of the RFC approval process: you work on your proposal, talk it over with your peers, and then you publish it. The documentation should be good enough to write code for it, and to leave no obvious questions unanswered. Better still, publish example code for your proposal.

[mousehouse]

What exactly are you tring to achieve?

No. SANA2 are device drivers located in DEVS:Networks. Kickstart is ROM only. Workbench 3.1 doesn't include any network drivers either. Typically these drivers were provided by the HW manufacturer. Later on drivers were provided for common PCMCIA network cards, for instance.

No library provides any functions.  The device drivers do provide the S2 commands.

I would like to write a software stack that interfaces with my SANA compliant network card (A2065, Ariadne2, USB thingie of Deneb).

If I understand correctly now, the device driver for the NIC "extends" the system with SANA compliant functions - correct? How would this work with multiple NICs present in the system? Does the device spec include some sort of unit numbering, where each unit corresponds to a unique set of SANA functions?

If SANA functions are provided by the network card device driver (eg. a2065.device or ariadne_ii.device) then the implementation of that device driver is according to SANA spec version - is there some way to check to which spec the driver conforms?