From: Jon Smirl <jonsmirl@gmail.com>
To: Mike Mestnik <cheako911@yahoo.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel@lists.sf.net, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Merging DRM and fbdev
Date: Sun, 3 Oct 2004 14:56:07 -0400 [thread overview]
Message-ID: <9e47339104100311566f66eb43@mail.gmail.com> (raw)
In-Reply-To: <20041003183839.36810.qmail@web11903.mail.yahoo.com>
On Sun, 3 Oct 2004 11:38:39 -0700 (PDT), Mike Mestnik
<cheako911@yahoo.com> wrote:
> What about moving the DRM and FB specific code into there own per card
> libs?
>
> radeon - attached to hardware
> radeon-drm
> drm - library
> radeon-fb
> fb - library
> fbcon - library
Fell free to convert the merged radeon driver in to a driver plus two
libs if you want. I'll accept the patch back. You'll need to wait
until I get the merged driver working.
What I don't want is two independent implementations of the hardware
initialization code like we currently have. The point of merging is to
make sure that a single logical driver programs the hardware is a
consistent way.
We spend so much time talking about splitting the radeon driver into
pieces. But I don't hear anyone saying I can't ship my product because
the radeon driver is 120K and all I can handle is 60K. I'm not going
to spend a week's work breaking things up and testing them just
because of some theoretical need for a non-existant embedded system.
When this hypothetical embedded system shows up the people making the
money off from the system can do the work.
If an embedded system is really that memory constrained they should
just use the existing fbdev radeon driver. There is no way a system
with that little of memory needs to worry about VT switching to X with
DRM.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-10-03 18:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 3:55 Merging DRM and fbdev Jon Smirl
2004-10-03 7:26 ` Dave Airlie
2004-10-03 15:33 ` Jon Smirl
2004-10-03 15:50 ` Vladimir Dergachev
2004-10-03 16:24 ` Jon Smirl
2004-10-03 16:59 ` Vladimir Dergachev
2004-10-03 17:55 ` Jon Smirl
2004-10-03 20:37 ` Vladimir Dergachev
2004-10-03 22:42 ` Jon Smirl
2004-10-03 22:16 ` Alan Cox
2004-10-03 22:19 ` Alan Cox
2004-10-04 1:56 ` Vladimir Dergachev
2004-10-03 18:38 ` Mike Mestnik
2004-10-03 18:56 ` Jon Smirl [this message]
2004-10-04 19:48 ` Bill Davidsen
2004-10-03 16:46 ` Jon Smirl
2004-10-04 17:47 ` Tonnerre
2004-10-04 18:42 ` Jon Smirl
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=9e47339104100311566f66eb43@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@linux.ie \
--cc=cheako911@yahoo.com \
--cc=dri-devel@lists.sf.net \
--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