diff options
Diffstat (limited to 'docs/future')
| -rw-r--r-- | docs/future/index.md | 46 | ||||
| -rw-r--r-- | docs/future/old.md | 26 |
2 files changed, 36 insertions, 36 deletions
diff --git a/docs/future/index.md b/docs/future/index.md index 9e869925..7dd031fa 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -74,8 +74,8 @@ Apparently, only 8MB VRAM is available on i945 GPUs (though it could do 64MB):\ phcoder: No. Hardware default is 8 MiB. When I wanted to make it configurable, I saw that docs mention only one other alternative: 1MiB. -Later isn\'t event enough for 1024x768 at 24bpp without any acceleration -or double buffering. It\'s possible that there are undocumented values. +Later isn't event enough for 1024x768 at 24bpp without any acceleration +or double buffering. It's possible that there are undocumented values. Which options do you have in vendor BIOS? How to find out how much vram you have:\ phcoder: TOM - BSM\ @@ -85,9 +85,9 @@ phcoder: not accorging to doc.\ phcoder: see mobile-945-express-chipset-datasheet page 93\ phcoder: see also src/northbridge/intel/i945/{early\_init,northbridge,gma}.c\ -vimuser: \"011 = DVMT (UMA) mode, 8 MB of memory pre-allocated for\ -vimuser: frame buffer.\"\ -vimuser: \"Others - reserved\"\ +vimuser: "011 = DVMT (UMA) mode, 8 MB of memory pre-allocated for\ +vimuser: frame buffer."\ +vimuser: "Others - reserved"\ phcoder: the easiest way is a loop at this position which tries different values and reads (and prints) BSM with them\ stefanct: vimuser: they suggest that you change the value and look how @@ -147,7 +147,7 @@ Original getregs.py script can be found at Masłowski. About fixing remaining LCD panels on 5345:\ -\'polarity\' is mentioned in coreboot log (cbmem -c). compare output +'polarity' is mentioned in coreboot log (cbmem -c). compare output (with working and non-working panel). (and see the other notes in docs/future/) @@ -240,7 +240,7 @@ i945 gfx: X60/T60 VBT implementation (experimental: testing) {#i945_vbt} intel\_bios\_dumper in intel-gpu-tools seems interesting. -**Use \'drm.debug=0x06\' kernel parameter when booting in grub!** +**Use 'drm.debug=0x06' kernel parameter when booting in grub!** Before each test run, boot a live USB and delete the old logs in /var/log (kernel log, xorg log, dmesg and so on). @@ -272,28 +272,28 @@ Results (\# means untested): - BOE-Hydis HV121X03-100: \# - **X60T SXGA+:** - BOE-Hydis HV121P01-100: \# -- **T60 14\" XGA:** +- **T60 14" XGA:** - Samsung LTN141XA-L01: \# - CMO N141XC: \# - BOE-Hydis HT14X14: \# - TMD-Toshiba LTD141ECMB: \# -- **T60 14\" SXGA+** +- **T60 14" SXGA+** - TMD-Toshiba LTD141EN9B: \# - Samsung LTN141P4-L02: \# - Boe-Hydis HT14P12: \# -- **T60 15\" XGA** +- **T60 15" XGA** - Samsung LTN150XG-L08: \# - LG-Philips LP150X09: \# - 13N7068 (IDtech): \# - 13N7069 (CMO): \# -- **T60 15\" SXGA+** +- **T60 15" SXGA+** - LG-Philips LP150E05-A2K1: \# - BOE-Hydis HV150P01-100: \# -- **T60 15\" UXGA** +- **T60 15" UXGA** - BOE-Hydis HV150UX1-100: \# - IDTech N150U3-L01: \# - BOE-Hydis HV150UX1-102: \# -- **T50 15\" QXGA** +- **T50 15" QXGA** - IDtech IAQX10N: \# - IDtech IAQX10S: \# @@ -314,7 +314,7 @@ the X60, X60 Tablet and T60 (Intel GPU). Here is an example of how VBT was implemented on the ThinkPad X230: <http://review.coreboot.org/#/c/5396>. -You\'ll need to build a T60 ROM with SeaBIOS and the VGA ROM (for Intel +You'll need to build a T60 ROM with SeaBIOS and the VGA ROM (for Intel GPU). An X60 ROM is also needed (same configuration, using the VGA ROM for X60). @@ -346,28 +346,28 @@ Test results (\# means untested and all had docks, unless noted). - BOE-Hydis HV121X03-100: \# - **X60T SXGA+ (1400x1050):** - BOE-Hydis HV121P01-100: \# -- **T60 14\" XGA (1024x768):** +- **T60 14" XGA (1024x768):** - Samsung LTN141XA-L01: \# - CMO N141XC: \# - BOE-Hydis HT14X14: \# - TMD-Toshiba LTD141ECMB: \# -- **T60 14\" SXGA+ (1400x1050):** +- **T60 14" SXGA+ (1400x1050):** - TMD-Toshiba LTD141EN9B: \# - Samsung LTN141P4-L02: \# - Boe-Hydis HT14P12: \# -- **T60 15\" XGA (1024x768):** +- **T60 15" XGA (1024x768):** - Samsung LTN150XG-L08: \# - LG-Philips LP150X09: \# - 13N7068 (IDtech): \# - 13N7069 (CMO): \# -- **T60 15\" SXGA+ (1400x1050):** +- **T60 15" SXGA+ (1400x1050):** - LG-Philips LP150E05-A2K1: \# - BOE-Hydis HV150P01-100: \# -- **T60 15\" UXGA (1600x1200):** +- **T60 15" UXGA (1600x1200):** - BOE-Hydis HV150UX1-100: \# - IDTech N150U3-L01: \# - BOE-Hydis HV150UX1-102: \# -- **T60 15\" QXGA (2048x1536):** +- **T60 15" QXGA (2048x1536):** - IDtech IAQX10N: \# - IDtech IAQX10S: \# @@ -378,7 +378,7 @@ Test results (\# means untested and all had docks, unless noted). Fallback patches {#fallback_patches} ================ -- Todo: test gnutoo\'s fallback patches: +- Todo: test gnutoo's fallback patches: <http://www.coreboot.org/Fallback_mechanism> see [this IRC log](gnutoo_fallback_patch) (warning, not cleaned up) @@ -393,11 +393,11 @@ Other - unlisted (low priority) {#other} <http://review.coreboot.org/#/c/6718/> - [dmesg](future/dumps/pte_x60_6718/dmesg) - [kern.log](future/dumps/pte_x60_6718/kern.log) - - This doesn\'t seem to cause any issues for general use. + - This doesn't seem to cause any issues for general use. - Implement INT 10H support in i945 native graphics. (this will be a lot of work. SeaBIOS has code for some geode boards, to get a general idea). -- T60 15\" QXGA (2048x1536): fixed issue where GRUB wouldn\'t show any +- T60 15" QXGA (2048x1536): fixed issue where GRUB wouldn't show any graphics. (Not many people have this panel) - It might be the same issue I ran into with Paul on the X60 (not enough memory being allocated) since the same code works on T60 diff --git a/docs/future/old.md b/docs/future/old.md index 62567bb5..33984065 100644 --- a/docs/future/old.md +++ b/docs/future/old.md @@ -41,7 +41,7 @@ Tablet (1024x768) and X60 Tablet (1400x1050) **Add backlight controls:** in *src/mainboard/lenovo/x60/devicetree.cb*, change **gpu\_backlight** to **0x879F879E** -That\'s all! **This has also been backported into libreboot 5th release +That's all! **This has also been backported into libreboot 5th release (line 1233 in src/mainboard/lenovo/x60/i915io.c)**. GNUtoo (Denis Carikli) told me about the register **BLC\_PWM\_CTL** and that you could set it to control backlight. I read that address using devmem2 while @@ -58,15 +58,15 @@ Further notes ------------- Reading **0xe4361254** (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 +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). This person says intel\_backlight has different values and uses the register. devmem2 works, needs checking **lspci -vv** for where the memory is mapped, which is different than on coreboot; mtjm found that it was 0xec061254 on his system (X60 Tablet), and the register value is different too. **This is relevant, because we still -don\'t know how backlight controls are actually handled. We got it +don't know how backlight controls are actually handled. We got it working by accident. We need to know more.**. Intel-gpu-tools may prove useful for further debugging: @@ -88,14 +88,14 @@ works**. mtjm goes on to say, that the register specifies the frequency used for PWM in its depending on the GPU core frequency, so it might be possible to calculate it without hardcoded laptop-specific values. Therefore, I -am supposed to find out the \'display core frequency\' (mtjm says there +am supposed to find out the 'display core frequency' (mtjm says there might be a register for it; also, it might be in 5320 or the replay code) and the PWM modulation frequency. https://en.wikipedia.org/wiki/Backlight\#Flicker\_due\_to\_backlight\_dimming phcoder (Vladimir Serbinenko) who is author of 5320 -(review.coreboot.org) talks about \'duty cycle limit\' and \'flickering -frequency\'. +(review.coreboot.org) talks about 'duty cycle limit' and 'flickering +frequency'. [Back to top of page](#pagetop) @@ -163,7 +163,7 @@ The correct way to do it is to set gtt address to (end of stolen memory - gtt size), which is what later versions of 5927 do (successfully). Here is some debugging output using intel\_gpu\_tools v1.2-1 (from -apt-get repositories) using tool \"intel\_gtt\": +apt-get repositories) using tool "intel\_gtt": - kernel 3.14.4: - with libreboot 5th release (using the 7c0000 gtt hack from @@ -184,12 +184,12 @@ i945/X60: Coreboot 5927 testing (3D fix for kernel 3.12+ on replay code) {#x60_c <http://review.coreboot.org/#/c/5927/>** **The latest version as-is (5927/11) has not been tested by me yet. -Always boot with \'drm.debug=0x06\' kernel parameter when testing +Always boot with 'drm.debug=0x06' kernel parameter when testing this.** This is the fix for 3D on kernel 3.12 and higher on i945 (ThinkPad X60 in this case). This is for the replay code. Libreboot 5th release has a -version of this backported already (based on 5927/3 using the \'7c0000\' +version of this backported already (based on 5927/3 using the '7c0000' hack). **The replay code is obsolete (see 5320 changeset on review.coreboot.org @@ -217,10 +217,10 @@ GTT (graphics translation table) size is PGETBL\_save, max 256 KiB. BSM - 5927/5: [5927\_5.tar.gz](dumps/5927_5.tar.gz) (GRUB graphics corrupt, 3D/everything still works after GRUB) - 5927/3: [5927\_3.tar.gz](dumps/5927_3.tar.gz) (3D still works! - kernel 3.14.4) - the \'7c0000\' hack + kernel 3.14.4) - the '7c0000' hack - 5927/2: [5927\_2.tar.gz](dumps/5927_2.tar.gz) (3D works! kernel - 3.14.4) - the \'7c0000\' hack -- 5927/1 (didn\'t fix the 3D issue): + 3.14.4) - the '7c0000' hack +- 5927/1 (didn't fix the 3D issue): - [cbmem -c](dumps/5927_cbmemc) - [/sys/class/drm/card0/error](dumps/5927_crashdump) - [.config](dumps/5927_config) |