and if PlayStation 3 and Xbox Next are released around the same time ...... I wonder which chip will get priority in the East Fishkill fab ......... CELL or the CPU for Xbox Next ..
No DLL support is understandable since there is only one application running at a time.No MS console OS will be anything like a desktop OS, Eg. Xbox has no DLL support which predate Win32!
It is unlikely you will see IBM fabs running at 100% capacity even if both Xbox Next and N5 are launched.You mean MS and Nintendo, since Sony has their own fab(I think....).
You're right, parable it is!Tahir said:That is not a metaphor... surely?
Not necessarily. The point I am trying to make is that MS needs the latest DX subsystem to drive XGPU2 for Xbox Next and NT kernel has the most upto date DX subsystem development.Aren't OS Kernel and API two really seperate things? They aren't completely dependant on each other.
and if PlayStation 3 and Xbox Next are released around the same time ...... I wonder which chip will get priority in the East Fishkill fab ......... CELL or the CPU for Xbox Next .
DaveBaumann said:However, regardless of where these things are from you have to look at the content and evalutate if there is actually any sense.
That's a total non-sequitur. DX interacts with the kernel purely through the driver interface, which won't even be there in an embedded console OS that targets a single hardware platform. Not to mention, the version of DX that targets the hardware that the Xbox Next will have probably hasn't even been written yet, for any OS (well, ok, it's probably being worked on, assuming the capabilities of the target hardware are reasonably stable).The point I am trying to make is that MS needs the latest DX subsystem to drive XGPU2 for Xbox Next and NT kernel has the most upto date DX subsystem development.
Deadmeat said:No DLL support is understandable since there is only one application running at a time.No MS console OS will be anything like a desktop OS, Eg. Xbox has no DLL support which predate Win32!
However, XBox Next does need the latest OS simply because it is a DX10 device. Because including DX10 for anything else involves too much reengineering.
More than likely.Wunderchu said:if Microsoft indeed ends up contracting IBM for their fabbing ... I wonder if IBM will use their East Fishkill fab for the job ..........
IBM is not producing the versions of CELL Sony will be using in the PS3. That will come out of Toshiba and Sony fabs. (You can search around for the specifics--it's certainly been mentioned enough in other threads.)and if PlayStation 3 and Xbox Next are released around the same time ...... I wonder which chip will get priority in the East Fishkill fab ......... CELL or the CPU for Xbox Next ..
Gubbi said:Deadmeat said:An NT kernel image cannot be fit into a 128 KB space.Each APU may have limits on program size but the entire unit as a whole won't.
It doesn't have to. The OS software runs on the PUs, not the APUs. It has to in order to control what process is running on the APUs.
Cheers
Gubbi
nobie said:I don't think each APU is an entire functioning processor unto itself. They seem more like independant ALUs each with their own bit of ram and register space. The PUs would be running the basic program, and keeping the APUs fed.
Panajev2001a said:nobie said:I don't think each APU is an entire functioning processor unto itself. They seem more like independant ALUs each with their own bit of ram and register space. The PUs would be running the basic program, and keeping the APUs fed.
APUs have their own Program Counter Register and they have their Stack and their Heap ( in the 128 KB of Local Storage they have ).
APUs can DMA to and from DRAM by talking to the DMAC and they can also do some form of I/O to and from I/O devices.
Deadmeat said:The whole point of my arguement was that MS needs to run NT kernel on Xbox Next and this excludes the possibility of MS licensing some kind of CELL device, since large NT kernel and CELL APUs are mutually incompatible.
nobie said:Panajev2001a said:nobie said:I don't think each APU is an entire functioning processor unto itself. They seem more like independant ALUs each with their own bit of ram and register space. The PUs would be running the basic program, and keeping the APUs fed.
APUs have their own Program Counter Register and they have their Stack and their Heap ( in the 128 KB of Local Storage they have ).
APUs can DMA to and from DRAM by talking to the DMAC and they can also do some form of I/O to and from I/O devices.
The point is the APU is dependant on either the PU or the compiler. It wouldn't run an operating system or perform the functions that the PU does, as Squeak suggested.
DLL exists to share library code between multiple running applications. Since Xbox Next will run only one application(game) at a time, there is no need for library sharing, so DLL can be omitted without a problem.No DLL support in XBox has got nothing to do with one application running.
At some point the latest DirectX will be handed to console team and they will reengineer alot of it. Thats what they've done with DX XBox and likely to happen on the next OS. DX Xbox is almost completely rewritten from the early version of DX 8 is split from.
Yes it is. MS has lots of code to port over, and it won't run on something like CELL.I doubt Operating System issues will play a major factor in the decision process if the performance gap between PowerPC vs CELL is large.
The rule of semiconductor biz is that no chip fabricated on identical process around a similar timing blows the other away by more than a factor of three. CELL won't be "vastly more powerful" than Power5 lite that MS is putting inside Xbox Next.If your opinion is that Microsoft won't go with CELL, even if it is vastly more powerfull