Hi Devin,
On 07/22/2013 09:48 PM, Devin Heitmueller wrote:
Hello,
I'm doing some cleanup on the au8522 driver, and one thing I noticed
was that you are actually allowed to issue an S_INPUT while streaming
is active. This seems like dangerous behavior, since it can result in
things like
Hi Alan,
On Monday 22 of July 2013 10:44:39 Alan Stern wrote:
On Mon, 22 Jul 2013, Kishon Vijay Abraham I wrote:
The PHY and the controller it is attached to are both physical
devices.
The connection between them is hardwired by the system
manufacturer and cannot be
[Fixed address of devicetree mailing list and added more people on CC.]
For reference, full thread can be found under following link:
http://thread.gmane.org/gmane.linux.ports.arm.kernel/252813
Best regards,
Tomasz
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
On Monday 22
Hi Hans,
On Sat, Jul 13, 2013 at 2:20 PM, Prabhakar Lad
prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
This patch series replaces existing resource handling in the
driver with managed device resource.
Lad, Prabhakar (5):
media: davinci: vpbe_venc:
All,
I do not know why I keep receiving these e-mails from multiple people. Could
you please remove me from your e-mail lists?
Thanks!
-Tobin Abraham
-Original Message-
From: davinci-linux-open-source-bounces+t-abraham=ti@linux.davincidsp.com
On Tue 23 July 2013 13:17:43 Prabhakar Lad wrote:
Hi Hans,
On Sat, Jul 13, 2013 at 2:20 PM, Prabhakar Lad
prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
This patch series replaces existing resource handling in the
driver with managed device resource.
Abraham,
On Tue, Jul 23, 2013 at 5:14 PM, Abraham, Tobin t-abra...@ti.com wrote:
All,
I do not know why I keep receiving these e-mails from multiple people. Could
you please remove me from your e-mail lists?
Please follow this link [1] to un subscribe yourself from the mailing list.
[1]
It is not allowed to build driver as a build-in when RC_CORE
(remote controller support) is build as a module.
randconfig build error with next-20130719, in drivers/media/usb
drivers/built-in.o: In function `dvb_usbv2_disconnect':
(.text+0x154b39): undefined reference to `rc_unregister_device'
The following changes since commit 1c26190a8d492adadac4711fe5762d46204b18b0:
[media] exynos4-is: Correct colorspace handling at FIMC-LITE
(2013-06-28 15:33:27 -0300)
are available in the git repository at:
git://linuxtv.org/anttip/media_tree.git kconfig_fix
for you to fetch changes up
Em Mon, 22 Jul 2013 20:24:41 -0600
Chris Lee update...@gmail.com escreveu:
- cleanup tuning code
- fix tuning for some systems/modulations/fecs
- add Digicipher II and DSS tuning abilities
- update the property_cache once tuning succeeds with the actual tuned values
- implement
Hi Fabio,
Am Montag, den 22.07.2013, 22:38 -0300 schrieb Fabio Estevam:
From: Fabio Estevam fabio.este...@freescale.com
Some resources were not being released in the error path and some were
released
in the incorrect order.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Em Mon, 22 Jul 2013 19:28:55 -0600
Chris Lee update...@gmail.com escreveu:
By using DTV_SET_PROPERTY I can run though a list of possible systems
to determine what is supported and what isnt. I havent looked too far
but I think it uses delsys to determine this information. Which I can
already
Hi Fabio,
Am Montag, den 22.07.2013, 22:38 -0300 schrieb Fabio Estevam:
From: Fabio Estevam fabio.este...@freescale.com
clk_prepare_enable() may fail, so let's check its return value and propagate
it
in the case of error.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
-
On Sat, Jul 20, 2013 at 1:57 AM, Chris Lee update...@gmail.com wrote:
In frontend.h we have a struct called dvb_frontend_ops, in there we
have an element called delsys to show the delivery systems supported
by the tuner, Id like to propose we add onto that with delmod and
delfec.
Its not a
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
Thanks for helping to clarify the issues here.
Okay. Are PHYs _always_ platform devices?
They can be i2c, spi or any other device types as well.
In those other cases, presumably
On Tuesday 23 of July 2013 10:37:05 Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
Thanks for helping to clarify the issues here.
Okay. Are PHYs _always_ platform devices?
They can be i2c, spi or any
Will do, thanks for being patient, Im new to submitting patch's. I've
got lots more coming :)
Digicipher requires no additional changes, Digicipher is close enough
to dvb that you can tune it and use any app you want just like normal.
DSS is another story, I'll leave that patch for last as I can
Signed-off-by: Chris Lee update...@gmail.com
---
drivers/media/usb/dvb-usb/gp8psk-fe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/dvb-usb/gp8psk-fe.c
b/drivers/media/usb/dvb-usb/gp8psk-fe.c
index 67957dd..5864f37 100644
---
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
Thanks for helping to clarify the issues here.
Okay. Are PHYs _always_ platform devices?
They can be i2c, spi or any other
Signed-off-by: Chris Lee update...@gmail.com
---
drivers/media/usb/dvb-usb/gp8psk-fe.c | 13 ++---
drivers/media/usb/dvb-usb/gp8psk.h| 1 +
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/media/usb/dvb-usb/gp8psk-fe.c
b/drivers/media/usb/dvb-usb/gp8psk-fe.c
Hi Sylwester,
On Mon, Jul 22, 2013 at 11:34 PM, Sylwester Nawrocki
s.nawro...@samsung.com wrote:
Hello,
This is a few patches for the v4l2-async API I wrote while adding
the asynchronous subdev registration support to the exynos4-is
driver.
The most significant change is addition of
Hi Sylwester,
On Mon, Jul 22, 2013 at 11:34 PM, Sylwester Nawrocki
s.nawro...@samsung.com wrote:
This is a purely cosmetic change. Since the 'subdev' member
points to an array of subdevs it seems more intuitive to name
it in plural form.
Signed-off-by: Sylwester Nawrocki
---
drivers/media/usb/dvb-usb/gp8psk-fe.c | 2 +-
include/uapi/linux/dvb/frontend.h | 4
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/usb/dvb-usb/gp8psk-fe.c
b/drivers/media/usb/dvb-usb/gp8psk-fe.c
index 223a3ca..fcdf82c 100644
---
Genpix Skywalker and 8psk-to-usb devices do not support dvb-s2.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
---
drivers/media/usb/dvb-usb/gp8psk-fe.c | 111 +-
drivers/media/usb/dvb-usb/gp8psk.h| 1 +
include/uapi/linux/dvb/frontend.h | 1 +
3 files changed, 111 insertions(+), 2 deletions(-)
diff --git a/drivers/media/usb/dvb-usb/gp8psk-fe.c
Correct, but many older userland applications used SYS_DVBS2 to tune
before SYS_TURBO was added. I have no problem removing it but others
might.
from gp8psk-fe.c
switch (c-delivery_system) {
case SYS_DVBS:
if (c-modulation != QPSK) {
deb_fe(%s: unsupported modulation selected (%d)\n,
__func__,
Hi Sylwester,
On 22 July 2013 22:48 Sylwester Nawrocki wrote:
On 07/15/2013 11:18 AM, Thomas Vajzovic wrote:
On 10 July 2013 20:44 Sylwester Nawrocki wrote:
On 07/07/2013 10:18 AM, Thomas Vajzovic wrote:
On 06 July 2013 20:58 Sylwester Nawrocki wrote:
On 07/05/2013 10:22 AM, Thomas Vajzovic
fix: DVB-S QPSK and TURBO QPSK have different fec tuning values
add: DSS
add: DCII
Signed-off-by: Chris Lee update...@gmail.com
---
drivers/media/usb/dvb-usb/gp8psk-fe.c | 180 ++
1 file changed, 116 insertions(+), 64 deletions(-)
diff --git
On Tue, Jul 23, 2013 at 08:48:24PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
Thanks for helping to clarify the issues here.
Correct, but many older userland applications used SYS_DVBS2 to tune
before SYS_TURBO was added. I have no problem removing it but others
might.
I think the best solution here would be not to put false info in the
driver and notify the author(s) of any apps still not updated to use
SYS_TURBO,
Hi Greg,
On Tuesday 23 July 2013 09:48 PM, Greg KH wrote:
On Tue, Jul 23, 2013 at 08:48:24PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
On Tue, Jul 23, 2013 at 09:58:34PM +0530, Kishon Vijay Abraham I wrote:
Hi Greg,
On Tuesday 23 July 2013 09:48 PM, Greg KH wrote:
On Tue, Jul 23, 2013 at 08:48:24PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013,
Not all tuners support all fec's
- genpix devices support an odd 5/11 fec for digicipher, pretty sure
no one else does.
- stv0899 supports 1/2, 2/3, 3/4, 5/6, 6/7, 7/8
- stv0900 supports 1/2, 3/5, 2/3, 3/4, 4/5, 5/6, 8/9, 9/10
Not all tuners support the entire range of fec's. I think this is
On Tuesday 23 of July 2013 09:18:46 Greg KH wrote:
On Tue, Jul 23, 2013 at 08:48:24PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi
Ive got no problem pulling it out, doesnt affect anything on my end.
Do I need to resubmit the patch ?
Chris Lee
On Tue, Jul 23, 2013 at 10:22 AM, VDR User user@gmail.com wrote:
Correct, but many older userland applications used SYS_DVBS2 to tune
before SYS_TURBO was added. I have no
#Sorry for sending to individual email ids
Hi,
I am trying to use Prof DVB-S2 USB device with Linux host. Device gets
detected. But, I am facing the following problems.
1. It takes approximately 21 minutes to get /dev/dvb/adapter0/frontend0
and /dev/dvb/adapter0/demux0 to get
Hi Laurent,
On Thu, Jul 18, 2013 at 03:07:26AM +0200, Laurent Pinchart wrote:
...
An unrelated thing, which is out of scope for now, but something to think
about: when passing around large amounts of (configuration) data the number
of times the data is copied really counts. Especially on
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Tue Jul 23 19:00:18 CEST 2013
git branch: test
git hash: c859e6ef33ac0c9a5e9e934fe11a2232752b4e96
gcc
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
Ick, no. Why can't you just pass the pointer to the phy itself? If you
had a priv pointer to search from, then you could have just passed the
original phy pointer in the first place, right?
IMHO it would be better if you
On Tue, Jul 23, 2013 at 10:37:05AM -0400, Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
Okay. Are PHYs _always_ platform devices?
They can be i2c, spi or any other device types as well.
In those other cases, presumably there is no platform data associated
with the PHY
On Tue, Jul 23, 2013 at 10:37:11AM -0700, Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
I fully agree that a simple, single string will not scale even in some, not
so uncommon cases, but there is already a lot of existing lookup solutions
over the kernel and
On Tuesday 23 of July 2013 10:37:11 Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
Ick, no. Why can't you just pass the pointer to the phy itself? If
you
had a priv pointer to search from, then you could have just passed
the
original phy pointer in
On Tue, Jul 23, 2013 at 06:44:56PM +0100, Mark Brown wrote:
On Tue, Jul 23, 2013 at 10:37:11AM -0700, Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
I fully agree that a simple, single string will not scale even in some,
not
so uncommon cases, but there
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang w...@the-dreams.de
---
Please apply via the subsystem-tree.
drivers/media/platform/coda.c |5 -
1 file changed, 5 deletions(-)
diff --git
clk_prepare_enable() may fail, so let's check its return value and propagate it
in the case of error.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Changes since v3:
- Adapt it to make error handling easier
Changes since v2:
- Release the previously acquired resources
Changes since
Some resources were not being released in the error path and some were released
in the incorrect order.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Changes since v3:
- Only disable the clocks after v4l2_m2m_ctx_release()
Changes since v2:
- Newly introduced in this series
When using devm_ioremap_resource(), we do not need to check the return value of
platform_get_resource(), so just remove it.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
Acked-by: Philipp Zabel p.za...@pengutronix.de
---
Changes since v3:
- None
Changes since v2:
- None
Changes since
On Tue, Jul 23, 2013 at 07:48:11PM +0200, Tomasz Figa wrote:
On Tuesday 23 of July 2013 10:37:11 Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
Ick, no. Why can't you just pass the pointer to the phy itself? If
you
had a priv pointer to search from,
This patch series is a refactoring of the exynos4-is driver to get rid
of the common fimc-is-sensor driver and to adapt it to use standard
sensor subdev drivers, one per each image sensor type.
Then a clock provider is added to the exynos4-is driver and the s5k6a3
subdev is modified to use one of
This patch adds subdev driver for Samsung S5K6A3 raw image sensor.
As it is intended at the moment to be used only with the Exynos
FIMC-IS (camera ISP) subsystem it is pretty minimal subdev driver.
It doesn't do any I2C communication since the sensor is controlled
by the ISP and its own firmware.
This patch converts the driver to use v4l2 asynchronous subdev
registration API an the common clock API.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/media/i2c/s5k6a3.c | 63
Use clk_prepare_enable()/clk_disable_unprepare() instead of
separately prearing/unparing the clk_cam clocks. This simplifies
the code that is now mostly not going to be used, function
__fimc_md_set_camclk() is only left for S5PV210 platform which
is not yet converted to Device Tree.
This patch adds clock provider to expose the sclk_cam0/1 clocks
for image sensor subdevs.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../devicetree/bindings/media/samsung-fimc.txt | 17 +++-
Add support registering external sensor subdevs using the v4l2-async API.
The async API is used only for sensor subdevs and only for platforms
instatiated from Device Tree.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
This patch removes the common fimc-is-sensor driver for image sensors
that are normally controlled by the FIMC-IS firmware. The FIMC-IS
driver now contains only a table of properties specific to each sensor.
The sensor properties required for the ISP's firmware are parsed from
device tree and
On Tue, Jul 23, 2013 at 11:01:10AM -0700, Greg KH wrote:
On Tue, Jul 23, 2013 at 06:44:56PM +0100, Mark Brown wrote:
What are the problems you are seeing with doing things with lookups?
You don't know the id of the device you are looking up, due to
multiple devices being in the system
On Tue, 23 Jul 2013, Tomasz Figa wrote:
IMHO it would be better if you provided some code example, but let's try to
check if I understood you correctly.
8
[Board file]
static struct phy my_phy;
static struct
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
You don't know the id of the device you are looking up, due to
multiple devices being in the system (dynamic ids, look back earlier in
this thread for details about that.)
I got copied in very late so don't have most of the
On Tuesday 23 of July 2013 12:44:23 Greg KH wrote:
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
You don't know the id of the device you are looking up, due to
multiple devices being in the system (dynamic ids, look back earlier
in
this thread for details about that.)
On Tuesday 23 of July 2013 15:36:00 Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
IMHO it would be better if you provided some code example, but let's
try to check if I understood you correctly.
8---
-
On Tuesday 23 of July 2013 11:04:14 Greg KH wrote:
On Tue, Jul 23, 2013 at 07:48:11PM +0200, Tomasz Figa wrote:
On Tuesday 23 of July 2013 10:37:11 Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
Ick, no. Why can't you just pass the pointer to the phy
On Tue, Jul 23, 2013 at 10:07:52PM +0200, Tomasz Figa wrote:
On Tuesday 23 of July 2013 12:44:23 Greg KH wrote:
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
You don't know the id of the device you are looking up, due to
multiple devices being in the system (dynamic ids,
On Tue, 23 Jul 2013, Tomasz Figa wrote:
That's what I was going to suggest too. The struct phy is defined in
the board file, which already knows about all the PHYs that exist in
the system. (Or perhaps it is allocated dynamically, so that when many
board files are present in the same
On Tue, Jul 23, 2013 at 10:17 PM, Chris Lee update...@gmail.com wrote:
Not all tuners support all fec's
Nitpick: tuner doesn't have anything to do with FEC, it just provides IQ
outputs to the demodulator. ;-)
That said;
Demods support all FEC's relevant to their delivery systems. It's just
Hi
As was a compilation error, I used git bisect skip. From what I've come up with
something that I think is not what I'm looking for.
Is it advisable to do it again? and where you get an error trying to git bisect
bad and see where it arrived and then git bisec good again.
what I got was:
On Tuesday 23 of July 2013 16:53:55 Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
That's what I was going to suggest too. The struct phy is defined
in
the board file, which already knows about all the PHYs that exist in
the system. (Or perhaps it is allocated
On Tuesday 23 of July 2013 13:50:07 Greg KH wrote:
On Tue, Jul 23, 2013 at 10:07:52PM +0200, Tomasz Figa wrote:
On Tuesday 23 of July 2013 12:44:23 Greg KH wrote:
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
You don't know the id of the device you are looking up, due to
On 23-07-13 18:52, Krishna Kishore wrote:
#Sorry for sending to individual email ids
Hi,
I am trying to use Prof DVB-S2 USB device with Linux host. Device gets
detected. But, I am facing the following problems.
You will need to provide much more information then that. What does
dmesg
On Tue, 23 Jul 2013, Tomasz Figa wrote:
If you want to keep the phy struct completely separate from the board
file, there's an easy way to do it. Let's say the board file knows
about N different PHYs in the system. Then you define an array of N
pointers to phys:
struct phy
On Tue, Jul 23, 2013 at 11:05:48PM +0200, Tomasz Figa wrote:
That's not so bad, as long as you let the phy core use whatever name it
wants for the device when it registers it with sysfs.
Yes, in regulator core consumer names are completely separated from this.
Regulator core simply
Nitpick: tuner doesn't have anything to do with FEC, it just provides IQ
outputs to the demodulator. ;-)
ya ya :) you knew what I meant, not what I said hehe
Demods support all FEC's relevant to their delivery systems. It's just that
some devices likely do support some additional states.
On Tuesday 23 of July 2013 17:14:20 Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
If you want to keep the phy struct completely separate from the
board
file, there's an easy way to do it. Let's say the board file knows
about N different PHYs in the system. Then you
Hi
I forgot, in this section I put BAD because not have picture or sound,
but if signal.
alfredo@linux-puon:/usr/src/git/linux git stash
Saved working directory and index state WIP on (no branch): 2827e1f
[media] tlg2300: convert set_fontend to use DVBv5 parameters
HEAD is now at 2827e1f
Hi Sylwester,
On Sun, Jul 21, 2013 at 10:38:18PM +0200, Sylwester Nawrocki wrote:
On 07/19/2013 10:28 PM, Sakari Ailus wrote:
On Sat, Jul 06, 2013 at 09:58:23PM +0200, Sylwester Nawrocki wrote:
On 07/05/2013 10:22 AM, Thomas Vajzovic wrote:
Hello,
I am writing a driver for the sensor
Revised patch, I seperated the DCII systems into their correct DCII system and
4x different modulations.
Chris Lee
---
drivers/media/usb/dvb-usb/gp8psk-fe.c | 263 +-
drivers/media/usb/dvb-usb/gp8psk.h| 2 +
include/uapi/linux/dvb/frontend.h | 6 +
3
Removes unnecessary query of buffer state. The code already checks if stream
is active or not.
Signed-off-by: Dean Anderson linux-...@sensoray.com
---
drivers/media/usb/s2255/s2255drv.c |9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git
On Wed, Jul 24, 2013 at 2:57 AM, Chris Lee update...@gmail.com wrote:
Nitpick: tuner doesn't have anything to do with FEC, it just provides IQ
outputs to the demodulator. ;-)
ya ya :) you knew what I meant, not what I said hehe
Demods support all FEC's relevant to their delivery systems.
The problems isnt for tuners where FEC_AUTO does work, its more for
ones that dont work like the genpix. Im sure there are others too. I
still think that userland applications should be able to poll that
info and that the ability to poll the info is a good thing not a bad
thing.
oh well, lets let
On Tue, Jul 23, 2013 at 3:57 PM, Chris Lee update...@gmail.com wrote:
The problems isnt for tuners where FEC_AUTO does work, its more for
ones that dont work like the genpix. Im sure there are others too.
If FEC_AUTO for turbo qpsk can be fixed in the Genpix firmware, maybe
it's worth seeing if
He is, I talked to him last month about various things and he
mentioned turbofec-qpsk FEC_AUTO is semi working and its in his plans.
Chris
On Tue, Jul 23, 2013 at 5:39 PM, VDR User user@gmail.com wrote:
On Tue, Jul 23, 2013 at 3:57 PM, Chris Lee update...@gmail.com wrote:
The problems isnt
On Tue, Jul 23, 2013 at 12:44:23PM -0700, Greg KH wrote:
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
statement. In any case this is why the APIs doing lookups do the
lookups in the context of the requesting device - devices ask for
whatever name they use locally.
What do
Vážení E-mail užívateľa;
Prekročili ste 23432 boxy nastaviť svoje
Webová služba / Administrátor, a budete mať problémy pri odosielaní a
prijímať e-maily, kým znova overiť. Musíte aktualizovať kliknutím na
odkaz nižšie a vyplňte údaje pre overenie vášho účtu
Prosím, kliknite na odkaz nižšie
82 matches
Mail list logo