From 0e3520f74d25bc43572a1afeaa4439bfedcc0d78 Mon Sep 17 00:00:00 2001 From: Francis Rowe <info@gluglug.org.uk> Date: Sun, 28 Jun 2015 02:20:19 +0100 Subject: s/machine/system It was annoying me. --- docs/future/index.html | 10 +++++----- docs/future/old.html | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) (limited to 'docs/future') diff --git a/docs/future/index.html b/docs/future/index.html index d39f8a9d..df677970 100644 --- a/docs/future/index.html +++ b/docs/future/index.html @@ -141,7 +141,7 @@ </p> <p> - Run that tool (resources/utilities/i945gpu/intel-regs.py) as root on machines with the offending panels in: + Run that tool (resources/utilities/i945gpu/intel-regs.py) as root on systems with the offending panels in: </p> <ul> <li>Coreboot (or libreboot, whatever) with VBIOS (disable native graphics also)</li> @@ -286,8 +286,8 @@ f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ Before each test run, boot a live USB and delete the old logs in /var/log (kernel log, xorg log, dmesg and so on). </p> <p> - Load (from the ROM) the runningvga.bin for each LCD panel on each machine; do not execute it, only load it! (coreboot will have to be modified). - Rename the ROM appropriately, based on the machine name and the panel name. coreboot_nativegfx_5868_plusrunningvga_t60_14_LTD141ECMB.rom, + Load (from the ROM) the runningvga.bin for each LCD panel on each system; do not execute it, only load it! (coreboot will have to be modified). + Rename the ROM appropriately, based on the system name and the panel name. coreboot_nativegfx_5868_plusrunningvga_t60_14_LTD141ECMB.rom, for instance. Keep a copy for later use. </p> @@ -299,7 +299,7 @@ f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ <p> With each boot, make notes about what you see and get logs using the <a href="#standard_test">standard test</a>. - You will need the files from <a href="#intelvbttool_results">#intelvbttool_results</a> for each machine. + You will need the files from <a href="#intelvbttool_results">#intelvbttool_results</a> for each system. </p> Results (# means untested): @@ -418,7 +418,7 @@ f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ </p> <p> - Backup both files (runningvga.bin and intelvbttool_out), renaming them to match the machine and LCD panel used. + Backup both files (runningvga.bin and intelvbttool_out), renaming them to match the system and LCD panel used. <a href="../misc/index.html#get_edid_panelname">../misc/index.html#get_edid_panelname</a> will show you how to get the name (model) of the LCD panel used. </p> diff --git a/docs/future/old.html b/docs/future/old.html index 950e2c43..42db7188 100644 --- a/docs/future/old.html +++ b/docs/future/old.html @@ -80,7 +80,7 @@ Reading <b>0xe4361254</b> (address) in Lenovo BIOS always yields FFFFFFFF, even when writing to it (and writing to it doesn't affect brightness controls). 'mtjm' on IRC found that the buttons (Fn keys) control /sys/class/backlight/acpi_video0 which has no affect on 61254 (BLC_PWM_CTL). He says intel_backlight has different values and uses the register. devmem2 works, needs checking <b>lspci -vv</b> for where the memory is mapped, - which is different than on coreboot; mtjm found that it was 0xec061254 on his machine (X60 Tablet), and the register value is different too. + which is different than on coreboot; mtjm found that it was 0xec061254 on his system (X60 Tablet), and the register value is different too. <b>This is relevant, because we still don't know how backlight controls are actually handled. We got it working by accident. We need to know more.</b>. </p> <p> @@ -225,7 +225,7 @@ <p> <b> The replay code is obsolete (see 5320 changeset on review.coreboot.org for better version - which supports more machines/screens, and then 5345 for T60). Information here for reference since that is where the fix was first applied. + which supports more systems/screens, and then 5345 for T60). Information here for reference since that is where the fix was first applied. </b> </p> -- cgit v1.2.3-70-g09d2