All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corbin Simpson <mostawesomedude@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: dri-devel@lists.sourceforge.net, Ian Romanick <idr@freedesktop.org>
Subject: Re: glint KMS - how to proceed?
Date: Wed, 14 Jul 2010 13:39:30 -0700	[thread overview]
Message-ID: <AANLkTim_ekRYETofUKIlaMrdENg-fOI2F4LTNIrzcreU@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1007141955360.19942@casper.infradead.org>

Whoo! I'll put this up on k.org as soon as I can get it working.

~ C.

On Wed, Jul 14, 2010 at 12:01 PM, James Simmons <jsimmons@infradead.org> wrote:
>
>> On Wed, Jun 23, 2010 at 1:22 PM, Matt Turner <mattst88@gmail.com> wrote:
>> > On Wed, Jun 23, 2010 at 12:03 PM, James Simmons <jsimmons@infradead.org> wrote:
>> >>
>> >>> I'm working on modesetting, and I'm kind of unsure how to proceed.
>> >>>
>> >>> My repository is here (ignore all the commit dates):
>> >>> http://git.kernel.org/?p=linux/kernel/git/mattst88/glint.git;a=summary
>> >>
>> >> I also did one for the 3Dfx drm driver. Just as a note make sure that your
>> >> glint driver works with the xorg driver. After I had a 3Dfx KMS driver the
>> >> xorg driver no longer worked :-(. I would need to rework the xord driver
>> >> first then be able to submit my KMS driver.
>> >
>> > Is your 3dfx DRM driver available somewhere? It would be interesting to see.
>> >
>> > Thanks,
>> > Matt
>>
>> Ping? Can we see your driver?
>
> http://www.infradead.org/~jsimmons/tdfx.diff
>
>        Sorry the driver bit rotted. I used modification to the dri core to get it
> going and be able to do real mode setting via the fbdev layer. Also the
> machine with a AGP bus I had no longer works. I need to get a new machine
> with a AGP bus that has some power behind it. This driver is updated but I
> doubt it will boot since I couldn't test it.
>        The framebuffer management has much to desire since I couldn't
> find any good docs on TTM. So currently I'm using drm_addmap, yuck :-(
> Tho the posted driver has some ttm hooks in it.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>



-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<MostAwesomeDude@gmail.com>

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--

  reply	other threads:[~2010-07-14 20:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18  1:39 glint KMS - how to proceed? Matt Turner
2010-06-21 17:19 ` Alex Deucher
2010-06-23 16:03 ` James Simmons
2010-06-23 17:22   ` Matt Turner
2010-07-13 17:43     ` Matt Turner
2010-07-14 19:01       ` James Simmons
2010-07-14 20:39         ` Corbin Simpson [this message]
2010-07-14 21:13           ` James Simmons
2010-07-15  1:33             ` Corbin Simpson
2010-07-14 21:03         ` Corbin Simpson

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=AANLkTim_ekRYETofUKIlaMrdENg-fOI2F4LTNIrzcreU@mail.gmail.com \
    --to=mostawesomedude@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@freedesktop.org \
    --cc=jsimmons@infradead.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 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.