Hi,
I am testing Linux v4.2-rc5 and I am sporadically getting crashes shortly after
startup in gk104_fifo_intr_runlist(). What I've found is that the 'mask' value
read from offset 0x2a00 comes back as '0xbad0da00'. This causes the 'engn'
variable to be assigned the value 9, which is invalid;
Alexandre, could you take a look? 0xbad* generally comes from bad mmio
reads.
On Aug 9, 2015 1:08 PM, Eric Biggers ebigge...@gmail.com wrote:
Hi,
I am testing Linux v4.2-rc5 and I am sporadically getting crashes shortly
after
startup in gk104_fifo_intr_runlist(). What I've found is that the
The Nvidia blob allows a pixel clock up to 225 MHz in version 346.59,
but only allowed 165MHz in version 295 for HDMI connections. This was
tested with a GF114 (Nvidia GTX 560 TI) and a HDMI monitor which used
225 MHz pixel clock and a signal link DVI monitor with a pixel clock of
less than 165
These patches are adding support for outputting 2560x1440@56 over HDMI.
This needs a pixel clock of 225 MHz which was not supported before.
This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and
one HDMI monitor running with 2560x1440@56 and one DVI monitor running
with
Without this patch a pixel clock rate above 165 MHz on a TMDS link is
assumed to be dual link. This is true for DVI, but not for HDMI. HDMI
supports no dual link, but it supports pixel clock rates above 165 MHz.
Only activate Dual Link mode when it is actual possible.
Signed-off-by: Hauke
