<fALSO>
anarsoul, lots of days since a new kernel ;-)
<kilobyte>
fALSO: you had 4.18 just a week ago. Linus pushes mainline every day. -next gets updated often. So do random integration and devel branches. So you can have as many "new kernels" as you want...
<fALSO>
i've seen now that theres a new linux-next
<kilobyte>
until the end of the merge window there'll be nothing interesting in -next; it's used for testing stuff meant for 4.20
<Wizzup>
I don't remember unfortunately, it's been a while. I think G2?
<plaes>
G2 has RTL8211E
<plaes>
and then there's rev K which has MICREL_KSZ9031
<plaes>
this patch is not yet upstreamed?
<Wizzup>
I don't think so, I took the patch from olimex github and forward ported it, I didn't have time to clean it up and see what upstream would think (it's a bit hackish atm)
<Wizzup>
I rebased that tree onto u-boot master a couple of days ago iirc
<plaes>
ok, cool, thanks :)
<plaes>
I had issues with rev K eMMC devices which had b0rked eMMC
leviathan has quit [Remote host closed the connection]
<karlp>
dgp: qfn80 is a much more appealing size to me at least, instead of all these jumbtron packages :) as long as we're dropping video pins and not net/io pins
Andy-D has joined #linux-sunxi
formruga has joined #linux-sunxi
<dgp>
karlp: once the SDK I bought from taobao finishes downloading I'll upload it somewhere.
<dgp>
karlp: it's much like the v3s but only one sdio controller, no rgb lcd driver
<karlp>
got a link to the board or specs at all?
jaganteki has quit [*.net *.split]
ptz has quit [*.net *.split]
<dgp>
karlp: so far I have a IP camera with the chip on it which I can ssh into now and the SDK with datasheets etc downloading.
nuuuciano has joined #linux-sunxi
<plaes>
dgp: what company is behind this SoC?
<buZz>
v3s? allwinner
<buZz>
oh
<buZz>
sry
<dgp>
plaes: a sub-company within mediatek called mstar
<plaes>
oh.. cool
<plaes>
which might mean that we might even get proper support
<dgp>
I've never seen a cortex a7 in a qfn before so I was surprised when I got a shell on the camera and did cat /proc/cpuinfo ;)
<plaes>
single or multi-core?
<dgp>
single. one sec. I'll put the datasheet somewhere
<willmore>
plaes, isn't the H5 more like an H3 with A53 cores? The A64 has tablet interfaces and stuff added.
<plaes>
willmore: I just took the text from wiki-page :S
<willmore>
Ahh, maybe we should fix that, then. :)
<martinayotte>
MoeIcenowy: wens: anarsoul: or any other, does someone got plain I2C working on H6 (not r-i2c) ? it should be straight forward, but I'm getting "bus locked" although PullUps are there...
<anarsoul|2>
I haven't tried
<anarsoul|2>
there's nothing on i2c on Pine-H64 board
<anarsoul|2>
(OK, there's nothing I need)
<martinayotte>
I don't see any DT commit to compare with my patches for OPiLite2 and OPiOne+.
<martinayotte>
anarsoul: no needs for I2C devices, only pullups and doing "i2cdetect -y 1" will give "bus locked" probably on PineH64 too, at least from what I understand. No diffs found between H5 and H6 datasheet other than register's addresses.
<martinayotte>
The strange thing is that R-I2C (added few months ago) is working fine ... Must be something I didn't found yet ...
<anarsoul|2>
martinayotte: check level on the lines
<anarsoul|2>
maybe something's pulling it low
<anarsoul|2>
(e.g. i2c pins are configured as gpio output and set to 0)
Andy-D has quit [Ping timeout: 250 seconds]
Andy-D has joined #linux-sunxi
mavkhime_ has joined #linux-sunxi
<martinayotte>
I've checked then with scope, they are fine... I've checked them with "devmem2 0x5002420" (Line Control Register) too and they are fine there too ...
<anarsoul|2>
OK, I'm out of ideas
<anarsoul|2>
:)
<martinayotte>
Me too ... Two days pulling my hairs ;-P
<martinayotte>
Should have bene trivial ...
<martinayotte>
s/bene/been/
mavkhimenia has quit [Ping timeout: 240 seconds]
f0xx has quit [Ping timeout: 245 seconds]
victhor has joined #linux-sunxi
Pe3ucTop has quit [Ping timeout: 250 seconds]
tllim has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
random_yanek has quit [Quit: random_yanek]
<mickenx>
how is u-boot on the smaller Pinebook? is it supposed to work?
<anarsoul|2>
mickenx: yes, with my patches
<anarsoul|2>
and Icenowy's patch to fix PLL settings
<OneManHateGroup>
somebody in the flashrom channel said that it was a UART controller
arand25 has joined #linux-sunxi
arand25 has quit [Remote host closed the connection]
<gnarface>
OneManHateGroup: this held me back a really long time too. there's a bunch of these industry standard acronyms that are nearly meaningless and nobody for some reason will admit to knowing that UART, JTAG and "serial controller" are all the same damned thing.
<gnarface>
that'll help your googling
<gnarface>
(there are dozens of programs and kernel modules that support these things and a massive amount of overlap in their compatibility)
<gnarface>
i don't know why that is the best kept secret in the industry
<gnarface>
maybe just run-of-the-mill ladder-yanking
<gnarface>
if you google for UART or JTAG and linux you'll be lead down a long mad rabbit hole
<KotCzarny>
serial connection is one thing, protocol running over it is another
<gnarface>
but if you google for how to connect to a serial terminal in linux you'll find tons of generic and specific UART/JTAG setup documentation tht's actually useful
<gnarface>
KotCzarny: that's accurate but that's not the part that's confusing
<gnarface>
or rather i should say, that's not the part that appears to have been made confusing on purpose
<KotCzarny>
confusion comes from money/patents wriggling
<KotCzarny>
and sometimes from plain reinventing the wheel in different parts of the world
BenG83 has quit [Ping timeout: 240 seconds]
BenG83_ has quit [Ping timeout: 245 seconds]
tllim has joined #linux-sunxi
<OneManHateGroup>
Thanks gnarface
<OneManHateGroup>
I like reinventing the wheel every once in a while... It eventually makes wheels better, or more profitable anyway
<KotCzarny>
and gets another asking about 'will it work'
<KotCzarny>
standards ARE useful
lurchi__ has joined #linux-sunxi
BenG83 has joined #linux-sunxi
<OneManHateGroup>
So, if I do a bunch of reading up on JTAG and UART I'll be able to reprogram this winbond chip?
vagrantc has quit [Quit: leaving]
* karlp
wonders where gnarface livecs that u_A_rt is somehow "the same" as jtag.
tllim has quit [Read error: Connection reset by peer]