repnzscasb has quit [Remote host closed the connection]
repnzscasb has joined #teamhacksung
Dragooon has quit [Ping timeout: 252 seconds]
AoM_Scott has quit []
squadzone has joined #teamhacksung
whatfedeabekat has joined #teamhacksung
squadzone has quit [Remote host closed the connection]
squadzone has joined #teamhacksung
lolwat has quit [Read error: Connection reset by peer]
whatfedeabekat has quit [Ping timeout: 260 seconds]
pershoot has joined #teamhacksung
<pershoot>
Entropy512, u here?
<codeworkx>
he's not here till tomorrow
<pershoot>
ah k
datagutt has quit [Quit: kthxbai]
detule has joined #teamhacksung
<pershoot>
with regards to this MMC bug hard bricking devices. one person ran the utility against their tab 10.1, and it reported a buggy/faulty chip. now i havent seen this bug on this tab ( i was able to always bring it back form the brink of death, no matter how i cleansed the partition(s), and CWM does a format of the partition not an MMC erase, so with that being said, im wondering whether
<pershoot>
to remove the whole block and void it out as a precautionary measure, cause who knows what unforseen thing could come up.
repnzscasb has left #teamhacksung [#teamhacksung]
<pershoot>
sorry that was a big ass run on sentence, ha
<codeworkx>
we've disabled mmc erase anyway
<pershoot>
yea
<codeworkx>
no need to panic :-D
<pershoot>
i guess maybe ill do the same. its not used here in any scenario i can think of
c00kies|repnzsca has joined #teamhacksung
c00kies|repnzsca has left #teamhacksung [#teamhacksung]
detule has quit [Ping timeout: 260 seconds]
Charkey has joined #teamhacksung
coolya is now known as coolya|away
stickyboy has joined #teamhacksung
<stickyboy>
Alright... got the ath6kl driver to compile in the smdk4210 kernel...
<stickyboy>
Lets see if it makes teh wifis magically work.
<stickyboy>
Err, I9300 ath6kl driver :)
jt1134 has joined #teamhacksung
mauimauer has left #teamhacksung [#teamhacksung]
detule has joined #teamhacksung
detule has quit [Changing host]
detule has joined #teamhacksung
Charkey has quit [Ping timeout: 246 seconds]
<stickyboy>
Nope. Still no wifis.
Charkey has joined #teamhacksung
jt1134 has quit [Quit: Leaving]
tumasgiu has joined #teamhacksung
tumasgiu has quit [Quit: Quitte]
squadzone has quit [Quit: wuzzzzzzz]
Rebellos has joined #teamhacksung
h8|BBIAB is now known as h8rift
vadi has joined #teamhacksung
vadi has quit [Changing host]
vadi has joined #teamhacksung
thelockz has joined #teamhacksung
stickyboy has quit [Quit: leaving]
squadzone has joined #teamhacksung
vadi has quit [Ping timeout: 252 seconds]
Parth has quit [Quit: Quack!]
Parth has joined #teamhacksung
<Entropy512>
<pershoot> with regards to this MMC bug hard bricking devices. one person ran the utility against their tab 10.1, and it reported a buggy/faulty chip. now i havent seen this bug on this tab ( i was able to always bring it back form the brink of death, no matter how i cleansed the partition(s), and CWM does a format of the partition not an MMC erase, so with that being said, im wondering whether - That's interesting, I'm fairly
<Entropy512>
certain CWM does an MMC erase in 5.5.x
<Entropy512>
or maybe that's something that was brought in midway through? I sort of recall some commits against CWM regarding usage of make_ext4fs changing
<Entropy512>
hmm, time to browse git
toastcfh_ has quit [Ping timeout: 240 seconds]
athurh has quit [Quit: athurh]
toastcfh_ has joined #teamhacksung
athurh has joined #teamhacksung
antiochasylum has joined #teamhacksung
<antiochasylum>
Can anyone enlighten me on where the cpu clock table is for the n7000?
noobnl has quit [Quit: noobnl]
athurh has quit [Quit: athurh]
athurh has joined #teamhacksung
antiochasylum has quit [Quit: Page closed]
thelockz has quit []
h8rift is now known as h8|brb
squadzone has quit [Remote host closed the connection]