[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fwd: [PATCH 1/2] Framebuffer split
From: |
Robert Millan |
Subject: |
Re: Fwd: [PATCH 1/2] Framebuffer split |
Date: |
Sun, 2 Aug 2009 23:29:22 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Sat, Aug 01, 2009 at 05:17:32PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Sat, Aug 1, 2009 at 5:14 PM, Michal Suchanek<address@hidden> wrote:
> > 2009/8/1 Robert Millan <address@hidden>:
> > I guess the current initialization is somewhat fishy. I haven't looked
> > at the code so far but the way it works is odd. When I change output
> > to gfxterm it apparently tries to initialize the vbe graphics but it
> > fails to find any videomode unless I run vbetest before starting
> > gfxterm.
> >
> > The situation is the same both pre- and post- split.
>
> insmod vbe
>
> Autoload right driver would be nice. Perhaps having a list of pairs
> (PCI vendor; driver) ?
I suppose this will make sense when we have hardware drivers for video.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
- Re: Fwd: [PATCH 1/2] Framebuffer split, (continued)
- Re: Fwd: [PATCH 1/2] Framebuffer split, Michal Suchanek, 2009/08/12
- Re: Fwd: [PATCH 1/2] Framebuffer split, Vladimir 'phcoder' Serbinenko, 2009/08/12
- Re: Fwd: [PATCH 1/2] Framebuffer split, Michal Suchanek, 2009/08/12
- Re: Fwd: [PATCH 1/2] Framebuffer split, Robert Millan, 2009/08/02
- Re: Fwd: [PATCH 1/2] Framebuffer split, Vladimir 'phcoder' Serbinenko, 2009/08/02
Re: Fwd: [PATCH 1/2] Framebuffer split, Michal Suchanek, 2009/08/01