Why vote for the lesser of two evils?

CTHULHU 2014!

https://bitbucket.org/braindam...

These are some of the worst and most uninformative commit messages I've ever seen...

1) Why are there so many commits to achieve the same thing?
2) Any commit message that is only a single line other than "fix typo" is a bad commit message

Seriously, even some of the worst/most incompetent Android kangers have written better commit messages than the shitpile of LKM removals I'm seeing there.

"Internet service would cost 80 a month to add where she lives" - You are not going to find any truly unlimited service for anywhere even remotely approaching that.

Thing is, Apple Pay used existing standards for contactless EMV. Which is why every single terminal that accepted Apple Pay already accepted Google Wallet.

It's the same deal as ISIS - Even before the Islamic extremists ruined the name (I think they changed it to SoftCard or something like that), all they did was hold back Google Wallet without providing consumers a viable alternative.

That ruined their name with consumers even before the Islamic extremists did. People are constantly pissed about vending machines that stopped accepting Wallet as soon as ISIS support was added. Partly because they still don't have any way to use ISIS, but more because they can't use their preferred method (Wallet) at those machines.

This whole thing DOES also explain why both Target and Wally World moved to contact-based payments to handle the upcoming EMV liability shift instead of contactless.

"unless it's being done by a 14yo who installed VNC on your machine and is just fucking with you"

Which is probably what it was. My guess is: Some 14yo didn't like her political views and decided to fuck with her, and used some social engineering tricks to make her think it was the big bad gubmint.

Betcha the classified documents came from Wikileaks or were forgeries.

"and kept politics contained in the opinion pages" - To play devil's advocate - this particular article IS in the Opinion section.

From looking at how their stuff works, no. The driver tries to change the PID on all devices, but genuine hardware doesn't actually write out the EEPROM until further action is taken, while clones immediately write out the EEPROM.

Although it isn't really a "brick" - it sets the PID to 0. Which is invalid, but happens often enough these days that you can still force the hardware to be used. Someone wrote a Linux patch that would register the correct driver for FTDI's VID and a PID of 0.

Another option FTDI could have done is: Change the PID to one reserved for clones, then spit out warnings when that PID is seen.

"are not sold as made by the company" - They use FTDI's USB VID/PID - this is representing yourself as an FTDI chip.

The tough thing is HOW to do it on first plug-in. The only method I can see that would work is to perform the same alteration the driver is doing, but instead of changing the PID to 0, change it to one reserved for fake chips. Then have the driver spit out lots of warnings if the "fake chip" PID is seen.

(As to how their driver is doing its thing - from what I've read of decompiled code, it attempts to change the PID to 0 on all chips. However, genuine hardware needs additional steps to actually start the EEPROM write, while clone hardware immediately writes out the EEPROM.)

"The issue is that the FTDI driver is deliberately reprogramming a chip that is not theirs"

Except they're only doing this to their USB VID/PID - which IS THEIRS.

If you use FTDI's VID/PID, you're trying to pass yourself off as an FTDI chip, and it is YOUR FAULT ALONE if an operation that does not cause issues on genuine FTDI hardware does bad things to your own.

(If you look at the decompiled code, the driver attempts to write the EEPROM on all hardware. However, genuine FTDI hardware won't actually START the write operation until the driver does "additional stuff" - but clones will immediately write the new EEPROM value.)

"This is because if you accidentally get a bad shipment of clone chips, and put them into your devices, your devices will be subject to bricking, creating returns and bad PR."

Not if you actually test your product before you ship it.

Not if you perform ANY sort of inspection/testing of incoming components.

Yup. And now they've got a surefire test for genuine chips.

Seriously - these people using counterfeit chips have to be testing the final product. If that final product dies with an official FTDI driver, they can sue the crap out of their supplier for selling them counterfeits.

Um, it's not 5 products out of several thousand. These are all screwups by a single division that refuses to learn from their mistakes and repeatedly makes the same kinds of mistakes over and over again.

They KNEW that the VYL00M/MAG4FA/KYL00M fwrev 0x19 was faulty, and they kept on shipping it for MONTHS in devices even though they had a newer fwrev (0x25) that didn't cause these problems.

They KNEW they had a track record of secure erase issues, and a year after becoming aware of a device-bricking bug, they were STILL shipping products vulnerable to that bug (the 840 Pro secure erase mess).

You simply don't see this sort of crap occur with eMMC chips from other manufacturers like Toshiba. Yeah, some of them have quirks, but none of them have such severe bugs that they render the device they're installed in unrepairable without a motherboard replacement.

Also:

"under a corporate aegis"

Depending on how the company manages the open source project, this can strongly discourage community members. Even if the company TRIES to encourage community development, a combination of licensing and other behaviors of the company might cause issues.

See http://readwrite.com/2013/08/0... - I once saw another article (can't find link) where one of the MariaDB guys said that with the new org structure of MariaDB, they have FAR more community contributions than MySQL ever did, even before getting purchased by Oracle.

Another example was the Cyanogen Focal relicensing incident. Cyngn's founders tried to use their CLA to obtain MySQL-style dual licensing (and the founders cite MySQL's business model as their inspiration despite the fact MySQL never had a vibrant community behind it) caused a nasty forking event, and also caused other community projects in the AOSP-derivatives space to reduce their cooperation with CyanogenMod. I keep on hearing/seeing evidence that implies numerous people on the "community" side of things that stayed with the project are pretty unhappy, only staying because it's still (for now) the dominant and most well known project in that space. Cyngn leads have even found themselves having to bribe people with devices to get them to stay.

(Disclaimer: I was one of those who left CM after the Focal relicensing dispute.)

Couldn't write a proper wear levelling algorithm if their life depended on it.

First the MAG4FA/KYL00M/VYL00M data corruption bug that affected the Galaxy Nexus - https://android.googlesource.c...

Then (actually BEFORE it, Google found it during Galaxy Nexus development but Samsung kept it hush-hush - but it became a public issue much later) - the infamous Samsung Superbrick fiasco (If you fired a secure erase command at the chip, it had a chance of permanently corrupting the wear leveller data to the point where the chip's onboard controller would crash until you power cycled it any time you accessed that region of flash). - https://git.kernel.org/cgit/li...

Then pre-release 840 PRO devices suffer from the SAME DAMN BUG SAMSUNG HAD BEEN AWARE OF FOR OVER A YEAR - http://www.anandtech.com/show/... - While this only affected review devices, the fact that this was a known bug since before the release of the Galaxy Nexus (a year earlier) is inexcusable.

Then there was the Galaxy S3 "Sudden Death Syndrome" issue in late 2013... - https://github.com/omnirom/and...

Then there were a few other issues - http://wiki.cyanogenmod.org/w/...

Now this...