powerpc

qrencode - Segmentation fault (core dumped)

帅比萌擦擦* 提交于 2019-12-08 09:43:42
问题 I have made a working program that generated an image given a certain string. It is fully working on my Slackware 32bit distro and others distros also 32bit. Now i need to implement it on the client machine, which is an AIX powerpc. It compiled without any problem, and seems to work (every other function works and gives correct results), except when i call these 2 functions "QRcode_encodeString" and "QRcode_encodeData". It keeps giving me Segmentation fault. You can assume my main() only line

What does “vperm v0,v0,v0,v17” with unused v0 do?

心已入冬 提交于 2019-12-07 05:30:15
问题 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

Is it possible to run Nodejs on powerpc based Linux?

穿精又带淫゛_ 提交于 2019-12-07 04:49:46
问题 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. 回答1: 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

P1010 MAC to Switch port direct connection without PHY

倾然丶 夕夏残阳落幕 提交于 2019-12-06 07:02:34
I have a custom board with freescale P1010 processor in which P1010's eTSEC2 ( Enhanced 3-speed Ethernet controller) port is directly connected to Marvell 88E6046 ethernet switch Port 9 in SGMII mode. Linux (3.17) DSA driver is able to probe and detect switch ( Port 9 is 'cpu' whereas port 0 and 1 are designated as 'lan1' and 'lan2'). The problem however is, that there is no PHY for switch to attach to ( 'ifconfig up' fails to attach to ethx). U-boot creates a 'generic PHY' eth0 since it finds there is something ( switch ) attached to processor P1010 but when Linux is up and switch is attached

Threading Implementation

若如初见. 提交于 2019-12-06 06:59:57
问题 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? 回答1: 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

PowerPC moving to variable SPR

ⅰ亾dé卋堺 提交于 2019-12-06 06:41:17
问题 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

Is low latency mode safe to use with Linux serial ports?

廉价感情. 提交于 2019-12-06 05:11:18
问题 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

How the assembly file is generated from the perl script in OpenSSL

ε祈祈猫儿з 提交于 2019-12-06 02:20:28
In the opensource code of OpenSSL(version 1.1.0e) I saw that some of the function definition is generated by the perl files present inside the folders. In the build.info file present in each folders inside the crypto, they have written some lines to generate the .s from the corresponding .pl. For example, for generating aes_p8_set_encrypt_key in crypto/aes/build.info : GENERATE[aesp8-ppc.s]=asm/aesp8-ppc.pl $(PERLASM_SCHEME) for generating OPENSSL_madd300_probe in crypto/build.info : GENERATE[ppccpuid.s]=ppccpuid.pl $(PERLASM_SCHEME) And also in the main Makefile(generated makefile), there are

PPC breakpoints

走远了吗. 提交于 2019-12-05 21:50:20
How is a breakpoint implemented on PPC (On OS X, to be specific)? For example, on x86 it's typically done with the INT 3 instruction (0xCC) -- is there an instruction comparable to this for ppc? Or is there some other way they're set/implemented? I'm told by a reliable (but currently inebriated, so take it with a grain of salt) source that it's a zero instruction which is illegal and causes some sort of system trap. EDIT: Made into community wiki in case my friend is so drunk that he's talking absolute rubbish :-) With gdb and a function that hexdumps itself, I get 0x7fe00008. This appears to

How to properly develop for the iPhone on a PowerPC Mac?

◇◆丶佛笑我妖孽 提交于 2019-12-05 19:04:30
I'm doing iPhone development on a PowerPC Mac. How do I get code signing to work properly so that I can build to my iPhone? The iPhone SDK doesn't officially support PowerPC, but with some fidgeting, it can be installed. See here . I've got the SDK installed and running fine in Xcode and the iPhone simulator works fine. However, I can't build to my iPhone in Xcode -- the code signing is fubar. Some clever people have created workarounds here . Namely, I used the codesign script that Tiku posted along with some of the corrections. This has helped me make some progress. The code compiles now,