On Mon, Feb 16, 2004 at 01:30:33PM +0100, Helge Hafting wrote:
Ville Syrjälä wrote:
[...]
I want to bypass the drm to do accel from user space. Doing an ioctl() for
each blit feels very expensive. Rather than do an ioctl() for each blit
the drm could check the commands in the DMA buffer
Ville Syrjälä wrote:
[...]
I want to bypass the drm to do accel from user space. Doing an ioctl() for
each blit feels very expensive. Rather than do an ioctl() for each blit
the drm could check the commands in the DMA buffer for bad stuff. But that
doesn't feel very efficient either.
If an
I've been getting a lot of mail about this both on and off list. First off, very
little code has been written, this is just a design concept.
One thing is clear there are two consoles involved. One is the system console
that receives printk's, the second is your garden variety command line
--- Ville Syrjälä [EMAIL PROTECTED] wrote:
And finally I find the current situation with multi-head cards quite
bad. I'd like the ablitity for a user space app to open the whole card
as one entity. That includes all CRTCs, outputs and the whole memory
(minus whatever is in use by other
On Tue, 2004-02-10 at 07:37, Ville Syrjl wrote:
On Sun, Feb 08, 2004 at 08:27:17PM -0800, Jon Smirl wrote:
Here's a quick and dirty chart of how I think things should be organised.
--
user space
---
| fbdev
--- Alex Deucher [EMAIL PROTECTED] wrote:
--- Jon Smirl [EMAIL PROTECTED] wrote:
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic
but I've
Nice work Jon! Very impressive! How about dualhead cards? how are
I haven't reached that stage yet so I'm open to any ideas that will work. Fell
free to download the code and work on whatever interests you.
My immediate goal is to get a login console up on a single screen. That means I
need to get the mode set, make fonts work and write a mini-terminal
Oh, and let me add that the notion of moving the console fully
to userland is definitely not something that has been accepted.
It is interesting to evaluate the solution, but lots of kernel
folks will just turn it down for some simple reasons, like not
beeing able to printk bug reports from
On Mon, 2004-02-09 at 15:27, Jon Smirl wrote:
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic but I've
mainly be working on an R200. It is still under development with lots of work to
do.
bk clone
On Mon, 2004-02-09 at 22:41, Benjamin Herrenschmidt wrote:
[ lots of good points ]
I agree with your points Ben, thanks for bringing them up.
--
Earthling Michel Dnzer | Debian (powerpc), X and DRI developer
Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
On Tue, Feb 10, 2004 at 09:40:25AM +1100, Benjamin Herrenschmidt wrote:
bk clone bk://mesa3d.bkbits.net/drm
ERROR-Lock fail: possible permission problem.
Oops.
OK, fixed. Sorry for the inconvenience.
(In the future, please let [EMAIL PROTECTED] know of such problems.)
-andy
In my test system I run X from a PCI ATI Rage128, my target is a AGP Radeon
9000. So when I boot the Rage gets initialized and the Radeon does not. When you
load the Radeon DRM driver it will detect that the Radeon is not initialized in
the hotplug event. To make the reset automatic you need a
--- Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
Oh, and let me add that the notion of moving the console fully
to userland is definitely not something that has been accepted.
It is interesting to evaluate the solution, but lots of kernel
folks will just turn it down for some simple
On Mon, 9 Feb 2004, Jon Smirl wrote:
There are lots of solutions to this:
1) queue the printk's
2) add an in-kernel path for write to console that cooperates with the normal
user space one
3) if you know you are going to be debugging code like this, use an alternative
solution like the
On Tue, Feb 10, 2004 at 08:41:40AM +1100, Benjamin Herrenschmidt wrote:
|
| - GL cannot be the _only_ API, simply because we don't (and may not have
| for some time) GL support on all cards, while still wanting this new console
| stuff so we don't have to keep the old cruft around
Just so long
--- Linus Torvalds [EMAIL PROTECTED] wrote:
On Mon, 9 Feb 2004, Jon Smirl wrote:
There are lots of solutions to this:
1) queue the printk's
2) add an in-kernel path for write to console that cooperates with the
normal
user space one
3) if you know you are going to be debugging code
On Sun, Feb 08, 2004 at 08:27:17PM -0800, Jon Smirl wrote:
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic but I've
mainly be working on an R200. It is still under development with lots of work to
do.
Ugh. I find
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic but I've
mainly be working on an R200. It is still under development with lots of work to
do.
Major features:
1) Get VBIOS ROM contents IOCTL
2) Driver automaps the
18 matches
Mail list logo
