Comment by daly

Comment by daly

So you'd like a YC presentation deck? I'll call Paul Graham for a lunch meeting :-)

Point 1: I am creating an FPGA in the robot hand that learns repetitive motion which will reduce the load on the main AI. The "Learned Hand" idea is based on the human ability to "get learning into the hand", for example, doing typing or playing piano. Notice that you don't have to think "adjust the fingers to play a C chord". A similar system would allow stable walking with no AI input, including fast recovery from tripping. It self-modifies (learns) over time.

Point 2: The phone ASIC makes sense because you have a very well specified, very engineered environment that will be replicated a billion times and will never require "over the air updates". Self-driving cars and robots will need to adapt to external environments, new sensors, etc. "over the air". If you replace a robot hand you'll only needs a few seconds of training to make it repeat precise motions of the previous hand. Each hand could be factory calibrated in the FPGA to a known-good standard.

Point 3: So you believe that Musk's Terafab won't be able to make a million FPGAs? By my calculation you could fit about 128k FPGAs on a 16 inch fab wafer. So we're talking a run of about 7 wafers per million FPGAs.

Point 4a: Economics: There are very large companies that create FPGAs so there is a known market. However the TAM (total addressible market) is much larger and being held back due to high cost of initial learning (a high end development board is several thousand dollars). Reducing this cost will greatly expand the market (look at Raspberry Pi for an example).

Point 4b: Economics: FPGA programming in Verilog is not hard to learn so anyone with a clever idea could build the circuits. Making it "nearly free" (under $100) would open the TAM. Rather than the artificial paywall the company makes money licensing the designs which is how ARM got rich. Another revenue path is consulting on board design.

Point 5: Fabrication: A low-cost large LUT chip costs nearly the same as a low-cost trivial LUT chip when factoring all of the costs. Since LUTs are replicated once designed adding more LUTs to the design is a minimal cost.

Point 6a: Design: The key issue in design comes down to timing and routing. The timing tree gets larger so clock skew becomes an issue. But this can be overcome in a large FPGA by arranging clock domains so processes can run on parallel clocks, in my case one per robot finger.

Point 6b: Design: Current FPGA designs use a lot of chip real estate with wires and switching. I suggested a novel design that would first layer the routing wires and then put the LUTs in a second layer. While this will make the design and fabrication more expensive it will shrink the chip (thus more per wafer) and improve the crossbar issues. Indeed, Intel has been creating a "back of wafer" power distribution. Something similar for wire routing would be a serious breakthrough. Or even better, use the new "gate all around" technology to create "a vertical LUT" with minimal space.

Point 7: Creativitiy: Musk is putting hardware in space. You could easily create replicated FPGAs and leave them unpowered. If an FPGA fails due to radiation you switch it off and use a dark hardware replacement. If the failure is "we found a faster algorithm" you can do "over the 'air'" updates.

Point 8: As Musk would say: this is only a matter of moving atoms and electrons. There is no physical reason this can't be done.

etc. Now that I've done my part perhaps you could refute it point-by-point?

Replies daly · 15h
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.