Wasn't the 68000 also considered for the CPU? Then, it may not have sucked shit (then again, the rest of the system architecture sucked shit), and it probably would've sold shit, too.
Actually, that makes me think of something, with another discussion from this thread.
His job, ostensibly, is to represent the people, correct?
So, every year, have his consitutents vote on his salary by writing a number. The average of the votes sets his salary. That salary is pulled equally from every constituent's taxes.
Taking part in a protest that is visible to non-citizens would be treason, but only if it were protesting something classified, and not everything that's being protested would be classified.
Reporting on the protest in a venue that is visible to non-citizens would be treason.
Also, if a person could reasonably believe, as determined by a jury of their peers, that non-citizens didn't have access to the information, then they could be acquitted.
Sealing the borders would likely be required for this to work, however.
Decay products, that take a long time to decay themselves and cool off.
You can't just turn off a reactor like you can an engine, when you insert the rods, you have to keep the reactor cool until the decay products have all decayed.
The odd thing is, the UK book actually uses "fuck" there, and takes out the whole bit about it being weird that "Belgium" is a swear word.
(Which makes it all kinds of weird when, as someone who read the US book, which is "censored" to Belgium, you're talking to someone who's read the UK book, but not heard the radio series.)
The American consumer actually claims to demand high horsepower, and then doesn't understand why they don't feel the horsepower when they put the accelerator at half throttle at 2000 RPM.
(And, really, if we weren't so goddamn stupid, we'd realize that diesel engines are perfect for our driving style...)
1. Automatically give every American citizen a clearance, and if they're found by a court to have leaked info to non-citizens, they're guilty of treason. 2. Have classified information, but treat overclassification - that is, classifying information that would reveal wrongdoing or does not affect the US's military strategy if it were to leak - as treason, and give a reward to the leaker of that information.
There's nothing to oppose them anyway, much of their power comes from buying off the government, and then getting the government to ignore its own laws to get more power...
There actually is a way for people to live far apart from other people, and live successfully, without having any expenses other than start-up expenses, or any income. (Or, some expenses and some income, but it's not a good way to make money.)
This includes the number of micro-operations for each main instruction and the source and destination requirements for each micro-operation. The processor can issue a series of micro-operations to the execution pipeline for each ARM instruction executed. Most ARM instructions execute only one micro-operation. More complex ARM instructions such as load multiples can consist of several micro-operations.
And, as of Cortex-A15, ARM is going the same route as that.
The problem with that approach is that it doesn't increase the address space per process, just the address space available to the OS. It's still very useful for many workloads, but there are still workloads that really need the address space to be "real", rather than bankswitched.
Citation needed on ARM having an opcode decompresser, with micro-ops and all.
All I'm finding is that it translates Thumb opcodes (which are a subset of ARM, meant to increase code density and, when on a 16-bit data bus, increase performance) to ARM before processing the opcode.
Actually, nowadays, Intel's CPUs go over 100% duty cycle - they overclock themselves for limited periods of time under certain workloads, and then downclock themselves once a certain amount of time has passed, power consumption exceeds a predefined amount, or the CPU is getting too hot.
They sell things like, oh, battery cells. That every laptop manufacturer in the world uses. (I've lucked out, all of my recent laptop purchases have used batteries with Sanyo cells.)
They sell intellectual property. Bought a computer with Windows or OS X, or a modern phone, or anything with a graphics card? You bought Sony's intellectual property.
Newer VWs have the following things all on a single CAN bus (and there actually is a justification for it):
Engine control unit Transmission control unit Anti-lock brakes/traction/stability control (and these can actually command the ECU to accelerate or decelerate) Instrument cluster (this one can command the ECU to shut down, if it thinks the car is stolen) Radio Climate control Central convenience module (handles remote locks, power windows, and things like that) Airbags Electric power steering
So, the reason for them all being connected... let's say you get into a crash.
Airbags deploy. This sends a message to the ECU to shut down, the instrument cluster that there's an airbag issue, the radio to shut down, the central convenience module to turn on the flashers, roll down the windows, and unlock the doors.
If you're not worried about malware, that makes sense, and the thought of malware attacking a radio is generally insane.
Technically, Intel does still own some XScale stuff, for their IOP line of SoCs meant for storage arrays.
(Oh, and as for StrongARM being incompatible... ARM9 made the same changes. The only other thing I can think that XScale did to break compatibility, relative to contemporary ARMs, was WMMX support in later versions, which used the same coprocessor ID as ARM's original FPA floating point unit, which meant that code that called the FPA would crash and burn, rather than throw an invalid instruction exception and get handled in software. Contemporary ARMs also started using Thumb, which couldn't coexist with support for 26-bit addressing. Both of those problems would've only affected Acorn's RISC OS, though. (The WMMX one didn't, as there wasn't any money to design any RISC OS-specific hardware by the time WMMX became an issue, and now that there's a shared source version, the porting efforts have focused on more modern SoCs that don't have WMMX either. 26-bit addressing, that one caused major issues, but the work was done to mitigate those issues in 2001, with the Iyonix, which uses an IOP321 (IIRC) XScale.)
Slashdot Mirror
Wasn't the 68000 also considered for the CPU? Then, it may not have sucked shit (then again, the rest of the system architecture sucked shit), and it probably would've sold shit, too.
Actually, that makes me think of something, with another discussion from this thread.
His job, ostensibly, is to represent the people, correct?
So, every year, have his consitutents vote on his salary by writing a number. The average of the votes sets his salary. That salary is pulled equally from every constituent's taxes.
Well, they could also leave the country.
(Then again, protectionist policies could actually help, there.)
Actually, no.
Under that idea:
Taking part in a protest that is visible to non-citizens would be treason, but only if it were protesting something classified, and not everything that's being protested would be classified.
Reporting on the protest in a venue that is visible to non-citizens would be treason.
Also, if a person could reasonably believe, as determined by a jury of their peers, that non-citizens didn't have access to the information, then they could be acquitted.
Sealing the borders would likely be required for this to work, however.
http://idle.slashdot.org/story/10/09/10/1723209/What-Happens-When-You-Let-100-Cats-Loose-Inside-An-IKEA
I guess WWV has been down for a while now, because 2012 happened 1.5 years ago.
Decay products, that take a long time to decay themselves and cool off.
You can't just turn off a reactor like you can an engine, when you insert the rods, you have to keep the reactor cool until the decay products have all decayed.
Do you have a laptop? If so, who makes the battery? It's probably Sanyo or Sony.
Do you have anything that has an H.264 decoder in it? (This includes Windows, OS X, and most smartphones.) If so, Sony gets licensing fees.
Do you have a digital camera or camcorder? If so, who makes the CCD or CMOS sensor? Sony makes those, too.
The odd thing is, the UK book actually uses "fuck" there, and takes out the whole bit about it being weird that "Belgium" is a swear word.
(Which makes it all kinds of weird when, as someone who read the US book, which is "censored" to Belgium, you're talking to someone who's read the UK book, but not heard the radio series.)
The American consumer actually claims to demand high horsepower, and then doesn't understand why they don't feel the horsepower when they put the accelerator at half throttle at 2000 RPM.
(And, really, if we weren't so goddamn stupid, we'd realize that diesel engines are perfect for our driving style...)
A couple options I can think of...
1. Automatically give every American citizen a clearance, and if they're found by a court to have leaked info to non-citizens, they're guilty of treason.
2. Have classified information, but treat overclassification - that is, classifying information that would reveal wrongdoing or does not affect the US's military strategy if it were to leak - as treason, and give a reward to the leaker of that information.
There's nothing to oppose them anyway, much of their power comes from buying off the government, and then getting the government to ignore its own laws to get more power...
Data bus width, for the P4 and newer.
(Actually, some Nehalems are 192-bit, plus the extra ECC bits, IIRC.)
There actually is a way for people to live far apart from other people, and live successfully, without having any expenses other than start-up expenses, or any income. (Or, some expenses and some income, but it's not a good way to make money.)
Reverting to homesteading.
Ah.
From the Cortex-A8 reference manual:
Instruction-specific scheduling information
This includes the number of micro-operations for each main instruction and the source and destination requirements for each micro-operation. The processor can issue a series of micro-operations to the execution pipeline for each ARM instruction executed. Most ARM instructions execute only one micro-operation. More complex ARM instructions such as load multiples can consist of several micro-operations.
The idea of arming the people to defend against lone crazies with guns isn't the actual intent of arming the people.
The intent of arming the people is to defend against governments with guns, treating the risk of an armed crazy as an acceptable risk.
And, as of Cortex-A15, ARM is going the same route as that.
The problem with that approach is that it doesn't increase the address space per process, just the address space available to the OS. It's still very useful for many workloads, but there are still workloads that really need the address space to be "real", rather than bankswitched.
Citation needed on ARM having an opcode decompresser, with micro-ops and all.
All I'm finding is that it translates Thumb opcodes (which are a subset of ARM, meant to increase code density and, when on a 16-bit data bus, increase performance) to ARM before processing the opcode.
HP t5325, although it's intended as a thin client.
Genesi Efika MX Open Client. That's intended as a desktop.
(Of course, both of those have badly outdated SoCs.)
It's a FUD attack at HP, Oracle's newest enemy, FWIW.
(HP is the only company that really uses Itanium any more.)
Actually, nowadays, Intel's CPUs go over 100% duty cycle - they overclock themselves for limited periods of time under certain workloads, and then downclock themselves once a certain amount of time has passed, power consumption exceeds a predefined amount, or the CPU is getting too hot.
Sony sells a lot more than entertainment devices.
They sell things like, oh, battery cells. That every laptop manufacturer in the world uses. (I've lucked out, all of my recent laptop purchases have used batteries with Sanyo cells.)
They sell intellectual property. Bought a computer with Windows or OS X, or a modern phone, or anything with a graphics card? You bought Sony's intellectual property.
Snap the disc and go without.
The game is designed to sell DLC, therefore, if someone else buys it, they might buy DLC, supporting Sony.
If you snap it in half, nobody can play that game - you take a loss, but you guarantee that Sony won't get any further income.
There's always going the OnLive route - basically, don't give people physical access, just give them a thin client.
Newer VWs have the following things all on a single CAN bus (and there actually is a justification for it):
Engine control unit
Transmission control unit
Anti-lock brakes/traction/stability control (and these can actually command the ECU to accelerate or decelerate)
Instrument cluster (this one can command the ECU to shut down, if it thinks the car is stolen)
Radio
Climate control
Central convenience module (handles remote locks, power windows, and things like that)
Airbags
Electric power steering
So, the reason for them all being connected... let's say you get into a crash.
Airbags deploy. This sends a message to the ECU to shut down, the instrument cluster that there's an airbag issue, the radio to shut down, the central convenience module to turn on the flashers, roll down the windows, and unlock the doors.
If you're not worried about malware, that makes sense, and the thought of malware attacking a radio is generally insane.
Technically, Intel does still own some XScale stuff, for their IOP line of SoCs meant for storage arrays.
(Oh, and as for StrongARM being incompatible... ARM9 made the same changes. The only other thing I can think that XScale did to break compatibility, relative to contemporary ARMs, was WMMX support in later versions, which used the same coprocessor ID as ARM's original FPA floating point unit, which meant that code that called the FPA would crash and burn, rather than throw an invalid instruction exception and get handled in software. Contemporary ARMs also started using Thumb, which couldn't coexist with support for 26-bit addressing. Both of those problems would've only affected Acorn's RISC OS, though. (The WMMX one didn't, as there wasn't any money to design any RISC OS-specific hardware by the time WMMX became an issue, and now that there's a shared source version, the porting efforts have focused on more modern SoCs that don't have WMMX either. 26-bit addressing, that one caused major issues, but the work was done to mitigate those issues in 2001, with the Iyonix, which uses an IOP321 (IIRC) XScale.)