From: Dave Airlie <airlied@linux.ie>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Keith Whitwell <keith@tungstengraphics.com>,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: DRM and 2.4 ...
Date: Mon, 16 Aug 2004 11:42:00 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0408161137330.21177@skynet> (raw)
In-Reply-To: <20040816101426.GB31696@devserv.devel.redhat.com>
>
> DRM_IOCTL_ARGS, DRM_ERR, DRM_CURRENTPID, DRM_UDELAY, DRM_READMEMORYBARRIER,
> DRM_COPY_FROM_USER_IOCTL etc etc existed prior to freebsd support? Oh my
> god...
I'm currently open for constructive critics with ideas on how to fix these
things, the DRM is open for business if we can fix things up now it will
be a lot easier while I'm knee deep with time than after I'm finished and
back travelling .. should we have try to implement Linux fns in BSD, what
do we do if more parameters/info are needed from a BSD side, or do we try
and sideline all these into a separate library of functions and wrap them
on both bsd and linux?
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person
next prev parent reply other threads:[~2004-08-16 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 5:56 Dave Airlie
2004-08-16 7:11 ` Arjan van de Ven
2004-08-16 9:43 ` Keith Whitwell
2004-08-16 9:46 ` Arjan van de Ven
2004-08-16 10:12 ` Keith Whitwell
2004-08-16 10:14 ` Arjan van de Ven
2004-08-16 10:42 ` Dave Airlie [this message]
2004-08-16 10:48 ` Arjan van de Ven
2004-08-16 11:42 ` Keith Whitwell
2004-08-16 11:58 ` Arjan van de Ven
2004-08-16 12:18 ` Keith Whitwell
2004-08-16 11:14 ` Alan Cox
2004-08-16 12:22 ` Dave Airlie
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=Pine.LNX.4.58.0408161137330.21177@skynet \
--to=airlied@linux.ie \
--cc=arjanv@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=keith@tungstengraphics.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®