Forgot your password?
typodupeerror

Comment: Re:Wtf? (Score 1) 453

by hedley (#45303139) Attached to: 20-Somethings Think It's OK To Text and Answer Calls In Business Meetings

Take the call. The world revolves around *you*. A sense of entitlement surrounds *you*. Ideally the call should be in a disparate language to the general meeting group. Lets assume English for the meeting, then the call would be in Hebrew, French, Farsi, Cantonese etc (esp languages where speakers naturally raise their tone when in heated conversation). Don't forget to speak loudly and quickly!, cell phones have notorious connection issues, make sure the other party hears *you*!. You are *important* your ideas and thoughts have a lot of merit that need to be conveyed one-way over the handset, everyone in the room realizes that and will make allowance for *you* because of the stature you present.

Comment: Re:32 bit? (Score 1) 122

by hedley (#45128431) Attached to: Imagination Tech Announces MIPS-based 'Warrior P-Class' CPU Core

I think it stems from the initial directions each co took.

MIPS started from a 32bit Stanford grad project (MIPS-X) spun out to become the R2000 workstation class CPU. No hint of embedded arch at all at that time.
They steamed on finally hitting 64bit archs relatively quickly. Once they got to the R4K32 series and upon adding MIPS-16, they had a small footprint embedded soln but...

ARM started from basically a hobbyist computer, already with some small footprint pedigree built in. Very quickly Thumb was adopted, arch just as a translator initially but subsequently with on chip native decode. Now they have a 64bit arch, but because of their small footprint roots and aggressive licensing, they
really caught the lions share of sockets. They can now come to capture a 64bit space that was MIPS's to own years ago by osmosis of the socket market.

ARM had a first mover advantage in embedded and they executed well and did not allow competition to unseat them. It could have been different, they could have mucked up a design and lost share, but that did not happen.

Both companies have first rate tool chains also (that can be a deal killer). Thus its a wash for softies when HW pitches a design, if the license is favorable, and the die area+power draw meets managements expectations, then that vendor will get the nod for new IP. ARM has been fortunate in that there is also a bit of industry simpatico wrt ARM adoption... others are using it, so why not us?

H.

Comment: The Internet of Disposable Things (Score 1) 177

by hedley (#45086331) Attached to: Nest Protect: Trojan Horse For 'The Internet of Things'?

1) When the CO sensor exceeds 5yrs. Replace: cost $129
2) CO sensor on the ceiling. Not where CO collects
3) For the A/C model, just 2 wires, not the red 9v interconnect protocol (Firex, Kidde). Thus all alarms (n * $129) need to be installed. This cannot coexist with a legacy detector system and provide the interconnected alarm.

Pretty enclosure though and the alerts are cool (verbal and web).

I just installed 7 A/C ionization alarms @9$ each. Good for 10years all interconnected.

H.

Comment: slashdot via wired 13years ago... (Score 1) 27

by hedley (#43518065) Attached to: Walking Distance from Wired: Kevin Kelly Surveys the Tech Scene

http://slashdot.org/story/00/03/26/116210/anti-dot-com-slogans-pepper-sf

The bubble has formed obviously. A new crop of 20 somethings are at the helm, the prior 20 somethings flushed so that the new ones can stake 'first mover advantage'. With a bubble cycle of 10+ years, its essential to keep employing 20 somethings or the employees will have actual memory or working in the bubble economy. (not to mention a) most likely single b) low wages). But... its not a Ponzi scheme right? (if we could just get some more eyeballs)...

Then I read the Grove in SF on Chestnut is folding under the crippling 20k/mo rent (50% rent increase). Somethings driving up prices... wonder what? ;)

H.

Comment: On a server with an HD? (Score 1) 146

by hedley (#42757561) Attached to: Turning the Belkin WeMo Into a Deathtrap

There I was, deep in dreamland one night when, from my server room I heard a faint beeping noise at regular intervals... Groggy, I wake up, totter over to the 'server room' door (spare bedroom) and have a gander. In a groggy state it took me a moment in the dark to perceive what was going on, the APC UPS was power cycling the server and other ancillary items at a regular interval, turns out, when the battery goes south, the UPC just crowbars the AC and reboots (repeat...). Now, HD's were connected to the server and each one was cycling up for a few seconds, then spun down only momentarily etc. Terrible on spinning media. Luckily all was well in the end but its important to understand the failure modes on UPCs for your application esp if spinning media is connected.

H.

Comment: V1.0? (Score 1) 138

by hedley (#42735499) Attached to: 50 Million Potentially Vulnerable To UPnP Flaws

How many vendors are going to patch some obsolete hw to get the lib updated? I would be surprised if they can build images for some of those old products. That said, it seems a bit of an uphill crack, you have to know the target CPU, the lib version, and prepare a useful injection rather than just a denial of service. Still, it is interesting that people are still acting as documented on data coming over the wire, sprintfs into buffers with %s was an eye opener to me. These days for web stuff I use the c++ string class, fixed c buffers look weak to me with unvalidated socket input.

H.

When in doubt, mumble; when in trouble, delegate; when in charge, ponder. -- James H. Boren

Working...