mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vladimir Dergachev <volodya@mindspring.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
	dri-devel@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Merging DRM and fbdev
Date: Sun, 3 Oct 2004 12:59:38 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0410031254280.17448@node2.an-vo.com> (raw)
In-Reply-To: <9e4733910410030924214dd3e3@mail.gmail.com>

>   km - library
>
> Libraries are kernel modules that don't attach to any specific
> hardware, they just supply routines for other drivers to call. We
> might want to change the name of these to libdrm, libfb, libkm.
>
> I haven't looked into Gatos yet but I'd like to see the radeon
> converted to follow the model of all of the other vl4 cards instead of
> having it's own system. In the X on GL world the 2D XAA radeon driver
> is gone. Gatos support will need to live somewhere else.

Jon, this is a common misconception - GATOS km module *does* provide a v4l 
interface.

What is different is that the device configuration (like setting the tuner 
or encoding) is done by Xserver.

All km does is check whether the card can supply a v4l stream and, if so, 
it provides it. This is little different from a webcam driver, especially
if a webcam has its own on/off switch.

The misconception arises from the fact that many v4l programs were only 
made to work with bt848 cards - they would *not* work with webcams any
more than they would work with km.

                               best

                                 Vladimir Dergachev

>
> -- 
> Jon Smirl
> jonsmirl@gmail.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>

  reply	other threads:[~2004-10-03 17:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-03  3:55 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 [this message]
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
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=Pine.LNX.4.61.0410031254280.17448@node2.an-vo.com \
    --to=volodya@mindspring.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jonsmirl@gmail.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®