Add initial device support for Sony Xperia T3 (sony-seagull)

The kernel is fetched from a sony copyleft archive, version 3.4.0. Display, touch and USB networking are working.

In essence, this is reopening #1180 @PureTryOut convinced me to merge this as a starter, it only needed to be updated to the latest devicenfo format. I might still try to port a more recent kernel, but I don't have much time right now...

I am not sure I can mirror the archive on GitHub. It's 142MB, and doesn't fit in a "release" post. Will it fit in a depot?

Wow, there are some new fancy wiki checks! Not sure why the CI failed, though...

By Mayeul C. on 2018-04-03T19:04:13

Created by: ollieparanoid

Thanks for making the PR! I didn't review it yet, but for here's a mirror of the source code: https://github.com/pmsourcedump/android_kernel_sony_seagull Also I'm not sure why Travis failed either (possibly the log was too long?) - I've kicked it off again.

By * postmarketOS Bot on 2018-04-04T01:28:47

Created by: mirh

Ehrm.. Didn't the tree I linked tickled?

By * postmarketOS Bot on 2018-04-04T22:32:18

Created by: mirh

I didn't link some random whatever kernel.. https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7

In other news I found Yukon dts even on this quite newer branch https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BR.1.3.3_rb2.14

By * postmarketOS Bot on 2018-04-05T09:41:13

@mirh No, I didn't use this kernel for now. I looked into it, and even mainlining the device, but I was kind of busy lately, and I think that merging it with the vendor fork is better than not merging it at all. I am still planning to work more on this. Actually, one of the reasons is that I am getting lost with all their tags on GitHub, and have no idea which kernels support my device; as I wasn't able to boot one.

@ollieparanoid: I don't know about using our own kernel repository. On one hand, people who use postmarketOS already rely on us for security, and "controlling" (still hosted on GitHub) the repository is better. On the other hand, fetching it from the official source seems more legit (and since the hash is the same, the replacement is easily verifiable). I could add the backup as a comment, or use it directly, which is what you would prefer, if I got it right?

By Mayeul C. on 2018-04-06T22:11:22

Created by: mirh

That's still downstream kernel tbh (so @opendata-like efforts would be needed to make "the big leap") But the point would be anyway, that it's a way newer branch then what stock rom had. 3.10 instead of 3.4 is quite huge imo.

Anyway, enough said, it's all your choice in the end.

By * postmarketOS Bot on 2018-04-06T22:47:19

Created by: ollieparanoid

@MayeulC: I would prefer downloading the source from our own mirror (assuming that you're not switching the kernel sources as you've said), so the download is smaller.

By * postmarketOS Bot on 2018-04-08T12:41:12

So, I'm back on this one -- on and off, sorry about that, I don't have much time these days. @ollieparanoid Actually, I had another mirror here (I should add tags), but thought you wanted to retain the checksum compatibility. As for a big kernel bump, I am afraid this will have to wait.

By Mayeul C. on 2018-04-12T22:03:23