rickman wrote:
> On 5/5/2013 3:40 AM, Steve wrote:
> >
> >
> > rickman wrote:
> >> On 5/2/2013 3:12 AM, Steve wrote:
> >>>
> >>> FPGA's were power hungry and slow, but the advantage was that you
> >>> could do things more directly, by passing code and in parralel, great
> >>> advantages, and response was very analogue. But in making a processor
> >>> things slow down with higher power consumption.
> >>
> >> I think you are not really that familiar with FPGAs. There are large,
> >> high power devices out there, but there are also smaller, low power
> >> devices that can rival many processors in terms of speed and efficiency.
> >
> >
> > Well the last time I looked was around four years ago at the new low
> > powered generation, silicon bye, or something like that, a far cry
> > from the 6 or so mw per node of misc that could be under 1 mw on the
> > latest process.
>
> You need to look again. Check out the iCE40 family from Lattice.
> Xilinx and Altera are very focused on the networking and comms markets
> where the large, power hungry devices are still in demand. The iCE40 is
> from a startup bought by Lattice, Silicon Blue who understands there is
> a market for small, low power devices.
>
Without going into all this, silicon blue low powered was my primary
point, in comparison to misc, so not even that with soft core beats
misc on an similar area use basis. It dies not matter about higher
powered, it gets worse for FPGA by area.
> >> I won't say there are any FPGAs that can match the speed/power
> >> consumption of the GA144, but I don't think there *are* any processors
> >> that can do that.
> >
> > Depends, but we are talking exclusively about softcore performance on
> > fpga aren't we?
>
> No, I am saying the GA144 has the highest speed/power tradeoff of any
> processor I've seen, at least for powerful processors. Some of the
> watch type processors might edge it out since they are designed just for
> low power with speed just not a consideration... above 32 kHz anyway.
But where we came from and what we were talking, about was about FPGA
softcore to misc comparison, jumping sideways does not invalidate
that, and is hardly fair or inconfusing, isn't it? My hlead can jump
around as fast as the next, Rick, but I keep it on track and pick
relavaent side lines, with some observations. If you want to talk
oranges when we are talking apples please talk oranges separately
instead of saying apples does not equal oranges and I am therefore
wrong, sort of thing. I could similarly next say something irrelevant
and claim that is more right, just does not make sense.
>
> > I expressed that for a direct parallel circuite it is
> > much better for fpga, but making a custom asic is better again, having
> > such a thing controlled by a processor is still better. But I suppose
> > if you if you compared most processor arrays to an fpga parallel
> > circuit the processor is going to pay in some way, either to much
> > current drain at speed, or too much circuit to run at lower speed in
> > parralel. But then it might inevitably depend, if you have a small fpga
> > up against a small speed processor, say a basic small arm converted
> > to a good high speed low powered chip process version, then there is only so much you
> > can fit into an equivalent die space (30k transistors, but on the same area on the FPGA less than that
>>) to run against it, realistically.
>
> You have too many typos for me to understand your statements.
>
Freakin auto spell correction, substitutes and splits into nonsense
words things it does not understand, and answering these posts in
depth is wearing my time out too much to keep up with correction.
Plus this keyboard has some issues. Sorry. I've corrected and
rearranged the little quote above for you to look at.
> >> But compared to a Cortex CM3, a softcore MISC processor can keep up and
> >> possibly be lower power.
> >
> >>
> >> I'm not sure what you are saying here. You seem to be saying that the
> >> GA144 is somehow better than softcore FPGA processors. That all depends
> >> on what you are using it for. I found the GA144 to be very difficult to
> >> use for most apps. There may be a few which it is well suited for, but
> >> it is *not* a general purpose CPU or MCU. It is a special beast all its
> >> own.
> >
> > We are only talking performance and power consumption, not
> > programming, and I did specify that misc had not reached it's peak, by
> > any stretch, to prove that. Plus, if it was at this pleak, it would
> > be easier to program, having at least one core that had large program
> > pace for regular programming like a general purpose. Please those are
> > in reference my words we are talking about.
>
> I am talking usability of the hardware. You are focusing on the CPU,
Again it was about what was talked about, and the topic/subtopic, if
you want to shift topic say, 'ok, whatever you think about the current
topic', then 'what about xyz different angle' for the next topic,
don't just call into question what I'm saying into relevance something
else. This just confuses it.
> but the CPU has to live on a board and do useful stuff. The GA144 is
> actually an MCU with a number of I/O pins and seems to be intended to be
> embedded in products, not the core of a phone or tablet. Turns out it
> sucks at this for several reasons, mostly because the I/O has
> shortcomings, but also because you need to add so many support chips.
> Products these days want to see integration. Put the Flash on the CPU,
> put all the interfaces on the CPU, including the funky I/O voltages they
> may need, like USB, etc. GA144 falls very short in this regard.
Yep, I hear you, that is why I am looking at attaching it to another
integrated processor, and just have it do processing, but the other
chip run everything else. Until it has a large execution space bus,
even processing will be slowed. A 32 bit with large execution space
you can do more. As it is, notice for the cheap version of the ring
computer I wanted only a few interfaces, like two or so, to keep it
very simple and basic. With the present version there is little you
can do. If it had a large execution bus, everything would be a bit
easier and you can do more, but even then, all the extra functionality
companion chips for cpu's would be drying up, because they are being
integrated with cpu's etc and are no longer needed.
>
> Even as a higher end processor it falls short by not having a memory
> controller, but rather depending on three CPUs to provide this. This
> ends up being a real bottle neck for processing.
Yep.
>
> >> I don't agree that the factor limiting the GA144 is that it isn't built
> >> on "top processes". This chip is hobbled by the lack of decent
> >> interfaces. They promote the use of soft interfaces which limit I/O to
> >> slow protocols. They also don't provide flexible voltage I/Os so
> >> anything other than 1.8 volt I/O requires messy level conversion. Try
> >> driving a simple clock LCD with a GA144. You will need a number of
> >> level conversion chips.
> >>
> >
> > I agree, the design needs to improve, though at top process, the
> > artificial software buss maybe able to run at 1ghz, and the software
> > stream how many instructions of a word that can be run in a cycle in
> > that design. This peak also includes redesign, I'm sorry if I did
> > not mention it. The rest of the array for stream processing. But
> > now they are free of higher consideratiibs handled by the control
> > node, then maybe they can be easier to program and more efficiently
> > program. That would be very power full compared to now. What would
> > you agree Rick?
> >
> > But many people miss things in what I write, and take it differently.
>
> Or they read exactly what you write...
You must have, because you didn't disagree this time. :-)
Now, I've had enough issues, and as elsewhere today, I would like to
close off this conversation, even though it was ok.
Thank you Rick for the good conversation here.
Steve.
> --
>
> Rick