All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgi Chorbadzhiyski <gf@unixsol.org>
To: Bjoern <lkml@call-home.ch>, Ralph Metzler <rjkm@metzlerbros.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Rudy Zijlstra <rudy@grumpydevil.homelinux.org>,
	Thomas Kaiser <thomas@kaiser-linux.li>
Subject: Re: ddbridge -- kernel 3.15.6
Date: Fri, 01 Aug 2014 08:08:52 +0300	[thread overview]
Message-ID: <53DB20E4.7020803@unixsol.org> (raw)
In-Reply-To: <1406868897.2548.15.camel@bjoern-W35xSTQ-370ST>

On 8/1/14 7:54 AM, Bjoern wrote:
> On Do, 2014-07-31 at 09:38 +0200, Ralph Metzler wrote:

>> It is not like drivers are not available and supported, just
>> not in the mainline kernel tree. 
> 
> Right... and I hope that can be changed. I really really like the DD
> hardware I have, but always having to rebuild everything with a new
> kernel is just not my idea of how hardware should run in 2014 on Linux
> anymore.

I have more than 30 ddbridge dvb-s devices and more than 30 dvb-c/t devices.

The fact that the drivers are not in the main tree is the biggest problem
with these devices. The hardware is great (never had a problem with it)
but having to install experimental media build is just stupid.

When I bought the devices I knew that the driver is not in the main tree
but I really hoped that this would change. Now 3 years later it is still
not the case. That's bullshit.

Come on Digital Devices, you have the drivers, please, pretty please, submit
them upstream, go through the merge process and make us - our clients a
happy bunch.

Like Bjoern said, it's 2014, you have the drivers, keeping them out
of main kernel and having your customers go through hoops to get them
working is not acceptable.

-- 
Georgi Chorbadzhiyski | http://georgi.unixsol.org/ | http://github.com/gfto/

  reply	other threads:[~2014-08-01  5:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 13:28 ddbridge -- kernel 3.15.6 Rudy Zijlstra
     [not found] ` <6E594BCC1018445BA338AAABB100405C@ci5fish>
2014-07-18 14:31   ` Rudy Zijlstra
     [not found]     ` <BAE402E8671443828B8815421BDD81CD@ci5fish>
2014-07-18 15:39       ` Rudy Zijlstra
2014-07-18 16:27         ` Rudy Zijlstra
     [not found]           ` <B7F8B540D6D44D08A40DBFA9508FA901@ci5fish>
2014-07-18 21:16             ` Rudy Zijlstra
2014-07-19 17:49 ` Thomas Kaiser
2014-07-30  5:13   ` Bjoern
2014-07-30 13:00     ` Antti Palosaari
2014-07-30 20:52       ` Antti Palosaari
     [not found]         ` <1406753806.49348.YahooMailNeo@web162403.mail.bf1.yahoo.com>
2014-07-30 21:04           ` Antti Palosaari
2014-07-30 21:06         ` Rudy Zijlstra
     [not found]     ` <21465.62099.786583.416351@morden.metzler>
2014-08-01  4:54       ` Bjoern
2014-08-01  5:08         ` Georgi Chorbadzhiyski [this message]
2014-08-01  7:38           ` Thomas Kaiser
2014-08-02 11:02           ` Bjoern
2014-08-02 11:14             ` Bjoern
2014-08-02 15:22             ` Antti Palosaari
2014-08-02 16:35               ` Ralph Metzler
2014-07-30 21:03   ` Rudy Zijlstra
2014-07-31  7:01     ` Thomas Kaiser

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=53DB20E4.7020803@unixsol.org \
    --to=gf@unixsol.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lkml@call-home.ch \
    --cc=rjkm@metzlerbros.de \
    --cc=rudy@grumpydevil.homelinux.org \
    --cc=thomas@kaiser-linux.li \
    /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.