public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Onno Kortmann <onno@gmx.net>
To: sid@sources.redhat.com
Subject: Hierarchical components/graphical components
Date: Sun, 11 Jun 2006 14:10:00 -0000	[thread overview]
Message-ID: <200606111610.36069.onno@gmx.net> (raw)

Hi,

now that I played around a bit with SID, I have a couple of questions:

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? For example, I'd like to have a microcontroller 
with the embedded periphery modeled as separate SID components but have the 
whole setup appear as another component in SID which I can reuse multiple 
times in a higher-level setup.

2.) Are there graphical editors for SID setups? More complicated setups are 
easier to edit graphically, I think. I'm thinking of something like a 
netlister for gschem or similar.

Best regards,

Onno

             reply	other threads:[~2006-06-11 14:10 UTC|newest]

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

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=200606111610.36069.onno@gmx.net \
    --to=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).