<Amit_T>
montjoie: we don't do DMA reset and assertion in H3 emac driver, it is not required ?
hulu1522_ has quit [Ping timeout: 276 seconds]
<montjoie>
DMA reset ?
<Amit_T>
Yes
<montjoie>
what do you mean ?
<Amit_T>
and assertion
<Amit_T>
I mean like we do emac and phy reset through clock framework
<Amit_T>
with this call we do reset_control_deassert for emac and PHY
<Amit_T>
Sorry if it is such stupid kind of question
<montjoie>
the DMA is done by EMAC, so it is reseted/asserted in the same time
<montjoie>
no use of external DMA device
<Amit_T>
ok
reev has joined #linux-sunxi
fredc has joined #linux-sunxi
libv_ is now known as libv
apritzel has joined #linux-sunxi
<wens>
bpi m3 & m2+, nice
mosterta|2 has quit [Read error: No route to host]
mosterta|2 has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
Worf has joined #linux-sunxi
bwarff has joined #linux-sunxi
paulk-collins has joined #linux-sunxi
hulu152__ has quit [Remote host closed the connection]
mosterta|2 has quit [Read error: No route to host]
mosterta|2 has joined #linux-sunxi
The_Loko has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 244 seconds]
tomboy64 has joined #linux-sunxi
tkaiser has joined #linux-sunxi
<tkaiser>
wens: Good, that SinoVoip starts to realize linux-sunxi's role. :) I already tried to hack together a dts for M2+ that seems to work except of WiFi/BT (linked to from our wiki page). Curious what I did wrong when you're finished :)
Worf has quit [Quit: Konversation terminated!]
yann|work has joined #linux-sunxi
<wens>
tkaiser: the wifi chip normally needs a 32.768kHz clock fed from the SoC (or AC100 on A83T)
<wens>
without it it won't reliably power up
<wens>
tkaiser: and it was someone from foxconn, so i'm actually meeting them tomorrow :)
<plaes>
nice
<wens>
and they don't have enough m2+ to give away atm, still in early validation stages i guess
<tkaiser>
wens: Even better when it's Foxconn. They're nearby, aren't they?
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft1 has joined #linux-sunxi
cnxsoft1 is now known as cnxsoft
iamfrankenstein1 has joined #linux-sunxi
oorezz has joined #linux-sunxi
<oorezz>
Hi, what is the difference of "uartX_pins_a" and "uartX_pins_b" in my .dtsi? I ask because i have to enable uart2 on the mainline linux kernel for my a20 banana pro board.
<oorezz>
Arg I found it myself. Sorry for the spam
cosm_ has joined #linux-sunxi
kdubious has joined #linux-sunxi
adj__ has quit [Ping timeout: 276 seconds]
mosterta|2 has quit [Read error: Connection timed out]
mosterta|2 has joined #linux-sunxi
iamfrankenstein1 has quit [Ping timeout: 240 seconds]
arete74 has quit [Ping timeout: 276 seconds]
arete74 has joined #linux-sunxi
Shirasaka-Hazumi has quit [Ping timeout: 268 seconds]
kdubious has quit [Quit: Page closed]
mosterta|2 has quit [Read error: No route to host]
mosterta|2 has joined #linux-sunxi
fredc has quit [Ping timeout: 240 seconds]
reev has quit [Ping timeout: 276 seconds]
<wmat>
the wiki is down again
<KotCzarny>
works here
<wmat>
hmmm, saving an edit returned a Gateway Time-out error
<KotCzarny>
might be one time
<KotCzarny>
or one of the gateways
afaerber has joined #linux-sunxi
<wmat>
i'll retry
<plaes>
wmat: we have general USB-UART page
<wmat>
plaes: yes, i saw that
<plaes>
we usually label only RX/TX/GND on image and add short desc
<wmat>
for my PINE64 I could not get a serial console via the Euler header but was successful on the EXP connector
<wmat>
the wiki keeps timing out for me, i guess i'll try again later to save my edits
mosterta|2 has quit [Read error: No route to host]
mosterta|2 has joined #linux-sunxi
afaerber has quit [Ping timeout: 268 seconds]
<apritzel>
wmat: the Euler connector is better anyway, because it should not feed back power into the rest of the board
<wmat>
apritzel: you mean the EXP right?
<apritzel>
wmat: but isn't this already documented on the Wiki?
<apritzel>
correct, I meant EXP
<wmat>
apritzel: it's documented, but indicates PINS 7,8,9 of EXP which didn't work for me
<wmat>
apritzel: i've found in the past that users tend to like #exactsteps ;)
<apritzel>
GND is both on pin6 and pin9
<apritzel>
IIRC
<apritzel>
so interesting that it didn't work for you, did you mix up RX and TX
<apritzel>
this happens to me all of the time, so I usually try both ways first before looking any further
<wmat>
i thought the same, so swapped TX/RX to no avail. I'll test again though, as it may have been that I was half asleep.
<wmat>
apritzel: apparently i was half asleep, as it's working on pin 9 as well
<apritzel>
wmat: so does the power LED illuminate for you even on the EXP connector?
<apritzel>
shouldn't happen and does not happen for me
<libv>
if this a development board, you really do not need to say much
<libv>
you should just follow the hints the template page gives you
<ssvb_>
wmat: I'm not very happy about this mac-specific part either
<wmat>
fair enough, content removed
<apritzel>
agreed: terse description, link to generic UART page plus a picture is all it needs
<libv>
but that requires reading comprehension, and the ability to see that you are not a beautiful snowflake, totally speciall and unique.
<apritzel>
I will update the Pine64 picture later today to point out the EXP UART pins as well
p1u3sch1_ has quit [Ping timeout: 260 seconds]
<wmat>
aaaand the wiki is down again
<wmat>
btw, in no way do I think I'm a special snowflake
<libv>
i urgently need to get my life in order again and get some spare time
<libv>
because the wiki really needs its wiki-nazi again
<KotCzarny>
wiki nazi?
* NiteHawk
imagines libv polishing his cluebat
<KotCzarny>
na na na na na na na na na na na na na bat-man?
p1u3sch1 has joined #linux-sunxi
cnxsoft has quit [Quit: cnxsoft]
<libv>
KotCzarny: there is a reason why our wiki has structure and why most or some of our device pages follow a pattern
<ssvb_>
wmat, libv: maybe we could clearly split the common UART howto page into the devboard specific part (relatively user friendly) and the tablet specific part (which involves disassembling the device and maybe soldering)?
<KotCzarny>
ssvb: i think showing where pins are is enough
<KotCzarny>
and disassembly of the tablet is not uart specific as you may want to do it for other reasons
<ssvb_>
wmat, libv: because the inexperienced devboard users may be overwhelmed and scared away by reading too much information
<plaes>
if you're smart enough to know about UART, you don't really need much guidance :)
<ssvb_>
KotCzarny: I'm talking about the https://linux-sunxi.org/UART page, which may be a bit too large and scary for some people :)
<KotCzarny>
ssvb: see plaes comment
<apritzel>
but since not getting serial output is a very early showstopper, we should not make it too hard for new users
<KotCzarny>
if one wants to get his/hers hands dirty, more info == better
<KotCzarny>
you may add tl;dr paragraph at the top
<KotCzarny>
:)
scream has quit [Ping timeout: 276 seconds]
<ssvb_>
except that one does not really need to be too smart to use the UART, at least with the devboards
<KotCzarny>
then dabble in gory details
<apritzel>
KotCzarny: yeah, sounds reasonable
<libv>
tldr to the "with connector available section"
<KotCzarny>
also, most inexperienced users only want working image
<wmat>
aren't the toc links at the top enough to get to specific content?
<ssvb_>
wmat: yes, assuming that the user is smart enough to click on the right link
<ssvb_>
it would be best if this "right link" was provided at the Pine64 page
adj__ has joined #linux-sunxi
<ssvb_>
apritzel: oh, it's nice to know that there are some other UART pins on the Pine64, which are not affected by the power leakage problem
<ssvb_>
probably we should just mention the best pins and remove the information about the problematic pins?
<apritzel>
ssvb_: yeah, right
<apritzel>
so there is an extra FET on the board for exactly this purpose (avoiding power leakage)
mosterta|2 has quit [Read error: Connection timed out]
<wens>
FET or diode?
mosterta|2 has joined #linux-sunxi
leio has quit [Ping timeout: 276 seconds]
The_Loko has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-sunxi
IgorPec has quit [Ping timeout: 276 seconds]
reinforce has quit [Quit: Leaving.]
mosterta|2 has quit [Read error: No route to host]
mosterta|2 has joined #linux-sunxi
bwarff has quit [Ping timeout: 240 seconds]
<apritzel>
wens: proper FET (BSN20 according to the schematics)
<lennyraposo>
hey apritzel, longsleep and anyone dealing with the pine 64
<lennyraposo>
got a bug reporting system going online tomorrow
<lennyraposo>
it should clean up the forum situation ;)
<kdubious>
Any ideas about grounding / pull-up/down for I2S pins?
<willmore>
Do pull up.
<kdubious>
with external resistors, for each of the 3 lines?
<kdubious>
and in the dts, they float?
scream has quit [Remote host closed the connection]
<willmore>
kdubious, I don't know what the DTS would need to be set to. That's newer than my experience and I haven't come up to speed.
<willmore>
Oh, brain turn on! Sorry, I2S, no, I don't think that needs pullups. Sorry, I was thinking I2C!
<kdubious>
The pins are all set as floating there, I assume by people (or someone) who knew that was the right thing to do
<willmore>
kdubious, they would know way more than me, sorry.
<kdubious>
So I should tie the 3 i2s pins to the 3.3v line with 47kOhm resistors
<willmore>
kdubious, ignore my advice. I was thinking I2C, not I2S.
NiteHawk has joined #linux-sunxi
<willmore>
Sorry for the confusion. I've been thinking about 3d printing all day and my brain is elsewhere.
<kdubious>
ah, ok
mossroy has quit [Quit: Quitte]
<cyrozap>
Hi, all. I recently received an Orange Pi PC and thanks to the amazing wiki, was able to compile and boot U-Boot via FEL without much hassle :)
<KotCzarny>
or you could've used an armbian image
<cyrozap>
I am running Armbian now, but I just wanted to make sure I could build and boot this stuff myself without having to rely on someone else's images/scripts.
<cyrozap>
i.e., I don't want to be SOL if Armbian disappears.
<KotCzarny>
cyrozap: armbian has whole build system scripts in place
<KotCzarny>
where you can assemble your whole image, not only uboot or kernel
<cyrozap>
I know, but I also like doing things the hard way so I can learn. I'll eventually want to get Arch Linux up and running on this board, but the current blocker is that I need a more recent kernel, preferably mainline.
<KotCzarny>
for h3 boards you have to wait till they get mainlined
<KotCzarny>
so unless your help writing missing drivers you just have to wait for good linux-sunxi folks
<cyrozap>
I'm well aware.
<cyrozap>
w/25
Guest6729 has quit [Ping timeout: 240 seconds]
keh has joined #linux-sunxi
kdubious has quit [Quit: Page closed]
reinforce has quit [Quit: Leaving.]
dev1990 has quit [Quit: Konversation terminated!]
kehcee has joined #linux-sunxi
keh has quit [Ping timeout: 244 seconds]
kehcee has quit [Client Quit]
paulk-collins has quit [Quit: Leaving]
nove has quit [Quit: nove]
edolnx has quit [Ping timeout: 250 seconds]
keh has joined #linux-sunxi
speakman has quit [Ping timeout: 276 seconds]
speakman has joined #linux-sunxi
edolnx has joined #linux-sunxi
Nacho has joined #linux-sunxi
Nacho_ has quit [Ping timeout: 252 seconds]
solarnetone has quit [Remote host closed the connection]
solarnetone has joined #linux-sunxi
<juri_>
ok, building a kernel with no debian patches.