Re: Talking to Logitech on the phone regarding webcam support for linux

Rui Miguel Silva Seabra wrote:

Not necessarily. Some of TI's wireless network stuff, for example, can
easily be convinced to broadcast at higher-than-normal power levels and
at completely bogus frequencies.

If they open up the driver, the source will be published and anyone with
a tiny bit of know-how can wreak havoc with local wireless networks.
Now, you could argue that TI should redesign the chipset (they have)
but what about all the chipsets that are already out there? Knowing how
lawyers are, TI would get hit with lawsuit after lawsuit. That being
the case, can you blame them for keeping the source closed? I don't.

So who's the boss on your computer? You or some hardware/software
provider?

A better question for most of us might be "who knows more about how to make it work best, you or the experts that designed it? And as far as changing it, wouldn't it be best to keep expenses down to let hardware providers make changes as frequently as technology permits, supplying drivers to match instead of waiting for an OS provider that might be dealing with thousands of other devices to catch up?


--
Les Mikesell
lesmikesell@xxxxxxxxx

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Talking to Logitech on the phone regarding webcam support for linux
    ... at completely bogus frequencies. ... If they open up the driver, the source will be published and anyone with ... you could argue that TI should redesign the chipset ... TI would get hit with lawsuit after lawsuit. ...
    (Fedora)
  • Re: Reading mm datasource
    ... the OLE syntax is not relevant here. ... Doug's post helped me identify that the client has the odbc dbase driver ... Word is trying to connect using the OLE DB provider ...
    (microsoft.public.word.mailmerge.fields)
  • Re: How to pass a WMI array
    ... > The provider parses the query, ... > NDIS dispatches that to your driver. ... > The provider parses the blob according to the MOF specification. ... > You, as a driver writer, cannot do much to speed this process up. ...
    (microsoft.public.win32.programmer.wmi)
  • Problem with Linked Server from SQL to DB2
    ... I'm trying to setup a linked server from SQL to DB2 UDB. ... Microsoft provided OLE DB driver for DB2 and the IBM DB2 OLE DB ... -- Invalid schema or catalog specified for provider 'IBMDADB2'. ...
    (microsoft.public.data.oledb)
  • Progress Linked Server
    ... I have the proper Data Source Connection and driver on my Windows 2003 server ... OLE DB provider 'MSDASQL' reported an error. ... I can see my tables in Enterprise Manager with the following linked server ...
    (microsoft.public.sqlserver.odbc)