File descriptors and connections in AADL

[Carlos]

This is more like a general S/W architecture connector question. I would like to model the concept of a device driver communicating with an application software via file descriptors. Our systems are based on ARINC 653 partitions, and modeling queuing ports and sampling ports has a nice mapping in AADL, but the topic of file descriptors is new for me and we have lots of drivers that use this means of communication. 

How would you do this in AADL?

[Hugues Jérôme]

Hi,

Why do you need to model a file descriptor for that?

Check this example. You'll see I have a device driver that uses a dedicated pattern. Because the logical connection is bound to a bus, and the device is also bound to this bus, we know that the port will use the device to communicate. The pattern I used for code generation takes care of sending the message through this driver.

On Oct 17, 2024, at 11:32 AM, 'Carlos' via OSATE <os...@googlegroups.com> wrote:

This is more like a general S/W architecture connector question. I would like to model the concept of a device driver communicating with an application software via file descriptors. Our systems are based on ARINC 653 partitions, and modeling queuing ports and sampling ports has a nice mapping in AADL, but the topic of file descriptors is new for me and we have lots of drivers that use this means of communication. 

How would you do this in AADL?

--
You received this message because you are subscribed to the Google Groups "OSATE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osate+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osate/65d40d25-7aa3-4e5b-a0e1-4da7edfb8fc7n%40googlegroups.com.