From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] BR + CT-NG integration
Date: Tue, 22 Dec 2009 09:44:09 -0300 [thread overview]
Message-ID: <4B30BF19.7030302@zacarias.com.ar> (raw)
In-Reply-To: <87a5b0800912220437t21fad1e9v7d8b1e15b6ca7981@mail.gmail.com>
Will Newton wrote:
> I don't know what AXIS internal plans are, but it would appear by "not
> available publically", they mean they are getting out of the chip
> business (selling ETRAX SoCs) and becoming a pure IP supplier. If
> that's the case you will still see CRIS architecture chips but from
> other vendors.
Very unlikely since CRIS is a propietary architecture from Axis which is
probably covered by some patents.
On a limb i'm betting they decided that maintaining their own
architecture wasn't worth the effort and they'll be switching to
something more generally-available like ARM or MIPS.
Remember they're mostly a netcam company, not a silicon or IP one. Their
ARTPEC chips (the engine behind their cams) were never sold, they were
for internal consumption.
Acme systems (www.acmesystems.it) which sold a range of products based
on their Etrax SoCs completely switched to ARM if that's any indication.
next prev parent reply other threads:[~2009-12-22 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 22:51 [Buildroot] BR + CT-NG integration Yann E. MORIN
2009-12-22 8:31 ` Anders Darander
2009-12-22 9:10 ` Yann E. MORIN
2009-12-22 10:50 ` Anders Darander
2009-12-22 12:31 ` Gustavo Zacarias
2009-12-22 12:37 ` Will Newton
2009-12-22 12:44 ` Gustavo Zacarias [this message]
2009-12-22 20:34 ` Peter Korsgaard
2009-12-22 20:47 ` Yann E. MORIN
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=4B30BF19.7030302@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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