rtnet-developers

[RTnet-developers] RTDM devices class and subclass

[Marcelo C. <mjc...@cr...>]

Hi Jan,


I've continuing the development of the serial device driver port to
Real-Time. I've seen both Rtai_serial driver and the rtdm api and now i
think i'm starting to make some progress... :)

Now i stumbled on detail that isn't referred on the RTDM api
specification: There are some macros defining the Class and Subclass of
a RTDM driver. These regulations are defined by the rtdm team, right? 
As i'm developing a serial device, my class and subclass should be
RTDM_CLASS_SERIAL and RTDM_SUBCLASS_MOXA (for a Moxa RS-422 driver).


Thanks for the help





DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

Re: [RTnet-developers] RTDM devices class and subclass

[Jan K. <jan...@we...>]

Marcelo Coelho wrote:
> Hi Jan,
>=20

Hmm, I wonder what made this message pop up on rtnet-devel. Nevermind. :)=


>=20
> I've continuing the development of the serial device driver port to
> Real-Time. I've seen both Rtai_serial driver and the rtdm api and now i=

> think i'm starting to make some progress... :)
>=20
> Now i stumbled on detail that isn't referred on the RTDM api
> specification: There are some macros defining the Class and Subclass of=

> a RTDM driver. These regulations are defined by the rtdm team, right?=20

Yes, that's a rather loooong process. It involves issuing a formal
request for the number, a first review and rejection, a submission of a
revised request, a public hearing, several meetings of the steering
committee (at the expense of the requester, of course!), and then,
maybe, the granting.

> As i'm developing a serial device, my class and subclass should be
> RTDM_CLASS_SERIAL and RTDM_SUBCLASS_MOXA (for a Moxa RS-422 driver).
>=20

Ok, I take this question as step 1 and continue with step 2: The Moxa is
a specific chip with different features than a normal 16550A-compatible
UART? Will you implement less / more IOCTLs for this driver or some
other service differently? My point is that defining a subclass is only
required when the programming model differs.

Jan


PS: Submitting your driver for inclusion in RTAI and/or Xenomai may help
to accelerate the subclass reservation. ;)

Re: [RTnet-developers] RTDM devices class and subclass

[Marcelo C. <mjc...@cr...>]

Hi again,


> Hmm, I wonder what made this message pop up on rtnet-devel. Nevermind. :)

Are you trying to say i'm not a developer?? :)


> PS: Submitting your driver for inclusion in RTAI and/or Xenomai may help
> to accelerate the subclass reservation. ;)

Don't worry that when i have something working, that could be usefull
for other users, i'll send it over to you!




DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

Re: [RTnet-developers] RTDM devices class and subclass

[Jan K. <jan...@we...>]

Marcelo Coelho wrote:
> Hi again,
>=20
>=20
>> Hmm, I wonder what made this message pop up on rtnet-devel. Nevermind.=
 :)
>=20
> Are you trying to say i'm not a developer?? :)

Definitely not. I was referring to the "rtnet" part - RTnet is only one
RTDM user.

>=20
>=20
>> PS: Submitting your driver for inclusion in RTAI and/or Xenomai may he=
lp
>> to accelerate the subclass reservation. ;)
>=20
> Don't worry that when i have something working, that could be usefull
> for other users, i'll send it over to you!
>=20

Looking forward!

Jan

Re: [RTnet-developers] RTDM devices class and subclass

[Marcelo C. <mjc...@cr...>]

> Definitely not. I was referring to the "rtnet" part - RTnet is only one
> RTDM user.

Yes, but you're the only developer i can contact, and this is the less
active mailling list...


Now about the driver, i searched in rtdm for something that could be
related to the TTY associated structs and functions. Neither in the
serial device nor in rtdm api, these functions are used. Is it possible
that you (the RTDM team) change that and start giving support for those
kind of devices in the same way the kernel does?

Thanks





DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

Re: [RTnet-developers] RTDM devices class and subclass

[Jan K. <jan...@we...>]

Marcelo Coelho wrote:
>> Definitely not. I was referring to the "rtnet" part - RTnet is only on=
e
>> RTDM user.
>=20
> Yes, but you're the only developer i can contact, and this is the less
> active mailling list...
>=20

I would prefer to see such a generic discussion on a generic mailing
list, like xenomai-core or rtai. There might be more people hanging
around, willing to contribute comments and ideas.

>=20
> Now about the driver, i searched in rtdm for something that could be
> related to the TTY associated structs and functions. Neither in the
> serial device nor in rtdm api, these functions are used. Is it possible=

> that you (the RTDM team) change that and start giving support for those=

> kind of devices in the same way the kernel does?

If this would be only about wrapping a *few* IOCTLs, I see no big
problems (except that the driver code may increase). What interfaces do
you have in mind?

Well, the termios interface as-is appeared to me as not well suited for
typical serial usage scenarios in hard-RT applications. Specifically,
the RTDM profile introduced an event concept and per-character
timestamping. As there were several extensions required anyway, I
consolidated the whole interface, making it more regular and targeted
with respect to UART devices - that's at least my feeling about it.

If your driver reveals some need to move common code into a high-level
serial layer anyway, adding a compat layer for certain IOCTLs the driver
does not need to know about might be an options. But note that, even
then, using tc*() functions will not work as they map to the Linux
ioctl() invocation, not the RTDM one.

Jan