KernelOFirmwareReport
|
⇤ ← Revision 1 as of 2011-02-16 16:39:08
Size: 2217
Comment:
|
← Revision 2 as of 2011-02-16 16:59:09 ⇥
Size: 2772
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| * '''Launchpad Entry''': UbuntuSpec:foo * '''Created''': |
* '''Launchpad Entry''': https://blueprints.launchpad.net/ubuntu/+spec/kernel-o-firmware-reporter * '''Created''': |
| Line 6: | Line 6: |
| * '''Packages affected''': | * '''Packages affected''': fwts |
| Line 10: | Line 10: |
| Discuss creation of a central repository for information about firmware (BIOS) errors as detected by the firmware test suite. Users of the fwts would be able to report results by running an optional command line argument such as --report-info. The central repository would store no personal user information. Information would include: Computer model number, BIOS version, and test results would be reported and stored. The web interface could be very simple, listing known bugs in bios versions. Where multiple versions of a BIOS are reported for a platform, the site could show which fwts errors have been resolved by the update. fwts could use this information when running tests to report to the user whether a later BIOS has been seen in the field which resolves the problem. If the site allows user registration, users could be emailed when BIOS updates for their machine are detected. BIOS reporting could be integrated with Landscape through the use of this data. |
|
| Line 12: | Line 26: |
| This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) It is mandatory. |
The fwrs (firmware reporting site) maintains information about BIOS versions encountered in the field and any errors in them which are detected by the Firmware Test Suite (fwts). It allows searching by computer model number and will display all BIOS versions for that platform which have been reported. This information may be helpful in resolving various problems including those with suspend/resume, CPU frequency scaling, audio, and video. |
| Line 24: | Line 36: |
| You can have subsections that better describe specific parts of the issue. |
|
| Line 27: | Line 37: |
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: |
|
| Line 32: | Line 40: |
| Should cover changes required to the UI, or specific UI that is required to implement this |
|
| Line 36: | Line 42: |
| Code changes should include an overview of what needs to change, and in some cases even the specific details. === Migration === Include: * data migration, if any * redirects from old URLs to new ones, if any * how users will be pointed to the new way of doing things, if necessary. |
Launchpad Entry: https://blueprints.launchpad.net/ubuntu/+spec/kernel-o-firmware-reporter
Created:
Contributors:
Packages affected: fwts
Summary
Discuss creation of a central repository for information about firmware (BIOS) errors as detected by the firmware test suite. Users of the fwts would be able to report results by running an optional command line argument such as --report-info.
The central repository would store no personal user information. Information would include:
Computer model number, BIOS version, and test results would be reported and stored.
The web interface could be very simple, listing known bugs in bios versions. Where multiple versions of a BIOS are reported for a platform, the site could show which fwts errors have been resolved by the update.
fwts could use this information when running tests to report to the user whether a later BIOS has been seen in the field which resolves the problem.
If the site allows user registration, users could be emailed when BIOS updates for their machine are detected.
BIOS reporting could be integrated with Landscape through the use of this data.
Release Note
The fwrs (firmware reporting site) maintains information about BIOS versions encountered in the field and any errors in them which are detected by the Firmware Test Suite (fwts). It allows searching by computer model number and will display all BIOS versions for that platform which have been reported. This information may be helpful in resolving various problems including those with suspend/resume, CPU frequency scaling, audio, and video.
Rationale
User stories
Assumptions
Design
Implementation
UI Changes
Code Changes
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
KernelTeam/Specs/KernelOFirmwareReport (last edited 2011-02-16 16:59:09 by user-69-73-1-154)