1 |
On Wed, Aug 25, 2010 at 01:29:29PM -0700, Kevin O'Gorman wrote |
2 |
|
3 |
> There are some confusing things about this. |
4 |
> - The log contains 1920x1080 modelines, but is not using them or |
5 |
> clearly stating the reason. |
6 |
> - The log contains the lines |
7 |
> (!!) MACH64(0): Virtual resolutions will be limited to 8191 kB |
8 |
> due to linear aperture size and/or placement of hardware cursor |
9 |
> image area. |
10 |
|
11 |
1920x1080 uses how many pixels? |
12 |
$ echo $(( 1920 * 1080 )) |
13 |
2073600 |
14 |
|
15 |
The programmers writing X drivers use ***FOUR*** bytes per pixel for |
16 |
24-bit colour. This is due to double-word addressing being *MUCH* |
17 |
easier and faster than sliding groups of 3 bytes per pixel. This means |
18 |
that to support 1920x1080 at 24 bits requires how many Kbytes... |
19 |
|
20 |
$ echo $(( 1920 * 1080 * 4 / 1024 )) |
21 |
8100 |
22 |
|
23 |
It'll just barely squeeze in a 1920x1080 image, but forget about |
24 |
acceleration or backing store, because there's almost no spare memory. |
25 |
What you might want to try is forcing 16-bit colour, which would use |
26 |
half the memory. See http://www.gentoo.org/doc/en/xorg-config.xml |
27 |
|
28 |
The magic option is DefaultDepth. You would want something like so, |
29 |
the identifiers changed to match your setup... |
30 |
|
31 |
Section "Screen" |
32 |
Identifier "Default Screen" |
33 |
Device "RadeonHD 4550" |
34 |
Monitor "Generic Monitor" |
35 |
DefaultDepth 16 |
36 |
# Skipping some text to improve readability |
37 |
SubSection "Display" |
38 |
Depth 16 |
39 |
Modes "1920x1080" |
40 |
EndSubSection |
41 |
EndSection |
42 |
|
43 |
When viewing hi-res colour images, you may see some banding due to |
44 |
the limited colourspace (64 K colours instead of 16 million), but it may |
45 |
offer full pixel resolution, and the banding may not be noticable most |
46 |
of the time. |
47 |
|
48 |
-- |
49 |
Walter Dnes <waltdnes@××××××××.org> |