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: <20100922203927.6ff60f7b@neptune.home>
Date:	Wed, 22 Sep 2010 20:39:27 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	James Simmons <jsimmons@...radead.org>
Cc:	Florian Tobias Schandinat <FlorianSchandinat@....de>,
	linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Bernie Thompson <bernie@...gable.com>
Subject: Re: [Patch, RFC] Make struct fb_info ref-counted with kref

On Wed, 22 September 2010 James Simmons <jsimmons@...radead.org> wrote:
> > This year someone said he/she would look at making it possible to have
> > multiple concurrently active consoles on distinct framebuffers.
> > Hopefully something is happening on that front (that would certainly
> > also include some fbcon cleanup)
> 
> That would be me.

Thanks for showing up (I didn't find the matching thread, probably
subject and my search terms were no good friends :)

> I have a tree at
> 
> http://git.infradead.org/users/jsimmons/linuxconsole-2.6.git
> 
> but currently fbcon is broken so I'm tracing down the problem.

Thanks for the reference to your tree!

What's you opinion regarding my changes to fbcon in my RFC patch?
Are they ok or would you prefer having fbcon changed to stop peeking
at registered_fb list and just operate directly on fb_info everywhere
it needs it? (that is let con2fb_map[] point to fb_info instead of
indexes into registered_fb? (I have a preference for the second one
and will try it out)

Thanks,
Bruno
--
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