From owner-freebsd-arm@FreeBSD.ORG Tue May 12 18:09:40 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA0F487D; Tue, 12 May 2015 18:09:40 +0000 (UTC) Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA835112F; Tue, 12 May 2015 18:09:40 +0000 (UTC) Received: by ykep21 with SMTP id p21so5968255yke.3; Tue, 12 May 2015 11:09:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BVzfhxLsKBGc8jugzFTTMMdtoyGpNpOElof6W1fCVXQ=; b=psOWY5kgWHVNvL+e6Lk8ceTfZiOZEbOKGPbVL4iu1YRqzS3GFD/qEgns7oPasQ8nKl xsGnzTamIz9yp3CVFjzOmfONEycLbljMLvwB3cNdmIFPoVfNW131MTzN0YWTN2yLp00Y o+xbAf0Q8mRVY0cUQCpC8F87Lgn9u7HJvD6a5ZHTsh8LSyjeB3alzjWJJmn8tppS8Qqe rTlNo0T6rZTabYBdhmmIwzAnKO77Ubz0c31HDTXouT49ECFUMuKRbANdHtbQLA78sGmC Hbs/pSK1owhBFceqOfR/YttsR430KBd5JrG80llWp0OgZzWOEL78r5GZuTo8OiyPWSRH QVNQ== MIME-Version: 1.0 X-Received: by 10.170.197.130 with SMTP id o124mr19012804yke.77.1431454179901; Tue, 12 May 2015 11:09:39 -0700 (PDT) Received: by 10.129.73.81 with HTTP; Tue, 12 May 2015 11:09:39 -0700 (PDT) In-Reply-To: <20150510190300.05772f5ceaaf047d47f32b75@ulrich-grey.de> References: <20150510112444.9e12a9739c7e2b91e5fc2ea4@ulrich-grey.de> <20150510190300.05772f5ceaaf047d47f32b75@ulrich-grey.de> Date: Tue, 12 May 2015 15:09:39 -0300 Message-ID: Subject: Re: Xorg on a RaspberryPI From: Luiz Otavio O Souza To: Ulrich Grey Cc: Adrian Chadd , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2015 18:09:41 -0000 On 10 May 2015 at 16:03, Ulrich Grey wrote: > On Sun, 10 May 2015 08:19:51 -0700 > Adrian Chadd wrote: > >> hm, there's something odd with 32 bit colours in the fb driver. The >> red and blue are swapped. That may be your problem. >> >> Can you try booting / running it on 24 bit colour instead? > > I have tried it with Depth 16, 24 and 32 in /etc/xorg.conf and /boot/msdos/config.txt. > The colors are still strange. > > Section "Device" > Identifier "Generic FB" > Driver "scfb" > EndSection > > Section "Screen" > Identifier "Screen" > Device "Generic FB" > Monitor "Monitor" > SubSection "Display" > Depth 16 #24 #32 > EndSubsection > EndSection > > config.txt: > framebuffer_depth=16 > disable_commandline_tags=1 > gpu_mem=64 > device_tree=rpi.dtb > device_tree_address=0x100 > kernel=uboot.img I 'think' that the 16bpp mode will work for you, but the above setting is being overwritten by default fb settings in FreeBSD. Could you post your fb details (from dmesg), it should look like this: fb0: on ofwbus0 fbd0 on fb0 VT: initialize with new VT driver "fb". fb0: 656x416(656x416@0,0) 24bpp fb0: fbswap: 1, pitch 1968, base 0x3daac000, screen_size 818688 The last two lines are the ones I'm interested in. Are you using the standard firmware (from official images or from u-boot-rpi) ? The recent firmware versions uses a different color mapping (the fbswap flag). In this case I think you could tell xorg to use the appropriate color mapping (but I don't know how to do that), look if you can find where you should specify the RGB or BGR mode. The 16bpp mode isn't affected by this change. Luiz