On Mon, Nov 4, 2013 at 7:13 PM, Fabio Estevam wrote:
> On Mon, Nov 4, 2013 at 9:20 PM, Matt Sealey wrote:
>
>> Fabio, Shawn, could you go so far as to bring this up with the i.MX
>> guys responsible for documentation or find the original transmitter IP
>> specs, or fi
On Tue, Nov 5, 2013 at 5:35 PM, Fabio Estevam wrote:
> On Tue, Nov 5, 2013 at 9:29 PM, Matt Sealey wrote:
>
>> I know about that one. BTW this isn't in the MX6SDL errata
>> documentation, but it is in the MX6QD errata. If this actually affects
>> the Solo etc. a
On Thu, Oct 31, 2013 at 4:48 PM, Matt Sealey wrote:
> On Thu, Oct 31, 2013 at 4:08 PM, Fabio Estevam wrote:
>> On Thu, Oct 31, 2013 at 7:00 PM, Russell King - ARM Linux
>> wrote:
>>
>>>> Interesting. With the monitor I have tested I am not able to see this
>
antify Troy's results by just
throwing numbers at it and then saying "no magenta line here"?
Growl,
Matt Sealey
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
iginal
DISPLAY_FLAGS? DRM_MODE_FLAG_PIXDATA_POSEDGE is easier to get your
head around if you know it is mapped from the DISPLAY_FLAGS_ version.
PDATEN and PPIXDATEDGE don't exactly map to things like EDID field
names either..
> +#define DRM_MODE_FLAG_PPIXDATEDGE (1<<
