Message-ID:

I dunno, I dream in Perl sometimes... -- Larry Wall in <8538@jpl-devvax.JPL.NASA.GOV>

devel / comp.arch.fpga / Re: Xilinx microblaze vs. picoblaze

Re: Xilinx microblaze vs. picoblaze

<877367c3-9f99-4e2f-bb3b-91fe1238662cn@googlegroups.com>

https://www.rocksolidbbs.com/devel/article-flat.php?id=268&group=comp.arch.fpga#268

X-Received: by 2002:a05:600c:4150:b0:37b:c68f:19f4 with SMTP id h16-20020a05600c415000b0037bc68f19f4mr5893789wmm.67.1645170956358;
Thu, 17 Feb 2022 23:55:56 -0800 (PST)
X-Received: by 2002:a0c:fd85:0:b0:42c:1f71:daad with SMTP id
p5-20020a0cfd85000000b0042c1f71daadmr5063570qvr.34.1645170955868; Thu, 17 Feb
2022 23:55:55 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.arch.fpga
Date: Thu, 17 Feb 2022 23:55:55 -0800 (PST)
In-Reply-To: <apcpog$8jh$1@slb7.atl.mindspring.net>
Injection-Info: google-groups.googlegroups.com; posting-host=122.163.228.151; posting-account=xTH7kwoAAABd7O8oJRamXH9r_9Yn8vyM
NNTP-Posting-Host: 122.163.228.151
References: <3DABA42C.8321741C@ecubics.com> <3DAC5864.321F9681@Xilinx.com>
<3DAC62E1.5246FDF7@ecubics.com> <3DAC6ED3.A8E721C4@Xilinx.com>
<aokms0$t0q$1@agate.berkeley.edu> <aokqak$2hh$1@slb0.atl.mindspring.net>
<3DB29F07.E022310F@algor.co.uk> <apcpog$8jh$1@slb7.atl.mindspring.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <877367c3-9f99-4e2f-bb3b-91fe1238662cn@googlegroups.com>
Subject: Re: Xilinx microblaze vs. picoblaze
From: alisha@launchigo.in (Alisha Pal)
Injection-Date: Fri, 18 Feb 2022 07:55:56 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

by: Alisha Pal - Fri, 18 Feb 2022 07:55 UTC

Re: Xilinx microblaze vs. picoblaze

<182b8383-644d-45ee-b8e1-1412bce30058n@googlegroups.com>

copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=269&group=comp.arch.fpga#269

copy link Newsgroups: comp.arch.fpga

X-Received: by 2002:a05:6000:1e04:b0:1e4:9b64:8cab with SMTP id bj4-20020a0560001e0400b001e49b648cabmr13472650wrb.608.1645395206119;
Sun, 20 Feb 2022 14:13:26 -0800 (PST)
X-Received: by 2002:ad4:5187:0:b0:42c:4f21:b91b with SMTP id
b7-20020ad45187000000b0042c4f21b91bmr13192611qvp.104.1645395205680; Sun, 20
Feb 2022 14:13:25 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.arch.fpga
Date: Sun, 20 Feb 2022 14:13:25 -0800 (PST)
In-Reply-To: <877367c3-9f99-4e2f-bb3b-91fe1238662cn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=84.65.5.84; posting-account=EZTXhQoAAABd8gcnPd92-pZGLzXhe3xe
NNTP-Posting-Host: 84.65.5.84
References: <3DABA42C.8321741C@ecubics.com> <3DAC5864.321F9681@Xilinx.com>
<3DAC62E1.5246FDF7@ecubics.com> <3DAC6ED3.A8E721C4@Xilinx.com>
<aokms0$t0q$1@agate.berkeley.edu> <aokqak$2hh$1@slb0.atl.mindspring.net>
<3DB29F07.E022310F@algor.co.uk> <apcpog$8jh$1@slb7.atl.mindspring.net> <877367c3-9f99-4e2f-bb3b-91fe1238662cn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <182b8383-644d-45ee-b8e1-1412bce30058n@googlegroups.com>
Subject: Re: Xilinx microblaze vs. picoblaze
From: matrixofdynamism@googlemail.com (Hassan Iqbal)
Injection-Date: Sun, 20 Feb 2022 22:13:26 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 7

by: Hassan Iqbal - Sun, 20 Feb 2022 22:13 UTC

On Friday, 18 February 2022 at 07:56:01 UTC, Alisha Pal wrote:
> There was a time when I knew pretty much everything about <a href="https://cloudplay.fm/cpu-cores-vs-threads/">CPU </a> design that wasn't covered by an NDA. Details (hardware and software) are definitely more significant than we can evaluate without a strong design to discuss for fine-grained work.
The OP is 20 years old. As of today, the picoblaze is not supported by Xilinx anymore.

Subject	Author
Re: Xilinx microblaze vs. picoblaze	Alisha Pal
Re: Xilinx microblaze vs. picoblaze	Hassan Iqbal