N900 Hardware Subsystems - Revision history

imported_>sixwheeledbeast: Protected "N900 Hardware Subsystems": Excessive vandalism ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2018-03-24T23:45:44Z

Protected "N900 Hardware Subsystems": Excessive vandalism ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

← Older revision	Revision as of 23:45, 24 March 2018
(No difference)

imported_>sixwheeledbeast: Reverted edits by 93.124.84.147 (Talk) to last revision by joerg_rw

2018-03-24T23:38:47Z

Reverted edits by 93.124.84.147 (Talk) to last revision by joerg_rw

@@ Line 85: / Line 85: @@
 ====Camera cover====
-http://achat-cialis-generique.net/ cialis pas her
+===Keyboard===
-http://commandercialisgenerique.net/ acheter cialis generique
+Matrix keyboard connected to row[7:0] x col[7:0] dedicated matrixscanner IO at GAIA.
-http://comprar-cialis-generico.net/ comprar cialis
-http://acquistarecialisitalia.net/ cialis ricetta medica
+All QCOL traces and QROW7 trace are equipped with ESD protection against static discharge.
 ===Proximity sensor===

93.124.84.147: commander cialis generique

2018-03-24T18:11:49Z

commander cialis generique

@@ Line 85: / Line 85: @@
 ====Camera cover====
-===Keyboard===
+http://achat-cialis-generique.net/ cialis pas her
-Matrix keyboard connected to row[7:0] x col[7:0] dedicated matrixscanner IO at GAIA.
+http://commandercialisgenerique.net/ acheter cialis generique
+http://comprar-cialis-generico.net/ comprar cialis
-All QCOL traces and QROW7 trace are equipped with ESD protection against static discharge.
+http://acquistarecialisitalia.net/ cialis ricetta medica
 ===Proximity sensor===

imported_>joerg_rw: /* Keyboard */ table-ize

2016-08-21T18:09:55Z

Keyboard: table-ize

← Older revision		Revision as of 18:09, 21 August 2016
Line 91:		Line 91:

	Each switch under a key is connected to one col and one row trace		Each switch under a key is connected to one col and one row trace
	~~<pre>~~
	(QCOL-> ~~7 6 5 4 3 2 1 0~~)		{\| class="wikitable" border=1
	QROW7: VOL- VOL+ I		!(QCOL->!! __7__ !! __ 6__ !! __5__ !! __4__ !! __3__ !! __ 2__ !! __1__ !! __0_)
	QROW6: U		\|-
	QROW5: Y		\|QROW7: \|\| \|\| \|\| \|\| \|\| \|\| VOL- \|\| VOL+ \|\| I
	QROW4: Shft Fn CTRL Rght Down T		\|-
	QROW3: Left SPC M N B V R		\|QROW6: \|\| \|\| \|\| \|\| \|\| \|\| \|\| \|\| U
	QROW2: C X Z CR Up . E		\|-
	QROW1: L K J H G F D W		\|QROW5: \|\| \|\| \|\| \|\| \|\| \|\| \|\| \|\| Y
	QROW0: S A Del , P O Q		\|-
	~~</pre>~~		\|QROW4: \|\| \|\| Shft\|\| Fn \|\| CTRL\|\| \|\| Rght \|\| Down \|\| T
			\|-
			\|QROW3: \|\| Left\|\| \|\| SPC \|\| M \|\| N \|\| B \|\| V \|\| R
			\|-
			\|QROW2: \|\| C \|\| X \|\| Z \|\| \|\| CR \|\| Up \|\| . \|\| E
			\|-
			\|QROW1: \|\| L \|\| K \|\| J \|\| H \|\| G \|\| F \|\| D \|\| W
			\|-
			\|QROW0: \|\| S \|\| A \|\| \|\| Del \|\| , \|\| P \|\| O \|\| Q
			\|}

	For example pressing W connects QCOL0 to QROW1.<br>		For example pressing W connects QCOL0 to QROW1.<br>
	The matrix controller applies a certain level (say +3V) to first col QCOL0 and checks which rows are going to same level (QROW1 for 'W'). Then next col is the one to get +3V, and so on.		The matrix controller applies a certain level (say +3V) to first col QCOL0 and checks which rows are going to same level (QROW1 for 'W'). Then next col is the one to get +3V, and so on.

188.195.163.148: /* Touchscreen */

2014-01-05T21:46:04Z

Touchscreen

