powerpc

In the latest iteration of Xcode, Xcode 4.0, the 10.4 SDK is no longer included. However, I still need to support 10.4 and PowerPC builds. I have installed latest Xcode 3.2.6 which still includes 10.4 support. Then I installed Xcode4. Has anyone found a simple way to "cheat" and get Xcode4 to use 3.2.6's SDKs? Mecki Yes, I did :) See here . XCode 4.0 supports deploying to Mac OS X 10.4 right out of the box, so you shouldn't have to do anything special. For example, I created a project then selected the project and right there, there is a field called "Deployment Target" where you can select 10

I'm working on an SHA-256 implementation using Power8 built-ins . The performance is off a bit. I estimate it is off by about 2 cycles per byte (cpb). The C/C++ code to perform SHA on a block looks like so: // Schedule 64-byte message SHA256_SCHEDULE(W, data); uint32x4_p8 a = abcd, e = efgh; uint32x4_p8 b = VectorShiftLeft<4>(a); uint32x4_p8 f = VectorShiftLeft<4>(e); uint32x4_p8 c = VectorShiftLeft<4>(b); uint32x4_p8 g = VectorShiftLeft<4>(f); uint32x4_p8 d = VectorShiftLeft<4>(c); uint32x4_p8 h = VectorShiftLeft<4>(g); for (unsigned int i=0; i<64; i+=4) { const uint32x4_p8 k =

I tried to build the latest Linux 64bit stable version with ./configure make and make install but ended up with this error: ../deps/openssl/openssl/include/openssl/../../crypto/bn/bn.h:803:23: error: unknown type name ‘BN_ULONG’ So is it actually possible to develop nodejs apps on Debian ppc? My setup is iMac G5 PowerPC with Debian Wheezy PPC on it. Andrew Low from IBM has developed a PowerPC port of node.js: https://github.com/andrewlow/node as well as V8: https://github.com/andrewlow/v8ppc 来源： https://stackoverflow.com/questions/18519899/is-it-possible-to-run-nodejs-on-powerpc-based-linux

I am trying to setup a driver for an embedded PowerPC board, and the correct way to do this today is to use the OpenFirmware Device Tree datastructure (the .dtb file, compiled from a .dts file). Creating a tree is pretty easy, but how do I get my device driver to find its node and the data in it? I have not managed to find any good reference on this, and books like "Linux Device Drivers" are too much into x86 land to be of much help for device trees that mostly pertain to Power Architecture-based machines (arch powerpc in the Linux kernel terminology). There seems to be very little

I wanted to know how to implement my own threading library. What I have is a CPU (PowerPC architecture) and the C Standard Library. Is there an open source light-weight implementation I can look at? At its very simplest a thread will need: Some memory for stack space Somewhere to store its context (ie. register contents, program counter, stack pointer, etc.) On top of that you will need to implement a simple "kernel" that will be responsible for the thread switching. And if you're trying to implement pre-emptive threading then you'll also need a periodic source of interrupts. eg. a timer. In

I'm writing an assembly macro to a C-program, and being quite new with this I have gotten stuck on something. I'm trying to write a macro for moving data from a general purpose register to a special purpose register. My problem is that the syntax I've found to move data from a GPR to an SPR takes a constant SPR value, while I want to use a variable one stored in another register. # SPR is constant, rA is the value to be written mtspr SPR, rA I'm after something that looks like this: # rA contains the number of the SPR, and rB the value to be moved. AWESOMEmtspr rA, rB Is there a reason there

Is it safe to use the low_latency tty mode with Linux serial ports? The tty_flip_buffer_push function is documented that it "must not be called from IRQ context if port->low_latency is set." Nevertheless, many low-level serial port drivers call it from an ISR whether or not the flag is set. For example, the mpc52xx driver calls flip buffer unconditionally after each read from its FIFO. A consequence of the low latency flip buffer in the ISR is that the line discipline driver is entered within the IRQ context. My goal is to get latency of one millisecond or less, reading from a high speed