path: root/serprog-protocol.txt
diff options
authorUwe Hermann <>2010-03-25 23:18:41 +0000
committerUwe Hermann <>2010-03-25 23:18:41 +0000
commit4e3d0b3a244067debc0c250986bf65bc2bc182ea (patch)
tree7e311c929ef697a3781145bc2cea68359deb2794 /serprog-protocol.txt
parentd4e5359372a6dc5facb2ea142358508fa058cf68 (diff)
Polish the flashrom code comments and outputs a bit
- Fix a number of typos (found via ispell). - Use correct vendor names (as per their websites) consistently. Corresponding to flashrom svn r985. Signed-off-by: Uwe Hermann <> Acked-by: Uwe Hermann <>
Diffstat (limited to 'serprog-protocol.txt')
1 files changed, 2 insertions, 2 deletions
diff --git a/serprog-protocol.txt b/serprog-protocol.txt
index 0d389e6..c5464a4 100644
--- a/serprog-protocol.txt
+++ b/serprog-protocol.txt
@@ -46,14 +46,14 @@ Additional information of the above commands:
cmd 7 support: byte 0 bit 7
cmd 8 support: byte 1 bit 0, and so on.
0x04 (Q_SERBUF):
- If the programmer has guaranteedly working flow control,
+ If the programmer has a guaranteed working flow control,
it should return a big bogus value - eg 0xFFFF.
0x05 (Q_BUSTYPE):
The bit's are defined as follows:
bit 0: PARALLEL, bit 1: LPC, bit 2: FWH, bit 3: SPI (if ever supported).
0x06 (Q_CHIPSIZE):
Only applicable to parallel programmers.
- An LPC/FHW/SPI-programmer can report this as not supported in the command bitmap.
+ An LPC/FWH/SPI-programmer can report this as not supported in the command bitmap.
If a programmer reports a bigger maximum write-n length than the serial buffer size,
it is assumed that the programmer can process the data fast enough to take in the
OpenPOWER on IntegriCloud