<libv>
VT1623 is a tv encoder once made by via, the follow-up of the VT1622, which was present on the EPIA M
<libv>
the EPIA M is what got me started on display development, as the xfree86 driver had broken virtual resolution support
<libv>
those tv encoders drove me to posit that what is modular in hardware, must be modular in software
<libv>
back in the day, people (yes, those deemed important in the xorg/fd.o world still) that those external ramdacs and encoders are why display driver development has to be done in the bios
<libv>
+claimed
<libv>
i proved them wrong, and got blackballed for being right.
<libv>
all because of the vt1622 and it's follow-up vt1623
<libv>
A20 chip id is 0x1623
* libv
somehow never noticed that before ;)
<hellsenberg>
is it a coincidence?
<libv>
or is it a message from the flying spaghetti monster?
<libv>
yeah, one of life's cute coincidences, which are of course noticed by people who spend their days recognizing patterns :)
<anarsoul>
it's a sign from the universe :)
<libv>
if only i had seen it in 2012
<libv>
then i would've known to run away
<wens>
lol
<libv>
i got bit by 1623 almost exactly a decade before ;)
warpme_ has quit [Quit: warpme_]
<libv>
bitten
<libv>
oh, a10 is 0x1623
<libv>
but the VE claims that, as the a20 engine is the same
quadjfet has quit [Quit: Leaving]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
aalm has joined #linux-sunxi
diego_r has joined #linux-sunxi
<slapin>
hi, all!
lurchi_ is now known as lurchi__
<slapin>
what is generally done about unknown firmwares we extract from vendor touchscreen drivers?
<libv>
slapin: does the wiki say anything?
<libv>
also, do those firmwares have some distinguishing info inside, like a string and some versioning?
gaston1980 has quit [Quit: Konversation terminated!]
diego_r has quit [Ping timeout: 240 seconds]
<willmore>
libv, reminds me of back in the late 80's/early 90's, I was doing work on DSPs and I needed a databook on SRAMs, so I called up Cypress. Their phone number ended in 6116--a popular SRAM. It didn't dawn on me until have way through the call and the person I was talking to though my reaction was hilarious. They not only sent me the databook, but a bunch of samples as well.
<willmore>
Still love Cypress.
florian has quit [Ping timeout: 246 seconds]
<slapin>
libv: well, I mean the ones we extract from drivers - I know what to do with firmware on image to put it where driver can it pick up in /lib/firmware
<slapin>
libv: my question is more about adding these to public repositories
<libv>
yes
<libv>
slapin: i have no clue about and no interest in touch at this time
<libv>
i have no idea what has been documented on them, or how that info has been structured
<libv>
i also have not formed an opinion on whether we should host those blobs or not
<libv>
and we seem to be the only two guys having this conversation right now
<libv>
so what is the state of touchscreen info in the wiki? is it as sparse as i think it is?
<slapin>
well, I found nothing new in Wiki, it has actually less info
<libv>
and my question about the distinguishing marks was whether it makes sense to even host them, if they are 1 blob per android image, and they almost no two are the same, there seems little point
<slapin>
there is gsl-firmware repo on github with more info on silead touchscreen
<libv>
ok, well, start by creating and or expanding a silead page on our wiki
<libv>
and link to that repo
<slapin>
additional work to extract them every time
<libv>
then go and create your own personal github repo with your working firmware added, and have the A13 Q8 tablet page for your device link to the blob in there
<slapin>
well, I could ask just add these images to that repo and move responsibility eslewhere, but that does not look mature decision though...
<libv>
if this is more persistent, then we can move it to github.com/linux-sunxi/
<libv>
but not for 1 firmware image :)
<slapin>
I'm more interested in consequencies
lurchi__ is now known as lurchi_
<libv>
well, we host or hosted arm binaries for mali before when arm was still being total somethings about those
<slapin>
if some person here knows somebody in Silead law department and they allow distribution of their firmwares, I'd prefer to host relevant ones on linux-sunxi umbrella
<libv>
it's very dark grey, but it seems to be the only way to make their hw work?
<libv>
anyway, provide the first bits in the chain first
<slapin>
I guess Silead touch is quite common on allwinner tablets as reference design uses it
<libv>
yeah
<slapin>
yes, no other way to make touchscreen work
<libv>
well, github knows about dmca requests
<libv>
if that hits, we can take things down
<libv>
until then, we remain grey
<libv>
but useful
<libv>
but please do the wiki work, so this thing has a chance of actually becoming useful
<libv>
others run into the same issues, and if it is not in the wiki, it is all time needlessly wasted
<slapin>
I know I know
<slapin>
do these Silead guys have even website? or they are hardcore aliexpress-only factory?
<slapin>
libv: github has massive DMCA outbreaks youtube-style in the past so I guess they are reluctant to be too quick about them...
<libv>
i actually filed a dmca claim once
<slapin>
also US has a law about reverse engineering to make stuff work is ok
<libv>
when that one idiot used his real name to post proprietary powervr sgx code to github
<slapin>
I remember how one guy DMCAed ALL android4 repos in github
<libv>
he found that in some LG thing
<libv>
and then pretty much the whole world was telling me to go look at it
<libv>
if i had not been burned on powervr through my nokia work already...