thanks for the explanation.Now I get it. What you explain (making a yun with a wifi router) is what I did with a linksys and a mega before yun existed.I'm probably lazy but I prefer a ready made package. As a shield fits on top of a arduino there is no way to beat the "size" and "build-in" characteristics.
Quote from: Jantje on Jul 31, 2014, 09:24 amthanks for the explanation.Now I get it. What you explain (making a yun with a wifi router) is what I did with a linksys and a mega before yun existed.I'm probably lazy but I prefer a ready made package. As a shield fits on top of a arduino there is no way to beat the "size" and "build-in" characteristics.With a "built-in" package, you are limited to a 32U4 And you can certainly beat the "size" characteristic by using a mini or micro board
Even better, on the same Linino Arduino Yùn page (http://www.linino.org/modules/yun/), there is a PDF file http://www.linino.org/wordpress/wp-content/uploads/2014/02/Arduino-Yun-V4-Schematic.pdf with the label "Arduino Yun R4 Schematic (pdf)". Its frame contains a date "Friday, February 28, 2014", so it looks like it is newer indeed and corresponds to the Arduino Yùn R4 design. There is an item "Arduino Yun R4 Gerber (pdf)", but no link to download And you can't trust this schematic anyway, as my board has 3 buttons ("32U4 RST", "YUN RST" and "WLAN RST"), but I only see 2 in the schematic ("32U4 Reset" and "USER BUTTON")!
Sorry to respond to this at a late date, but I was doing some follow up reading as a result of the article on Hackaday. I suggest you look at this schematic again... as I can quite clearly see three button. 32U4 Reset in the middle, and a user button and reset button linked to the wifi module on the left. So if that is the sole reason for discounting this schematic as valid, you might want to take another look at it.
However, as a Arduino supporter, I am very disappointed that documentation of even this level is present on the website. I would however suggest that you consider emailing the developers mailing list to see what documentation is available, and to discuss this further.