linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: efifb swapping Red/Blue color
Date: Wed, 21 Nov 2012 14:54:34 +0000	[thread overview]
Message-ID: <20121121155434.2bdab6cf@neptune.home> (raw)
In-Reply-To: <20121121001457.2672d788@neptune.home>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 5021 bytes --]

Hi Peter,

On Wed, 21 November 2012 Peter Jones <pjones@redhat.com> wrote:
> On Wed, Nov 21, 2012 at 12:14:57AM +0100, Bruno Prémont wrote:
> > On a MacBookAir2,1 with 9400M C79 nVidia GPU fbcon on efifb has
> > red and blue colors swapped.
> > 
> > Extract from kernel log:
> > efifb: probing for efifb
> > efifb: framebuffer at 0x80010000, mapped to 0xffffc90004580000, using 6400k, total 6400k
> > efifb: mode is 1280x800x32, linelength92, pages=1
> > efifb: scrolling: redraw
> > efifb: Truecolor: size=8:8:8:8, shift$:0:8:16
> > 
> > On another system with radeon GPU and externally connected DVI monitor
> > colors are set properly.
> > 
> > Probably efifb should be looking at something to determine if display
> > is RGB or BGR...
> 
> Right - normally we get it from the firmware graphics driver, but on a
> few generations of Intel Macs they gracefully omitted an implementation
> of that part of the spec, which is why we have a DMI table that just has
> best-effort entries.
> 
> So that on that hardware, it doesn't really give us anything to look
> at.  Though if the same machine comes with two different video cards
> that are, by default, configured opposite ways, there may be something
> we can do.  Could show me the "lspci -v" for each of those devices (the
> nvidia and the radeon)?

The system with Radeon is not the Mac (it's some Gigabyte mainboard that
has EFI support).

Here is lspci for the MacBook:
00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a82] (rev b1)
00:00.1 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a88] (rev b1)
00:03.0 ISA bridge [0601]: NVIDIA Corporation MCP79 LPC Bridge [10de:0aaf] (rev b2)
00:03.1 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0aa4] (rev b1)
00:03.2 SMBus [0c05]: NVIDIA Corporation MCP79 SMBus [10de:0aa2] (rev b1)
00:03.3 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a89] (rev b1)
00:03.4 RAM memory [0500]: NVIDIA Corporation Device [10de:0a98] (rev b1)
00:03.5 Co-processor [0b40]: NVIDIA Corporation MCP79 Co-processor [10de:0aa3] (rev b1)
00:04.0 USB controller [0c03]: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa5] (rev b1)
00:04.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1)
00:06.0 USB controller [0c03]: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1)
00:06.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1)
00:08.0 Audio device [0403]: NVIDIA Corporation MCP79 High Definition Audio [10de:0ac0] (rev b1)
00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Bridge [10de:0aab] (rev b1)
00:0b.0 SATA controller [0106]: NVIDIA Corporation MCP79 AHCI Controller [10de:0ab9] (rev b1)
00:10.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0aa0] (rev b1)
00:15.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac6] (rev b1)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation C79 [GeForce 9400M] [10de:0870] (rev b1)
03:00.0 Network controller [0280]: Broadcom Corporation BCM4321 802.11a/b/g/n [14e4:4328] (rev 05)

and DMI info:
# dmidecode 2.10
# SMBIOS entry point at 0x7fec7000
SMBIOS 2.4 present.
37 structures occupying 1888 bytes.
Table at 0x7FEC6000.

...
Handle 0x000E, DMI type 0, 24 bytes
BIOS Information
	Vendor: Apple Inc.
	Version:    MBA21.88Z.0075.B03.0811141325
	Release Date: 11/14/08
	ROM Size: 4096 kB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		ACPI is supported
		IEEE 1394 boot is supported
		Smart battery is supported
		Function key-initiated network boot is supported
	BIOS Revision: 0.1

Handle 0x000F, DMI type 1, 27 bytes
System Information
	Manufacturer: Apple Inc.
	Product Name: MacBookAir2,1
	Version: 1.0
	Serial Number: xxxxxxxxxxx
	UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
	Wake-up Type: Power Switch
	SKU Number: System SKU#
	Family: MacBook

Handle 0x0010, DMI type 2, 16 bytes
Base Board Information
	Manufacturer: Apple Inc.
	Product Name: Mac-F42D88C8
	Version: Not Specified
	Serial Number: Base Board Serial#
	Asset Tag: Base Board Asset Tag#
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Part Component
	Chassis Handle: 0x0011
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0011, DMI type 3, 21 bytes
Chassis Information
	Manufacturer: Apple Inc.
	Type: Notebook
	Lock: Not Present
	Version: Mac-F42D88C8
	Serial Number: xxxxxxxxxxx
	Asset Tag: Asset Tag#
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Other
	Security Status: Other
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: Unspecified
	Contained Elements: 0
...

Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2012-11-21 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 23:14 efifb swapping Red/Blue color Bruno Prémont
2012-11-21 14:38 ` Peter Jones
2012-11-21 14:54 ` Bruno Prémont [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121121155434.2bdab6cf@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=linux-fbdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).