From: Steven Toth <stoth@linuxtv.org>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Devin Heitmueller <devin.heitmueller@gmail.com>,
rvf16 <rvf16@yahoo.gr>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Multiple em28xx devices
Date: Thu, 09 Apr 2009 12:52:27 -0400 [thread overview]
Message-ID: <49DE27CB.6080600@linuxtv.org> (raw)
In-Reply-To: <d9def9db0904090932o4438902bt83d303f0853e5e11@mail.gmail.com>
Markus Rechberger wrote:
> On Thu, Apr 9, 2009 at 6:28 PM, Steven Toth <stoth@linuxtv.org> wrote:
>> Markus Rechberger wrote:
>>> On Thu, Apr 9, 2009 at 5:48 PM, Mauro Carvalho Chehab
>>> <mchehab@infradead.org> wrote:
>>>> On Thu, 9 Apr 2009 11:39:47 -0400
>>>> Devin Heitmueller <devin.heitmueller@gmail.com> wrote:
>>>>
>>>>> 2009/4/9 rvf16 <rvf16@yahoo.gr>:
>>>>>> So does the upstream driver support all the rest ?
>>>>>> Analog TV
>>>>> Yes
>>>>>
>>>>>> FM radio
>>>>> No
>>>> Yes, it does support FM radio, provided that you proper add radio
>>>> specific
>>>> configuration at em28xx-cards.c.
>>>>
>>> I plan to add support for it to the existing kerneldriver anyway, but
>>> by using userspace drivers.
>>> Those drivers are just ontop of everything and no changes are required
>>> for the existing drivers.
>>>
>>> I'll just intercept all the calls as I do right now already with the
>>> latest device. I ported the entire configuration framework to userland
>>> and it also works on Apple OSX without any change. I'm just using
>>> usbfs for it, PCI config support is possible by using libpci or
>>> opening the corresponding node in the proc filesystem too. This time
>>> there's nothing you can do against it since it requires no change as
>>> it is.
>> Userspace drivers won't be accepted but it's not worth re-opening that old
>> wound - especially since I haven't followed this specific thread.
>>
>
> no problem, as I wrote it sits ontop of everything not needing any kernel hooks.
That's fine, if it's not derived then I have no problem with you keeping control
over your own code.
>
>> I _am_ interested in the fact that you've ported GPL code (frameworks and/or
>> drivers) to Apple, creating derived works.
>>
>
> hehe, I did not touch any GPL code.
>
>> Obviously you'll need to make those changes to the community. Where can I
>> download these?
>
> The framework will be opened when it's time to be opened, right now
> it's only available to interested developers.
Ahh, if it's not GPL code (or derived from GPL) then I'm not interested in it,
and I'm not interested in paying you for access.
- Steve
next prev parent reply other threads:[~2009-04-09 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 14:39 Multiple em28xx devices rvf16
2009-04-09 14:51 ` Markus Rechberger
2009-04-09 15:39 ` Devin Heitmueller
2009-04-09 15:48 ` Mauro Carvalho Chehab
2009-04-09 15:51 ` Devin Heitmueller
2009-04-09 15:52 ` Markus Rechberger
2009-04-09 16:28 ` Steven Toth
2009-04-09 16:32 ` Markus Rechberger
2009-04-09 16:52 ` Steven Toth [this message]
2009-04-09 16:55 ` Markus Rechberger
2009-04-09 16:56 ` Steven Toth
2009-04-09 16:59 ` Markus Rechberger
-- strict thread matches above, loose matches on Subject: below --
2009-04-09 14:17 rvf16
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=49DE27CB.6080600@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=devin.heitmueller@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mrechberger@gmail.com \
--cc=rvf16@yahoo.gr \
/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