All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH 2/6] crownbay: customize the xorg.conf for the flat panel on the corwnbay kit
Date: Mon, 30 Jul 2012 08:28:05 -0700	[thread overview]
Message-ID: <5016A805.4050807@linux.intel.com> (raw)
In-Reply-To: <ADD6A3980E8C39419A432FF422031B4C0318F3FC@ORSMSX106.amr.corp.intel.com>



On 07/30/2012 02:50 AM, Kamble, Nitin A wrote:
> 
> 
>> -----Original Message----- From: Darren Hart
>> [mailto:dvhart@linux.intel.com] Sent: Saturday, July 28, 2012 3:27
>> AM To: Kamble, Nitin A Cc: yocto@yoctoproject.org;
>> bruce.ashfield@windriver.com; Zanussi, Tom Subject: Re: [yocto]
>> [PATCH 2/6] crownbay: customize the xorg.conf for the flat panel on
>> the corwnbay kit
>> 
>> 
>> 
>> On 07/26/2012 10:31 PM, Kamble, Nitin A wrote:
>>>>>> On 07/23/2012 03:06 AM, nitin.a.kamble@intel.com wrote:
>>>>>>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>>>>>>> 
>>>>>>> The kit has Auo 800x600 LCD screen. Configuring Xorg for
>>>>>>> it.
>>>>>> 
>>>>>> I presume the crownbay has additional display options? how
>>>>>> does this impact those?
>>>>>> 
>>>>> This change sets the resolution of the screen to 800x600. And
>>>>> this is applicable to LCD screen on the kit as well as
>>>>> external monitor. I will add a note about it in the log.
>>>> 
>>>> I presume that without this change it was able to detect the 
>>>> appropriate resolution of the connected monitor, but not of the
>>>> LCD?
>>>> 
>>>> If so, this change effectively breaks that autodetection and
>>>> forces everything to the 800x600 display which is arguably
>>>> very low-resolution by today's standards. Why should this be
>>>> the default? When you refer to "the kit", what exactly are you
>>>> referring to?
>>>> 
>>>> Also, is this a discussion you have already had with Tom? I
>>>> don't want to contradict what he has said regarding this BSP.
>>> 
>>> 
>>> EMGD driver on crownbay gives few resolutions as options. By
>>> default it tries to set 1366x768 resolution for both LCD and
>>> external monitor. The Crownbay kit is a suitcase kind of box,
>>> which has builtin LCD screen of resolution 800x600. This LCD
>>> screen shows only 800x600 of the default 1366x768 area. So The
>>> LCD is not able to show all the screen, and IMO it is a
>>> functional issue.
>>> 
>>> For my Dell 1704FPTi monitor which has 1280x1024 native
>>> resolution; When connected to the crownbay,  X cannot find a
>>> working mode for this monitor. But if I set 800x600 in the
>>> xorg.conf as this commit does, then both LCD & external monitor
>>> can show the X screen without any issues.
>> 
>> This seems like a bug to me. The driver should be able to probe the
>> display and use the optimal resolution without it being specified
>> in the Xorg.conf. So far as I know we don't specify resolution in
>> any of the meta-intel BSPs:
>> 
>> dvhart@envy:~/source/poky/layers/meta-intel [denzil] $ find .
>> -name xorg.conf | xargs grep -i Modes
>> 
>> So while I agree the kit screen should work out of the box, the
>> fact that even your dell lcd monitor doesn't work is cause for
>> concern. Is there anything in the Xorg log that indicates why it
>> isn't able to get the EDID data?
>> 
>> -- Darren
>> 
> 
> In the xorg log I do not see any useful EDID information. Either
> these displays do not support EDID, or the EDID support in the EMGD
> driver is not working well with these devices. And the EMGD driver is
> closed source. So we can't fix it. So IMO keeping the resolution to
> 800x600 is the best possible solution for crownbay BSP.

Tom,

I've never booted a crownbay machine. What has your experience been with
the displays on this board?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


  reply	other threads:[~2012-07-30 15:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 10:06 [PATCH 0/6] commits to move crownbay BSP to v3.4 kernel I v1.14 EMGD driver nitin.a.kamble
2012-07-23 10:06 ` [PATCH 1/6] emgd-driver-bin: upgrade from 1.10 to 1.14 nitin.a.kamble
2012-07-24 10:59   ` Kamble, Nitin A
2012-07-26 20:07   ` Darren Hart
2012-07-23 10:06 ` [PATCH 2/6] crownbay: customize the xorg.conf for the flat panel on the corwnbay kit nitin.a.kamble
2012-07-26 20:10   ` Darren Hart
2012-07-27  4:00     ` Kamble, Nitin A
2012-07-27  4:02       ` Darren Hart
2012-07-27  5:31         ` Kamble, Nitin A
2012-07-27  5:42           ` Kamble, Nitin A
2012-07-27 21:57           ` Darren Hart
2012-07-30  9:50             ` Kamble, Nitin A
2012-07-30 15:28               ` Darren Hart [this message]
2012-07-30 15:57                 ` Tom Zanussi
2012-07-23 10:06 ` [PATCH 3/6] crownbay: update emgd driver version in the README nitin.a.kamble
2012-07-26 20:13   ` Darren Hart
2012-07-23 10:06 ` [PATCH 4/6] crownbay: add recipe extension for linux-yocto-3.4 nitin.a.kamble
2012-07-26 20:19   ` Darren Hart
2012-07-23 10:06 ` [PATCH 5/6] crownbay: make v3.4 the default kernel nitin.a.kamble
2012-07-23 10:06 ` [PATCH 6/6] gnu-efi: fix whitespace usage nitin.a.kamble
2012-07-26 20:22   ` Darren Hart
2012-07-26 19:51 ` [PATCH 0/6] commits to move crownbay BSP to v3.4 kernel I v1.14 EMGD driver Darren Hart
2012-07-26 20:23   ` Darren Hart

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=5016A805.4050807@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=nitin.a.kamble@intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.