linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Otto Solares <solca@guug.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: ioremap problem on highmem
Date: Wed, 15 Oct 2003 17:34:35 -0700 (PDT)	[thread overview]
Message-ID: <20031016003435.45380.qmail@web14912.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310160012230.13660-100000@phoenix.infradead.org>

--- James Simmons <jsimmons@infradead.org> wrote:
> > Another issue I am having trouble with is having mode setting/EDID code in
> a device driver. That is a lot of seldom used code sitting in a device
> driver.
> 
> Prehaps but on platforms lacking firmware that sets the video mode this is 
> a problem. A good example is most mips boxes. The prom almost nevers 
> initializes the graphics cards. You have to set the video mode yourself. 
> No way around it. 
> 
How about making a small driver with all of it's code marked __init that
initializes the mode on boxes with absolutely no support? That would be enough
to get us to the point where we can run user mode code and provide a more full
featured driver. The user mode driver would have full support for mode
setting/edid in user space libraries.

=====
Jon Smirl
jonsmirl@yahoo.com

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  reply	other threads:[~2003-10-16  0:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 19:18 ioremap problem on highmem Otto Solares
2003-10-13 20:30 ` Jon Smirl
2003-10-14  0:14   ` Otto Solares
2003-10-14  0:46     ` Jon Smirl
2003-10-14  1:56       ` Otto Solares
2003-10-14  4:51         ` Jon Smirl
2003-10-15  1:13           ` Otto Solares
2003-10-15  1:37             ` Jon Smirl
2003-10-15 23:11             ` James Simmons
2003-10-16 10:15               ` Benjamin Herrenschmidt
2003-10-16 16:56                 ` Otto Solares
2003-10-17 16:58                   ` James Simmons
2003-10-14  8:30         ` Geert Uytterhoeven
2003-10-14  8:34       ` Geert Uytterhoeven
2003-10-14 14:42         ` Jon Smirl
2003-10-14 17:25           ` James Simmons
2003-10-14 17:23         ` James Simmons
2003-10-14 16:49       ` James Simmons
2003-10-14 17:59         ` Jon Smirl
2003-10-15 23:17           ` James Simmons
2003-10-16  0:34             ` Jon Smirl [this message]
2003-10-16 10:12               ` Benjamin Herrenschmidt
2003-10-16  0:43             ` I2C standalone vs integrated? Jon Smirl
2003-10-16 10:14               ` Benjamin Herrenschmidt
2003-10-17 16:43                 ` James Simmons
2003-10-16 10:09             ` ioremap problem on highmem Benjamin Herrenschmidt
2003-10-15 16:46       ` Benjamin Herrenschmidt

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=20031016003435.45380.qmail@web14912.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=solca@guug.org \
    /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).