445 karma · joined November 22, 2011
Still, considering I'm paying less than a coffee per month for LTD, and personally knowing someone who was once working as a top tier developer and got into a serious biking accident that left him with brain injuries, I'm going to buy into it. Next year I'm going to push HR about that 24 month clause.
It provides me benefits from 6 months after my disability (I decided not to pay for short term which starts at 2 weeks until 6), and will keep going until I am ~65 years old.
Apple isn't custom designing the IPCores for the processor or graphics. I'm willing to bet that almost all of this chip is off the shelf stuff. What they can do is choose parameters like number of cores, cache sizes, CPU options (like you said, stuff that is available with existing suppliers) and also include additional units that they can license separately (e.g. earSmart)
The blog post mentions stuff like Frameworks and Apps. Unless I am very out of touch with SoC offerings these days, you don't get a MapKit.framework accelerator. You get things like H264 encoding/decoding and AES, or DSP functions which these frameworks can use. However, the faster performance you want with one function, the more locked in you get. An example of this is comparing encryption speeds on an Intel processor with AES-NI. AES is an order of magnitude faster than just about everything else. Everything else however, uses the same vector extension set that were designed specifically to speed up sub operations of common algorithms.
The other advantage they get by doing an in house chip is that they can choose the on board peripherals they want (possibly remove some chips that would normally be external), and the exact number of external busses they need for all the external peripherals, which can lead to a smaller, cheaper, more power efficient chip.
Where's the blink getting the timer from? What happens if I update the main PLLs? I'll refrain from making assumptions however until I can see their driver libraries. I'm hopeful, but having played around with the 1830 it's not a simple chip.
I know people have put the OpenSPARC code on FPGAs, but I don't know of any use in industry in FPGAs or ASICS. I'd be interested if anybody knows any.
A COTS implementation would be interesting. Securing SSL keys would require very quick public key crypto and probably a PCI-E interface to talk to the server, the PCI-E interface making it much more expensive (FPGAs with PCI-E hard blocks have gone down in price, but are by no means cheap, not to mention the increased cost of the PCB). Prototypes probably wouldn't need VC for a proof of concept, but after that you typically need to put up a bit of money for any manufacturing.
I'd be interested in a way to securely generate and store a Root CA certificate and sign other keys with it. Ideally using something like secret sharing so that no single person can access the Root CA as well without having n out of m people.
Probably means nothing however. I doubt that anybody with the ability to get into the system would want to get only developer certificates.
grep -E "Revocation Date: Jul 17 .{8} 2013" wwdrccrl.txt | wc -l
3065
grep -E "Revocation Date: Jul 18 .{8} 2013" wwdrccrl.txt | wc -l
2289
grep -E "Revocation Date: Jul 19 .{8} 2013" wwdrccrl.txt | wc -l
2
grep -E "Revocation Date: Jul 20 .{8} 2013" wwdrccrl.txt | wc -l
0
grep -E "Revocation Date: Jul 21 .{8} 2013" wwdrccrl.txt | wc -l
0
These are the two certificates that were revoked on the 19th grep -A 3 -B 1 -E "Revocation Date: Jul 19 .{8} 2013" wwdrccrl.txt
Serial Number: 2628C7F90970D227
Revocation Date: Jul 19 03:14:04 2013 GMT
CRL entry extensions:
X509v3 CRL Reason Code:
Key Compromise
--
Serial Number: 1A51ABFA4844BD45
Revocation Date: Jul 19 03:24:03 2013 GMT
CRL entry extensions:
X509v3 CRL Reason Code:
Key Compromise
To generate the wwdrccrl.txt file I used: openssl crl -inform DER -text -noout -in wwdrca.crl > wwdrccrl.txt
Just to be clear -- every entry there I see lists the reason as Key Compromise, just interesting that they usually seem to revoke at least 2000 certificates a day but suddenly stopped on the 19th with just revoking 2.I wonder where the CRL for the dev certificates is -- we might see an update to it soon.
Cool to think that that waste function can still compile with todays compilers. A quick disassembly it seems to take up 751 bytes compiled on x64 using clang on O0.
init(s, t)
char s[]; {
would be equivalent to: int init(char s[], int t) {
This still works with modern compilers.I'd be interested if anyone has any more info about this:
waste() /* waste space */
{
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
waste(waste(waste),waste(waste),waste(waste));
}
Found in last1120c/c10.c Python 3.2.3 (default, Oct 19 2012, 20:10:41)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import re
>>> re.match(r'\d', '੧')
<_sre.SRE_Match object at 0x7f188f6d4850>With the most advanced fab technologies there's a much smaller number of companies that can both afford the initial capital investment (these plants are _insanely_ expensive) and the engineering expertise / tools to even design at these processes. Meanwhile, the $3 microcontroller I buy that runs as 12mhz fits every requirement I have while being manufactured at a cheaper, but much larger process. The high end processors and FPGAs however, benefit much more from smaller feature sizes (and those FPGAs cost accordingly).
As far as I know, when these 4 companies make advancements, the entire industry benefits. For example, Nikon comes out with a more advanced stepper for 14nm processes, Intel is the one paying the premium for them, and later the rest of the industry can benefit from a more reliable 65/45/32nm process after the cutting edge companies have moved on. I believe this is true for the EDA tool space as well.
The last paragraph is a bit of speculation on my part. I'm not in the semiconductor field but I know a bit about it, and logically it makes sense for tools / equipment. It does not include things like internal knowledge about manufacturing reliably on a certain process however.
Now, for most hobbyist designs the rule of thumb is use a simple LDO and the recommended input/output caps (1-10uF) for it and use wide traces to route the power in a star like fashion. Also put a 100nF capacitor next to each power pin for noise and to serve as a power reserve.
More complicated circuits / circuits that will need to go through FCC will require more complicated power distributions. Most professional boards (with high frequency signals on it) that will meet FCC will be 4+ layers, with a dedicated ground and power planes. A PCB I just designed with an FPGA on it had something like 50 capacitors for just the 1 chip, with physical size requirements for each type (the smallest capacitors were 1mm x 0.5mm to block the highest frequency noise, anything bigger won't be as effective).
Don't let this deter you however, looking back on my first schematic/PCB designs I'm amazed at how much better I've gotten. Microcontroller designs with a few chips are very, very lenient. If you mess something up it will likely still work, but your performance won't be as good (i.e. if you use a built in ADC it may not be as accurate, or you might not be able to reliable run it at it's max clock speed)
1 nit pick, I think wherever you use a wire assignment you need the assign keyword. e.g
wire [1:0] command = mem_out[7:6];
wire [2:0] destination_addr = mem_out[6:3];
wire [2:0] source_addr = mem_out[2:0];
should be assign wire [1:0] command = mem_out[7:6];
assign wire [2:0] destination_addr = mem_out[6:3];
assign wire [2:0] source_addr = mem_out[2:0];
Or maybe it's wire assign. I usually first declare the wire in a single statement then use assign on a new line. else if($.isNumeric(arg)
There's no native JavaScript equivalent to it if I recall correctly, but there's a bunch of alternatives to it as well.It should be easy enough to extract out the logic and repackage it. Maybe I'll fork it tomorrow and do the changes myself.
They're probably doing a single stream to CDNs which then fan them out.
I'd be curious if there exists such a company or even any good open source libraries that can tie into other servers.
8b/10b has exactly 25% overhead, this is the difference between baud per second (what the line is capable of transmitting, which is on the 10b side), and bits per second (which is the decoded 8b data). If you have a 10kilobaud/second line, you'll have an effective data rate of 8kbit/second.
Encryption is done before the encoding stage, the encoding scheme doesn't care and isn't affected by the encryption.
(require 'package)
(dolist (source '(("technomancy" . "http://repo.technomancy.us/emacs/)
("elpa" . "http://tromey.com/elpa/)))
(add-to-list 'package-archives source t))
(package-initialize)
(defvar my-packages '(starter-kit zenburn-theme auctex color-theme-solarized csharp-mode ecb_snap find-file-in-project flymake-css flymake-php idle-highlight ido-ubiquitous ipython python-mode magit markdown-mode paredit pastels-on-dark-theme php-mode rainbow-mode smex solarized-theme starter-kit-js zenburn-theme)
"A list of packages to ensure are installed at launch.")
(dolist (p my-packages)
(when (not (package-installed-p p))
(package-install p)))
Where you add the package name to my-packages. It's kinda cool to see it download and compile everything on a new install.The [next word + register] instruction is also a bit annoying to deal with in the given time tables and a simple register file design, though I haven't thought about the design of that too much.
At this point however I became so used to the virtual keyboard on my iPhone that I doubt I would get any speed increases by switching to morse code. The only reason why it would be more convenient is to ensure typing accuracy when not looking at the phone.