flict, but
adding Jiri to CC for the case there was any preference.
Acked-by: Bruno Prémont
> Cc: Bruno Prémont
> Cc: linux-in...@vger.kernel.org
> Reviewed-by: Daniel Vetter
> Signed-off-by: Jani Nikula
> ---
> drivers/hid/hid-picolcd_fb.c | 3 +--
> 1 file changed, 1
Hi,
I have a system with multiple monitors and would like to send
notification sounds to the monitor on which corresponding
window is visible.
For a workstation and a tiny computer things look different:
- workstation (Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz):
00:02.0 VGA compatible controller [
On Wed, 12 Sep 2018 20:06:43 +0200 Takashi Iwai wrote:
> On Wed, 12 Sep 2018 19:46:58 +0200,
> Ville Syrjälä wrote:
> >
> > On Tue, Sep 11, 2018 at 03:50:13PM +0200, Bruno Prémont wrote:
> > > Hi,
> > >
> > > I have a system with multiple monit
CCing intel-gfx as otherwise it will probably not get seen by developers.
On Sun, 11 May 2014 Carbonated Beverage wrote:
> Hi all,
>
> I rarely upgrade kernels these days -- so when updating to 3.14.3, I found
> the X display was blank -- switching to a text console appears to work, but
> I stil
ation/how-report-bugs
when you report the bug so all important information is included.
If you can do so from console, check for possible MESA or
xf86-video-intel updates. If there are none (that help), manually
compiling more recent releases or -git versions of xf86-video-intel, libdrm
and mes
On Wed, 12 March 2014 Ben Johnson wrote:
> My hardware:
> Asrock Z77 Extreme4 with iGPU Multi-Monitor enabled. Primary graphics is
> set to PCIe but that doesn't make a difference.
> i7 3770k / HD 4000
> nVidia GTX 660 running nVidia's binary drivers v334.21, although
> multiple versions have th
Hi Kenneth,
On Fri, 28 March 2014 Kenneth de Mello wrote:
> On my system, the maximum resolution of my monitor, 2560x1440, is no longer
> automatically detected properly with kernel 3.13.7. This worked with
> 3.13.6, and 5 with this hardware and identical kernel configs.Now the
> autodetect
et some image to the monitor but with weird "scaling" effects!
Bruno
> Kenneth
>
> On Sun, Mar 30, 2014 at 2:36 PM, Bruno Prémont wrote:
> > Hi Kenneth,
> >
> > On Fri, 28 March 2014 Kenneth de Mello wrote:
> > > On my system, the maximum resolution
Hi Stephen,
You may want to CC intel-gfx@lists.freedesktop.org for i915 issues (even
if you are not subscribed and you mail will wait for a moderator to let
it go through).
In case of intel GPU hangs you should at least include
/sys/kernel/debug/dri/0/i915_error_state, probably submitting as a
b
4 Controller
> 05:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
> Adapter (rev 19)
> 05:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 01)
> 05:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter
> (rev 0a)
> 05:
Hi Stephen,
On Wed, 20 November 2013 Stephen Clark wrote:
> Hi Bruno,
>
> I have tested the latest kernel and X, mesa etc, but am still using
> wine-1.3.24.
> I am working on upgrading that. If I still have the error I will file
> a bug report at bugs.freedesktop.org. I already have a login beca
Hi Ville,
On Thu, 05 December 2013 Ville Syrjälä wrote:
> On Wed, Dec 04, 2013 at 09:09:22PM +0100, Bruno Prémont wrote:
> > [1.621199] [drm:intel_pipe_config_compare] *ERROR* mismatch in
> > adjusted_mode.crtc_clock (expected 108000, found 48000)
>
> Hmm. Kind of loo
Hi Ville,
On Mon, 09 December 2013 ville.syrj...@linux.intel.com wrote:
> There appear to be some gen2 machines that don't really like the current PLL
> limits we have. We also have some accuracy problems with the PLL calculations.
> This series aims to eliminate those problems, and at least my 85
Hi Ville,
On Tue, 10 December 2013 Ville Syrjälä wrote:
> On Tue, Dec 10, 2013 at 12:52:27PM +0100, Bruno Prémont wrote:
> > On Mon, 09 December 2013 Ville Syrjälä wrote:
> > > There appear to be some gen2 machines that don't really like the current
> > > PLL
&g
CCing intel-gfx as it is related to intel GPU driver and might get missed
by intel developers on LKML.
Looking at the linked pastebins ddcontrol seems to make use of the same
i2c/DDC line but getting different results.
Surprising info I see in dmesg, that does apply to both kernels, is
that uvesa
Hi Mark,
[CCing intel-gfx]
On Fri, 12 October 2012 Mark Hounschell wrote:
> Not sure this is the correct place to ask about a possible drm issue. I
> have an intel based PC with an HDMI port that I'm trying to connect to
> an LG TV. I have successfully used this HDMI port connected to an Optim
Hi Mark,
On Sat, 13 October 2012 Mark Hounschell wrote:
> On 10/13/2012 02:57 PM, Mark Hounschell wrote:
> > On 10/12/2012 05:14 PM, Bruno Prémont wrote:
> >>> TV - LG 42lb9df
> >>> PC - intel DH77DF motherboard
> >>
> > I have another AMD based
On Sun, 14 October 2012 Mark Hounschell wrote:
> On 10/14/2012 04:41 AM, Bruno Prémont wrote:
> > Your best solution is probably to write an EDID blob (or reuse one you find
> > somewhere) that provides at least one mode matching your TV's native mode
> > (probabl
On Sun, 14 October 2012 Daniel Vetter wrote:
> On Sun, Oct 14, 2012 at 5:41 PM, Mark Hounschell wrote:
> > There is something amiss. Here is my i915_pci_probe routine. I Added a
> > couple more printks. NONE of these show up in dmesg. Not even the "Entered"
> > printk.
>
> That's rather st
Hi Mark,
On Sun, 14 October 2012 Mark Hounschell wrote:
> I've taken the EDID data from that service manual. I've looked at the
> EDID-Howto for how to specify the connector but all I see is:
>
> "An EDID data set will only be used for a particular connector,
> if its name and a colon are pre
On Sun, 14 October 2012 Mark Hounschell wrote:
> >> And could I ask if this simple pgm might work to build the file I need?
> >
> > It looks fine. You can also check the output with hexdump just to
> > make sure it looks sane.
>
> Did that and the data looks swapped compared to the array written,
On Sun, 14 October 2012 Mark Hounschell wrote:
> I gave it a try. I don't think it liked my kernel cmdline. dmesg attached.
> There is a lot more in there now that nomodeset is gone and the debug is
> turned on.
>
> # ls -al /lib/firmware/edid/lg42lb9df.edid
> -rw-r--r-- 1 root root 1024 Oct 14
Hi mark,
On Sun, 21 October 2012 Mark Hounschell wrote:
> I have a TV that appears to not provide proper EDID info to the HDMI or DVI
> ports of my Intel DH77DF motherboard. I received some pointers from this
> list that pointed me in the direction of creating my own EDID file and I
> now have
Hi Mark,
On Sun, 21 October 2012 Mark Hounschell wrote:
> On 10/21/2012 10:58 AM, Bruno Prémont wrote:
> > On Sun, 21 October 2012 Mark Hounschell wrote:
> >> I have a TV that appears to not provide proper EDID info to the HDMI or DVI
> >> ports of my Intel DH77DF m
On Mon, 22 Oct 2012 17:54:26 Mark Hounschell wrote:
> Another interesting thing. I changed the boot file to only
> "video=HDMI-A-1:e" and the monitor on the DVI port complains about the
> resolution being to high. I then put the hdmi cable onto my dvi/hdmi
> adapter and plug it into the DVI port
Hi,
You should look at KMS (Kernel Mode Setting) with i915 driver that you
find under DRI. (CONFIG_DRM_I915 + CONFIG_DRM_I915_KMS)
KMS can also be manually enabled/disabled with i915.modeset kernel
parameter when i915 is built-in.
VESA only knows a few standard predefined modes but not the wide
r
e help me.
> With the latest Kernel file with CONFIG_DRM_I915 enabled, how do I set
> different
> screen resolutions. Please let me know.
>
> Thanks & Best Regards,
> Sanjay
>
>
>
>
>
> From: Bruno Prémont
> To
le/i915/parameters/*" and "uname -a" returned nothing.
Weird...
> Also I am attaching my basic graphic display file where I amusing VESA frame
> buffer.
As long as framebuffer console is not properly setup it makes no sense to look
at your program, the issue lying in i915 d
hen I tried with "grep /sys/module/i915/parameters/*" command system didn't
> return anything and it was stuck there. I had to restart the system.
A litte '.' is missing in the grep command (my bad), thus if there were
less than 2 matches for the glob grep would be wait
[CCing intel-gfx]
On Tue, 12 April 2011 Wojciech Zabołotny wrote:
> After I've upgraded my kernel to 2.6.38.2, I started to experience very
> often screen corruption in X (it happened also earlier with 2.6.37.3,
> but now is very often.
> Hardware seems to be OK. I attach sample screendumps, co
Hi Wojtek,
Your best chance to see the bugs fixed is to report a bug following
guidelines at http://intellinuxgraphics.org/how_to_report_bug.html
For GPU hangs, collecting the error state (while GPU is hung) under
debugfs is very helpful.
Report contents of (as well as details on your software st
90c5e31ac37f24.
>
> Cc: bonbon...@internet.lu
Please swap my old "bugzilla e-mail" address with
Bruno Prémont
Thanks,
Bruno
> Cc: sta...@vger.kernel.org
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=87171
> Signed-off-by: Ville Syrjälä
> ---
> dri
32 matches
Mail list logo
