public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Onno Kortmann <onno@gmx.net>
Cc: sid@sources.redhat.com
Subject: Re: Hierarchical components/graphical components
Date: Mon, 12 Jun 2006 01:23:00 -0000	[thread overview]
Message-ID: <20060612012330.GA11729@redhat.com> (raw)
In-Reply-To: <200606111610.36069.onno@gmx.net>

Hi -

On Sun, Jun 11, 2006 at 04:10:35PM +0200, Onno Kortmann wrote:

> [...]
> 1.) Is there a way to make a prototype setup and declare a component out of 
> this prototype setup, or some way of nesting configurations to enable 
> hierarchies of components? [...]

We have no support for that in the raw configuration language.  It
should not be hard to write a tcl script to perform the subsystem
configuration and to turn that into a first-class component, but it
would have to handle intricacies like passing down pin/bus
connectivity and attribute value traffic.  Extending cfgroot to
implement some sort of nesting directly would not be hard either, but
then one has to define not just the instantiation operation (which
sounds easy on paper), but also the create-a-composite-component
operation (which is hard: needs to define not just inner connectivity,
but also all the external-internal interfaces).

> 2.) Are there graphical editors for SID setups? [...]

Sorry, I don't now of any.  We didn't get far enough with hand-written
configurations to justify this.  If anything, the command-line-based
configuration generator system was a movement in the other direction.


- FChE

      reply	other threads:[~2006-06-12  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 14:10 Onno Kortmann
2006-06-12  1:23 ` Frank Ch. Eigler [this message]

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=20060612012330.GA11729@redhat.com \
    --to=fche@redhat.com \
    --cc=onno@gmx.net \
    --cc=sid@sources.redhat.com \
    /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).