linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Jim Hague <jim.hague@acm.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: New API and X option UseFBDev
Date: Tue, 9 Sep 2003 18:40:26 +0200	[thread overview]
Message-ID: <20030909164026.GC4428@iliana> (raw)
In-Reply-To: <XFMail.20030909145758.jim.hague@acm.org>

On Tue, Sep 09, 2003 at 02:57:58PM +0100, Jim Hague wrote:
> On 09-Sep-2003 Sven Luther wrote:
> > On Tue, Sep 09, 2003 at 07:49:55AM +0100, Jim Hague wrote:
> >> I have a problem when I try and run X (Debian 4.2.1-11 20030829103906). My
> >> config uses the Glint driver with UseFBDev true, and works fine on 2.4.22.
> >> [....]
> >> It's occurred to me that maybe this just doesn't work and I need an updated
> >> fbdevhw. Do I? Or should it really Just Work?
> > 
> > I think the glint driver is hardcoded to expect amiga hardware when
> > using pm2 with fbdev. Just don't use the usefbdev option, and everything
> > should be fine.
> > 
> > the glint driver does not really support usefbdev anyway, only as a
> > hacky workaround for amigas with cybervision/bvision graphic board.
> 
> Unfortunately, I do rather think I need to use UseFBDev. Hardware is

Ok, i was wrong, it has been some time since i looked at the glint
driver for fbdev stuff, altough i am kind of the default maintainer of
the glint driver now, or at least part-wise with Alan Hourihane. After
looking at it, i saw that the fbdev code is hardcoded to use a ti_pm2,
and will not work with other graphic chips. But the pm3 X driver i wrote
worked perfectly well without it.

> Graphics Exxtreme, x86, BTW. Without, things just don't work properly -
> something isn't quite right with the mode set by X, and you can't switch back
> to the console. Well, you can try, but it seems to hang the kernel.
> 
> I'm currently using UseFBDev on 2.4, for the same reasons. I will keep on
> digging.

Mmm, notice that the :

(--) GLINT(0): Linear framebuffer at 0xCE800000
(--) GLINT(0): MMIO registers at 0xCFFE0000
(EE) GLINT(0): mmap mmio: Invalid argument
(EE) GLINT(0): mmap mmio: Invalid argument

means that the linear framebuffer and mmio registers, values given to
you by pm2fb, are correct (but check this fact with lspci). GLINTMapMem
should call fbdevHWMapVidmem, so i suppose the message you see are from
fbdevhw. Try enabling the DEBUG #define in glint_driver.c to get a bit
more context. 

Friendly,

Sven Luther


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-09 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09  6:49 New API and X option UseFBDev Jim Hague
2003-09-09  9:21 ` Michel Dänzer
2003-09-09 13:53   ` Jim Hague
2003-09-09 10:08 ` Sven Luther
2003-09-09 13:57   ` Jim Hague
2003-09-09 16:40     ` Sven Luther [this message]
2003-09-09 22:59       ` Jim Hague
2003-09-10  4:52         ` Sven Luther
2003-09-10  9:52         ` Jim Hague
2003-09-10  9:58           ` Sven Luther
2003-09-10 10:48             ` Jim Hague
2003-09-10 10:55               ` Sven Luther
2003-09-12 18:16           ` James Simmons

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=20030909164026.GC4428@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=jim.hague@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).