public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: Staging tree status for the .32 kernel merge
Date: Mon, 7 Sep 2009 18:14:58 -0700	[thread overview]
Message-ID: <20090908011458.GA29317@kroah.com> (raw)
In-Reply-To: <20090907202134.4feebe6f@caramujo.chehab.org>

On Mon, Sep 07, 2009 at 08:21:34PM -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 2 Sep 2009 21:14:30 -0700
> 
> > 	- go7007.  Ugh.  Unless someone steps up now to take this over,
> > 	  it's going to be removed in .33.  There is no hardware made
> > 	  with this anymore, and no specs around that I know of, and the
> > 	  code isn't the nicest in the world.
> 
> I think nobody will cry if you remove this one. This is an old hardware, and not
> manufactured anymore. The chipset of the compression hardware is
> obsolete and orphaned, as the audio/video unit were sold to another company.

I agree.  I do have a device around here, but it was only for testing,
the company who produced it said they could not release the specs due to
ownership issues.

> > 	- udlfb.  Video over USB, it doesn't get anymore whacked than
> > 	  that.  This is still being developed but the developer doesn't
> > 	  like to do incremental updates for some odd reason.  Hopefully
> > 	  he pops up again with an update.  But for now, it is quite
> > 	  workable for a number of developers.
> 
> Is this a video streaming driver (like other V4L2 drivers) or a video adapter
> driver?

Video adapter driver, it's a frame buffer driver, sorry for any
confusion.

thanks,

greg k-h

  reply	other threads:[~2009-09-08  1:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03  4:14 Staging tree status for the .32 kernel merge Greg KH
2009-09-03  8:49 ` Johannes Berg
2009-09-03 12:48   ` Stefan Lippers-Hollmann
2009-09-03 17:57     ` Greg KH
2009-09-03 18:35       ` Kalle Valo
2009-09-03 19:01         ` Greg KH
2009-09-03 13:14   ` Bartlomiej Zolnierkiewicz
2009-09-03 16:17   ` Christoph Hellwig
2009-09-03 17:55     ` Greg KH
2009-09-03 18:40       ` Christoph Hellwig
2009-09-03 18:55         ` Greg KH
2009-09-03 19:16           ` Christoph Hellwig
2009-09-05  0:16           ` Marcel Holtmann
2009-09-05  0:29             ` Greg KH
2009-09-03 19:35   ` Luis R. Rodriguez
2009-09-03 19:41     ` Greg KH
2009-09-04 10:20 ` Wolfram Sang
2009-09-04 18:25 ` Belisko Marek
2009-09-05 12:39 ` Willy Tarreau
2009-09-05 14:50   ` Greg KH
2009-09-10 21:57     ` Peter Huewe
2009-09-06  5:28 ` Pavel Machek
2009-09-07 15:55   ` Daniel Walker
2009-09-09  9:57     ` Pavel Machek
2009-09-09 14:19       ` Daniel Walker
2009-09-09  8:01         ` Pavel Machek
2009-09-09 21:47         ` Pavel Machek
2009-09-09 21:53         ` Brian Swetland
2009-09-09 22:25           ` Huntsman, Bryan
2009-09-07 23:12   ` Mauro Carvalho Chehab
2009-09-09  8:10     ` Pavel Machek
2009-09-07 23:21 ` Mauro Carvalho Chehab
2009-09-08  1:14   ` Greg KH [this message]
2009-09-12 19:40 ` Frontier USB Drivers (Was: Staging tree status for the .32 kernel merge) Dave Taht
2009-09-14 17:35   ` Greg KH
2009-09-15  9:29     ` Clemens Ladisch

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=20090908011458.GA29317@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox