Bugzilla – Bug 12418
Add ability to remember case color
Last modified: 2010-05-27 14:20:21 UTC
Maybe use the 8-level id?
It would be cool if this could come from the bar code. -dean On Jun 17, 2009, at 12:07 PM, bugs@bugs.slimdevices.com wrote: > https://bugs-archive.lyrion.org/show_bug.cgi?id=12418 > > Summary: Add ability to remember case color > Product: Baby > Version: unspecified > Platform: PC > OS/Version: Windows XP > Status: NEW > Severity: normal > Priority: -- > Component: Bootloader > AssignedTo: richard@slimdevices.com > ReportedBy: richard@slimdevices.com > CC: dean@slimdevices.com > > > Maybe use the 8-level id? > > -- > Configure bugmail: https://bugs-archive.lyrion.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug.
So I want to suggest something different to remember the baby case color, that means I don't need to do any work (other than write this email) :) . At the moment we remember three things in the bootloader: - mac address - uuid - board_serial The board serial is currently defined as: board_serial is formatted as follows: DDMM-YYbd-idAB-CDEF where DDMM-YY are the production DateMonth-Year 0512-08 => 05-12-2008 bd-id are the board ID 00-01 => 0001 AB-CDEF are the last half of the MAC 08-0512 => 0x08:0x05:0x12 David and myself made this up for fab4, but you can see that both the board id (that's hardcoded in the bootloader) and the mac address are duplicated in here. It makes some sense to keep a slot for the board id here, so allow this to be set and not hardcoded in the bootloader. But we don't need the mac address duplicated, so why not use "AB-CDEF" in the board id for other information like the case color. Whenever this was discussed I suggested using the Agile id (8 level I think) to store the case color, but everyone seemed to hum and arr about that. Thinking about it that would also make it harder to use, as we would need a table in the firmware for every 8 level id produced. I'm not sure how often that's changed, but it might not be practical tracking that. So my suggestion is: - On future fab4 builds, keep that as "00:00:00" - On baby builds, use "00:00:0X" where X==00 is black, X==01 is red This information is then easily available in /proc/cpuinfo.
David, these bugs came up during the bug meeting. Is there any update on them? Thanks!
Ping David. Does this still need to be open?
ping David, just tell us the status, thanks!
I talked to David and he reports this is implemented and appears to be working. Since this is a factory/process bug, I'd like to wait until we see some MP units before I mark this closed.
Rearranging Radio bug 'Components' in Bugzilla