![[XIX]Secutor](/data/avatars/s/4193/4193179.jpg?1600603409){kind=avatar}
-
Introducing XDA Computing: Discussion zones for Hardware, Software, and more! Check it out!
[INFO]GT-N7000 JB kernel source code released
- Thread starter [XIX]Secutor
- Start date
Oh my.. cant wait for speedmod for jb
_____________________________
via GT-N7OOO using XDA-2
_____________________________
via GT-N7OOO using XDA-2
probably better custom roms with better battery life, performance ect,
dont quote me though
To see if any kernel has the Emmc brickbug or not, simply need to open the kernel image and see if MMC_CAP_ERASE script its enabled or not. There's dont need to search in kernel sources
__________________________________________________________
A source code can be implemented on Cm10 based roms, better battery autonomy, smooth animations, faster phone, can be overclocked and other things. Also, with this source code we will have updated modded kernels like speedmod, hydra etc..
Sorry my bad english!
Z
zylor
Guest
Unpack kernel.tar.gz and look into: drivers > mmc > host > sdhci.c
This is where MMC_CAP_ERASE is... and look into it!
Easy
Last edited:
Unpack kernel.tar.gz and look into: drivers > mmc > host > sdhci.c
This is where MMC_CAP_ERASE is... and look into it!
Easy
But Entroy512 says this:
http://forum.xda-developers.com/showthread.php?t=1953932
I don't understand.
Z
zylor
Guest
What Samsung did was to implement this fix:
https://patchwork.kernel.org/patch/1526741/
So basically you can use format commands normally in stock kernels and a normal format of the partition is done but without triggering the brickbug :highfive:
And viewing sources you can see that the fix from Samsung was applied around lines 2349 to 2396 in: driver > mmc > card > block.c
as follows:
Code:
#define CID_MANFID_SAMSUNG 0x15
static const struct mmc_fixup blk_fixups[] =
{
MMC_FIXUP("SEM02G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM04G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM08G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM16G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM32G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
/*
* Some MMC cards experience performance degradation with CMD23
* instead of CMD12-bounded multiblock transfers. For now we'll
* black list what's bad...
* - Certain Toshiba cards.
*
* N.B. This doesn't affect SD cards.
*/
MMC_FIXUP("MMC08G", 0x11, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD23),
MMC_FIXUP("MMC16G", 0x11, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD23),
MMC_FIXUP("MMC32G", 0x11, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD23),
/*
* Some issue about secure erase/secure trim for Samsung MoviNAND
*/
MMC_FIXUP("M8G2FA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("MAG4FA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("MBG8FA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("MCGAFA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("VAL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("VYL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("KYL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("VZL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
END_FIXUP
};This fix according to Samsung fixes the brickbug... but neither me and Entropy512 trust Samsung on this one...
You can view more info on this issue in here:
Discussion thread for /data EMMC lockup/corruption bug
Z
zylor
Guest
Most likely fixes and addictions. No changelog was provided from Samsung so no idea!
.....
This fix according to Samsung fixes the brickbug... but neither me and Entropy512 trust Samsung on this one...
So, we are sure?
Z
zylor
Guest
Mate the info came from messaging with Entropy who told me to look into the commits and that commit was made by Samsung, so if you trust Samsung yes...
blog.gsmarena.com/samsung-releases-galaxy-note-jelly-bean-source-code/
Article has link to source of info and link to source code download (have not checked this myself though, don't know what to do with it)
Article has link to source of info and link to source code download (have not checked this myself though, don't know what to do with it)
B
baz77
Guest
Z
zylor
Guest
I did already post some mirrors for it here:
http://forum.xda-developers.com/showthread.php?t=2166223
Sent from my GT-N7000 using Tapatalk 2
