The other questionable versions are 1.0.5 and 1.0.6, maybe 1.0.6 for M/D and 1.0.5 for Tablet? TXE is such a Bugger Vance: Thank you the reports, pictures etc. Since there doesn’t seem to be any way to determine which firmware is meant for tablet and which for desktop/mobile, I appreciate you letting me know which is which. seems to be PV/PC and not Beta/Alpha based on the PV-bit: I will add 1.1.1 as Tablet and 1.1.2 as M/D at the thread. I checked both 1.1.2 and 1.1.1, the only differences I found after unpacking were these at BUP and TPM (apart from the signatures, $MN2 date/vcn etc): That would also explain why 1.0.6 firmware was "older" than 1.0.5, they were targeting different platforms. is for I, all other versions are either betas or vendor-specific releases.ĬodeRush thank you a lot for that piece of information. is now the latest release version for M/D and 1. You are right, Intel now has separate releases for BYT-I and BYT-M/D, which makes much pain in some well-known place for BIOS developers because now need 2 BIOS versions for the same board.īTW 1. Attached below if you want to try, though I understand completely if you don’t want to. firmware? According to VCN and date it should be newer than v1. Since you have a programmer and the required knowledge, can you try this “tablet” (as I call it for now) v1. But analyzing both “m/d” and “tablet” firmware shows no important changes, not at SKU or anything else not-worthy (at least as far as I can see). I was thinking that maybe Intel has a separate branch for Tablet/IVI systems apart from the usual Mobile/Desktop. This is strange because the “older” version is actually newer. which a) has a higher VCN (12 instead of the old 11) and b) a latter date (November instead of August 2014). is the latest firmware, I recently found version 1. Did it work as intended? Did TXEInfo and TXEManuf report everything as working properly?Īlso, although as far as version itself is concerned, 1. I hadn’t found a user to test such a thing until now. Although it should be fine according to Intel, you are the first I’ve seen doing it. I noticed that you upgraded using FPT or a programmer from TXE 1.0.x to 1.1.x. I know this is not the reason for your topic but since finding more advanced users is rare, I wanted to ask you some things regarding your TXE updates. Otherwise i have no idea where the hardcoded battery values are stored, it may be more practical to edit these instead. Other registers like temperature (0x1E) aren’t exposed. My idea was to add new registers for the fuelgauge, correct the max capacity and edit BIXP object informations.įuelgauge seems to be described at: Scope (_SB.I2C1) on i2c bus 0x0055.ĭECC = FG3C įUEC = FG0E īUFC = FG0C -> RECT īU1C = FG1C -> PERC The fuelgauge is a Texas Instrument BQ27441: The main problem is that the battery stats are completely impractical, with a probably false hardcoded max capacity value and improper acpi functions. They all share the same basic intel uefi layout, with small differences suited for the integrated hardware. On my Bay Trail based tablet there is a problem with the battery implementation, this seems pretty common on earlier Z3735D revisions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |