| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
the maximum available memory in one piece; firmware version 0x2616
|
|
the picture is looking good now, although it seems that the fields
are still swapped. strange...
|
|
<robert_s@gmx.net>
|
|
|
|
|
|
|
|
- if the analog module is detected, the saa7113 is initialized and
some more v4l2 ioctls are available. you can use "xawtv" now to
switch between "dvb" and "analog" input. when you are one the
"analog" input, you can tune in analog channels with the cursor
keys via v4l2.
currently, this is a big hack -- tuning is not mutually exclusive,
so "szap" and v4l2 tuning can interfere with each other. the
demodulator address is hardcoded to 0x09.
Other changes:
- changed the saa7146 ioctl parameters, give out the data of the
current device open "fh" (=> "file handle"), not the pointer to the
device structure "dev". It is "dev = fh->dev".
Some stuff does not work:
- analog audio does not work. does the msp3400 need to be reprogrammed?
- one field is "missing", so the picture is very bad and
capturing does not work neither. this needs to be investigated by
looking at the programming the windows driver uses for the saa7146
|
|
|
|
weiterarbeiten gehindert. Folglich auch keine weiteren Events...
found by wjoost
|
|
firmware version 0x2615
|
|
"build-2.4" and 2.5.70
|
|
- move some more files from build-2.4 to analog-2.4
- get build-2.4 to compile again
|
|
to a separate "analog-2.4" directory. Main reasons:
- the drivers don't have anything to do with dvb 8-)
- the drivers are already in the kernel (besides the "Hexium" driver)
and don't change that much any more
- the analog drivers rely on the i2c subsystem, which was heavily modified
between 2.4 and 2.5. When making a new DVB patchset I have to work around
these differences every time, which is very annoying
|
|
|
|
|
|
- change some includes
|
|
|
|
"kernel shape":
I mainly changed all "typedef struct foo_s {...} foo_t"
to "struct foo {}". Please don't start a policy war, I know the pros
cons of typedefs and structures.
We should, however, stick to the coding rules of the kernel: typedefed
structs are only used for opaque data types, where the internal
representation is irrelevant and we have get()/set() functions for
accessing them (ie. spinlock_t)
|
|
err != 0 to make other errors visible
|
|
|
|
|
|
- void* arguments can only be casted safely to unsigned long
- some debug print fixes where types did not match
But: the debi stuff in av7110 needs to be rewritten, because
u32 arguments are used as pointers, too... 8-/
|
|
|
|
driver subsystem.
|
|
to implement FE_GET_FRONTEND
|
|
|
|
|
|
combinations used by Siemens and Technotrend on their DVB-C cards
|
|
|
|
- Makes zigzag to not change frequency for DVB-c at all. It only resets
the parameters over and over again. - The IF of 35937500 might be better to be 36000000. This might be what the
card designer meant. My card shows the AFC fine tuning offset to be closest
to zero with 35937500 (one step below 36MHz). Some other cards might be
different. I have not heard of any complaints about my patch not working
for someone in this respect.
- Has anyone ever tested this auto inversion thing? DVB-c is far too slow to
tune and lock for this auto inversion code to work. Therefore you need to
manually set it. Maybe zigzag changes above allow the auto inversion to work. - QAM registers have been tweaked to non-specification values. I do not know
if someone has counterexamples, but this works for a lot of people.
|
|
|
|
(patch supplied by Volker Cordes)
|
|
|
|
- implemented SEC_VOLTAGE_OFF for stv0299 and alps_bsrv2
|
|
| if (crystal chip present)
| av7110->adac_type = DVB_ADAC_CRYSTAL;
| else if (MSP34xx chip present)
| av7110->adac_type = DVB_ADAC_MSP;
| else if (av7110->saa->device->subsystem_vendor == 0x110a)
| av7110->adac_type = DVB_ADAC_NONE;
| else
| av7110->adac_type = adac;
The adac parameter will only be used if the card cannot be
autodetected.
|
|
with DMX_OUT_TS_TAP (recording); return EBUSY instead
|
|
(workaround needed for kernel 2.4 because kernel_thread() fails when
the process opening the frontend device is ptraced)
(untested with kernel 2.5, but the kernel_thread(9 implementation in
2.5 looks fixed to me)
|
|
|
|
"kernel_thread_setup()" (now: dvb_kernel_thread_setup()) and
dvb_usercopy() function.
Because of the fact that we want to separate the dvb subsystem, it's
sometimes necessary to have some wrapper functions (for example
dvb_delay() or dvb_kernel_thread_setup()) to encapsulate linux
kernel facilities that can't be expressed as a one-liner.
The place for such functions is "dvb_functions.c". By this, we can
get rid of "dvb_compat.h" for 2.5 completely. Hooray!
I hope I did not break everything again, some cleanup is expected for
the build-template stuff, though.
|
|
it compile again under both 2.5 and 2.4.
|
|
ongoing i2c changes in 2.5. Because of the fact that they are already
in the kernel and won't change any more, they can be removed here
and added to the build-2.4 directory.
|
|
build process again, due to the unknown licensing issues with
the firmware.
|
|
dirty way, using #ifdef(LINUX_VERSION) stuff, because devfs changes in
2.5 are likely to happen again.
This should be cleaned up.
|
|
|
|
TODO: use scatter/gather DMA for clipping informations, too.
|
|
|
|
Should still work with 2.4 kernels..
|
|
|
