Author(s):	Julien Goodwin
Location	A1
Date	jan Wed 23	Days Raw Files
Start	16:45	First Raw Start	16:29
Duration	0:45:0	Offset	0:15:18
End	17:30	Last Raw End	17:28
Chapters	00:00 0:14:28 0:39:58
Total cuts_time	42 min.

https://2019.linux.conf.au/schedule/presentation/127/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Designing_manufacturing_a_custom_embedded_linux_machine.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	These days there’s many cheap & abundant options for embedded Linux machines, from Raspberry Pi, BeagleBone and their derivatives to dozens of more obscure options. But what if none of those options work for your use case, perhaps a needed pin is in-use by an onboard peripheral, all the existing boards with the right features are too big, or just to integrate a transceiver. In the past designing an embedded machine capable of running Linux required dealing with low-level concepts such as DRAM timing, requiring an effort more than most hobbyists or small scale commercial uses could justify. However there are now far more integrated components making this within the reach of even hobbyists. In this talk we’ll cover the design of a custom BeagleBone variant forming the core of custom NTP server project, preparing it for manufacturing, and the low-level configuration for Linux to work with this new board. markdown
Comment:	production notes