I’ve just pushed an update to the bone101 presentation up on github:
http://beagleboard.github.io/
Having a github pages representation should make it much easier for people to push patches, so I hope you’ll take this opportunity to check it all out and report/fix issues in the documentation that ships on the boards.
Now that Jekyll is being used, we won’t be able to do a simple git clone to put the content onto the boards as Jekyll will need to be run to process the content. I’ll be working with Robert to enable that operation, but would also love any hints on the best way to keep the repository on the boards something that is easily editable. Not having a macro for the baseurl was just proving too difficult.
This is also in preparation to merging a Google Summer of Code project that has the intention to make adding new tutorials to bone101 much easier. You can get some info at http://beagleboard.org/gsoc, but there will be further information coming out about it in the next few days as coding is wrapping up and documentation is being finalized.
Regards,
Jason
Jason,
The 101 page linked to through your github page still discusses the updating of the Angstrom image. With Rev C shipping with Debian, should there be two links for updating or is Angstrom no longer being updated? Additionally, the BBB spec still indicates 2MB eMMC.
Regards,
David Richards
Thanks.
Jason,
The 101 page linked to through your github page still discusses the updating
of the Angstrom image. With Rev C shipping with Debian, should there be two
links for updating or is Angstrom no longer being updated?
Angstrom continues to get updated, but there hasn't been a community
push to verify the new images and have them pushed up to
Latest Software Images - BeagleBoard. If I get sufficient requests,
I'll update that page with one of the newer Angstrom images. For now,
there is just the last Angstrom image that was used for production
images.
Additionally, the
BBB spec still indicates 2MB eMMC.
See Update for Rev C · beagleboard/bone101@49b9139 · GitHub
and let me know if this fixes it.
Jason,
The Bone 101 page has updated to reflect Rev C and 4 GB.
From this paragraph on the 101 page: See updates for the step-by-step guide.
The link to update images from the revised page http://beagleboard.github.io/Support/BoneScript/updates/
results in a page not found error.
Also, the paragraph below that still points to the Beagleboard/Angstrom page. There is no explanation of the earlier boards shipping with Angstrom nor the Rev C boards shipping with Debian and a link to an updates page.
One question regarding links from this page. When a new user connects to the board via USB, unless a wifi module has been magically installed, or, instead, the connection is over ethernet through a router, without internet connection sharing enabled on the PC, will the links not fail?
Regards,
David
Jason,
The Bone 101 page has updated to reflect Rev C and 4 GB.
From this paragraph on the 101 page: See updates
<http://beagleboard.github.io/Support/BoneScript/updates/> for the
step-by-step guide.
The link to update images from the revised page
http://beagleboard.github.io/Support/BoneScript/updates/
results in a page not found error.
Also, the paragraph below that still points to the Beagleboard/Angstrom
page. There is no explanation of the earlier boards shipping with Angstrom
nor the Rev C boards shipping with Debian and a link to an updates page.
Can you propose specific language? I'd really expected folks to feel
encouraged to send pull requests to update content.
One question regarding links from this page. When a new user connects to
the board via USB, unless a wifi module has been magically installed, or,
instead, the connection is over ethernet through a router, without internet
connection sharing enabled on the PC, will the links not fail?
If your board is plugged in via USB to the same computer or Ethernet on the
same LAN (and your computer supports mDNS), the page should auto-discover
the board. Otherwise, you can also type in the IP address of your board.