From: Jon Smirl <jonsmirl@yahoo.com>
To: Otto Solares <solca@guug.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: ioremap problem on highmem
Date: Mon, 13 Oct 2003 21:51:43 -0700 (PDT) [thread overview]
Message-ID: <20031014045143.53369.qmail@web14912.mail.yahoo.com> (raw)
In-Reply-To: <20031014015656.GE454@guug.org>
--- Otto Solares <solca@guug.org> wrote:
I almost have the DRI changes done.
I haven't tried adjusting the DRI Creator3D driver for my changes since I don't
have Sparc hardware. Does sparc use the same kind of PCI ID probing that x86
does in a kernel module? Which 3D hardware do you have?
I'll check the DRI changes in as soon as they work; they are pretty minor. Then
I can get back to working on standalone Mesa. The whole purpose in doing this
is to fix things so that standalone Mesa doesn't need a config file.
Dummy con is spac equivalent of VGA con on X86.
> Without fbcon, where the printk goes?
How does klogd get the printk's? I think it reads them from /proc/kmsg. The
terminal program can get them the same way.
> Hey, this sound too cool to be true ;) any code yet? i would like to develop
> on such beast.
Want to write the terminal program? or work on the user libs? Go ahead and
start coding. See the drmtest program in the mesa tree.
=====
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
next prev parent reply other threads:[~2003-10-14 4:51 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 [this message]
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
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=20031014045143.53369.qmail@web14912.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--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).