meta-raspberrypi - Hardware specific BSP overlay for the RaspberryPi device

Age	Commit message (Collapse)	Author
2017-10-12	docs: Drop comment on broken raspberrypi3-64 HDMI output	Paul Barker
	Graphical output on raspberrypi3-64 should now be fixed. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-24	Support using u-boot with Image format for raspberrypi3-64	Paul Barker
	For raspberrypi3-64 we need to use the Image or Image.gz format with u-boot instead of the legacy uImage format. We also need to issue the 'booti' command to boot the kernel instead of 'bootm'. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-09-08	extra-apps.md: Document limitations of raspberrypi3-64	Khem Raj
	Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-09-01	linux-raspberrypi: Add option for disabling rpi boot logo.	Zdzisław Krajewski
	Signed-off-by Zdzisław Krajewski <zdzichucb@gmail.com>
2017-05-26	docs: Format all links correctly	Paul Barker
	Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-05-26	docs: small editorial fix	Mirza Krak
	Signed-off-by: Mirza Krak <mirza.krak@endian.se>
2017-05-26	docs: drop "Device tree support" section	Mirza Krak
	We no longer provide any Linux kernel which do not have device-tree support and all machines setup KERNEL_DEVICETREE correctly. Signed-off-by: Mirza Krak <mirza.krak@endian.se>
2017-05-26	docs: fix alignment of "code blocks"	Mirza Krak
	We provide a lot of variable examples as code blocks in the following format: some text: `Variable` or some test: `Variable` Which is not as pretty as (when converted to html/pdf): some text: Variable Converted all and hoppefully this will improve readability a bit. Signed-off-by: Mirza Krak <mirza.krak@endian.se>
2017-05-26	docs: Remove incompatible table format	Paul Barker
	Sadly sphinx doesn't support pipe tables in markdown at the minute. Let's use a bullet-point list instead. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-05-26	docs: Include readme in sphinx documentation	Paul Barker
	This allows us to avoid having to duplicate any information in the readme into another documentation file. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-05-26	docs: Initial sphinx configuration	Paul Barker
	This allows us to create documentation by running 'make html' or 'make latexpdf' in the docs directory. It depends on sphinx and the recommonmark python module (for parsing markdown files in sphinx). Creation of the PDF document requires a full LaTeX toolchain to be installed. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
2017-05-26	docs: Initial split of README into docs directory	Paul Barker
	The top-level README document has got pretty unwieldy and so we need to switch to add some more structure to our documentation. The first step is to split out sub-sections of the README document into separate files in a new 'docs' directory. Whilst splitting up the README, we can also take the opportunity to tidy things up and fix a couple of typos. Signed-off-by: Paul Barker <pbarker@toganlabs.com>