lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1101131752190.311@casper.infradead.org>
Date:	Thu, 13 Jan 2011 17:55:14 +0000 (GMT)
From:	James Simmons <jsimmons@...radead.org>
To:	Anca Emanuel <anca.emanuel@...il.com>
cc:	Christian Borntraeger <borntraeger@...ibm.com>,
	Dave Airlie <airlied@...ux.ie>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for rc1


> > > With your patch, I can boot the system. But nouveau is not loaded.
> > > dmesg attached.
> > >
> > 
> > Forget to mention: the revert makes first steps of boot look the same
> > (change the resolution of the text)
> > but with your patch, I see a big ugly ununtu logo, (I think that is
> > because nouveau is not loaded)

Okay, can you do one more experiment for me. Since you already reverted 
the patch to get it booting I like to ask you to add 

drm_fb_helper_fill_fix(info, fb_helper->fb);

back into the drm_fb_helper_set_par function in drm_fb_helper.c. You have 
something like this:

        mutex_lock(&dev->mode_config.mutex);
        for (i = 0; i < fb_helper->crtc_count; i++) {
                crtc = fb_helper->crtc_info[i].mode_set.crtc;
                ret = crtc->funcs->set_config(&fb_helper->crtc_info[i].mode_set);
                if (ret) {
                        mutex_unlock(&dev->mode_config.mutex);
                        return ret;
                }
                drm_fb_helper_fill_fix(info, fb_helper->fb);
        }
        mutex_unlock(&dev->mode_config.mutex);
 
Tell me if your system is still usable after that. Thanks for testing for 
me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