US companies will be required by law to use close sourced OS's (ie M$) raising the cost of building their products. Foreign companies will not be under similar constraints (at least for the business they do outside the US) and wont have to pay M$.
In the long run higher paid US jobs will go overseas...
They would/could get those things as part of discovery in the Mother's putative suit. No reason for a lawsuit there (unless she wont give them up)
A more likely reason would be slander/libel etc because of what she's saying in the press about Sony - but if they're smart they'll ignore her and hope she goes away
that was back in the days when the signals carrying those frequencies moved on wires between chips - they could radiate - trust me (as a chip designer) no one is even trying to run signals at 2.4GHz between chips in your PCs. Of course a little bit always gets out but at those frequencies lead inductance is going to kill much of it anyway.
The FCC is very carefull about making sure people's hardware doesn't radiate and interfere with various radio services - that's why you have metal cases on boxes rather than cheapo plastic ones -
he sais that the article referenced by slashdot has caused him to re-examine the CUMULATIVE effects of a number different recent development, not just the Bernstein paper
If you think Scientology wont do this thing again - they picketted my kids on their way home from primary school with signs claiming I'm a religious bigot (because I exercised my 1st amendment rights and publically protested their spamming of news groups and complained about their human rights abuses - check xenu.net for first hand accounts of their US prison labor camps).
Want a simple way to counter scientology? - tell everyone you know about Xenu. He's the space-alien-devil in the scientology religion, most people think they are wierd but they keep the believing in space aliens thing rather quiet (all the better to pull in new recruits). If "scientology" and "space aliens" become synonomous more people will stay away from them - expect of course the real UFO nutters:-)
Weird shit happens when you start throwing multiprocessors made out of aluminum cans.
true but read on...
It takes a very precise cache coherency protocol to make the whole system behave in a deterministic way. If one processor has a slight modification to the coherency protocol (say an extra delay cycle) that the other doesn't, then you're in for trouble....... Next an IO buffer gets used by two processes simultaneously. Then suddenly they are sending two different devices corrupt data.
This is true on a slot-1 style (ie P2/3) bus where both chips are on the same bus and snooping each other's transactions - Athlon uses the Alpha EV6 bus which doesn't work that way. Instead each CPU has it's own private bus to the north bridge which is responsible for managing cache coherency between CPUs. The CPUs simply respond to the cache commands from the bridge.
Even a single CPU (on a non-MP chip set) has to honor the cache coherency protocol... because DMA transfers from PCI (but not AGP) are required to be cache coherent. This requires at the very least cache-line shootdown/flush support on all CPUs.
Having said that it's quite possible that there are cache transactions used in a real MP system that aren't needed for PCI support and AMD screwed up on their first silicon and didn't support all the cache transations correctly (not having an MP bridge around to test it on and all that) which might require a chip spin and an 'MP' version - but bug fixes like that are going to be in all their future parts (as a chip designer I know you don't touch stuff once it works right:-)
I disagree - the fact that they could do in in '98 means it's possible - I suspect this is another case of something the win95/98/... group did but the nt/2k/xp group didn't track. In an environment where IRQ sharing is required you're just going to have to make it work in all the possible environments. By the way the arguement "we changed the hardware" and "you just have to live with not having enough interrupt lines" kind of show a distinct lack of forethought.
Oh yeah and as a past NuBus card (and more recent PCI chip) designer I am NOT living in the ISA days (never designed one, never will) Apple gave each NuBus card it's own geographiclly address interrupt line - a smart idea - the current PC PCI/AGP card addressing issues are direct legacy of hardware decisions made 1` years ago
....Windows XP does not have this ability because of the more complex hardware schemas that Windows XP is designed to support. Windows 98 does not have to support IOAPICs, multiple root PCI buses, multiple-processor systems, and so on.....
most of this post was clipped from a MS site... and frankly it's a bunch of BS - on one hand it sais that XP is wonderfull because it supports a whole bunch more hardware configurations and at the same time uses that as a justification for not supporting this one - it sounds to me more like "we didn't want to solve a hard problem so we made the problem space smaller".
if i yelled at this coffee cup, and all the energy of my voice went into heat...
Ah - you're missing the point.... you have to get a straw an blow bubbles into it..... the hard part (which will require real engineering if we really want a table-top Mr Fusion) will be to figure out how to stop the coffee spraying all over the table
well of course anyone who uses a GPL'd paper's going to have to include the copyrights and GPL notices... so it's going to be pretty obvious who wrote what (otherwise the GPL will kick in and it does become a copyright issue)
well Pascal is VERY trickle down from Algol68, and C is from BCPL, and all of them from Algol60. But since Pascal and C were created roughly in parallel I doubt one could say that C is derived from Pascal - Though I suspect that C's later development of a stronger type system was probably encouraged by Pascal's wide spread acceptance in universities at the time
But is this using copyright to restrict rights beyond the intention of copyright law?
Well the copyright law basicly gives the copyright holder the right to decide what the license is.
At another level copyright is intended to encourage people to write and publish, certainly GPL encourages this in a way that tends to result in a sort of chain reaction publishing or more source - so I think it results in exactly what the original authors intended in a way that a simple giveaway of a library to the public domain does not
actually why it's an issue at all is shrouded in history..... Arabic numerals were originally written in - well - Arabic which is a right-to-left writing system... however in the original numbers were written LSdigits first, which makes sense since a culture of traders back in those days mostly did addition, which is done LSdigit to MSdigit.... it seems that some monk in Spain (where the Arabic numbering system was adopted when the Moors were driven south from Spain)... didn't really realize what he was doing an copied the Arabic system into Roman scripted languages (ie left to right) without reversing the order of the digits - the result is the mess we're in today - a scripting system where we think of text being left-to-right, but numbers being right-to-left (except we're so used to them we don't realise this). This means that there's no real culturally 'natural' way to handle byte ordering for us (if our first stored program computers had been invented by native Arabic speakers they'd all be little endian and it wouldn't be an issue)
yup - the basic problem is very simple - propagation is proportional to RC (the resistance times the capacitance) - you have to charge up the capacitance of the wire (wrt ground and other wires around) as well as the target gate(s) before you can measure the signal at the other end.
That's why copper wires were important - they reduced R. C on the other hand is a different matter - for years and years (untill about 3-4 years ago) no-one cared about the capacitance of wires - because they were usually small compared with the capacitance of gates and the ratios tended to scale down as device features scaled down - everything got faster together... then as wires started to get really thin something called the 'edge effect' started to kick in - basicly the wire is a flat plate and the capacitance is proportional to it's area (for fixed width wires that also means proportional to it's length) plus the edge effect which is proportional to it's perimiter. The edge effect was always there but small, it changes roughly linearly when a chip is scaled while area changes with the square of the area - the area component has been getting smaller a lot faster than the edge-effect one which now often dominates.
To make matters worse many of our CAD tools have untill quite recently made statistical guesses about wire capacitance which worked OK during things like synthesis (compiling to gates) when the wire capacitance was a small part of the equation, now it does matter and means the the whole structure of synthesis tools will have to change to perform combined synthesis and layout operations in order to create optimal circuits
actually on cu/si waveguides (ie normal wires on a die) it's way slower than that.
Even at today's high-end speeds (2GHz) 100 cycles (50nS) is fast for dram access. This is why keeping fast chips stoked these days requires heavy caching (L1/2/even 3 on-chip is a must and heading for 50% plus of die area)
Those are probably there for the cpu to north bridge traces - the clocks need a tiny delay so that the data (which is launched at about the same time) meets setup and hold at the far end
Slashdot Mirror
and transfer data at a rate equivalent to 100 Human Genomes per second.
....
Yeah but then so can a fully laden school bus
And, on a side note: can somebody explain to me his remark at the last page of the Tour: This picture just screams "only in America," doesn't it?
...... conspicuous consumption at its er finest
I suspect he was refering to the combination of mono-rail and hot-tub
No - they're australians
In the long run higher paid US jobs will go overseas
A more likely reason would be slander/libel etc because of what she's saying in the press about Sony - but if they're smart they'll ignore her and hope she goes away
The FCC is very carefull about making sure people's hardware doesn't radiate and interfere with various radio services - that's why you have metal cases on boxes rather than cheapo plastic ones -
he sais that the article referenced by slashdot has caused him to re-examine the CUMULATIVE effects of a number different recent development, not just the Bernstein paper
Want a simple way to counter scientology? - tell everyone you know about Xenu. He's the space-alien-devil in the scientology religion, most people think they are wierd but they keep the believing in space aliens thing rather quiet (all the better to pull in new recruits). If "scientology" and "space aliens" become synonomous more people will stay away from them - expect of course the real UFO nutters
bah - I mean moonrace2001.org
check out moonrace2001.org (well sort of)
true but read on
It takes a very precise cache coherency protocol to make the whole system behave in a deterministic way. If one processor has a slight modification to the coherency protocol (say an extra delay cycle) that the other doesn't, then you're in for trouble.
This is true on a slot-1 style (ie P2/3) bus where both chips are on the same bus and snooping each other's transactions - Athlon uses the Alpha EV6 bus which doesn't work that way. Instead each CPU has it's own private bus to the north bridge which is responsible for managing cache coherency between CPUs. The CPUs simply respond to the cache commands from the bridge.
Even a single CPU (on a non-MP chip set) has to honor the cache coherency protocol
Having said that it's quite possible that there are cache transactions used in a real MP system that aren't needed for PCI support and AMD screwed up on their first silicon and didn't support all the cache transations correctly (not having an MP bridge around to test it on and all that) which might require a chip spin and an 'MP' version - but bug fixes like that are going to be in all their future parts (as a chip designer I know you don't touch stuff once it works right
they've been involved in a number of greate pro-bono cases
Oh yeah and as a past NuBus card (and more recent PCI chip) designer I am NOT living in the ISA days (never designed one, never will) Apple gave each NuBus card it's own geographiclly address interrupt line - a smart idea - the current PC PCI/AGP card addressing issues are direct legacy of hardware decisions made 1` years ago
most of this post was clipped from a MS site
it sounds to me more like "we didn't want to solve a hard problem so we made the problem space smaller".
aparently it only really works if everyone else in the room is singing "tiny bubbles" ....
Ah - you're missing the point
well of course anyone who uses a GPL'd paper's going to have to include the copyrights and GPL notices ... so it's going to be pretty obvious who wrote what (otherwise the GPL will kick in and it does become a copyright issue)
there's that same big block of legaese at the beginning that will trigger the filter every time :-)
well Pascal is VERY trickle down from Algol68, and C is from BCPL, and all of them from Algol60. But since Pascal and C were created roughly in parallel I doubt one could say that C is derived from Pascal - Though I suspect that C's later development of a stronger type system was probably encouraged by Pascal's wide spread acceptance in universities at the time
Well the copyright law basicly gives the copyright holder the right to decide what the license is.
At another level copyright is intended to encourage people to write and publish, certainly GPL encourages this in a way that tends to result in a sort of chain reaction publishing or more source - so I think it results in exactly what the original authors intended in a way that a simple giveaway of a library to the public domain does not
actually why it's an issue at all is shrouded in history
That's why copper wires were important - they reduced R. C on the other hand is a different matter - for years and years (untill about 3-4 years ago) no-one cared about the capacitance of wires - because they were usually small compared with the capacitance of gates and the ratios tended to scale down as device features scaled down - everything got faster together
To make matters worse many of our CAD tools have untill quite recently made statistical guesses about wire capacitance which worked OK during things like synthesis (compiling to gates) when the wire capacitance was a small part of the equation, now it does matter and means the the whole structure of synthesis tools will have to change to perform combined synthesis and layout operations in order to create optimal circuits
Even at today's high-end speeds (2GHz) 100 cycles (50nS) is fast for dram access. This is why keeping fast chips stoked these days requires heavy caching (L1/2/even 3 on-chip is a must and heading for 50% plus of die area)
yup - you got it - block them in your firewall right away - make them use a real person next time ....
Those are probably there for the cpu to north bridge traces - the clocks need a tiny delay so that the data (which is launched at about the same time) meets setup and hold at the far end