Talk:Manufacturing data

wireless

The wireless mac number: I presume this is the only location for the MAC address: there is no mac address in the wireless logic itself? I don't believe in dupicating information that may become inconsistent. What is the format of this string? (presuming it is a string).

No, this is merely a record of the MAC address of the wireless card installed when the unit left the factory. The original MAC address of the wireless module (while changeable) is hardwired into a EEPROM in the module. It is not used by any operating software--Wad 00:24, 8 April 2010 (UTC)

locale

I'm not sure language is appropriate in the area at all. What is this going to be used for?

The software load has a default locale already, and multiple languages may be supported by a single software load. We've been working hard to not have to localize the BIOS user-interface by using iconic representations, both to avoid the manufacturing headaches and because the machines are often being used by kids/parents not yet literate.

I love these basic questions about a system that has been in use for over two and a half years! The Locale manufacturing tag is how the operating software determines its default locale at first boot. After that time, it is ignored by the operating software. This allows us to customize the default locale on a SKU/SKU basis, while using an identical operating software image.--Wad 00:27, 8 April 2010 (UTC)

Keyboard types, however, are very important to know (and while are usually related to language, they aren't necessarily a one-to-one mapping). There are actually 2 pieces to this: the physical layout of the keys (physical size and position of keyboards), of which there will be relatively few variations (but there will be some variation), and how the keys are labeled (a silkscreening like process). There will be many, many of those. But you want to have both pieces of information.

And we do: These are the KV and KL tags.

Include calibration data for "everything analog" too?

if they are tested anyway it might make sense to include:

• Calibration data for battery voltage and current measurement

Included in the EEPROM in the battery, as batteries move between laptops.

• Sensitivity/output power/frequency deviation of WLAN

Burned into the WLAN module's EEPROM at manufacturing time.

• Write speed to NAND (sorry I maybe completely off track but some internally timed flash devices exhibit an increased programming time toward end-of-life. No idea whether this would be available on the NAND used)

The write speed varies mostly on a single parameter: the rated write speed of the SD card used. This is not currently recorded anywhere, but can be directly read through Linux's SD card driver.

• Display brightness (RGB)

Huh ? OFW always restores full brightness at boot --- it is up to the operating system to recall the user's brightness setting and restore it.

• Reading of MIC input in Analog Input Mode

Why ?

• Touchpad calibration

Theoretically, this must be redone frequently. It isn't a one-time operation, and the resulting calibration information never leaves the touchpad module.

• Temperature at which the tests were performed

The factory is climate controlled (at roughly 22C and 50% RH), but the actual temperature is somewhat higher in the run-in racks.--Wad 00:35, 8 April 2010 (UTC)

Consistent date format within tags, YYYYMMDD or YYYY-MM-DD prefered?

The dates included within the tags seem to use two different date formats:

T#: 20061113-B001
SD: 14/11/2006

Please go for YYYYMMDD or YYYY-MM-DD (ISO8601). Some reasoning given there: http://www.uic.edu/depts/accc/software/isodates/index.html --Frief 08:18, 20 November 2006 (EST)

Table from Trac bug 435

Here is the table from David Woodhouse:

System SKU

B1-1

B1-2

B1-3

B1-4

B1-5

B1-6

B1-7

B1-8 (special hinge)

B1-9

1st level PN (5 in 1)

1CL1XZU0KD0

1CL1XZU0KDB

1CL1XZT0KD0

1CL1XZT0KD1

1CL1XZP0KD0

1CL1XZP0KD1

1CL1XZ-0KD0

1CL1XZ-0KD1

1CL1XZQ0KD0

1CL1XZQ0KD1

1CL1XZABKD0

1CL1XZABKD1

1CL1XZQ0KD0

1CL1XZQ0KD1

1CL1XZU0KD6

1CL1XZU0KD1

1CL1XZU0KD6

1CL1XZU0KD1

Packing

5 in 1

Single

5 in 1

Single

5 in 1

Single

5 in 1

Single

5 in 1

Single

5 in 1

Single

5 in 1

Single

5 in 1

Single

5 in 1

Single

DRAM

256

256

256

256

256

256

256

256

256

3rd level PN

31CLMB0002

31CLMB0002

31CLMB0002

31CLMB0002

31CLMB0002

31CLMB0002

31CLMB0002

31CLMB0002

31CLMB0002

K/B language

English (USA)

Portuguese

Spanish

Thai

Arabic

Hausa;Igbo

Arabic

English (USA)

English (USA)

Country

OLPC

Brazil

Argentina

Thailand

Libya

Nigeria

Palestine

OLPC

OLPC

Adaptor (Plug)

EU

US

AU

US

EU

UK

EU

US

US

Orphaned?

Checking the Orphaned pages I found this one... which doesn't seem very logical. There are 142 other 'lost' pages, some are definitely worth losing, others, I'm in no position to tell. Thought I raised the issue. --Xavi 22:16, 2 December 2006 (EST)

Maybe this page is worth losing, since I can't even edit it. That's probably why there are so many lost pages; in general all the logical places to link from have been "protected". (this "protection" is like not being able to repair the roof on a historic building) AlbertCahalan 17:53, 17 March 2007 (EDT)

I'm no position to argue if this page should be protected or not—although it seems to harbor some hard data that could prove sensitive if edited carelesly or by mistake.

Notwithstanding, an orphan page can only be de-orphaned by editing other pages, so its protected status is irrelevant... --Xavi 18:44, 17 March 2007 (EDT)

I meant that differently. This page is difficult to usefully de-orphan because so many other pages are protected. I could de-orphan it by linking it from your talk page, but that sure wouldn't be useful. I did in fact find a semi-useful place to link it from, but there were many better places that I was unable to edit. Going the other way, I can't use this page to de-orphan something else. I could copy the page to something editable, but that probably isn't so great for the quality of this wiki. Most of the protected pages have very few links to other pages, despite obvious need. I suppose you could fix the problem by handing out admin rights to all non-spammer users, but unprotecting all the pages looks like the logical solution. AlbertCahalan 21:28, 17 March 2007 (EDT)

What I don't understand is why you don't just make suggestions on the discussion pages of the protected pages when you think there are changes that should be made? --Walter 21:41, 17 March 2007 (EDT)

In linking a wiki, overall quality comes from a great number of very tiny changes. I could indeed say "under header W, Nth sentence in the Mth paragraph (currently starting with "X"), please link the word Y to article Z. I could do that hundreds or thousands of times. That would be way too tedious for me, almost certainly way too tedious for you (but I don't know your personality), and a major source of talk page pollution. There is also something unpleasant about working hard to write complicated notes that might never get noticed. AlbertCahalan 22:21, 17 March 2007 (EDT)

Make the length byte unsigned

I am new to this, but how about making the length byte unsigned, since the 8th bit of this byte is unused.

more dates?

When is the software download date (SWDL) set? Do we need an activation date as well (for warranty purposes)?

need editing instructions

Nothing is said about how to repair defective data from the "ok" prompt. People, especially developers and people doing repairs, may need to...

• add a tag with no data
• add a tag with a string
• delete a tag
• modify a tag
• list the tags

To list the tags, just do .mfg-data at the ok prompt. For tag deletion and hints at the other stuff, see the tag editing page.

AK flag

What is the rationale for adding the AK column to the keyboard table? I see the rationale for adding it to a SKU table, but it is otherwise entirely uncorrelated with keyboards. --Walter 12:52, 28 March 2008 (EDT)

When we started, the only variation between SKUs was the keyboards so the table listing SKU parameters was called the "Keyboard table". As we've grown older, we've had to support more variations in SKUs (such as different power supplies, whether the laptop has security enabled (the AK tag), and variations in touchpads (CL1 vs. CL1A). When moving to XO-1.5, this variation has increased even more (SD card size, amount of DRAM installed, etc.).--Wad 00:40, 8 April 2010 (UTC)

Page title should be "Manufacturing data" not "Manufacturing Data" (2nd word lowercase)

The wiki redirects you to the first title anyway. But internally it refers to itself by the wrong title.

You are correct, resolved with page move to "Manufacturing data" with redirect from "Manufacturing Data" cjl 03:20, 17 November 2008 (UTC)

Pashto

Pashto keyboard says "pa-olpc" under KV. Is this right? cjl 05:20, 5 January 2009 (UTC)

Wouldn't it be useful to hotlink SKU ?

Not everybody may now what this stands for. --SvenAERTS 19:56, 5 January 2014 (UTC)

I don't think it would be used. --Quozl 06:36, 6 January 2014 (UTC)