Search results

I use my old CC Pandora as a brown noise generator. It is connected to speakers and running that program continuously. I turn on the speakers when I want brown noise in my bedroom.

You can't call a Linux syscall directly in C like that, the calling convention doesn't match up. Instead you should use the syscall wrapper function to do so: #include <stdio.h> #include <sys/syscall.h> #include <linux/random.h> int main() { int r; syscall(SYS_getrandom, &r, sizeof(int)...

Sorry, I didn't see the context that this was about syscalls, not ordinary C function calls. For ARM Linux EABI the first seven parameters are passed in r0 through r6. I don't know how you pass further parameters, or if any Linux syscalls even have more than 7 parameters.. This is actually...

I call ARM functions from C all the time and yes, this is how it works. But only for the first four parameters. The rest (if there are more) are stored on the stack.

I don't think it's a last minute change because I don't think they've yet committed any real resources towards their true proposed electrical design. Hence why they're showing demos running off of off-the-shelf dev boards. It's a sliver of good news though, seeing as how DDR4 is decently more...

Does anyone have any estimate of dimensions from this render? Using the USB C socket as a reference I'm coming up with around 17mm (not counting the grips of course) If reasonably accurate that's quite a bit thinner than GPD Win which is 23.5mm. Meanwhile their prototype is what, 50mm at least...

Applies more or less to ARM9, but not so much to anything newer.

Better how? Faster? Less code? It really depends on everything else you're doing and what processor you're running it on. The way you're proposing is not very intuitive but there are circumstances where it could be a good idea. If you perform a rotate with flags set the carry flag will reflect...

SGX544MP2 is built up from two units but I doubt it can really work like two independent GPUs with separate registers and command interfaces and everything. This was standard scaling for IMG but I don't think it works that way for Vivante's "Vega" GPUs - there are much higher end offerings than...

They did it that way to allow running two OSes on the same SoC without having to virtualize the GPU (which is tricky business and not totally viable on all of them) But I wonder if their hardware/drivers/whatever is good at making the two GPUs perform as well as one GPU when it needs to.

For anyone wondering more about the i.MX8 GPU the series is outlined here; http://www.cnx-software.com/2014/04/19/vivante-gc7000/ It should be the plain GC7000, but i.MX8Quad series seems to have two of them. There's more detailed information from NXP here...

28nm FDSOI process? Well that's certainly different, I'll give them that. Should be more efficient than what OMAP5 is made on but probably not as efficient as the FinFET processes.

Eh, I've seen better.

It's up to the particular CPU whether or not instructions have branch prediction applied, but there's no good reason why cmp+branch instructions wouldn't work with branch prediction.

This is an important point and I'm glad to see it being addressed. The relationship between performance and power consumption may not be that obvious, except that more performance needs more power. Some mobile SoCs in the last few years have gone to extremes to provide their highest few clock...

To expand on this, the reason why I see this as valuable for some recompilers is less because it can save an instruction sometimes and more because it preserves the current flags. This is useful if you're storing emulated flags or some other emulated state in native flags.

ARM supplies their CPUs in one of two forms: a "hard macro" that is designed directly for some manufacturing process and can be dropped directly into an SoC for it, and an RTL description that needs to be laid out/synthesized. Smaller companies will tend to choose the latter because they don't...

Caveat: those MIPS numbers actually mean "Dhrystone MIPS" which is the result of a really old and mostly meaningless benchmark that has a ton of problems. Even though it continues to be used for marketing today I wouldn't put too much stock in it. Real performance is going to vary quite a lot...

Also, open source licensing and the merits of FSF validation in particular.

There's no need for the reputation of Wikipedia to uphold the validity of any individual claim made there. If it has a citation that appears credible you'd may as well source the citation. If it doesn't have a citation that appears credible then it's probably not worth mentioning. It's a great...