User:Aarondabomb/PineNote Documentation - Revision history

Fxc: User article

2023-02-20T19:51:01Z

User article

← Older revision		Revision as of 19:51, 20 February 2023
Line 1:		Line 1:
	~~{{Under construction}}~~

	This space is intended to track the current status of documentation. As documentation is generated and organized in a more cohesive way, this may no longer be necessary.		This space is intended to track the current status of documentation. As documentation is generated and organized in a more cohesive way, this may no longer be necessary.

Fxc: Fxc moved page PineNote Documentation to User:Aarondabomb/PineNote Documentation: Chaotic draft

2023-01-12T21:10:32Z

Fxc moved page PineNote Documentation to User:Aarondabomb/PineNote Documentation: Chaotic draft

← Older revision

Revision as of 21:10, 12 January 2023

Hmpthcs at 20:48, 14 December 2022

2022-12-14T20:48:05Z

← Older revision		Revision as of 20:48, 14 December 2022
Line 42:		Line 42:
	=== USB ===		=== USB ===
	=== Stylus ===		=== Stylus ===

			== Software ==


			=== Stock Partition Layout ===

			As output by the [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] <code>ppt</code> (print partition) command:

			<pre>
			********Partition Info(GPT)********
			NO LBA Name
			00 00004000 uboot
			01 00006000 trust
			02 00008000 waveform
			03 00009000 misc
			04 0000B000 dtbo
			05 0000D000 vbmeta
			06 0000D800 boot
			07 00021800 security
			08 00023800 recovery
			09 00063800 backup
			10 00123800 cache
			11 00323800 metadata
			12 0032B800 super
			13 0093F800 logo
			14 00947800 device
			15 00967800 userdata
			</pre>

			In order, the partitions are:
			* <code>uboot</code>: holds the [https://en.wikipedia.org/wiki/Das_U-Boot Das U-Boot] open-source bootloader for embedded systems
			* <code>trust</code>: holds secrets such as keys; while such secrets are usually stored in NV-RAM or in a TPM, they can also be stored in a partition encrypted by a key held in a TPM
			* <code>waveform</code>: holds files specifying the voltage waveforms applied to the charged particles in the e-ink screen to manipulate them into displaying a desired image
			* <code>misc</code>: stores miscellaneous files needed by the firmware
			* <code>dtbo</code>: stores [https://en.wikipedia.org/wiki/Devicetree device tree] binary files, a description of the hardware configuration of the device
			* <code>vbmeta</code>: stores data needed for the verified boot process

			For backup, the stock partition images are available for download [https://pwarren.id.au/pinenote/partitions/ here].

			== Bootloader ==

			Without modifying the bootloader, u-boot will automatically load android. Under these circumstances, an alternative OS may be loaded by manually inputting commands to the u-boot terminal, which must be accessed by sending an interrupt signal (ctrl+c) to the device via UART during boot. Thus modifying u-boot is not, strictly speaking, necessary but will be desirable for most users wishing to use linux as their primary OS in a dual boot arrangement.

			There exists more than one approach to avoid having to do this each time the device is restarted. Two of these are detailed below.

			=== Option 1: Build U-boot from Scratch ===
			reference: https://github.com/JoshuaMulliken/pinenote_uboot

			=== Option 2: Extract and Modify Existing U-boot Image ===
			reference: https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f

Hmpthcs: /* Hardware */

2022-07-24T06:39:56Z

Hardware

← Older revision		Revision as of 06:39, 24 July 2022
Line 32:		Line 32:

	== Hardware ==		== Hardware ==
	Images and ~~diagrams~~ of the Pinenote's internals to be added		Images, diagrams and technical data of the Pinenote's internals to be added
	=== System on Chip ===		=== System on Chip ===
	=== Display ===		=== Display ===

Hmpthcs at 06:08, 24 July 2022

2022-07-24T06:08:29Z

← Older revision		Revision as of 06:08, 24 July 2022
Line 41:		Line 41:
	=== Audio ===		=== Audio ===
	=== USB ===		=== USB ===
			=== Stylus ===

Hmpthcs at 05:57, 24 July 2022

2022-07-24T05:57:30Z

← Older revision		Revision as of 05:57, 24 July 2022
Line 29:		Line 29:

	Right now, of the above personas, none of them are getting effective documentation, with hardware developers getting the most information of the bunch.		Right now, of the above personas, none of them are getting effective documentation, with hardware developers getting the most information of the bunch.


			== Hardware ==
			Images and diagrams of the Pinenote's internals to be added
			=== System on Chip ===
			=== Display ===
			=== Touch Panel ===
			=== Wacom ===
			=== Radios ===
			=== Accelerometer ===
			=== Audio ===
			=== USB ===

Rjulian: Added a few more items to needs to get done.

2022-06-12T16:20:05Z

Added a few more items to needs to get done.

@@ Line 6: / Line 6: @@
 Hopefully anyone! These are people who are thinking especially hard about this:
 * Aarondabomb
 == What needs to get done ==
@@ Line 12: / Line 13: @@
 # Create a getting started page
 # Page to more clearly describe what "the project" even is
 ## There are a number of folks doing different things. There is no cohesive effort, but what someone else accomplishes may help you, and documenting/organizing these efforts can maximize the chances for cross-pollination.

Fxc: +templ

2022-06-05T13:58:06Z

+templ

← Older revision		Revision as of 13:58, 5 June 2022
Line 1:		Line 1:
			{{Under construction}}

	This space is intended to track the current status of documentation. As documentation is generated and organized in a more cohesive way, this may no longer be necessary.		This space is intended to track the current status of documentation. As documentation is generated and organized in a more cohesive way, this may no longer be necessary.

Aarondabomb: /* What needs to get done */

2022-06-04T23:25:49Z

What needs to get done

← Older revision		Revision as of 23:25, 4 June 2022
Line 6:		Line 6:

	== What needs to get done ==		== What needs to get done ==
	# Reorganize the information that's already at [[PineNote Development]]. ~~This should give high level overview of development efforts~~		# Reorganize the information that's already at [[PineNote Development]].
	#: ~~I made~~ [[PineNote ~~Development copy~~]] ~~to draft some reorgs~~.		#: This means creating new pages, like [[PineNote: Getting Started]] that contains the important info.
	# Create a getting started page		# Create a getting started page
	# Page to more clearly describe what "the project" even is		# Page to more clearly describe what "the project" even is
	## There are a number of folks doing different things. There is no cohesive effort, but what someone else accomplishes may help you, and documenting/organizing these efforts can maximize the chances for cross-pollination.		## There are a number of folks doing different things. There is no cohesive effort, but what someone else accomplishes may help you, and documenting/organizing these efforts can maximize the chances for cross-pollination.
	~~# Pull up to date 'getting started' information together~~

Aarondabomb: /* What needs to get done */

2022-06-04T23:22:14Z

What needs to get done

← Older revision		Revision as of 23:22, 4 June 2022
Line 6:		Line 6:

	== What needs to get done ==		== What needs to get done ==
	# Reorganize the information that's already at [[PineNote Development]].		# Reorganize the information that's already at [[PineNote Development]]. This should give high level overview of development efforts
	#: I made [[PineNote Development copy]] to draft some reorgs.		#: I made [[PineNote Development copy]] to draft some reorgs.
			# Create a getting started page
	# Page to more clearly describe what "the project" even is		# Page to more clearly describe what "the project" even is
	## There are a number of folks doing different things. There is no cohesive effort, but what someone else accomplishes may help you, and documenting/organizing these efforts can maximize the chances for cross-pollination.		## There are a number of folks doing different things. There is no cohesive effort, but what someone else accomplishes may help you, and documenting/organizing these efforts can maximize the chances for cross-pollination.
	# Pull up to date 'getting started' information together		# Pull up to date 'getting started' information together