From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Frank Ch. Eigler'" <fche@redhat.com>,
"Mikael Starvik" <mikael.starvik@axis.com>
Cc: <sid@sources.redhat.com>
Subject: RE: Future of SID
Date: Wed, 30 Mar 2005 06:34:00 -0000 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C668014C786D@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66802906D97@exmail1.se.axis.com>
Yes, we will release everything later when the real silicon has been
verified. The configuration files reveal some of the capabilities
so I'm, not sure if I can release them in this open forum. I'll check.
/Mikael
-----Original Message-----
From: sid-owner@sources.redhat.com [mailto:sid-owner@sources.redhat.com] On
Behalf Of Frank Ch. Eigler
Sent: Wednesday, March 30, 2005 12:16 AM
To: Mikael Starvik
Cc: sid@sources.redhat.com
Subject: Re: Future of SID
Hi -
On Tue, Mar 29, 2005 at 09:33:21AM +0200, Mikael Starvik wrote:
> [...]
> During the development of a new System-On-Chip ASIC we have developed SID
> components of most parts of the system including CPU, MMU, DMA, Ethernet,
> UART etc. We have used this to develop a working Linux port [...]
Wonderful! Do you expect to be able to eventually share any of this
modelling effort outside Axis? Even just the sid configuration files
you use would be informative.
- FChE
next parent reply other threads:[~2005-03-30 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C66802906D97@exmail1.se.axis.com>
2005-03-30 6:34 ` Mikael Starvik [this message]
[not found] <BFECAF9E178F144FAEF2BF4CE739C66802906D96@exmail1.se.axis.com>
2005-06-17 11:03 ` Mikael Starvik
2005-06-18 22:43 ` Frank Ch. Eigler
[not found] <BFECAF9E178F144FAEF2BF4CE739C6680290621A@exmail1.se.axis.com>
2005-03-29 7:33 ` Mikael Starvik
2005-03-29 22:15 ` Frank Ch. Eigler
2005-03-28 14:17 kobi maller
2005-03-28 17:56 ` 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=BFECAF9E178F144FAEF2BF4CE739C668014C786D@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=fche@redhat.com \
--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).