All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Walrond <andrew@walrond.org>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Dual screen framebuffer development advice
Date: Fri, 10 Dec 2004 04:01:54 +0800	[thread overview]
Message-ID: <200412100401.56026.adaplas@hotpop.com> (raw)

--- Andrew Walrond <andrew@walrond.org> wrote:

> On Monday 22 Nov 2004 22:14, Antonino A. Daplas
> wrote:
> > On Tuesday 23 November 2004 05:35, Andrew Walrond
> wrote:
> > >
> > > I've got this working nicely now. I have a
> recent agp nvidia card and an
> > > old pci matrox millenium in this dual opteron
> machine running 64bit
> > > linux. I boot into a console on the matrox using
> the built-in matroxfb
> > > driver, then startx which runs on the nvidia
> card using the nv driver. I
> > > can then work on my fb application in X, viewing
> the output on the second
> > > monitor via the matrox card. Nice!
> >
> 
> I've just done a bk pull from linus and build a new
> kernel (was using post rc2 
> before) and now this nice scheme (see above) fails
> to work:
> 
> When I 'startx', the X log complains about no core
> keyboard, my usb keyboard 
> stops responding and both screens go blank. I can
> only get access by ssh from 
> another machine.
> 
> Nothing changed other than kernel; using same
> .config.
> 
> If I boot on rivafb console instead of matroxfb,
> startx and keyboard work 
> fine.
> 
> Before I start hunting down the problem; Do any
> recent changes spring to mind?

-rc3 is bug-fix only, so no, I can't think of any changes in fbdev/fbcon
that will cause your problem, unless someone submitted changes without
passing through this list.

Anyway, here's linus' changelog between rc2 and rc3.

  o fbdev: Fix for using >16 pixel wide font in fb console*** 
  o fbdev: Support for bigger than 16x32 fonts in softcursor
  o fbdev: Support for bigger than 16x32 fonts in rivafb cursor
  o fbcon: Disable fbcon cursor if vt softcursor is enabled***
  o fbdev: Allow mode change even if EDID block is not found
  o fbdev: Fix cursor in doublescan mode in atyfb
  o fbdev: Fix typo in atyfb
  o fbdev: Change the find_mode behavior***
  o rivafb: fix broken burst length calculation
  o fbdev: Fix screen corruption in neofb
  o fbdev: Fix lockup when switching to/from X/console
  o fbdev: Fix module_param in rivafb
  o fbdev: Fix crash if fb_set_var() called before register_framebuffer()***
  o fbdev: fix wrong colors at 16 bpp in tridentfb

*** affects core fbcon/fbdev layer

Tony




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

             reply	other threads:[~2004-12-09 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 20:01 Antonino A. Daplas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-19 13:55 Dual screen framebuffer development advice Andrew Walrond
2004-06-19 20:25 ` Antonino A. Daplas
2004-11-22 21:35   ` Andrew Walrond
2004-11-22 22:14     ` Antonino A. Daplas
2004-12-08 23:02       ` Andrew Walrond
2004-12-09  9:25       ` Andrew Walrond

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200412100401.56026.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=andrew@walrond.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.