Hi Jose,
On Wed, Dec 13, 2017 at 12:07:05PM +, Jose Abreu wrote:
> On 13-12-2017 11:05, Hans Verkuil wrote:
> > On 13/12/17 11:30, Maxime Ripard wrote:
> >> Hi Hans,
> >>
> >> On Fri, Dec 08, 2017 at 04:48:47PM +0100, Hans Verkuil wrote:
> >>> When I connected my cubieboard running 4.15-rc1 to
Hi,
On 13-12-2017 11:05, Hans Verkuil wrote:
> On 13/12/17 11:30, Maxime Ripard wrote:
>> Hi Hans,
>>
>> On Fri, Dec 08, 2017 at 04:48:47PM +0100, Hans Verkuil wrote:
>>> When I connected my cubieboard running 4.15-rc1 to my 4k display I got no
>>> picture. Some
>>> digging found that there is no
On 13/12/17 11:30, Maxime Ripard wrote:
> Hi Hans,
>
> On Fri, Dec 08, 2017 at 04:48:47PM +0100, Hans Verkuil wrote:
>> When I connected my cubieboard running 4.15-rc1 to my 4k display I got no
>> picture. Some
>> digging found that there is no check against the upper pixelclock limit of
>> the
Hi Hans,
On Fri, Dec 08, 2017 at 04:48:47PM +0100, Hans Verkuil wrote:
> When I connected my cubieboard running 4.15-rc1 to my 4k display I got no
> picture. Some
> digging found that there is no check against the upper pixelclock limit of
> the HDMI
> output, so X selects a 4kp60 format at 594
When I connected my cubieboard running 4.15-rc1 to my 4k display I got no
picture. Some
digging found that there is no check against the upper pixelclock limit of the
HDMI
output, so X selects a 4kp60 format at 594 MHz, which obviously won't work.
The patch below adds a check for the upper bound
