From: zePh7r <zeph7r@gmail.com>
To: Albert Comerma <albert.comerma@gmail.com>
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Support for Asus My-Cinema U3000Hybrid?
Date: Mon, 11 Aug 2008 13:39:16 +0100 [thread overview]
Message-ID: <48A032F4.6000602@gmail.com> (raw)
In-Reply-To: <ea4209750808100251j3d027cable1e5cd81ceb4995@mail.gmail.com>
Albert Comerma escreveu:
> Sorry, I didn't explained much... it also took some time to me to
> understand how it's working... Since xc2028 is the tunner it has no Id
> information on the code. The id's are on the usb bridge code. You
> should add your deviece id's at;
> /v4l-dvb/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h and then insert
> your device at
> /v4l-dvb/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c first
> the device descriptors (at arround line 1120) and then the device
> itself, I would try it around line 1418. This last file, has already
> the include to the xc2028 code and calls the tunner funcions. Looking
> the code around this lines I guess you will understand how it works.
>
> Albert
>
> 2008/8/9 zePh7r <zeph7r@gmail.com <mailto:zeph7r@gmail.com>>
>
> Albert Comerma escreveu:
>
> Just to clarify things...
>
> Xceive chips are just tunners, RF chips, mostly analogue with
> some digital interface, they don't do anything with usb or
> comunication with the computer, for this reason you need the
> dibcom chip, it's a usb bridge + decoder + something else...
> To start to develop something you must first be sure of what
> chips it's using.
> If not you can try blindly if modifying the code for the
> U3000-Mini works or Pinnacle 320cx (dibcom 7700 + xceive2028)
> work (you just need to add your device usb id's).
>
> Albert
>
> Thank you for replying Albert.
> I've been exploring the files downloaded through the mercurial
> repository and though I have found files which seem like they
> relate to that purpose in
> /v4l-dvb/linux/drivers/media/common/tuners (which are
> tuner-xc2028.c , tuner-xc2028.h and tuner-xc2028-types.h) I can't
> find any section in the above files with some sort of list of
> device ID's so as to resemble them. There should be something like
> an xc2028-cards.c right?
> This must seem a noob question but this whole process looks like
> something someone who's not deeply into this project couldn't do
> easily..
>
>
When I try to compile the drivers I get this:
zeph7r@zeph7r-laptop:~/v4l/v4l-dvb> make all
make -C /home/zeph7r/v4l/v4l-dvb/v4l all
make[1]: Entering directory `/home/zeph7r/v4l/v4l-dvb/v4l'
Updating/Creating .config
Preparing to compile for kernel version 2.6.25
File not found: /lib/modules/2.6.25.11-0.1-default/build/.config at
./scripts/make_kconfig.pl line 32, <IN> line 4.
make[1]: *** No rule to make target `.myconfig', needed by
`config-compat.h'. Stop.
make[1]: Leaving directory `/home/zeph7r/v4l/v4l-dvb/v4l'
make: *** [all] Error 2
any hints on what might be causing this? I went look at that dir and
found a makedumpfile.config , perhaps I should edit config-compat.h and
set it to go look for that file instead..
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-08-11 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 12:32 [linux-dvb] Support for Asus My-Cinema U3000Hybrid? Albert Comerma
[not found] ` <489CCD82.5030406@gmail.com>
2008-08-10 9:51 ` Albert Comerma
2008-08-11 11:22 ` zePh7r
2008-08-11 12:39 ` zePh7r [this message]
2008-08-11 13:29 ` Albert Comerma
2008-08-11 15:28 ` zePh7r
2008-08-11 15:40 ` Albert Comerma
2008-08-11 15:51 ` zePh7r
2008-08-11 18:42 ` zePh7r
[not found] <48A1B85E.5070800@net.novis.pt>
2008-08-12 19:30 ` Albert Comerma
2008-08-12 20:14 ` zePh7r
2008-08-13 9:29 ` Albert Comerma
2008-08-13 21:10 ` zePh7r
[not found] ` <d9def9db0808131417t168bc1abvfb3b08101980405d@mail.gmail.com>
2008-08-16 13:28 ` [linux-dvb] " zePh7r
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=48A032F4.6000602@gmail.com \
--to=zeph7r@gmail.com \
--cc=albert.comerma@gmail.com \
--cc=linux-dvb@linuxtv.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 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.