not reading the parts above, but saying this is Steven, not caring
about the main people who work on something.

There's a split between a few people here (including myself) and other
people from that scene who just don't care about anything.

Manu and the others put in alot work, why screw what he wrote (code)
he has been on vacation (I know he married a few weeks ago - since I
got the invitation) Hauppauge people (Michael Krufky and Steven Toth)
are running their personal own game .. sorry to say that but it's that
way.

I have logs and mails here where Steven and Mike wrote hey that would
be a cool idea about compatibility but when "I" mentioned it again and
spent work on it it was like hey we're linux only (I don't only care
about linux since I also work alot with commercial companies in that
area look at the dibcom website - Job requirement 'independent' code
neither do I want to depend on Windows nor Linux but having something
that works on both in case of hardware is fine - especially I2C is
trivial to realize for everything).

Rethink your position and try to get people onboard but don't try to
screw people and run your own game.

Seeing the comments Acked-By: xyz - I cannot review neither contribute
code but I can provide webspace .. hilarious. get down on earth again
Steven, Mike expecially Mauro - try to get Manufacturers onboard
instead working against you.
I talked alot with Manu he has good connections and is avoing to work
together just as I am because of certain Monopoly and copyright
infringements which you are building here (I see Mauro using leaked
code here!) . Mauro is spreading foo, Manu has the specs for xyz. I
fully understand Manu's point since Mauro did the same with me,
however .. I better don't comment it.

Let's put another thing in here: Greg Kroah Hartman Linux Guy reverted
my patch in favour of supporting the binary Firmware upload tool of
Dell (I fully support Dell here too) although claiming to be
opensource but still running after ...
[ message continues ]

If you're going to spell my full last name out, please get it right, you

What patch specifically are you referring to here?

And what does this have to do with v4l and DVB issues?

thanks,

greg k-h
--

[ message continues ]

Hi,

Markus submitted a patch to the firmware loader code that fixed a
sysfs filename collision by appending a suffix to the sysfs filename
it used. This bug broke the use of the firmware loader from i2c device
drivers (specifically, the drivers for the xc3028 TV tuner chip) with
certain (not particularly unusual) kernel configurations - IIRC, it
affected kernels with I2C compiled as a module and a particular value
of some option related to sysfs depreciated support. The patch was
reverted by you because it broke binary-only firmware upload tools for
Dell hardware, screwing over normal desktop users in the process.

See, for example, http://lkml.org/lkml/2008/4/26/319 - this is fairly
typical. IIRC, the only drivers for the xc3028 that aren't affected
are Markus' recent ones, since they compile the firmware into the
driver (ugh). This may have been fixed since, but I'm not sure.

(Incidentally, looking at the conversation, I believe your remark that
"the i2c devices can fix things by changing their module names so this
collision doesn't happen :)" may be inaccurate. The firmware loader
copies the name it uses from the device passed to it, so I'm not sure
how much can be done, short of hacking around the issue by creating a
fake device to pass to the firmware loader or making potentially
compatibility-breaking changes to either the i2c core or the firmware
loader. Of course, I haven't looked at the issue that closely, so I
may be wrong.)

Aidan
--

[ message continues ]

I've learned never to expect anything different from you, such a pity.

Steve
--

[ message continues ]