From: John Hunter <zhjwpku@gmail.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: Why no geode subsystem contained in drm
Date: Tue, 17 Mar 2015 17:09:28 +0800 [thread overview]
Message-ID: <CAEG8a3+XA1VH1=RaAnJbWbc+E+h+jx6q5v0brK_Ge2QqmEAQ7A@mail.gmail.com> (raw)
In-Reply-To: <CAH9NwWfuyVjysUvuRipPpnqNdyAo4nyV5Ba_4Z-VvefJ7OyGHg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]
Thank you, Christian
Cheers,
John
On Tue, Mar 17, 2015 at 4:43 PM, Christian Gmeiner <
christian.gmeiner@gmail.com> wrote:
> Hi John
>
> > I noticed that there is no geode subsystem in the drm directory.
> > I have a system using the geode LX framebuffer and
> > xserver-xorg-video-geode. I am wondering if we can add the drm
> > part of geode lx to let it support the dri?
> >
>
> The geode thing is nearly EOL and is quite old to do some serious work.
> But you
> can always do everything you want in your spare time. I think there maybe
> some
> guys and girls out there which would love some thing like this :)
>
> > How about VIVANTE then?
> >
>
> wip -
> https://github.com/austriancoder/linux/tree/master/drivers/staging/etnaviv
>
> greets
> --
> Christian Gmeiner, MSc
>
> https://soundcloud.com/christian-gmeiner
>
--
Best regards
Junwang Zhao
Microprocessor Research and Develop Center
Department of Computer Science &Technology
Peking University
Beijing, 100871, PRC
[-- Attachment #1.2: Type: text/html, Size: 1760 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-03-17 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 8:19 Why no geode subsystem contained in drm John Hunter
2015-03-17 8:43 ` Christian Gmeiner
2015-03-17 9:09 ` John Hunter [this message]
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='CAEG8a3+XA1VH1=RaAnJbWbc+E+h+jx6q5v0brK_Ge2QqmEAQ7A@mail.gmail.com' \
--to=zhjwpku@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.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.