From: Ilija Kocho <ilijak@siva.com.mk>
To: ecos-devel@ecos.sourceware.org
Subject: Re: tty.cdl
Date: Sun, 27 Mar 2011 19:55:00 -0000 [thread overview]
Message-ID: <4D8F963A.6050501@siva.com.mk> (raw)
In-Reply-To: <alpine.DEB.2.00.1103272236150.16726@sg-laptop>
On 27.03.2011 21:39, Sergei Gavrikov wrote:
> On Sun, 27 Mar 2011, Ilija Kocho wrote:
>
>> On 27.03.2011 19:11, Sergei Gavrikov wrote:
>>> On Sun, 27 Mar 2011, Ilija Kocho wrote:
>>>
>>>> On 27.03.2011 14:45, Sergei Gavrikov wrote:
>>>>> Hi Ilija,
>>>>>
>>>>> I get it (about your attempting to build the in-lines using CDL), but, I
>>>>> would keep things simpler, i.e. just would add two absent entries for
>>>>> TTY4, TTY5, TTYx in tty.c. Those are conditional definitions depend on
>>>>>
>>>> Adding two additional TTYs is an alternative indeed, it is simple and
>>>> straightforward to implement.
>>>>
>>>> My idea was to make system auto extensible and configurable. I have
>>>> fixed number of TTYs to 6, but as you suggest in your research below it
>>>> could be defined as a variable. HAL could provide an override too. Also
>>>> maintenance may be simpler since we avoid duplicated code?!
>>> Indeed. But, now I think that I gave bad suggest about extension via
>>> environment variable (How to document this "feature"? Who will know
>>> about? It looks like a trick) Ilija, so far, I take a timeout to think
>>> and test your substitutions and I will try to find compromise solution
>>> without the tricks and complex Tcl/CDL expressions.
>>>
>> Thanks,
>> In meantime I have a code that compiles and works. I will post to
>> Bugzilla so we can continue there.
>>
>> Ilija
> I was writing the below a few minutes ago
>
> Ilija, I tried something and I see that your request can be managed with
> CDL property 'make' and external Tcl script to generate some kind of
> io_serial_tty.inl on a fly like eCos 'heapgen.tcl' generates that
> heap.hxx, but I have a doubt about such a "complexity". By other hand
> the original tty and termios config files won't to have a mess with
> complex scripting as all details can be hidden in the external Tcl
> script. Eternal dilemma: Universality vs. Simplicity. I would prefer S.
> here (c & p), but, this is my view only.
>
> I think that you have to create bugzilla report is describing your issue
> (=request) without a solution and then we will discuss the ways to
> resolve the issue and I hope you will have more hands for that.
>
Sergei, I started this discussion in order to discuss this issue before
I drop any code. Your proposal sounds rational. I shall open a Bug and
reference this discussion.
Thanks
Ilija.
> Thank you,
> Sergei
next prev parent reply other threads:[~2011-03-27 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 10:22 tty.cdl Ilija Kocho
2011-03-26 18:33 ` tty.cdl Sergei Gavrikov
2011-03-27 11:40 ` tty.cdl Ilija Kocho
2011-03-27 12:45 ` tty.cdl Sergei Gavrikov
2011-03-27 15:46 ` tty.cdl Ilija Kocho
2011-03-27 17:11 ` tty.cdl Sergei Gavrikov
2011-03-27 19:34 ` tty.cdl Ilija Kocho
2011-03-27 19:39 ` tty.cdl Sergei Gavrikov
2011-03-27 19:55 ` Ilija Kocho [this message]
2011-03-27 21:11 ` tty.cdl Sergei Gavrikov
2011-03-28 10:42 ` tty.cdl Ilija Kocho
2011-03-28 12:16 ` tty.cdl Sergei Gavrikov
2011-03-28 19:00 ` tty.cdl Ilija Kocho
2011-03-28 19:25 ` tty.cdl Sergei Gavrikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8F963A.6050501@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-devel@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).