The peripherals (serial ports, sound, LCD,...) are still clocked. The core is synchronised with peripherals by peripheral bus interlocks.
This is not really any different than the way a clocked core synchronises with peripherals. These days devices like the PXA255 etc used in PDAs run independent clocks for the peripherals and the CPU. This allows for things like speed stepping to save power etc.
GPS nav is just a part of the instrumentation. You still need to be a responsible driver to use one.
As a driver you should never drive where (s)he can't see or at speeds that are uncontrollable. What if there's backed up traffic/accident? What if the road has been washed away or a kid is playing in the road?
Anyone killed by a GPS nav giving them guidance over a cliff deserves what they get. This is Darwinian selection at work (or if you believe God speaks to you via GPS, then it is ID).
Open email. If email screws up PC, then rebuild PC. Otherwise, if tit looks like a sales pitch for some nifty product like Viagra, forward email to purchasing department. Otherwise, send to BG.
I've done a lot of embedded Linux work and WinCE work, and a biut less with other RTOSs.
You're right that the price tag is not a significant influencing factor in getting embedded Linux uptake. Compared to WinCE, Linux development is **way** faster for numerous reasons. First off, the Linux code that runs on an embedded device is the same as on a PC or IBM mainframe (obviously low level driver/CPU stuff is different). This makes for better consistency. WinCE != WinNT and has different features/bugs.
Secondly, the open source means you can get in and fix/tune things when you want to instead of having to convince MS there's a problem then wait for them to fix it on their timescales. Being able to see the code helps debug problems far quicker. Theres a lot more open discussion on Linux than there is on most other OSs.
Linux build times are pretty quick. The time it takes from when I modify a line of code to having it running on a target (ie. make -> download reboot target) is only a few seconds. My WinCE builds take 20+ minutes to do the same thing. This means less builds in a day.
Linux has a bunch of v cool debug things like procfs.
These things add up to making Linux development far faster than WInCE. Some of these concepts carry across to other RTOSs too.
In application space, I will forst get an app going on a PC before tyring to get it working on an embedded device. This development is far faster and easier to debug than on a target. Having consistency of OS from host to target reduces migration issues.
These are some of the factors that make Linux cheaper, not just the price tag.
With a nice machine crunching video into edges, I guess even a 32x32 image could be useful to show the edges of sidewalks, obstructions etc. All sounds well within the scope of a PDA-level CPU.
I have quite a bit of OS development experience (written a Linux file system and numerous drivers) so I pretty much understand what is in Linux. Still, what does and does not consitute an OS is a bit blurry.
Linux is not "just a kernel" if you include all the drivers and file systems etc that go with it. Indeed the term "kernel" is hard to apply to Linux because the term only really makes sense with something like a micro-kernel architecture that has driver managers etc (eg. something like WinNT or WinCE, or Hurd).
When an application runs on Linux, it interacts directly with Linux. There is no gcc "middleware" involved. Sure GNU provides a bunch of useful (and even vital) apps, but I really struggle to see what GNU adds to the OS.
I used to have a "doctor's bag", but being an embedded developer I soon found that this bag was getting full of all kinds of other shit like serial cables, power supplies, debuggers etc.
Recently our IS department switched to good quality backpacks. These are far easier to carry around than a hand bag and hold all the extra crap well too.
Of course I'm doing something to be healthy: I drink in a sports bar, ride in a Sports Utility Vehicle, play golf on my PC and wear running shoes around the office.
Surey if the spirit is true freedom then I should be able to use it without having to GNU/everything? Why should RMS feel he has naming rights on Linux boxes? There is nothing in the GPL (the agreement) suggesting we GNU/ everything.
Stop this before it gets silly: "Announcing the GNU/Linux/Bell/GSM/Nokia 3477 phone that connects to the the DARPA/Al Gore/Internet for CERN/web browsing. The unit features a 400MHz Turing/von Neumann/Babbage/CPU and has a Faraday/battery providing 5 days of typical usage...."
A low altitude hill climb would also be far easier to clean up after, film etc, but I guess does not have the same wow factor. Most high altitude missions leave behind a huge mess. I have visions of the HAL mission leaving a trail of spent AA batteries.
If you've read anything that Linus has written on the subject you'd know that he doesn't give a monkey's anus about politics, either using Linux as a political tool or personally. Nor does he really care if people use Linux or not (ie. he is not in a Linux vs the rest ego war).
Well, duh to this research... It's pretty obvious isn't it.
Primitive brains (flies etc) are pretty much hard-wired. They don't learn a lot and are pretty much capable of 100% of full potential at birth. A fly isn't ever going anywhere special. At the other end of the spectrum is the human baby. It is almost completely helpless at birth and probably only at a percent or so if its full brain potential. The "programming" takes a long time.
Kids that take a longer time to program are possibly forming much more complex wiring.... ( or maybe they're just brain damaged:-))
Theres nothing of substance that I didn't see in the building security/access control industry over 20 years ago. The pictures show nothing new. The electronics is too big/costly to fit in a traditional bolt or such.
My hunch is that this is just one of the few similar recent releases that might kick off another dot.bomb venture captical cycle.
Words like "dominate" etc. don't work well in cyberspace. The Pentagon is all hung up on being bigger and better and stronger. Sure that works in traditional warfare where you throw things at eachother. If your throwing machine is better than the oppositions, then you can win. Having aircraft carriers makes you strong.
But look at what happens when the game is changes. A few punks go buy $20 of box cutters, hijack some planes and fly them into some buildings. There's nobody to point the aircraft carriers at.
In cyberspace it gets even harder to launch an attack. A recycles 486 running a firewall is as much security as anyone needs.
Remember (well probably most/.ers are to young) how the evil tobacco companies resisted all the studies about smoking and various illnesses. It seems like we're seeing the same with telcos and cellphone users.
I wonder whether we'll start to tobacco-style class actions etc.... the next few years will be interesting.
There does often seem to be a "if you don't like it, then leave" aapproach to problem solving. But it must be hard for people who've been in a company for a long time and want to see things get better. Anyone who's been at MS for more than 10, or maybe even as short as 5 years, must be feeling a bit down about how MS has performed over the last few years.
Here's how: Get an organisation to set up as a charity that wants some softwae developed. Programmers write code and donate this to the charity. The charity then gives the programmer a receipt for a charitable donation which can be used at tax time.
If Clinton could claim for the used underpants he gave away, why should programmers not get a break too?
There is nothing special in the water in SV that makes people more clever or anything. SV seems to be where tech money goes, so people follow the money. A bit like Hollywood and film making.
Stupid people throw their money around. This destabilises the industry. A lot of people get hurt.
About the only people that didn't get hurt were those that were able to get big wads of cash out of the system and into other havens. Don't settle for stock options that are years out. Even if the company is based on a solid business model, dot.bomb collateral damage can still wipe you out. Instead, turn your equity into tangible assets ASAP. Don't piss your money against the wall and sign up for huge expenses. That Hummer will eat your money that you might need to live through some unemployment when the dot.bomb happens again.
Slashdot Mirror
This is not really any different than the way a clocked core synchronises with peripherals. These days devices like the PXA255 etc used in PDAs run independent clocks for the peripherals and the CPU. This allows for things like speed stepping to save power etc.
ARM, followd by PowerPC, are the most common cores for embedded Linux and embedded Linux boxes far outnumber servers and desktops (where x86 rule).
As a driver you should never drive where (s)he can't see or at speeds that are uncontrollable. What if there's backed up traffic/accident? What if the road has been washed away or a kid is playing in the road?
Anyone killed by a GPS nav giving them guidance over a cliff deserves what they get. This is Darwinian selection at work (or if you believe God speaks to you via GPS, then it is ID).
Open email. If email screws up PC, then rebuild PC. Otherwise, if tit looks like a sales pitch for some nifty product like Viagra, forward email to purchasing department. Otherwise, send to BG.
You're right that the price tag is not a significant influencing factor in getting embedded Linux uptake. Compared to WinCE, Linux development is **way** faster for numerous reasons. First off, the Linux code that runs on an embedded device is the same as on a PC or IBM mainframe (obviously low level driver/CPU stuff is different). This makes for better consistency. WinCE != WinNT and has different features/bugs.
Secondly, the open source means you can get in and fix/tune things when you want to instead of having to convince MS there's a problem then wait for them to fix it on their timescales. Being able to see the code helps debug problems far quicker. Theres a lot more open discussion on Linux than there is on most other OSs.
Linux build times are pretty quick. The time it takes from when I modify a line of code to having it running on a target (ie. make -> download reboot target) is only a few seconds. My WinCE builds take 20+ minutes to do the same thing. This means less builds in a day.
Linux has a bunch of v cool debug things like procfs.
These things add up to making Linux development far faster than WInCE. Some of these concepts carry across to other RTOSs too.
In application space, I will forst get an app going on a PC before tyring to get it working on an embedded device. This development is far faster and easier to debug than on a target. Having consistency of OS from host to target reduces migration issues.
These are some of the factors that make Linux cheaper, not just the price tag.
s/nose/dick/ those split keyboards are for computer sex.
With a nice machine crunching video into edges, I guess even a 32x32 image could be useful to show the edges of sidewalks, obstructions etc. All sounds well within the scope of a PDA-level CPU.
Still, if enough states and countries do this
Linux is not "just a kernel" if you include all the drivers and file systems etc that go with it. Indeed the term "kernel" is hard to apply to Linux because the term only really makes sense with something like a micro-kernel architecture that has driver managers etc (eg. something like WinNT or WinCE, or Hurd).
When an application runs on Linux, it interacts directly with Linux. There is no gcc "middleware" involved. Sure GNU provides a bunch of useful (and even vital) apps, but I really struggle to see what GNU adds to the OS.
Recently our IS department switched to good quality backpacks. These are far easier to carry around than a hand bag and hold all the extra crap well too.
Of course I'm doing something to be healthy: I drink in a sports bar, ride in a Sports Utility Vehicle, play golf on my PC and wear running shoes around the office.
Stop this before it gets silly: "Announcing the GNU/Linux/Bell/GSM/Nokia 3477 phone that connects to the the DARPA/Al Gore/Internet for CERN/web browsing. The unit features a 400MHz Turing/von Neumann/Babbage/CPU and has a Faraday/battery providing 5 days of typical usage...."
A low altitude hill climb would also be far easier to clean up after, film etc, but I guess does not have the same wow factor. Most high altitude missions leave behind a huge mess. I have visions of the HAL mission leaving a trail of spent AA batteries.
If you've read anything that Linus has written on the subject you'd know that he doesn't give a monkey's anus about politics, either using Linux as a political tool or personally. Nor does he really care if people use Linux or not (ie. he is not in a Linux vs the rest ego war).
All the dough will go to the feds... Perhaps they'll just set up the malware vendors as the next wave of cyber munitions makers.
Primitive brains (flies etc) are pretty much hard-wired. They don't learn a lot and are pretty much capable of 100% of full potential at birth. A fly isn't ever going anywhere special. At the other end of the spectrum is the human baby. It is almost completely helpless at birth and probably only at a percent or so if its full brain potential. The "programming" takes a long time.
Kids that take a longer time to program are possibly forming much more complex wiring.... ( or maybe they're just brain damaged :-))
My hunch is that this is just one of the few similar recent releases that might kick off another dot.bomb venture captical cycle.
But look at what happens when the game is changes. A few punks go buy $20 of box cutters, hijack some planes and fly them into some buildings. There's nobody to point the aircraft carriers at.
In cyberspace it gets even harder to launch an attack. A recycles 486 running a firewall is as much security as anyone needs.
I don't think BG ever looks in the rear-view mirror at the wrecks he leaves behind. All his good works are to soften things up for the present/future.
I wonder whether we'll start to tobacco-style class actions etc.... the next few years will be interesting.
There does often seem to be a "if you don't like it, then leave" aapproach to problem solving. But it must be hard for people who've been in a company for a long time and want to see things get better. Anyone who's been at MS for more than 10, or maybe even as short as 5 years, must be feeling a bit down about how MS has performed over the last few years.
So how does one tell whether this is real or just a fabrication? I doubt the bloggers lest DNA samples.
If Clinton could claim for the used underpants he gave away, why should programmers not get a break too?
There is nothing special in the water in SV that makes people more clever or anything. SV seems to be where tech money goes, so people follow the money. A bit like Hollywood and film making.
About the only people that didn't get hurt were those that were able to get big wads of cash out of the system and into other havens. Don't settle for stock options that are years out. Even if the company is based on a solid business model, dot.bomb collateral damage can still wipe you out. Instead, turn your equity into tangible assets ASAP. Don't piss your money against the wall and sign up for huge expenses. That Hummer will eat your money that you might need to live through some unemployment when the dot.bomb happens again.