<KotCzarny>
We didn't test all the Qualcomm chips. We only tested on the Google Pixel2/Pixel3. Results of our tests indicate that unpatched phones running on Qualcomm Snapdragon 835,845 may be vulnerable.
<wens>
*sigh*
diego_r has joined #linux-sunxi
rpirea has joined #linux-sunxi
rpirea has quit [Quit: rpirea]
rpirea has joined #linux-sunxi
<libv>
wens: was that samsung vs qualcom chip thing not primarily about the modem?
<libv>
at least, that was how it started i think
Andy-D has joined #linux-sunxi
<willmore>
KotCzarny, hasn't there been AMD in ARM phone SoCs for years? Maybe I forgot how Ardreno came about....
<KotCzarny>
willmore, but this might be a refresher
<libv>
willmore: yes
<libv>
when the credit crunch happened, amd needed cash bad
<willmore>
Yep. :(
<willmore>
Penny wise, pound foolis
<willmore>
h
<libv>
they shut down the suse partnership over radeonhd
<libv>
which was not going well with amd ati internal struggles anyway
<willmore>
"mistakes were made"
<libv>
they sold off their fabs to the saudis
<willmore>
I remember.
<libv>
now globalfoundries
<wens>
libv: I don't think they ever officially explained it , or they did and it fell on deaf ears
<libv>
and they sold off their mobile bits, which was then shipping in... marvell and... something else
<willmore>
MoeIcenowy, I didn't know China Telecom uses CDMA! I didn't think that junk was used outside of the Americas.
<libv>
z340 comes to mind
<libv>
for like 60m
<wens>
willmore: China also has some CDMA variant not seen elsewhere
<willmore>
wens, I guess that's not surprising. China tends to do some odd stuff, too. Can't let the US do all the stupid things.
<willmore>
KotCzarny, Ardreno2, GPU buggaloo?
<libv>
the credit crunch happened like more than a year after the whole of AMD (including that steaming pile of bankrupt shit, ATI) was worth less than what they paid for ATI 1.5ys earlier
<libv>
and before the credit crunch the stockmarket was crazy
<libv>
so amd was in a real bind
<libv>
and their cpu plans were not great either, they were too busy trying to fix up ati i think
<libv>
(and ended up being eaten alive from within)
<libv>
we had partner meetings where bulldozer and such were pre-pre-announced
<libv>
i was too busy with other things to notice how perhaps their ideas depended on ati too much
<libv>
but for the radeonhd project it was clear how the revenue streams of cpus versus discrete graphics dominated politics
<libv>
and by mid 2008, it was bad.
<libv>
and then the credit crunch happened
<wens>
I would've assumed discrete graphics made more money
<libv>
well, amd cpu products were no longer competitive
<libv>
and they were quickly losing the server market then
<libv>
and linux == server market
<MoeIcenowy>
wens: do you mean TD-SCDMA
<libv>
this is why we got to free ati drivers and why we got to do radeonhd
<libv>
amd bought ati, ati and fglrx were seriously bad marketing for their server business
<libv>
so amd managers looked for a solution, and some amd managers were suse employees when SuSE enabled the amd hammer (as no-one else would)
<libv>
and amd still spends a lot of money on the suse toolchain guys under now 16-18y old partner agreements
<libv>
and as luck had it, the greatest display developer ever (;p) just had his job interview at suse when one of those managers called
<libv>
so we took on that challenge and wrote a working driver
<libv>
first massively hailed by amd management
<libv>
but as time went by, ati got the upper hand, as amd was getting more and more in trouble
<libv>
and then... total collapse
<wens>
MoeIcenowy: yes
<libv>
heh, looking at the dates of when bulldozer was shipped, that thing was massively delayed
<libv>
amd was talking it up in early 2008 already
<libv>
and it only was announced in Q3 2011, and shipped in Q1 2012
<KotCzarny>
amd survived tho
<KotCzarny>
and is now kicking around
<KotCzarny>
maybe someone sacrificied their firstborn
<KotCzarny>
*sacrificed
<libv>
KotCzarny: it took them a decade
<libv>
and they had to go back to their roots
<libv>
i think it needed a serious downswing in ati relevance compared to nvidia first
reinforce has quit [Quit: Leaving.]
Da_Coynul has joined #linux-sunxi
<libv>
for the political will to internally develop to finally go back to where they came from before they bought ati
<libv>
and to let ati not influence the greater company
cnxsoft has quit [Quit: cnxsoft]
<KotCzarny>
lets hope they dont run out of the firstborns, competition is nice
<libv>
well, you saw what intel has been doing since sandy bridge
<libv>
all we got was minor ipc and price increases since then
<KotCzarny>
they got better with igpu
<libv>
and peripherals, so usb3 and beyond, nvme
<wens>
still waiting for ice lake to check out igpu improvements
<libv>
but the actual cpu space was without competition and there was therefore no drive to push things forward
<libv>
and the much touted arm servers... well
<libv>
intel ran away screaming from the mobile market
<libv>
(and killed off wayland with it)
<libv>
and we still have not seen much in the way of big iron with arm cores
Da_Coynul has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
return0e has quit [Remote host closed the connection]
return0e has joined #linux-sunxi
jstefanop has joined #linux-sunxi
return0e has quit [Remote host closed the connection]
return0e has joined #linux-sunxi
return0e has quit [Remote host closed the connection]
Da_Coynul has joined #linux-sunxi
Mangy_Dog has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
Da_Coynul has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
Andy-D has quit [Ping timeout: 252 seconds]
craigo has joined #linux-sunxi
dddddd has joined #linux-sunxi
chewitt has quit [Quit: Adios!]
Andy-D has joined #linux-sunxi
<libv>
meh, DEFE kills csi1 memory bandwidth
<libv>
and of course, our driver does not properly disable it when we're done
<libv>
i am going to have to use yuv444 on debe it seems and use the csc with 1,1,1
Andy-D has quit [Ping timeout: 252 seconds]
<libv>
wens: about dram controller priority, i added some port info that i could find
<libv>
do you have, in the back of your mind, some recollection of whether more info on that was ever known, or if someone went and figured out what value was for what subsystem?
jstefanop has quit [Remote host closed the connection]
<wens>
libv: I only remember someone got the info for mbus, but not a10 though
<libv>
ok
<libv>
yeah, this seems to have been 2014
<libv>
linux-sunxi, since august 2012 btw. 7ys
<wens>
how come? # killed off wayland
<mru>
just the usual libv hyperbole
<libv>
wens: well, intel stopped paying their own developers to work on wayland in late 2013 early 2014
<mru>
intel killed _their_ support for it
<libv>
krh suddenly started working on mesa
<mru>
not the entire project
<libv>
then moved on to google
<libv>
and one former nokia teammate first was moved to improving chromeos performance, then a lot of people in .br were made redundant
<libv>
i do not know the backstory
<libv>
but it was after chris wilson was forced to move mir patches out of the X driver for intel
<libv>
and around the time when it became clear to intel that intel mobile was not going to fly
<libv>
(i'd like to think that my hardhitting blog entry caused all that though ;p)
<mru>
we know you think highly of yourself
<wens>
mru: was your musb patch ever picked up?
<mru>
which patch?
<mru>
the dt one?
<mru>
don't think so
<wens>
hmm
<mru>
nope, not in linux-next
<wens>
probably needs a resend
<mru>
_another_ resend
<wens>
:/
<mru>
done
gaston_ has joined #linux-sunxi
jstefanop has joined #linux-sunxi
jstefanop has quit [Ping timeout: 245 seconds]
nexgen2 has quit [Quit: Leaving]
afaerber has quit [Quit: Leaving]
kaspter has quit [Ping timeout: 245 seconds]
yann has quit [Ping timeout: 272 seconds]
<fALSO>
megi, youre MEGOUS ?
<fALSO>
megi, i've been trying to clone your linux kernel repo
<fALSO>
megi, but after a few hours it ends saying that the repo is corrupt
<fALSO>
the only way i can clone it is if i make a shallow copy
<mru>
hours? slow connection?
<fALSO>
but after that... if i git pull to update it
<fALSO>
it tries to download everything again, and errors out
<fALSO>
mru,
<fALSO>
remote: Enumerating objects: 3887430
<fALSO>
hours on this...
<mru>
slow remote then
<KotCzarny>
for a quickie try --depth=1
<KotCzarny>
if you only need quick checkout
<fALSO>
yes, that what i did, but with that, you cant update it
<mru>
or add the remote to an existing clone
<mru>
then you only need to get the difference
tuxillo has quit [Ping timeout: 246 seconds]
<KotCzarny>
yup, but at least you can check what works etc
<fALSO>
i cant clone it complety
<fALSO>
im gonna wait until it fails so that i can show you guys the error ;-P
<fALSO>
i had to reboot earlier so i dont have it
tl_lim has joined #linux-sunxi
tllim has joined #linux-sunxi
<megi>
fALSO: clone it from github
<megi>
fALSO: I'll keep that bug as a punishment for people trying to deplete my bandwidth quota on my VPS
<megi>
:D
tllim has quit [Client Quit]
<megi>
your download ended, sorry
<KotCzarny>
:)
<libv>
fALSO: i keep a linus tree somewhere and update that regularly
<libv>
i clone from there
<libv>
then remove the origin, and add the target origin
<libv>
so only the relevant changes need to be retrieved over the net
<megi>
yes please, that I'd recommend too, clone linus's tree and 'git add remote someone someurl ; git fetch --all'
<megi>
s/add remote/remote add/
vagrantc has joined #linux-sunxi
airwind has quit [Quit: airwind]
reinforce has joined #linux-sunxi
kaspter has joined #linux-sunxi
<fALSO>
megi, going to try it out
<fALSO>
megi, do you have a mirror of your repo in github?