I fucking got an NB programmer from HTC, Qualcomm, and Google.

Below is

For Google/Qualcomm.

 

The BUG_ON macro is clearly written and should not be used easily. If there is any self-made problem in the driver, BUG_ON will be used. Go to the code for the release of the nexus one version, and let's just look at it.

 

A high level cannot be said, Here (uint16_t)-1 shake cool, there is (~ 0) playing cool; I am an amateur programmer who worships very closely. I wonder if he has a very short time than me?

 

The following is for HTC.

 

At first, there was a simple CPU adjustment frequency drive, which was the highest when the screen was on, and the lowest when the screen was dark. Later, Google/HTC/Qualcomm may feel embarrassed, so I changed this to On Demand.

 

Later On, HTC had to change the operating mode of ARM9. if On Demand was run On ARM11, It would be stuck to B. So what do you guess?

 

HTC has written another driver, the Performance Lock of TM. Its role is to Hack the behavior of the On Demand driver, so that the frequency is basically the highest during work, and the lowest frequency during sleep.

 

En en: Well, it is closed to modification and open to expansion. It is really a master, but he is not confused by the wide spread of a lot of logic? It's hard for him to go back in a circle?

 

It's okay to be unconventional. We have to use firmware with different interfaces on ARM9. it doesn't seem like this does not reflect the difference between HTC brand and GPhone. It's cool to maintain different versions of pay-as-you-go, sure enough.

 

The following is for Qualcomm.

 

A fucking broken camera architecture, from G1 to NexusOne. How many years have it been? I don't want HTC/Google to do a good job. The piles of FIXME in the Code are simply wrong, or take it out.

 

Thanks to Google's courage, you can use it if you dare to provide it. HTC is also keeping up with the trend. To be honest, these days I have understood why the space shuttle is exploding.

 

Then, with such a function, the private library of a task from the Modem to the kernel to the user space spans several layers. I know, not only do Web like to layer, this is a common hobby of everyone.

 

Switch every layer... case once, this number of lines of code is brushed up, poor people Linus brother and sister plus disciples do not appreciate, every day on the Mail ask you how to write this where so design?

 

Do you want TM to enter the main line? Don't care! When you synchronize the maintenance of these layers, you will not be afraid of a low-level error that will scare users away? By the way, Google is the one that gets hacked.

 

And Google.

 

Some people have written such proportional code over the past three years and added things to the Linux kernel. What they don't understand is how the most basic functions can be so rough, this is not the case if you look for a webpage.

 

Put functional code in mach; put irrelevant things in a file or module; put coherent things in different files; then control their macros.

 

In fact, except for the weird stuff that Google programmers make, any company's mistake can be attributed to Google.

 

As the core host of the project, I don't know how to do it, and I can do anything at will. It seems that this is a consistent style of Google. My brother has a good media relationship and does not do anything?

 

This combination is really amazing; the product quality is comparable to that of Windows 3.1 nearly 20 years ago.

 

I haven't written a line of code in the past half a month, and the entire TM is fighting against these things. Conclusion: Fortunately, TM intends to further study in these areas. Otherwise, as a programmer, TM will never buy such a mobile phone.

 

There are still a lot of complaints, so I won't say much. Wait for me to be idle and shake down the details. Find a specific example to express some of my own constructive ideas.

 

Update:

 

Reading a book published by the blog Park, what is the name of "The beauty of architecture"? It seems to be a bad name. It seems to be a collection of personal experiences and views, I think it is worth reading. I will buy one if I have time.

 

But let's say, don't be confused by the surface of the word. In fact, the architecture is very small, the reason for the formation of the architecture is very specific, and the architecture is not complex: it is no higher than any other work.

 

This is not intended to belittle anything. Even if a person is a so-called "architect", he will be truly competent only when he truly put down his fantasies about the architecture and acts as a specific problem.