You need enough power to make the device work, and not too much power for safety reasons. POTS already does this.
You would also need an additional pair or two to come into each house for power (10/100/1000baseT are differential which I don't think can be biased and homes are only wired with a single copper pair from pole to house), or you have to modulate the data signal and separate the power and data with a bias T (this is how the cable amps work on the pole). Telcos are very reluctant to rewire the entire country (hence DSL on existing copper).
At high frequencies, the pins on a package aren't really short circuits (ie, zero resistance); they have a capactiance and inductance which mess with the signals. Making removable pins would make this a lot worse.
I'm not sure if the i860 was the failure that everyone is saying it was. This may be true on the desktop, but it was a fairly popular processor in the embedded world for offloading computation.
With most cell phones, especially CDMA, power is very carefully controlled. I seriously doubt that an increase in antenna efficiency would cause problems with current installations. Basically, the phone would just input less power to the output PA and get the same EIRP. On the receiving end, it would just look like a better connection. Cell phones already know how to deal woth signals from multiple basestations.
Not really. There isn't much assembly necessary on a modern embedded platform.
Ditto. I have only really used asm in two or three places in embedded projects. One is in the initial bootloader. The second is in instances where the compiler won't do what I want. The third is to access special instructions that the compiler doesn't know about (eg, eieio on the PPC). The second and third instances can't mostly be dealt with inline asm and cpp macros, and gcc make this a lot easier if you have access to it.
What I want is for the environment on which I code to be less convoluted.
A big part of being an embedded developer is being able to adapt to different development environments and being able to develop and debug a system with minimal tools. Sometimes you have a VT100, sometimes, JTAG, other times remote debug via Ethernet. I have worked on systems where I have had to debug software with a logic analyzer because that is all that was available.
"QNX is what you trust your nuclear reactor to." Which would be rather stupid. From the license:...
I seem to recall print ads from the early to mid 90's that showed QNX being used in a nuclear facility. I think the ad told about how they were able to update the system without taking it down because of the microkernel architecture.
Secondly, review is not *just* a moderation process, its a feedback process.
I just want to second this. I had an article published in an IEEE journal last year, and the comments from my editor were invaluable. I also helped review a textbook this winter, and I know some of the comments resulted in big rewrites of sections.
If it is expensive to publish, then most publications would become "an organizational property" -- if you look at patents, the CEO puts his/her name even though he/she is not involved in it, and the patent will anyway be the property of the company.
With a fair number of journals, the author already pays. I am fairly certain that the author or institution has to pay for articles in the IEEE Transactions, and the ACM SIGs may be the same way. In most instances, articles are written by college researches, so the school picks up the tab.
Microsoft should just go back to the C64 days of 'What is the third word of the fifth paragraph on the fifteenth page of your EULA?'
My favorite was the decoder wheel that came with Bard's Tale III. Can you imaging having to use that every time you booted up or opened a Word document?
Dont flash cards have a maximum number of write operations? Or is that USB keys?
All FLASH devices have a limited number of write cycles. Looking at the specs for a random device shows that modern devices support over 100,000 write cycles, and I think this is per sector.
A good device driver will use various techniques, such a wear leveling, to extend the life of the device.
Assuming the poster is referring to ``variable spreading factor orthogonal frequency code division multiplexing (WSF-OFCDM) downstream technology'', the name describes exactly how the technology works. Without reading a technical paper on the technology, I don't know the exact details, but I know what it is doing and what it isn't doing.
The thing that boggles my mind about all of this is that it seems like Brown thinks or wants to convince others that Linux ``magically'' appeared in a robust form.
I started using Linux in December 1991 with version 0.11. Stable and mature aren't quite the words I would use for that version, especially when you consider that I had to reinstall it about twice a day and it didn't even have login or a proper shutdown command.
There's all the MORE hope for standards. standards that will actually be adhered to creating a sea of non-monoculture browsers, all working to a common goal, instead of one megacorp defining in secret what a browser should do.
That would be great if the vast majority of people would use them. The last time I looked, about 95% of people are using IE. Even if those numbers are off, most people use IE. That means that people have to make sure that their pages work in IE.
Standards are good. Standards that people develop to are better. Standards, no matter how good, that don't impact the majority of end-users are useless.
Me, too. I remember the Christmas when I got my first Star Wars action figures (Luke, Darth Vader, and C3PO). It was pretty much all I got since we were fairly poor at the time.
George Lucas owes all of our parents refunds for all of the merchanside they bought for us after he put out those last two horrible movies.
Thanks for the correction. Some people use the terms OFDM and COFDM interchangably, but COFDM is correct. I have only worked with DVB, and I forgot that 8VSB is used in the US.
OFDM is used for over-the-air digital TV, and it is fairly robust to nasties. A digital receiver can eliminate interference to an extent through adaptive processing, or compensate for it through FEC, but you can always get to a point where interference and/or noise will wonk a signal (eg, sun outages in geostationary satellite applications).
I can't comment on the drive controllers, since I don't know much about that area, but I know some about the other two.
As for the radar and comm hardware, I suspect that these started out on workstation hardware, and Linux made the transition to actual hardware much easier. I used to do a ton of comm simulation work, and would have loved this luxary. This would be a good fit for Linux in the embedded world, but it wouldn't surprise me if a traditional RTOS was used for the control functions.
Regarding the switch software, do you know if Linux is used at all levels of the SS7 stack, or just on the processing at the higher levels?
Slashdot Mirror
Power over ethernet?
You need enough power to make the device work, and not too much power for safety reasons. POTS already does this.
You would also need an additional pair or two to come into each house for power (10/100/1000baseT are differential which I don't think can be biased and homes are only wired with a single copper pair from pole to house), or you have to modulate the data signal and separate the power and data with a bias T (this is how the cable amps work on the pole). Telcos are very reluctant to rewire the entire country (hence DSL on existing copper).
Great. Any the next time I lose power at my house, how will I call the power company? Or 911?
Another convention is that M=10e6, and m=10e-3.
At high frequencies, the pins on a package aren't really short circuits (ie, zero resistance); they have a capactiance and inductance which mess with the signals. Making removable pins would make this a lot worse.
I wouldn't go, even if I had the bear proof suit.
I don't use my PDA anymore since I don't have a need.
My wife uses her PDA a lot since she often needs to do work in locations where she needs access to information, and using a laptop is infeasible.
My sister uses a PDA at work for easy access to reference material.
My doctor writes prescriptions from a PDA, and prints them out from a wireless printer.
I have a doctor friend who also uses a PDA at work, but I'm not sure for what.
I'm not sure if the i860 was the failure that everyone is saying it was. This may be true on the desktop, but it was a fairly popular processor in the embedded world for offloading computation.
With most cell phones, especially CDMA, power is very carefully controlled. I seriously doubt that an increase in antenna efficiency would cause problems with current installations. Basically, the phone would just input less power to the output PA and get the same EIRP. On the receiving end, it would just look like a better connection. Cell phones already know how to deal woth signals from multiple basestations.
Not really. There isn't much assembly necessary on a modern embedded platform.
Ditto. I have only really used asm in two or three places in embedded projects. One is in the initial bootloader. The second is in instances where the compiler won't do what I want. The third is to access special instructions that the compiler doesn't know about (eg, eieio on the PPC). The second and third instances can't mostly be dealt with inline asm and cpp macros, and gcc make this a lot easier if you have access to it.
What I want is for the environment on which I code to be less convoluted.
A big part of being an embedded developer is being able to adapt to different development environments and being able to develop and debug a system with minimal tools. Sometimes you have a VT100, sometimes, JTAG, other times remote debug via Ethernet. I have worked on systems where I have had to debug software with a logic analyzer because that is all that was available.
"QNX is what you trust your nuclear reactor to." Which would be rather stupid. From the license: ...
I seem to recall print ads from the early to mid 90's that showed QNX being used in a nuclear facility. I think the ad told about how they were able to update the system without taking it down because of the microkernel architecture.
Secondly, review is not *just* a moderation process, its a feedback process.
I just want to second this. I had an article published in an IEEE journal last year, and the comments from my editor were invaluable. I also helped review a textbook this winter, and I know some of the comments resulted in big rewrites of sections.
If it is expensive to publish, then most publications would become "an organizational property" -- if you look at patents, the CEO puts his/her name even though he/she is not involved in it, and the patent will anyway be the property of the company.
With a fair number of journals, the author already pays. I am fairly certain that the author or institution has to pay for articles in the IEEE Transactions, and the ACM SIGs may be the same way. In most instances, articles are written by college researches, so the school picks up the tab.
Microsoft should just go back to the C64 days of 'What is the third word of the fifth paragraph on the fifteenth page of your EULA?'
My favorite was the decoder wheel that came with Bard's Tale III. Can you imaging having to use that every time you booted up or opened a Word document?
There are a bunch of others. My favorite is PARI-GP.
Dont flash cards have a maximum number of write operations? Or is that USB keys?
All FLASH devices have a limited number of write cycles. Looking at the specs for a random device shows that modern devices support over 100,000 write cycles, and I think this is per sector.
A good device driver will use various techniques, such a wear leveling, to extend the life of the device.
Is speeding up like moving farther from your phone company's CO and using DSL? (slower speed)
The faster you are going means the Doppler effect is more pronounced. Wide Doppler ranges can be a pain to deal with in the receiver.
Who comes up with these names...
Assuming the poster is referring to ``variable spreading factor orthogonal frequency code division multiplexing (WSF-OFCDM) downstream technology'', the name describes exactly how the technology works. Without reading a technical paper on the technology, I don't know the exact details, but I know what it is doing and what it isn't doing.
The thing that boggles my mind about all of this is that it seems like Brown thinks or wants to convince others that Linux ``magically'' appeared in a robust form.
I started using Linux in December 1991 with version 0.11. Stable and mature aren't quite the words I would use for that version, especially when you consider that I had to reinstall it about twice a day and it didn't even have login or a proper shutdown command.
Do you know if Illustrator works well under Wine? I would bet that most Flash developers care more about Illustrator support that Photoshop support.
There's all the MORE hope for standards. standards that will actually be adhered to creating a sea of non-monoculture browsers, all working to a common goal, instead of one megacorp defining in secret what a browser should do.
That would be great if the vast majority of people would use them. The last time I looked, about 95% of people are using IE. Even if those numbers are off, most people use IE. That means that people have to make sure that their pages work in IE.
Standards are good. Standards that people develop to are better. Standards, no matter how good, that don't impact the majority of end-users are useless.
I am part of the original Star Wars Generation
Me, too. I remember the Christmas when I got my first Star Wars action figures (Luke, Darth Vader, and C3PO). It was pretty much all I got since we were fairly poor at the time.
George Lucas owes all of our parents refunds for all of the merchanside they bought for us after he put out those last two horrible movies.
Thanks for the correction. Some people use the terms OFDM and COFDM interchangably, but COFDM is correct. I have only worked with DVB, and I forgot that 8VSB is used in the US.
OFDM is used for over-the-air digital TV, and it is fairly robust to nasties. A digital receiver can eliminate interference to an extent through adaptive processing, or compensate for it through FEC, but you can always get to a point where interference and/or noise will wonk a signal (eg, sun outages in geostationary satellite applications).
I can't comment on the drive controllers, since I don't know much about that area, but I know some about the other two.
As for the radar and comm hardware, I suspect that these started out on workstation hardware, and Linux made the transition to actual hardware much easier. I used to do a ton of comm simulation work, and would have loved this luxary. This would be a good fit for Linux in the embedded world, but it wouldn't surprise me if a traditional RTOS was used for the control functions.
Regarding the switch software, do you know if Linux is used at all levels of the SS7 stack, or just on the processing at the higher levels?