Hi Daniel,
On Tue, Dec 19, 2017 at 11:05:04AM +0100, Daniel Vetter wrote:
> On Mon, Dec 18, 2017 at 08:50:46AM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > On Fri, Dec 15, 2017 at 06:06:32PM +0100, Daniel Vetter wrote:
> > > On Fri, Dec 15, 2017 at 05:46:19PM +0100, Hans Verkuil wrote:
> > > > Whe
On 19/12/17 11:05, Daniel Vetter wrote:
> On Mon, Dec 18, 2017 at 08:50:46AM +0100, Maxime Ripard wrote:
>> Hi,
>>
>> On Fri, Dec 15, 2017 at 06:06:32PM +0100, Daniel Vetter wrote:
>>> On Fri, Dec 15, 2017 at 05:46:19PM +0100, Hans Verkuil wrote:
When I connected my cubieboard running 4.15-rc1
On Mon, Dec 18, 2017 at 08:50:46AM +0100, Maxime Ripard wrote:
> Hi,
>
> On Fri, Dec 15, 2017 at 06:06:32PM +0100, Daniel Vetter wrote:
> > On Fri, Dec 15, 2017 at 05:46:19PM +0100, Hans Verkuil wrote:
> > > When I connected my cubieboard running 4.15-rc1 to my 4k display I got no
> > > picture.
Hi,
On Fri, Dec 15, 2017 at 06:06:32PM +0100, Daniel Vetter wrote:
> On Fri, Dec 15, 2017 at 05:46:19PM +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
On Fri, Dec 15, 2017 at 05:46:19PM +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 MHz, which
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
