On 19-09-12 22:52, Devin Heitmueller wrote:
On Wed, Sep 19, 2012 at 2:44 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly.
Scanning using
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly.
Scanning using dvbscan works without problems, Locking onto a channel
using tzap also works fine. Only playback using tzap -r +
On 19-09-12 23:36, Antti Palosaari wrote:
This is review, please fix those minor findings mentioned and resend
fixed patch!
Will do!
On 09/19/2012 09:44 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The
On 09/20/2012 09:57 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly.
Scanning using dvbscan works without problems, Locking onto a channel
using
On Thu, Sep 20, 2012 at 2:54 PM, Oliver Schinagl
oliver+l...@schinagl.nl wrote:
dvbscan and dvbv5-scan does constantly say 'tuning failed' but it does say
that on my terratec too. It does work fine however, so probably a bug in
driver/tool unrelated to this patch.
Just to be clear, the message
On 20-09-12 21:15, Antti Palosaari wrote:
On 09/20/2012 09:57 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly.
Scanning using dvbscan works
On 09/20/2012 10:28 PM, Oliver Schinagl wrote:
On 20-09-12 21:15, Antti Palosaari wrote:
On 09/20/2012 09:57 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and
On 19-09-12 00:42, Antti Palosaari wrote:
On 09/19/2012 01:22 AM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly. It uses the
af9035 USB Bridge
On 19-09-12 00:51, Antti Palosaari wrote:
On 09/18/2012 08:18 PM, Oliver Schinagl wrote:
On 09/17/12 23:57, Oliver Schinagl wrote:
On 09/17/12 23:07, Antti Palosaari wrote:
On 09/17/2012 11:43 PM, Oliver Schinagl wrote:
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is
On 09/19/2012 12:52 PM, Oliver Schinagl wrote:
On 19-09-12 00:42, Antti Palosaari wrote:
On 09/19/2012 01:22 AM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and
On 09/19/2012 01:41 PM, Oliver Schinagl wrote:
On 19-09-12 00:51, Antti Palosaari wrote:
On 09/18/2012 08:18 PM, Oliver Schinagl wrote:
On 09/17/12 23:57, Oliver Schinagl wrote:
On 09/17/12 23:07, Antti Palosaari wrote:
On 09/17/2012 11:43 PM, Oliver Schinagl wrote:
On 09/17/12 17:20,
On 09/19/12 12:41, Antti Palosaari wrote:
On 09/19/2012 12:52 PM, Oliver Schinagl wrote:
On 19-09-12 00:42, Antti Palosaari wrote:
On 09/19/2012 01:22 AM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The
On 09/19/12 19:57, Oliver Schinagl wrote:
On 09/19/12 12:41, Antti Palosaari wrote:
On 09/19/2012 12:52 PM, Oliver Schinagl wrote:
On 19-09-12 00:42, Antti Palosaari wrote:
On 09/19/2012 01:22 AM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly.
Scanning using dvbscan works without problems, Locking onto a channel
using tzap also works fine. Only playback using tzap -r +
On Wed, Sep 19, 2012 at 2:44 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly.
Scanning using dvbscan works without problems, Locking onto a
This is review, please fix those minor findings mentioned and resend
fixed patch!
On 09/19/2012 09:44 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads
Devin Heitmueller dheitmuel...@kernellabs.com wrote:
On Wed, Sep 19, 2012 at 2:44 PM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The
driver
in its current form gets detected and loads properly.
Scanning
On 09/17/12 23:57, Oliver Schinagl wrote:
On 09/17/12 23:07, Antti Palosaari wrote:
On 09/17/2012 11:43 PM, Oliver Schinagl wrote:
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is really working and it says chip id is 0x5a
then it is different than driver knows. It could
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly. It uses the
af9035 USB Bridge chip, with an af9033 demodulator. The tuner used is
the FCI FC2580.
I have only done a quick dvb
On 09/19/2012 01:22 AM, oli...@schinagl.nl wrote:
From: Oliver Schinagl oli...@schinagl.nl
This is initial support for the Asus MyCinema U3100Mini Plus. The driver
in its current form gets detected and loads properly. It uses the
af9035 USB Bridge chip, with an af9033 demodulator. The tuner
On 09/18/2012 08:18 PM, Oliver Schinagl wrote:
On 09/17/12 23:57, Oliver Schinagl wrote:
On 09/17/12 23:07, Antti Palosaari wrote:
On 09/17/2012 11:43 PM, Oliver Schinagl wrote:
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is really working and it says chip id is
0x5a
On 09/17/2012 06:20 PM, Oliver Schinagl wrote:
On 17-09-12 15:52, Antti Palosaari wrote:
On 09/17/2012 04:26 PM, Oliver Schinagl wrote:
On 17-09-12 15:16, Antti Palosaari wrote:
On 09/17/2012 04:02 PM, Oliver Schinagl wrote:
On 17-09-12 10:25, Oliver Schinagl wrote:
On 17-09-12 01:36, Antti
On 17-09-12 01:36, Antti Palosaari wrote:
On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I
On 17-09-12 10:25, Oliver Schinagl wrote:
On 17-09-12 01:36, Antti Palosaari wrote:
On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
On 17-09-12 15:16, Antti Palosaari wrote:
On 09/17/2012 04:02 PM, Oliver Schinagl wrote:
On 17-09-12 10:25, Oliver Schinagl wrote:
On 17-09-12 01:36, Antti Palosaari wrote:
On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM,
On 09/17/2012 04:26 PM, Oliver Schinagl wrote:
On 17-09-12 15:16, Antti Palosaari wrote:
On 09/17/2012 04:02 PM, Oliver Schinagl wrote:
On 17-09-12 10:25, Oliver Schinagl wrote:
On 17-09-12 01:36, Antti Palosaari wrote:
On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
On 09/16/12 19:25, Antti
On 17-09-12 15:52, Antti Palosaari wrote:
On 09/17/2012 04:26 PM, Oliver Schinagl wrote:
On 17-09-12 15:16, Antti Palosaari wrote:
On 09/17/2012 04:02 PM, Oliver Schinagl wrote:
On 17-09-12 10:25, Oliver Schinagl wrote:
On 17-09-12 01:36, Antti Palosaari wrote:
On 09/17/2012 01:10 AM,
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is really working and it says chip id is 0x5a
then it is different than driver knows. It could be new revision of
tuner. Change chip_id to match 0x5a
Ah, so it's called chip_id on one end, but tuner_id on the other end.
If/when
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is really working and it says chip id is 0x5a
then it is different than driver knows. It could be new revision of
tuner. Change chip_id to match 0x5a
Ah, so it's called chip_id on one end, but tuner_id on the other end.
If/when
On 09/17/2012 11:43 PM, Oliver Schinagl wrote:
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is really working and it says chip id is 0x5a
then it is different than driver knows. It could be new revision of
tuner. Change chip_id to match 0x5a
Ah, so it's called chip_id on
On 09/17/12 23:07, Antti Palosaari wrote:
On 09/17/2012 11:43 PM, Oliver Schinagl wrote:
On 09/17/12 17:20, Oliver Schinagl wrote:
If tuner communication is really working and it says chip id is 0x5a
then it is different than driver knows. It could be new revision of
tuner. Change chip_id to
Any pointers where else to look? I'm kinda lost at the moment :)
Oliver
On 09/10/12 19:28, Oliver Schinagl wrote:
On 09/10/12 16:29, Oliver Schinagl wrote:
On 10-09-12 13:46, Antti Palosaari wrote:
On 09/10/2012 12:58 PM, Oliver Schinagl wrote:
Changed the address as recommended, which
Hello
You have about all the possible info. There is chipset vendor driver
look example and existing Linux drivers for all the used chips. Just few
lines of code needed for the device profile. I surely can help, but it
is not something I would like to teach and say do that and test that. It
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
Since all the pieces should be there, fc2580 driver, af9033/5 driver,
it's just a matter of glueing things together, right? I'll dig
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
You could capture data from Linux too (eg. Wireshark).
But with a little experience you
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
You could capture data from Linux too (eg.
On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
On 09/16/12 19:25, Antti Palosaari wrote:
On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
I don't have windows, so capturing using windows is near impossible.
Also since the vendor driver used to work, I guess I will have to dig
into that more.
On 09/10/2012 12:58 PM, Oliver Schinagl wrote:
Changed the address as recommended, which after reading 7bit and 8bit
addressing makes perfect sense (drop the r/w bit and get the actual
address).
static struct fc2580_config af9035_fc2580_config = {
- .i2c_addr = 0xac,
+ .i2c_addr =
On 10-09-12 13:46, Antti Palosaari wrote:
On 09/10/2012 12:58 PM, Oliver Schinagl wrote:
Changed the address as recommended, which after reading 7bit and 8bit
addressing makes perfect sense (drop the r/w bit and get the actual
address).
static struct fc2580_config af9035_fc2580_config = {
-
On 09/10/12 16:29, Oliver Schinagl wrote:
On 10-09-12 13:46, Antti Palosaari wrote:
On 09/10/2012 12:58 PM, Oliver Schinagl wrote:
Changed the address as recommended, which after reading 7bit and 8bit
addressing makes perfect sense (drop the r/w bit and get the actual
address).
static struct
From: Oliver Schinagl oli...@schinagl.nl
Initial support for the Asus MyCinema U3100Mini Plus. This currently
does not work however. It uses teh af9033/5 demodulater with an
FCI FC2580 tuner.
Signed-off-by: Oliver Schinagl oli...@schinagl.nl
---
drivers/media/dvb-core/dvb-usb-ids.h | 1 +
Hi All/Antti,
I used Antti's previous patch to try to get some support in for the Asus
MyCinema U3100Mini Plus as it uses a supported driver (af9035) and now
supported tuner (FCI FC2580).
It compiles fine and almost works :(
Here's what I get, which I have no idea what causes it.
dmesg
On 09/09/2012 11:49 PM, Oliver Schinagl wrote:
Hi All/Antti,
I used Antti's previous patch to try to get some support in for the Asus
MyCinema U3100Mini Plus as it uses a supported driver (af9035) and now
supported tuner (FCI FC2580).
It compiles fine and almost works :(
Here's what I get,
On 09/09/12 23:51, Antti Palosaari wrote:
On 09/09/2012 11:49 PM, Oliver Schinagl wrote:
Hi All/Antti,
I used Antti's previous patch to try to get some support in for the Asus
MyCinema U3100Mini Plus as it uses a supported driver (af9035) and now
supported tuner (FCI FC2580).
It compiles fine
On 09/10/2012 01:26 AM, Oliver Schinagl wrote:
On 09/09/12 23:51, Antti Palosaari wrote:
On 09/09/2012 11:49 PM, Oliver Schinagl wrote:
Hi All/Antti,
I used Antti's previous patch to try to get some support in for the Asus
MyCinema U3100Mini Plus as it uses a supported driver (af9035) and now
45 matches
Mail list logo
