<speakman>
oneinsect: that's why I told you to remove the sunxi-rtc driver from the kernel
<oneinsect>
indeed
<oneinsect>
i will try that now
dlan has joined #linux-sunxi
dlan has quit [Changing host]
dlan has joined #linux-sunxi
maz has joined #linux-sunxi
doppo has quit [Ping timeout: 250 seconds]
doppo has joined #linux-sunxi
apritzel has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
doppo has quit [Ping timeout: 250 seconds]
enrico_ has joined #linux-sunxi
doppo has joined #linux-sunxi
doppo has quit [Ping timeout: 260 seconds]
doppo has joined #linux-sunxi
paulk-collins has joined #linux-sunxi
doppo has quit [Ping timeout: 276 seconds]
Worf has quit [Quit: Konversation terminated!]
doppo has joined #linux-sunxi
IgorPec has joined #linux-sunxi
doppo has quit [Ping timeout: 260 seconds]
doppo has joined #linux-sunxi
doppo has quit [Ping timeout: 260 seconds]
sirblackheart has joined #linux-sunxi
doppo has joined #linux-sunxi
oliv3r has quit [Ping timeout: 244 seconds]
doppo has quit [Ping timeout: 276 seconds]
doppo has joined #linux-sunxi
kaspter has joined #linux-sunxi
kaspter has quit [Ping timeout: 244 seconds]
kaspter has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
<Amit_T>
apritzel: Sorry to bother , Just wanted to check , would it be a good idea to debug EMAC for pine64 from u-boot ?
<apritzel>
Amit_T: instead of leaving it broken? ;-)
<apritzel>
if you want to debug your H3/A64 EMAC driver, I'd use an OPi at the moment
<Amit_T>
apritzel : sorry didn't get you
<apritzel>
with an internal PHY
<apritzel>
once that works, try it on the Pine64
<Amit_T>
apritzel: Ok I was thinking it would be bit more easy
<apritzel>
debugging your driver from the very scratch on the Pine64 is probably not helpful at the moment
<Amit_T>
Yes, thats the plan in my mind
<Amit_T>
but for my driver I can able to send proper packet on wire from OPi to host
<Amit_T>
its just receive path I have to debug
<apritzel>
and back? send more packets? I think you still have work to do and I'd do it on the same platform that you know at least partially works
<apritzel>
instead of creating a whole bunch of new problems and uncertainties with moving to the Pine64
pitelpan has quit [Ping timeout: 260 seconds]
<Amit_T>
send more packets? , you mean to say from OPi to host again, right ?
IgorPec has quit [Ping timeout: 276 seconds]
<apritzel>
well, you mentioned that you can send exactly _one_ packet the other day
<apritzel>
I meant finish debugging and fixing on one platform
<Amit_T>
ok, sure :)
<apritzel>
once you can load a kernel via TFTP on the OPi, we can look at the Pine64
<Amit_T>
hmm
<apritzel>
if you are fed up with U-Boot, you can try to debug the Linux driver on the Pine64
<apritzel>
it's in the a64-wip branch on my github
<Amit_T>
ok
<Amit_T>
I am trying to work it out on this weekend .
<Amit_T>
Thanks for your time.
doppo has quit [Ping timeout: 250 seconds]
pitelpan has joined #linux-sunxi
doppo has joined #linux-sunxi
doppo has quit [Ping timeout: 268 seconds]
doppo has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
paulk-collins has quit [Quit: Leaving]
doppo has quit [Ping timeout: 250 seconds]
doppo has joined #linux-sunxi
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 252 seconds]
cnxsoft1 is now known as cnxsoft
doppo has quit [Ping timeout: 250 seconds]
doppo has joined #linux-sunxi
<speakman>
While we're at it; I need to add an i2c device which requires interupt pin. Stuck with the 3.4 kernel (without Device Tree) I don't really know how to achieve that in a proper way.
philippe_fouquet has joined #linux-sunxi
<oneinsect>
hmm
<oneinsect>
btw the legacy sometimes doesnt compile well with latest gcc
doppo has quit [Ping timeout: 250 seconds]
<speakman>
No, it doesn't support gcc5 iirc
<oneinsect>
even with some versions of gcc 4.8
doppo has joined #linux-sunxi
<oneinsect>
it fails
<oneinsect>
so i revert to 4.7 or older
cosm_ has joined #linux-sunxi
doppo has quit [Ping timeout: 250 seconds]
paulk-leonov has joined #linux-sunxi
fredy has quit [Excess Flood]
fredy has joined #linux-sunxi
zoobab has quit [Ping timeout: 260 seconds]
doppo has joined #linux-sunxi
<topi`>
anyone with Orange Pi PC and the Xunlong Camera Module with 4.x kernel?
<topi`>
the only way I got the camera to work, was to use Loboris's 3.4.x kernel image
<jelle>
topi`: CSI support isn't mainlined yet
<topi`>
but firmware loading (for a usb wifi adapter) doesn't work on that kernel
doppo has quit [Ping timeout: 276 seconds]
<topi`>
I need to find the source code for that loboris kernel
<topi`>
so that I can try to enable FW loading
lemonzest has joined #linux-sunxi
doppo has joined #linux-sunxi
doppo has quit [Ping timeout: 250 seconds]
fl_0 has quit [Ping timeout: 250 seconds]
fl_0 has joined #linux-sunxi
doppo has joined #linux-sunxi
reev has quit [Ping timeout: 260 seconds]
<philippe_fouquet>
Hi
<philippe_fouquet>
some body have try to use the kernel sunxi3.4 with android
<jelle>
plaes: hmm don't see any license issues, more the issue that there are no docs
doppo has quit [Ping timeout: 276 seconds]
<wens>
jelle: the driver was taken from h3/a64 bsp, which does not have proper license headers
<plaes>
hmm
<wens>
and it was not officially released by allwinner
<jelle>
wens: oh I see
* jelle
isn't really a license hero
<wens>
so they could claim it was leaked or something
<jelle>
damn that sucks
<plaes>
I plan to push some clocks for a10/20 drm later this week
<wens>
cool
<plaes>
btw, how do you apply series from mailing lists? :P
<wens>
i suppose if you had a cubietruck you could look into getting vga working?
<wens>
use pwclient to do git-am from patchwork :
<wens>
:)
<wens>
keyboard is on the fritz...
<jelle>
isn't the h3 ethernet situation the same then?
<plaes>
nope, IIRC it's written from scratch
<jelle>
ah ok
<jelle>
so basically, never copy code from the BSP
<plaes>
now if someone could figure out the glue layer for HDMI, one could use existing DesignWare controller
fl_0 has quit [Ping timeout: 276 seconds]
<wens>
plaes: technically the structure looks more like stmmac :p
<plaes>
hdmi?
<wens>
but since most if not all the code was replaced, you could claim it as an original work?
<wens>
h3 emac
<plaes>
oh.. I was implying on HDMI controller (A64/H3
<plaes>
)
kaspter has joined #linux-sunxi
<wens>
i asked foxconn people to rely our requests
<wens>
though don't get your hopes too high
<plaes>
yea :S
fl_0 has joined #linux-sunxi
<ssvb>
wens: leaked? wasn't the h3 bsp released by xunlong for their boards?
<wens>
ssvb: yes, but are they allowed to?
<wens>
and also, numerous files are missing license headers
<jelle>
:-(
<ssvb>
wens: well, somebody has the obligation to release the GPL kernel sources, otherwise no binary images can be distributed for the boards
<ssvb>
wens: if Allwinner is unhappy about the h3 bsp "leak", then where is the DMCA takedown show? and if Allwinner is happy, then what's the problem?
fathead has quit [Quit: leaving]
<wens>
the takedown show can always happer after the code is merged
<mripard>
the released code has not been released under a GPL-compatible license
<wens>
is there a license at all? seems more like someone just put up a tarball and that's it
<KotCzarny>
for a start try: rm /lib/modules/3.4.39-02-lobo/*.bin; depmod -a
<oneinsect>
busybox --help BusyBox v1.24.1 (2015-12-16 08:00:31 GMT) multi-call binary. BusyBox is copyrighted by many authors between 1998-2015. Licensed under GPLv2. See source distribution for detailed copyright notices.
<oneinsect>
yes
<KotCzarny>
also, somehow your modules are built with preempt
<oneinsect>
hmmm
<oneinsect>
may be your modules will work?
<KotCzarny>
but i've tarred my dir
<oneinsect>
okie let me check
<KotCzarny>
maybe i've changed some settings at some point
<oneinsect>
great i have them
<oneinsect>
what you gave
<oneinsect>
i did not use them infact i used
<oneinsect>
my own compiled ones
<oneinsect>
may be thats the problem
<oneinsect>
let me build a modloop
<oneinsect>
based on your files
<KotCzarny>
yes, yours are built with preempt
<KotCzarny>
mine without
<oneinsect>
do you have firmware folder?
<KotCzarny>
yes
<KotCzarny>
but only wifi chip firmware installed
<oneinsect>
oooh
<oneinsect>
probably then i dont need them
<oneinsect>
may be later on
<oneinsect>
let me first get this thing rolling
<oneinsect>
okie repacking
<KotCzarny>
but it's plain debian, so you can simply grab firmware package from jessie and unpack
<KotCzarny>
that rtc page looks like a scratch notes anyway, so just add a paragraph of 'how i added ds3231 to nanopi'
<oneinsect>
yes
iamfrankenstein has quit [Quit: iamfrankenstein]
<oneinsect>
i will now in sometime
<oneinsect>
let me register
paulk-collins has joined #linux-sunxi
<oneinsect>
aah registration email is taking time
<oneinsect>
linux-sunxi.org could not send your confirmation mail. Please check your email address for invalid characters. Mailer returned: Unknown error in PHP's mail() function.
<oneinsect>
can someone please check why thats happening
<KotCzarny>
using utf8 chars? or something weird?
<oneinsect>
mine is a very simple email
<oneinsect>
oneinsect@gmail.com
<KotCzarny>
turl, libv, nitehawk ^
<KotCzarny>
oneinsect, you shouldnt write emails on public irc channels
<oneinsect>
oooh
<oneinsect>
sorry i didnt know
<oneinsect>
i will be hit by spam
<oneinsect>
i guess
<KotCzarny>
not that much, google filters spam quite well
<NiteHawk>
oneinsect: that address is obviously valid, so i'm wondering if that error is misleading / covering up some other issue. we've been running out of (disk) space a few times on the server...
<oneinsect>
hmmm
<NiteHawk>
oneinsect: are you "Atlury"?
<oneinsect>
yes sire
<oneinsect>
i am
<NiteHawk>
i've manually promoted your account, so you should be able to edit pages now even if that confirmation mail doesn't get through
<oneinsect>
great
<oneinsect>
thanks
<oneinsect>
i will now write the i2c page
<oneinsect>
NiteHawk:
<oneinsect>
You do not have permission to edit this page, for the following reason: You must confirm your email address before editing pages
<NiteHawk>
ok, thought that might happen... so that needs to be sorted out first. i don't have administrative permissions on the (mail) server, so that's something that only libv or turl might be able to handle
<oneinsect>
uptime 01:00:37 up 1:00, load average: 1.00, 1.00, 0.95
<oneinsect>
KotCzarny:
<oneinsect>
no issues till now
<KotCzarny>
oneinsect, good
iamfrankenstein has joined #linux-sunxi
<longsleep>
lvrp16: nice thanks - i might want to get one of those then
khuey is now known as khuey|away
<lvrp16>
longsleep: i have rk3368 based tv boxes coming in next week, if you want one of those to play around with, let me know
<longsleep>
lvrp16: running android?
<lvrp16>
yes, i'm not sure if you can hack it yet since i don't have one in hand
<longsleep>
lvrp16: mhm i have tried with some rk tv boxes from last year without much success
<longsleep>
and i have no use for another android whatever box
<lvrp16>
i will try to hack it and let you know
<oneinsect>
Some but not all of the drivers for the RK3368 are in the mainline 4.4 kernel, maybe enough to do what I want (ethernet and serial console, don’t care about video at all) but I’m not sure
<bananan00b>
Hi, I have trouble booting (https://github.com/ssvb/sunxi-bootsetup/releases) from by Banana Pi board. A few days ago someone here suggested attaching an UART adapter. I did so but the serial console stays black. Armbian works, but no serial console output, too. Any suggestions?
<KotCzarny>
did you connect it right?
<naraic>
bananan00b: is your adapter definitely working?
<naraic>
try connecting tx and rx to form a loopback
<KotCzarny>
black to gnd, white to tx(on board), green to rx(on board)
<naraic>
and see if you recieve what you send in a serial console
<KotCzarny>
red NOT CONNECTEd
<naraic>
and what KotCzarny said :P
IgorPec has quit [Ping timeout: 260 seconds]
<bananan00b>
Hmmm.. I have a separate cable, so colors are not meaningful.. But the adapter and board have pins named gnd txd and rxd, respectively.
<bananan00b>
those are connected
<bananan00b>
what do you mean by form a loopback?
<bananan00b>
I just got this adapter deliver. Technically I have no idea wheter it works or not
<KotCzarny>
remember that tx in adapter should connect to rx on board
<ssvb>
be sure to connect the TX and RX pins correctly (the GND is rather obvious), if you connect them in the wrong order, then you obviously don't get a working console
<bananan00b>
ah. That might be the reason
<bananan00b>
I thought it
<bananan00b>
was rx <--> rx and tx <--> tx ...
<KotCzarny>
nope
<KotCzarny>
logically there is no master/slave in serial pinout
<ssvb>
BTW, where do you expect to see the serial console on your desktop pc? Are you running "screen /dev/ttyUSB0 115200"?
<KotCzarny>
ssvb, most likely its just wrong cable order
<KotCzarny>
and simple cat /dev/ttyUSB0 should work too
<KotCzarny>
at least it works on my boxes
<bananan00b>
Tried screen and cu. Both stay black. I am not even able to type anything.
<ssvb>
KotCzarny: yes, but using wrong UART configuration can be a problem too (9600 instead of 115200)
<bananan00b>
Tells me about the adapter: idVendor and idProduct and ofc "pl2303 converter now attached to ttyUSB0"
<bananan00b>
Should not make a big difference, should it?
<KotCzarny>
do you have any other device you can test this adapter on?
<bananan00b>
A raspberry. naraic said something about forming a loopback. Should it be possible to connect rx and tx of the adapter to "chat" with myself? Would be faster to test.
<KotCzarny>
yes, that's what he meant
<bananan00b>
K. I'check that. Give me a minute or two.
khuey|away is now known as khuey
<bananan00b>
Same as when connecting to the board. "Connected." message shows up and then it seems like the terminal freezes. I dont get any output and can't type anything.
<KotCzarny>
try different usb port? maybe different linux distro? livecd? even windows with putty
<KotCzarny>
you can even boot armbian and test on device itself
afaerber has quit [Quit: Ex-Chat]
pitelpan has quit [Ping timeout: 260 seconds]
pulser_ is now known as pulser
pitelpan has joined #linux-sunxi
<bananan00b>
Ok. On the Banana Pi board running armbian, I get some different results: "cu: Unsupported baud rate 9660" but 115200 connects me and I get anything printed in the serial console I pipe into /dev/ttyUSB0
<KotCzarny>
so adapter works
<KotCzarny>
the problem is your pc/linux then?
<bananan00b>
Seems so. Do I need some special packages/kernel settings to use a serial console adapter?
<KotCzarny>
nope
<KotCzarny>
maybe some stupid app interferes with serial port?
<bananan00b>
What do you mean?
<KotCzarny>
remember networkmanager and what it does if one sets network interfaces in shell?
<KotCzarny>
maybe there is something similar that 'manages' serial ports
mossroy has quit [Quit: Quitte]
<bananan00b>
Ah. Might be. I'ver never used serial ports before so I am not aware of that. Do you have any hints?
<KotCzarny>
nope
<KotCzarny>
modemmanager maybe?
<bananan00b>
Hmm.. not installed at all
<KotCzarny>
did you try different usb port on pc?
<bananan00b>
Yes. 3/4. Just to be sure, I check the 4th one.
<bananan00b>
Does not work either
<KotCzarny>
setserial?
<bananan00b>
That is?
<bananan00b>
Ok. can google it myself
<KotCzarny>
command line to set serial ports
<cyrozap>
bananan00b: Make sure you have hardware and software flow control disabled in your serial terminal software.
<cyrozap>
And that you have the right permissions to access the /dev/ttyUSB0 device
<bananan00b>
How do I do disable those? I'm trying to connect as root which I added to dialout so this should not be an issue.
<bananan00b>
Actually, cu seems to fall back to some other group. However it did not work before I added root to dialout
<KotCzarny>
hmm
<KotCzarny>
what if you just do cat /dev/ttyUSB0 or 1 and do something on the bpi?
<cyrozap>
bananan00b: What? What distro are you using on your host PC?
<KotCzarny>
another tool to configure tty lines is stty
<KotCzarny>
maybe compare settings when connected to bpi via usb?
<KotCzarny>
other than that, just try different distro on pc
<KotCzarny>
even some livecd/usb
<KotCzarny>
nite!
<bananan00b>
Thx alot
<bananan00b>
cyrozap: I'm running debian jessie, "screen /dev/ttyUSB0 9600,-ixon,-ixoff" is different in that way that 'echo msg >> /dev/ttyUSB0' does not block anymore. But I still don't get output nor can I write to the serial console
<cyrozap>
And you're sure 9600 is the right baudrate?
<bananan00b>
I am clueless
<apritzel>
bananan00b: have you tried 115200? That's the usual baudrate.
<cyrozap>
Ok, then try 115200 first (it's by far the most common), then 57600, 38400, and 19200.
<apritzel>
Also does your serial adapter have LEDs on it? Mine has and whenever I press a key in screen, a green LED lights up
<apritzel>
that is a good way to ensuring you are talking to the right thing
<bananan00b>
Yep. Same behaviour. But no output on my serial console
kz1_ has joined #linux-sunxi
<bananan00b>
The other baud rates give the same results
kz1 has quit [Ping timeout: 250 seconds]
kz1_ is now known as kz1
<bananan00b>
Hmm.. interestingly cu does block the console and pipes to /dev/ttyUSB0 and does not cause the LED to trigger, while screen only blocks the console but LEDs work and piping does not block.
<bananan00b>
Apparently the behaviour is independent of ixoff and ixon.
<cyrozap>
Maybe try rebooting (to get rid of any of the temporary configuration changes you made), then try all those baud rates again. If it still isn't working, try using minicom instead. At least then I can help you better since it's what I use :)
<bananan00b>
Ok. Ty. I think I'll also try KotCzarnys suggestion and show up again in case nothing works.