← Older revision		Revision as of 21:46, 5 January 2014
Line 69:		Line 69:
	===Touchscreen===		===Touchscreen===

	The touch screen controller is a TSC 2005.		The touch screen controller is a [http://www.ti.com/product/tsc2005 TSC 2005].

	===Accelerometer===		===Accelerometer===

imported_>joerg_rw: /* Keyboard */

2011-07-15T13:23:05Z

Keyboard

← Older revision		Revision as of 13:23, 15 July 2011
Line 119:		Line 119:
	Looking at this matrix, we notice two things:<br>		Looking at this matrix, we notice two things:<br>
	1: Nokia missed to give real dedicated col-lines to the qualifier keys, though there would have been plenty, by simply arranging the keys in matrix in a smarter way. That would have completely avoided the above described N-key rollover issue<br>		1: Nokia missed to give real dedicated col-lines to the qualifier keys, though there would have been plenty, by simply arranging the keys in matrix in a smarter way. That would have completely avoided the above described N-key rollover issue<br>
	Another common method to fix this problem is to use diodes in series with the key switches. A diode for Ctrl, Shift, and Fn would be just enough here, adding to the BOM with only 3 parts a 2ct each.		Another common method to fix this problem is to use diodes in series with the key switches. A diode for Ctrl, Shift, and Fn would be just enough here, adding to the BOM with only 3 parts a 2ct each.<br>
	2: U has its own row, and U is used for flashing (USB-flashing mode). Coincidence?		2: U has its own row, and U is used for flashing (USB-flashing mode). Coincidence?
	Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO		Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO

imported_>joerg_rw: /* Keyboard */

2011-07-15T13:21:15Z

Keyboard

← Older revision		Revision as of 13:21, 15 July 2011
Line 88:		Line 88:
	Matrix keyboard connected to row[7:0] x col[7:0] dedicated matrixscanner IO at GAIA.		Matrix keyboard connected to row[7:0] x col[7:0] dedicated matrixscanner IO at GAIA.

	All QCOL and QROW7 ~~traces~~ are ~~eqipped~~ with ESD protection against static discharge		All QCOL traces and QROW7 trace are equipped with ESD protection against static discharge.

	Each switch under a key is connected to one col and one row trace		Each switch under a key is connected to one col and one row trace
	<pre>		<pre>
Line 118:		Line 119:
	Looking at this matrix, we notice two things:<br>		Looking at this matrix, we notice two things:<br>
	1: Nokia missed to give real dedicated col-lines to the qualifier keys, though there would have been plenty, by simply arranging the keys in matrix in a smarter way. That would have completely avoided the above described N-key rollover issue<br>		1: Nokia missed to give real dedicated col-lines to the qualifier keys, though there would have been plenty, by simply arranging the keys in matrix in a smarter way. That would have completely avoided the above described N-key rollover issue<br>
			Another common method to fix this problem is to use diodes in series with the key switches. A diode for Ctrl, Shift, and Fn would be just enough here, adding to the BOM with only 3 parts a 2ct each.
	2: U has its own row, and U is used for flashing (USB-flashing mode). Coincidence?		2: U has its own row, and U is used for flashing (USB-flashing mode). Coincidence?
	Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO		Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO

89.27.110.196: Imagination Technologies is a fabless IP company.

2010-08-09T18:28:05Z

Imagination Technologies is a fabless IP company.

← Older revision		Revision as of 18:28, 9 August 2010
Line 30:		Line 30:
	==Video==		==Video==

	The GPU is a SGX530 ~~manufactured by~~ Imagination Technologies.		The GPU is a SGX530 licensed from Imagination Technologies.

	===Display===		===Display===

imported_>joerg_rw: /* Keyboard */

2010-08-08T22:56:17Z

Keyboard

← Older revision		Revision as of 22:56, 8 August 2010
Line 118:		Line 118:
	Looking at this matrix, we notice two things:<br>		Looking at this matrix, we notice two things:<br>
	1: Nokia missed to give real dedicated col-lines to the qualifier keys, though there would have been plenty, by simply arranging the keys in matrix in a smarter way. That would have completely avoided the above described N-key rollover issue<br>		1: Nokia missed to give real dedicated col-lines to the qualifier keys, though there would have been plenty, by simply arranging the keys in matrix in a smarter way. That would have completely avoided the above described N-key rollover issue<br>
	2: U has its own row, and U is used for flashing (USB-flashing mode). ~~Incidence~~?		2: U has its own row, and U is used for flashing (USB-flashing mode). Coincidence?
	Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO		Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO

imported_>joerg_rw: /* Keyboard */

2010-08-05T02:38:05Z

Keyboard

← Older revision		Revision as of 02:38, 5 August 2010
Line 120:		Line 120:
	2: U has its own row, and U is used for flashing (USB-flashing mode). Incidence?		2: U has its own row, and U is used for flashing (USB-flashing mode). Incidence?
	Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO		Let's assume Nokia EE thought (for whatever weird reason) it might be clever to have a dedicated row for U (so they just pull high QCOL0 in NOLO bootloader and check the 8 row lines by reading in that byte). Then we might start to wonder what's with Y. And with I? And with T R W E Q? Nota bene press&hold multiple of those keys will always still deliver a nice clean easy-to-read 8bit result, on the presumed test during boot in NOLO

			(p.s: maybe the rows are driven high - or even low - and the cols are the sensing inputs. I've not checked this, as it doesn't change anything in the basic function principle and neither changes the problem with N-key rollover. For the NOLO speculations it makes more sense to have inputs on rows and drivers on cols, though)

	====Keyboard Slide====		====Keyboard Slide====